Course Outline
Introduction
- The System Development Life Cycle through the lens of the Harmony Process (IBM/Telelogic)
- A broad look at UML/SysML diagrams applied to requirements gathering, system analysis, and design within the systems engineering domain
- A method-based framework for collecting requirements, conducting system analysis, and designing solutions
Gathering Requirements and Transforming them into System Specifications
- Ensuring traceability of business and system requirements using the SysML requirement diagram
- Defining the system scope, which comprises functions and the use cases that invoke them
- Modeling the System Life Cycle to orchestrate state transitions where specific functions are triggered
- Developing test cases through scenarios that realize Use Cases and System Functions
- Case Study: Modeling the system scope and the utilization of system functions based on defined requirements
Transforming System Specifications into Design Level Components
- Creating and refining the system’s Block Diagram using internal blocks
- Detailing the Communication Architecture between sub-systems utilizing Parts, Ports, and Interfaces
- Case Study: Developing Block and Internal Block diagrams guided by system specifications and accounting for design-level decisions
- Modeling white-box interactions at the design level
- Case Study: Representing interactions between blocks and internal blocks based on design-level choices
- Mapping operations to the components (Parts) of blocks
- Elaborating on 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 systems engineering
- Maintaining traceability between requirements and the resulting software
- Conducting 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 high-quality traceability between requirements and underlying solutions. Concepts are first introduced through basic examples, followed by drafting solutions to your specific challenges. Following this session, we can support you by reviewing and validating your solutions as needed.
Requirements
Professional Experience:
- A minimum of two years of hands-on experience in software development, systems engineering, business/technical analysis, or technical architecture.
Methodological Background:
- A fundamental grasp of the software development lifecycle (SDLC) and concepts in the systems engineering lifecycle (such as the V-Model or Agile/Iterative delivery).
- Understanding of requirements engineering principles, including the distinction between functional and non-functional requirements, constraints, and verification methods.
Technical & Modeling Concepts:
- Basic knowledge of Object-Oriented Analysis and Design (OOAD) principles, including classes, instances, inheritance, composition, and interfaces.
- Familiarity with basic visual diagrams (like flowcharts or introductory UML) is advantageous, although prior expertise in SysML is not a prerequisite.
Testimonials (1)
Ms Malavika is a very good trainer. Very hard working and answering my queries well. I understand that scope for SysML and EA is very vast, she tried her best to present the training in the most suitable way. She has even spent her break time looking for answers to our queries. My respect! A great teacher!
