Course Outline
Introduction
- The System Development Life Cycle within the context of the Harmony Process (IBM/Telelogic)
- An overview of UML/SysML diagrams applied to requirements gathering, system analysis, and design in the System Engineering domain
- A method-based framework for requirement collection, system analysis, and design
Capturing Requirements and Transforming them into System Specifications
- Establishing traceability for business and system requirements using the SysML requirement diagram
- Defining the system scope, comprising functions and the use cases that invoke them
- Modeling the System Life Cycle to orchestrate state transitions where functions are triggered
- Developing test cases based on scenarios that realize Use Cases and System Functions
- Case Study: Modeling the System Scope and the usage of system functions based on gathered requirements
Translating System Specifications into Design-Level Components
- Creating the Block Diagram of the system and refining it with internal blocks
- Developing the Communication Architecture between sub-systems using Parts, Ports, and Interfaces
- Case Study: Elaborating Block and Internal Block diagrams based on system specifications and 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
- Developing 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 specification within system engineering
- Traceability links between requirements and software implementation
- 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 high-level traceability between requirements and underlying solutions. Concepts are introduced through foundational examples before progressing to draft solutions for your specific challenges. Following the session, we can provide continued support by reviewing and validating your solutions as needed.
Requirements
Professional Experience:
- A minimum of two years of professional background in software development, systems engineering, business/technical analysis, or technical architecture.
Methodological Foundation:
- A solid grasp of the Software Development Life Cycle (SDLC) and systems engineering lifecycle concepts, such as the V-Model and Agile/Iterative delivery methods.
- Familiarity with requirements engineering principles, including the distinction between functional and non-functional requirements, constraints, and verification techniques.
Technical & Modeling Concepts:
- Basic understanding of Object-Oriented Analysis and Design (OOAD) principles, such as classes, instances, inheritance, composition, and interfaces.
- Exposure to fundamental visual diagrams, like flowcharts or basic UML, is advantageous, though prior specialized 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!
