System Architecture Creation Using System Composer
Sudeep Kulkarni, Mercedes-Benz Research and Development India
The process which we follow in requirement-based software development lacks a standard process of creating requirement specifications. Currently, the specification used by the developer might be in the form of a flow chart, textual requirements, or hand drawing.
The process for analyzing the requirements and creating a system architecture that can be used for software development is necessary.
To address this void, architecture-based software development shall be adopted with minimal changes in the conventional process.
System Composer™ can address this void. As it is a Simulink® product, the conventional process of software development won’t be altered much.
After going through the presentation, the participants can correlate to the advantages of architecture-based software development over requirements-based software development.
The aim is to create a standard process of analyzing the requirements, creating a system level architecture, and using it for software development.
With this process, the developer has access to the entire architecture while implementing the software and can relate to how the requirements are affecting the entire system with functional background. It will be easy for the developer to understand the entire architecture even if he is new to the topic. Other advantages of using System Composer would be requirement traceability and impact analysis of change of requirements on the design or vice versa.
On the other hand, this process will be easy if the software development is done in Simulink, as the integration between System Composer and Simulink is seamless. Additional scripts might be required if the software development is done in another software such as TargetLink®.
Published: 25 May 2021
