Get in Touch
 Duration 21 hours

Course Outline

Introduction

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

Gathering Requirements and Transforming them into System Specifications

  • Ensuring traceability of business and system requirements using the SysML requirement diagram
  • Defining the system scope by identifying the functions and use cases that invoke these functions
  • Modeling the System Life Cycle to orchestrate state transitions where functions are triggered
  • Developing test cases using scenarios that realize Use Cases and System Functions
  • Case Study: Modeling the System Scope and the utilization of system functions based on captured requirements

Transforming System Specifications into Design Level Components

  • Creating the Block Diagram of the system and refining it with internal blocks
  • Elaborating the Communication Architecture between Sub-Systems using Parts, Ports, and Interfaces
  • Case Study: Developing block and Internal Block diagrams based on system specifications, taking design-level choices into account
  • Modeling white box Interactions at the design level
  • Case Study: Modeling interactions between blocks and Internal Blocks based on design-level choices
  • Mapping Operations to 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
  • Establishing traceability between requirements and the 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 explained using basic examples, followed by drafting solutions to your specific problems. Following the session, we can support you by reviewing and validating your solutions according to your specific needs.

Number of participants


Price per participant

Testimonials (1)

Provisional Upcoming Courses (Require 5+ participants)

Related Categories