Course Outline
Introduction
- The System Development Life Cycle aligned with the Harmony Process (IBM/Telelogic)
- An overview of UML/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 between business and system requirements using the SysML requirement diagram
- Defining the system scope, composed of functions and the use cases that invoke them
- Modeling the system life cycle to orchestrate state transitions where functions are triggered
- Developing test cases using scenarios that realize both Use Cases and System Functions
- Case Study: Modeling the system scope and the utilization of system functions based on gathered requirements
Transforming System Specifications into Design Level Components
- Modeling the system Block Diagram and refining it through the use of internal blocks
- Elaborating the communication architecture between sub-systems using Parts, Ports, and Interfaces
- Case Study: Developing block and internal block diagrams based on system specifications while considering 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 decisions
- Mapping operations onto 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 the resulting software
- Conducting system integration and acceptance tests for requirements
Note: These interactive training-mentoring sessions utilize Requirement Engineering and Modeling tools such as Enterprise Architect (EA) to guarantee high levels of traceability between requirements and underlying solutions. Concepts are first introduced via basic examples, followed by applying solution drafts to your own specific problems. Post-session, we can further support you by reviewing and validating your solutions according 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 foundational understanding of the software development lifecycle (SDLC) and systems engineering lifecycle concepts (e.g., V-Model, Agile/Iterative delivery).
- Familiarity with 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 (e.g., classes, instances, inheritance, composition, interfaces).
- While prior exposure to basic visual diagrams (such as flowcharts or introductory UML) is advantageous, 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!