Course Outline
Introduction
- The System Development Life Cycle utilizing the Harmony Process (IBM/Telelogic)
- An overview of UML/SysML diagrams applied to requirements gathering, system analysis, and design within the System Engineering domain
- Establishing a method-based framework for requirement gathering, system analysis, and design
Gathering Requirements and Transforming them into System Specifications
- Ensuring traceability between business and system requirements through SysML requirement diagrams
- Defining the system scope, encompassing functions and the use cases that invoke them
- Modeling the System Life Cycle to orchestrate state transitions that trigger functions
- 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 defined requirements
Transforming System Specifications into Design Level Components
- Modeling the system’s Block Diagram and refining it with internal blocks
- Detailing 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 choices
- 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
- 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
- Maintaining traceability between requirements and the resulting software
- Conducting System Integration and Acceptance Tests for requirements
Notice: These interactive training and mentoring sessions utilize Requirement Engineering and Modeling tools, such as Enterprise Architect (EA), to ensure strong traceability between requirements and underlying solutions. Concepts are first introduced through basic examples, followed by drafting solutions to your specific challenges. Post-session, we can support you by reviewing and validating your solutions tailored to your needs.
Requirements
Professional Experience:
- A minimum of two years of professional experience in software development, systems engineering, business/technical analysis, or technical architecture.
Methodological Background:
- A solid understanding 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 processes.
Technical & Modeling Concepts:
- Basic knowledge of Object-Oriented Analysis and Design (OOAD) principles, including classes, instances, inheritance, composition, and interfaces.
- Exposure to basic visual diagrams, such as flowcharts or introductory UML, is advantageous, although prior expertise in SysML is not required.
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!