Enterprise Architect version 15.2

download
purchase

enzh-CNcsnlfrdehiiditkoplptruskessv

My Profile

Social Media Channels

facebook  twitter  youtube   linkedin

Wednesday, 12 August 2020 17:38

Implementation of MBSE based on EA

Written by
Rate this item
(2 votes)

Introduction of MBSE

MBSE (Model Based System Engineering) is an effective method to analyze, design and develop complex systems. At present, the scale of aviation, automobile, machinery, ship, machinery and enterprise information system is becoming larger and larger, involving more and more specialties, which makes the system construction face unprecedented challenges:

  • Involve multiple levels: system , subsystem and module.
  • Cover Multiple Disciplines: software, electronics, mechanics, photo electricity, thermal.
  • Need several roles collaborating : System Engineer, software engineer, electronic engineer, professional engineer, test engineer.
  • Involve a variety of development tools and languages.

The process framework of MBSE is as follows:

Engineers can use models to communicate. When the system becomes more and more complex, it is more important to track the relationship between each part clearly. The model can make the analysis and design work to evolve from a Concept to clarity in a complex design, improve the ability of analysis and design, and then improve the quality and efficiency of engineering.

MBSE can help us track and manage the whole development cycle of the system based on the model, and realize forward engineering, including:

  • Analysis and verification of user requirements.
  • System requirements analysis, system design and verification.
  • Software requirements analysis, software design, implementation and verification.

MBSE Workflow

MBSE involves the whole system development cycle. The following is the overall workflow of MBSE.

The tasks performed by each role are:

Role

Task

Requirement Engineer

User demand survey: investigate the original needs of users.

User demand analysis: sort out and analyze the original needs of users.

System Engineer

System requirements analysis: analyze the functional and non-functional requirements of the system.

System design: design the structure, interface and interaction of the system.

System verification: the behavior and state of the system are simulated and verified

Software  Engineer

Software requirements analysis: analyze the functional and non-functional requirements of software.

Software design: design the software structure, interface and process.

Software implementation: use development language, write software program, compile into executable program.

Software test and verification: test the function, performance and reliability of the software.

Electronic Engineer

Hardware requirements analysis: analyze the functional and non-functional requirements of hardware.

Hardware design: design the hardware structure, interface and process.

Hardware implementation: use hardware implementation language, write software program, compile into executable program.

Hardware and verification: test the function, performance and reliability of the hardware.

Mechanical Engineer

Mechanical demand analysis: analyze the functional and non-functional requirements of machinery.

Mechanical design: design the structure, interface and physical efficiency of the machine.

Mechanical realization: processing and manufacturing mechanical parts, and assembling into mechanical devices.

Mechanical test and verification: to test the function, performance and reliability of machinery.

Integration Engineer

System integration: assembly software, hardware, machinery as a whole system.

Test Engineer

System test: test the function, performance and reliability of the whole system.

MBSE's artifacts

Various models will be used in the whole cycle of MBSE. The following are the main models:

These models involve different modeling languages, such as:

  • System analysis and design modeling: SysML.
  • Software analysis, design modeling: UML.
  • Hardware modeling: VHDL and Verilog HDL.
  • Physical system modeling: Modelica .

EA’s supporting for MBSE

Enterprise Architect supports SysML and UML , and from SysML can simulate plots using Modelica or Matlab's Simulink and then when the simulation is verified, Enterprise Architect can generate the model to a variety of software codes including VHDL.

The following is a view of the workflow (including tasks, roles, artifacts, and tools) that EA supports for MBSE:

EA supports MBSE as follows:

Task

Description

Model based requirements management

The user requirements, system requirements, software requirements and other requirements are modeled, the list view is edited and managed, and the tracking management between various requirements models can be realized.

System analysis, design and model

Using SysML modeling language, the system engineering analysis and design are carried out, the system requirements and system design model are output, and the system model can be run, simulated and verified.

Software analysis, design and model

Using UML modeling language and software engineering analysis and design method, the software requirements and design model are output, and the model is simulated and verified. Code can be generated based on the design model.

Algorithm modeling and simulation

The system structure unit is modeled by module diagram, control logic is described by state machine, and algorithm module is used to model algorithm function, which can generate code, simulate and verify.

Software Develop

Using various programming languages (for example: C, C + +, Java, C ා, python, JavaScript) to write software programs, code checking, compiling into executable programs.

Software Test

Unit test classes and test cases can be generated based on classes,

Software test cases can be generated based on software requirements,

System test cases can be generated based on system requirements.

Track and manage test cases.

   

更多信息:http://tool.um

 
Read 725 times Last modified on Wednesday, 19 August 2020 05:46
Zu Tao

I am the founder of Pitaya Software Engineering Technology Center.

From a research project started in 1998, I started to learn UML. Up to now, I have been focusing on requirements analysis and architecture design with models. I hope to be able to communicate with more peers.

 

Login to post comments