|
|
| Solution: MBSE (Model Based Systems Engineering) Based on EA |
| Author: Zu Tao, Pitaya Software Engineering |
Based on EA as a Modeling platform, integrate other tools through models,
implement MBSE (Model Based Systems Engineering) |
| |
|
|
 MBSE Tool Chain |
| |
 |
| |
| MBSE Solution Introduction: |
| MBSE (Model Based Systems Engineering) is an effective method for the Analysis, Design and development of complex Systems. At present, the System scale of aviation, automobile, machinery, ship and enterprise informatization is getting larger and larger, and more and more specialties are involved, so that the construction of the System is facing unprecedented challenges: |
- Multiple levels are involved: System - subSystem - module
- Multiple specialties: Software, electronics, mechanical, optoelectronics, thermal...
- A variety of roles are required: Systems engineer, Software engineer, electronics engineer, professional engineer, test engineer
- Multiple development tools and languages are involved
|
 |
| When the System becomes more and more complex, the clear tracking of the relationship between various parts becomes more important. The model can guide engineers to sort out the work content, evolve from chaos to clarity, and then improve the ability of Analysis and Design. On this basis, the model will become the basis of professional accumulation and communication. |
|
 |
|
| In the field of Systems Engineering, MBSE (Model-Driven Systems Engineering) can help us to conduct reasoning decomposition of System Analysis and Design, Software Analysis and Design, and hardware Analysis and Design Based on models, to achieve rigorous transformation and close tracking at each stage. Thereby improving quality and efficiency. |
|
 |
|
| MBSE (Model-Driven Systems Engineering) involves the whole System development cycle, and the following is the overall workflow of MBSE: |
|
 |
|
| All kinds of models are used throughout the System Engineering process |
|
| These models involve different Modeling criteria, such as: |
- Enterprise Architecture Modeling：Archimate
- Workflow Modeling：BPMN
- System Analysis Design Modeling：SysML
- Software Analysis, Design Modeling：UML
- Physical System Modeling：Modelica
|
| If different Modeling tools are used, there is a huge communication cost and expertise span at each level of Modeling, and EA supports all of the above Modeling, enabling users to do all of the Modeling, simulation, and tracking Management in one tool when doing MBSE. |
|
 |
|
| MBSE support tool platform: |
| In order to support the implementation of MBSE methodology, we choose the mainstream tools in each link of MBSE, integrate them into MBSE tool solutions, open the interface between various tools, realize MBSE through the data flow, and provide Engineering warehouses to store various Engineering data centrally. |
|
| It is best to have a Modeling tool that can support the various models of MBSE. EA can provide the full cycle Modeling of MBSE: enterprise Architecture, System Modeling, Software Modeling, algorithm Modeling, hardware Modeling, and can interface with various tools. |
 |
|
| As an integration platform for MBSE tools, the relationship between EA and other tools is as follows: |
|
|
| MBSE Work Directory: |
| Work |
Work Description |
Model Based Requirements Management
|
The Requirements model, Design model, code model and test model are displayed in the form of a list of items, and all the models of System Engineering can be associated and tracked in the form of a list, including Requirements , Design, code and test. |
Requirement item Management
|
Register Requirements in the form of item lists, import Requirements documents, and you can associate and track Requirements . |
| System Analysis Design and Modeling |
System Engineering Analysis and Design method is adopted, SysML Modeling System is adopted to analyze and Design model, and the System model can be run simulation, index Analysis and verification. |
Software Analysis Design and Modeling
|
Software Engineering Analysis and Design method is adopted, Software Requirements and Design model are modeled by UML, and code can be generated Based on the Design model to simulate and verify the model. |
Algorithm
Modeling and Simulation
|
Using module diagram to model System structure unit, using state machine to describe control logic, using algorithm module to model algorithm function, can generate code, simulation and verification. |
System Operation Architecture Modeling
|
For the Analysis and Design of various physical Systems, Modelica can be used to model various physical units, algorithm logic and interface relations, generate code and simulation verification. |
Electronic Analysis Design and Modeling
|
Electronic circuits can be analyzed, Designed and modeled, and electronic devices, circuit nodes and lines can be modeled using PCB, and codes and simulations can be generated. |
Physical System Analysis, Design and Modeling
|
For the Analysis and Design of various physical Systems, Modelica can be used to model various physical units, algorithm logic and interface relations, generate code and simulation verification. |
Various document editing and reading
|
Various information can be described Based on natural language (Chinese, English, French, German), and various figures can be interspersed to describe relationships and tables to list similar information, which can be read by various stakeholders as a carrier of communication between people. |
Software Development
|
Write Software programs in various programming languages (e.g. C, C++, Java, C#, Python, JavaScript) and compile them into executable programs. |
Continuous Integration
|
Code review, unit testing, integration testing, functional testing. |
Tool Bus
|
Model the workflow, tool, and artifact relationships throughout the System development cycle, supporting the interfaces of the various tools above:
The System Analysis Design model in EA generates word documents: System Requirements documents and System Design documents
The Software Analysis Design model in EA generates the state machine algorithm model in matlab simulink
Requirements in Doors imported into EA: as a source for Requirements models
Software Design model generation code in EA: import to development tools Eclipse, VS.net for development
Components in EA are imported into the continuous integration platform integrator: drive code inspection, build, unit testing, integration testing
The System Analysis Design model in EA is imported into OpenModelica: for the Design and simulation of the physical System
The Software Design model in EA is imported into AADL: for runtime Design and simulation.
The hardware modules in EA are imported into Protel: for board Design |
|
|
|
| Introduction to EA |
| As a Modeling support tool for MBSE, EA can fully support MBSE-related Modeling, simulation, document generation, code generation, model tracking and Management work. The following is the functional Architecture of MBSE Based on EA: |
 |
|
 |
| EA Details |
| |
| Why choose EA |
|
| 400,000 users worldwide, tens of thousands of businesses and teams have chosen EA, such as: Methodologies of Continental Automotive Electronics, Bosch Automotive Electronics, United Automotive Electronics, Shanghai GM, Huawei R&D Center, Siemens Medical Devices, Siemens Power Automation, Philips R&D Center, Neusoft, Methodologies Corporation, Design of Information Systems, Fujitsu R&D Center, ZTE. Schneider Electric, Honeywell, ABB of Switzerland. |
| The reasons for choosing an EA are as follows: |
- Support MBSE entire lifecycle Modeling: business Modeling, System Modeling, Software Modeling, physical System Modeling, hardware Modeling, data Modeling, workflow Modeling.
- Supported Modeling standards: UML, SysML, BPMN, Archimate,DataFlow...
- The most complete code support: support more than 10 kinds of code reverse Engineering: java, C#, C, C++, Python, SystemC, JavaScipt, Php and other more than 10 languages, you can also customize the code language.
- The most comprehensive Modeling areas supported: Systems Engineering, Software Engineering, embedded Software, Enterprise Architecture
- Integrated tools are:：
- Integrated development tools: Eclipse, VS.Net, implementation model and coding integration.
- Integrated Office tools: Word, Excel, PPT to achieve the integration of documents and models.
- Provides interfaces with other Modeling tools: Visio, Rose, PowerDesigner, etc., to achieve model asset reuse.
- Provides and Requirements Management tool interface: Doors, implementation of Requirements entry import.
- Provide an interface with the database: you can directly connect to the physical database to realize data Modeling and database instance synchronization.
- Powerful documentation functions: document Modeling, document template customization, document generation, document Management.
- The most powerful asset reuse: can reuse the model, the existing model into the asset library, to achieve reuse.
|
| MBSE Service Directory |
|
| Provide an interface with the database: you can directly connect to the physical database to realize data Modeling and database instance synchronization. |
|
|
| |
| EA China General Agent
-- Pitaya Software (China's leading Software Engineering service provider) |
| Contact us Email:umlooo@hotmail.com |
| |
|
|
| |
| |
Views 
|
|
