Course Outline
Introduction
- The System Development Life Cycle, specifically using the Harmony Process (IBM/Telelogic).
- An overview of UML and SysML diagrams applied in requirements gathering, system analysis, and design within the System Engineering domain.
- A framework-based methodology for requirement gathering, system analysis, and design.
Gathering Requirements and Transforming them into System Specifications
- Establishing traceability for business and system requirements using the SysML requirement diagram.
- Defining the system scope, which consists of functions and the use cases that invoke them.
- Modeling the System Life Cycle to orchestrate state transitions where functions are triggered.
- Preparing 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 defined requirements.
Transforming System Specifications into Design Level Components
- Modeling the Block Diagram of the system and refining it with internal blocks.
- Detailing the Communication Architecture between sub-systems using Parts, Ports, and Interfaces.
- Case Study: Developing Block and Internal Block diagrams based on system specifications and considering design-level choices.
- Modeling white-box interactions at the design level.
- Case Study: Modeling interactions between Blocks and Internal Blocks based on design-level decisions.
- Mapping Operations to the Components (Parts) of Blocks.
- Elaborating the Parametric Diagram of the System Functions.
- Case Study: Updating Block and Internal Block Diagrams based on design-level scenarios.
Conclusion
- The steps involved in requirement analysis and system specifications in system engineering.
- Traceability between requirements and the final software.
- System Integration and Acceptance Tests for requirements.
Notice: The above training-mentoring sessions are conducted interactively using Requirement Engineering and Modeling tools like Enterprise Architect (EA) to ensure a high level of traceability between requirements and underlying solutions. Concepts are first explained using basic examples and are then followed by solution drafts applied to your own problems. After this session, we can accompany you by reviewing and validating your solutions depending on your needs.
Requirements
Professional Experience:
- Minimum of two years of professional experience in software development, systems engineering, business or technical analysis, or technical architecture.
Methodological Background:
- A solid grasp of software development lifecycle (SDLC) and systems engineering lifecycle concepts, including V-Model and Agile/Iterative delivery methods.
- Knowledge of requirements engineering principles, such as distinguishing between functional and non-functional requirements, constraints, and verification processes.
Technical & Modeling Concepts:
- Basic understanding of Object-Oriented Analysis and Design (OOAD) principles, such as classes, instances, inheritance, composition, and interfaces.
- Familiarity with basic visual diagrams, such as flowcharts or introductory UML, is advantageous, although prior expertise in SysML is not a requirement.
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!
