Course Outline
Introduction
- Exploring the System Development Life Cycle through the Harmony Process (IBM/Telelogic)
- Reviewing UML/SysML diagrams applied to requirements gathering, system analysis, and design in System Engineering
- Utilizing a method-based framework for requirement capture, analysis, and design
Transforming Requirements into System Specifications
- Establishing traceability between business and system requirements using the SysML requirement diagram
- Defining the system scope by identifying functions and the use cases that invoke them
- Modeling the System Life Cycle to orchestrate state transitions where functions are triggered
- Developing test cases through scenarios that realize Use Cases and System Functions
- Case Study: Modeling system scope and function usage based on defined requirements
Translating Specifications into Design-Level Components
- Creating the system 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 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 choices
- Mapping Operations to the Components (Parts) of Blocks
- Elaborating 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
- Ensuring traceability between requirements and software implementation
- Conducting System Integration and Acceptance Tests for requirements
Note: These interactive training sessions utilize Requirement Engineering and Modeling tools, such as Enterprise Architect (EA), to ensure robust traceability between requirements and underlying solutions. Concepts are introduced through basic examples before transitioning to solution drafts for specific problems. Following the session, we can support you by reviewing and validating your solutions according to your specific needs.
Requirements
Professional Experience:
- A minimum of 2 years of professional experience in software development, systems engineering, business/technical analysis, or technical architecture.
Methodological Background:
- A solid grasp of software development lifecycle (SDLC) and systems engineering lifecycle concepts, including the V-Model and Agile/Iterative delivery.
- Working knowledge of requirements engineering principles, such as functional vs. non-functional requirements, constraints, and verification.
Technical & Modeling Concepts:
- Fundamental understanding of Object-Oriented Analysis and Design (OOAD) principles, including classes, instances, inheritance, composition, and interfaces.
- Basic familiarity with visual diagrams (such as flowcharts or basic UML) is advantageous, though prior expertise in SysML is not necessary.
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!
