Get in Touch

Course Outline

Introduction

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

Requirements Gathering and Transformation into System Specifications

  • Establishing traceability for business and system requirements using the SysML requirement diagram
  • Defining the system scope by outlining the functions and use cases that trigger them
  • Modeling the system life cycle to orchestrate state transitions where functions are initiated
  • 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 defined requirements

Transforming System Specifications into Design-Level Components

  • Modeling the system's block diagram and refining it with internal blocks
  • Defining the communication architecture between sub-systems using parts, ports, and interfaces
  • Case Study: Developing block and internal block diagrams based on system specifications, incorporating design-level decisions
  • 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 to the components (parts) of blocks
  • Refining the parametric diagram of system functions
  • Case Study: Updating block and internal block diagrams based on design-level scenarios

Conclusion

  • Key steps in requirement analysis and system specification 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 explained using fundamental examples, followed by drafting solutions to your specific challenges. Subsequently, we can support you by reviewing and validating your solutions based on your requirements.

 21 Hours

Number of participants


Price per participant

Testimonials (1)

Upcoming Courses

Related Categories