Get in Touch

Course Outline

Introduction

  • The System Development Life Cycle within the Harmony Process (IBM/Telelogic)
  • An overview of UML/SysML diagrams applied to requirements gathering, system analysis, and design within the System Engineering domain
  • A method-based framework for conducting requirements gathering, system analysis, and design

Gathering Requirements and Transforming them into System Specifications

  • Establishing traceability for business and system requirements using the SysML requirement diagram
  • Defining the system scope, comprising functions and the use cases that invoke these functions
  • Modeling the System Life Cycle to orchestrate transitions between states where functions are triggered
  • Developing test cases using scenarios that realize Use Cases and System Functions
  • Case Study: Modeling the system scope and the usage of system functions based on requirements

Transforming System Specifications into Design Level Components

  • Modeling the system’s Block Diagram and refining it through internal blocks
  • Developing the communication architecture between sub-systems using Parts, Ports, and Interfaces
  • Case Study: Elaborating block and Internal Block diagrams based on system specifications, incorporating design-level choices
  • Modeling white-box interaction descriptions at the design level
  • Case Study: Modeling interactions between blocks and Internal Blocks based on design-level choices
  • Mapping operations onto the Components (Parts) of Blocks
  • Elaborating the Parametric Diagram for System Functions
  • Case Study: Updating Block and Internal Block Diagrams based on design-level scenarios

Conclusion

  • Key steps in requirement analysis and system specifications within system engineering
  • Ensuring traceability between requirements and the resulting software
  • System Integration and Acceptance Testing of requirements

Note: These interactive training and mentoring sessions utilize Requirement Engineering and Modeling tools, such as Enterprise Architect (EA), to ensure robust traceability between requirements and underlying solutions. Concepts are first introduced through basic examples, followed by drafting solutions to your specific problems. Following the session, we can support you by reviewing and validating your solutions as needed.

 21 Hours

Testimonials (1)

Upcoming Courses

Related Categories