Do you see any value in the use of SysML for modelling software intensive systems?
SysML is good for building electro-mechanical systems with embedded software components but if you are building a Command and Control software or any other complex software application, it seems SysML is ineffective and does not produce real value (my opinion). I would like to know your opinion and experience on the use of SysML in software intensive systems excluding platform applications such as automobiles or aircrafts.
Thanks a lot.
Alper Akarsu
SysML supports the specification, analysis, design, verification and validation of a broad range of systems and systems-of-systems. These systems may include hardware, software, information, processes, personnel, and facilities.
SysML is a dialect of UML 2, and is defined as a UML 2 Profile (UML customization that defines language extensions via Stereotypes, Tagged Values, and Constraints.)
SysML is an enabling technology for Model-Based Systems Engineeering (MBSE) applications.
The Systems Model (or User Model) needs a Metamodel to ensure consistency between 9 SysML diagrams.
This is terrible a very bad modeling expereince for software intensive systems.
I would suggest you try the Structure-Behavior Coalescence (SBC) Process Algebra (PA) for the software modeling.
The SBC-PA is a metamodel as well as a systems model for software intensive systems.
-----------------------------------------------
Introduction of SBC-PA can be found in the paper
https://ieeexplore.ieee.org/document/8603734
- Badges
- Science topic
- Similar topics
- Computer Science and Engineering
- Software