A System Organic Architecture based on Dynamic Functional Architecture Modeling

A System Organic Architecture based on Dynamic Functional Architecture Modeling Jacques Simonin and Pierre-Yves Pillain Institute Mines-Telecom Atlantique Lab-STICC UMR CNRS 6285, UBL 29238 Brest, France [email protected] Abstract—We focus on dynamic model usability and utility, performed throughout system engineering. The dynamic model is designed in relation to the system use scenarios. We generate then automatically the static models (data model, component model) from the dynamic one. A dynamic functional modeling based method is proposed to generate automatically the static and the dynamic organic architecture of a system. The method consists of the definition of system engineering rules constraining the transformation of a dynamic functional model of the system into static and dynamic organic models. The system engineering rules conform to a 3-layers organic architecture. The implementation of this transformation with operational-QVT allows an automatic generation of the organic models. The illustration of the transformation concerns a system of ordering. This work discusses on the relevancy of this method based on Model Driven Engineering. Keywords—system engineering; model based engineering; dynamic modeling; static modeling; functional architecture; organic architecture. I. INTRODUCTION Improving system design processes can be done either with tools or models that are meant to support this process, but also through the adaptation of system and software engineering processes (as specified for example in ISO/IEC/IEEE 15288 for system [1] or in ISO/IEC 12207 for software [2]). User involvement is one of the known keys of success. In most of system engineering methodologies, the functional analysis of the user needs is first specified. Then, during the design, the developers have to define each system part or how each function will perform. System Engineering (SE) [3] suggests a structured process to build complex systems. SE consists in specifying needs or requirement analysis (“what”), proposing a solution or architectural design and implementation (“how”), integration, verification, validation of this solution and then its maintenance. Several processes described in the ISO standard associated to system or software life cycle, or UP (Unified Process) [4] are necessary to perform the project. SE uses various formalisms to model functional and organic architectures, including static and dynamic points of view. The dynamic point of view is defined by the situation scenario of the static one for all the interactions with the system (triggered by another system or a user). Some basic activities are commonly recognized: stakeholder needs elicitation of requirements, functional analysis, architectures and coding. Activity artefacts as described in [3] are: 1) During stakeholder needs collection, the functional and non- functional requirements have to be identified for the system that must be developed. 2) Functional analysis results from the system specification. The use cases describe what the system has to perform. The scenarios which illustrate the use cases define a dynamic use of them. 3) Functional architecture is designed from functional requirement specification. As such, functional components participate in the dynamic use of the system. 4) Technical architecture satisfies the collected non- functional requirements and is described by nodes and execution environment. 5) Organic architecture, in relation to SE, is based on the design of the components’ interfaces. These interfaces implement the functional architecture of the system and components are deployed on the technical architecture. These activities are defined in the EA4UP (Enterprise Architecture for Unified Process) [5] method, which constrains a system engineering with EA (Enterprise Architecture) recommendations [6]. This mapping of the architecture design of a system with the architecture design of its IS (Information System) is based on MDE (Model Driven Engineering). Our contribution is twofold. It proposes (i) a dynamic meta- modeling of the functional architecture and a dynamic meta- modeling of the organic architecture of a system and (ii) a method allowing the transformation of dynamic functional modeling into an organic one. The transformation conforms to a chosen 3-layers organic architecture. The organic static models (data model and component model) are automatically generated from the dynamic one. Section III presents the transformation (meta-modeling and architecture rules), which results in an organic architecture model. In Section IV, the organic architecture models resulting

A System Organic Architecture based on Dynamic Functional Architecture Modeling

Documents

system engineering

model based engineering

dynamic modeling

static modeling

functional architecture

organic architecture