Get in Touch

Course Outline

Introduction

  • The System Development Life Cycle within the Harmony Process (IBM/Telelogic)
  • Overview of the UML/SysML diagrams utilised for requirements gathering, system analysis, and System Engineering domain design
  • A methodology-based framework for requirements gathering, system analysis, and design

Gathering Requirements and Transforming them into System Specifications

  • Ensuring business and system requirements are traceable through the use of the SysML requirement diagram
  • Defining the system scope, comprising functions and the use cases that invoke these functions
  • Modelling the System Life Cycle to orchestrate transitions between states where functions are triggered
  • Preparing test cases using scenarios that realise Use Cases and System Functions
  • Case Study: Modelling the System Scope and the utilisation of system functions based on requirements

Transforming System Specifications into Design Level Components

  • Modelling the system Block Diagram and refining it using internal blocks
  • Developing the Communication Architecture between Sub-Systems using Parts, Ports, and Interfaces
  • Case Study: Developing block and Internal Block diagrams based on system specifications and design-level choices
  • Modelling the description of white box Interactions at the design level
  • Case Study: Modelling interactions between blocks and Internal Blocks based on design-level choices
  • Mapping Operations onto the Components (Parts) of Blocks
  • Developing the Parametric Diagram of the System Functions
  • Case Study: Updating the Block and Internal Block Diagrams based on design-level scenarios

Conclusion

  • Steps involved in requirement analysis and system specifications within system engineering
  • Traceability between requirements and the software
  • System Integration and Acceptance Tests of the requirements

Notice: The aforementioned training and mentoring sessions are conducted interactively using Requirement Engineering and Modeling tools such as Enterprise Architect (EA) to ensure a robust level of traceability between requirements and underlying solutions. Concepts are initially explained using basic examples, followed by the development of solution drafts tailored to your specific problems. Following this session, we can assist you further by reviewing and validating your solutions according to your needs.

 21 Hours

Testimonials (1)

Upcoming Courses

Related Categories