Get in Touch

Course Outline

Introduction

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

Capturing Requirements and Translating Them into System Specifications

  • Ensuring traceability of business and system requirements using SysML requirement diagrams
  • Defining the system scope, encompassing functions and the use cases that invoke them
  • 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 defined requirements

Converting System Specifications into Design-Level Components

  • Creating and refining the system’s Block Diagram using internal blocks
  • Developing the Communication Architecture between sub-systems utilizing Parts, Ports, and Interfaces
  • Case Study: Elaborating Block and Internal Block diagrams grounded in system specifications and design-level choices
  • Modeling white-box Interactions at the design level
  • Case Study: Modeling interactions between blocks and Internal Blocks based on design-level decisions
  • Mapping Operations to the Components (Parts) of Blocks
  • Developing the Parametric Diagram for System Functions
  • Case Study: Updating Block and Internal Block Diagrams based on design-level scenarios

Conclusion

  • Reviewing the steps involved in requirement analysis and system specifications in system engineering
  • Establishing traceability between requirements and the software implementation
  • Discussing System Integration and Acceptance Tests for requirements

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

 21 Hours

Number of participants


Price per participant

Testimonials (1)

Upcoming Courses

Related Categories