GooBiz

System Engineering and Embedded System Design using UML 2 and SysML (3 days)

Objective : Helping Analysts and Designers of the System Engineering domain to understand how to efficiently gather requirements then go through the embedded software design implementation on the basis of system specifications using UML 2 and SysML.

This 3 days training aims at assisting system analysts to express efficiently their needs and designers to make the appropriate architectural design of the system on the basis of these needs.

The resulting system architecture provides a good level of agility to the embedded system software in face of changes as it allows a coherent traceability of the business rules encapsulated in system functions and those of the usage choices (use cases) of the end-users toward the software implementation level.

 

Detailed description :

 

Introduction

 The System Development Life Cycle with the Harmony Process (IBM/Telelogic)
 Overview of the UML/SysML diagrams used in requirements gathering, system analysis and design of the System Engineering domain
 A Method based Framework for requirement gathering, system analysis and design

 

Gathering Requirements and Transforming them into System Specifications

 Making business and system requirements traceable using the SysML requirement diagram

 Define the scope of the system composed of functions and use cases that invoke these functions

 Model the Life Cycle of the System that orchestrates transitions between its states where functions are triggered

 Prepare test cases using scenarios that realize Use Cases and System Functions
 Case Study : Model the System Scope and the usage of the system functions on the basis of requirements

Transforming System Specifications into Design Level Components
 Model the Block Diagram of the system and refine it using internal blocks
 Elaborate the Communication Architecture between Sub-System using Parts, Ports and Interfaces
 Case Study : Elaborate the block and Internal Block diagrams on the basis of system specifications and by considering design level choices

 Model the description of white box Interactions at the design level

 Case Study : Model interactions between blocks and Internal Blocks on the basis of design level choices

 Mapping of Operations on the Components (Parts) of Blocks
 Elaborate the Parametric Diagram of the System Functions

 Case Study : Update the Block and Internal Block Diagrams on the basis of design level scenarios

Conclusion
 Steps of requirement analysis and system specifications in system engineering
 Traceability between requirements and the software
 System Integration and Acceptance Tests of the requirements

 

Notice : The above training-mentoring sessions are conducted interactively using Requirement Engineering and Modeling tools like Enterprise Architect (EA) in order to ensure good level of traceability between requirements and underlying solutions. Concepts are explained first using basic examples and are then followed by solution drafts to your own problems. After this session, we can accompany you by reviewing and validating your solutions depending on your needs.

The logos UML, SysML, MDA referenced on this site are trademarks of the Object Management Group (OMG).

The RUP is a trademark of the IBM / Rational.