Course Outline
Introduction
- The System Development Life Cycle within the context of the Harmony Process (IBM/Telelogic)
- A survey of UML/SysML diagrams applied to requirement gathering, system analysis, and design in the System Engineering domain
- A method-based framework for conducting requirement gathering, system analysis, and design
Transforming Requirements into System Specifications
- Establishing traceability for business and system requirements using the SysML requirement diagram
- Defining the system scope by outlining the functions and use cases that invoke these functions
- Modeling the system Life Cycle to orchestrate state transitions where functions are triggered
- Developing test cases using scenarios that realize Use Cases and System Functions
- Case Study: Modeling the System Scope and the usage of system functions based on defined requirements
Translating System Specifications into Design-Level Components
- Constructing the system’s Block Diagram and refining it through 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 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
- Maintaining traceability between requirements and software implementation
- Conducting System Integration and Acceptance tests for requirements
Note: These interactive training and mentoring sessions utilize Requirement Engineering and Modeling tools such as Enterprise Architect (EA) to ensure robust traceability between requirements and underlying solutions. Concepts are first introduced through basic examples, followed by drafting solutions to your specific problems. Post-session, we can provide ongoing support by reviewing and validating your solutions as needed.
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 software development lifecycle (SDLC) and systems engineering lifecycle concepts (e.g., V-Model, Agile/Iterative delivery).
- Familiarity with requirements engineering concepts, including functional vs. non-functional requirements, constraints, and verification.
Technical & Modeling Concepts:
- Basic knowledge of Object-Oriented Analysis and Design (OOAD) principles (e.g., classes, instances, inheritance, composition, interfaces).
- Prior exposure to basic visual diagrams (such as flowcharts or basic UML) is beneficial, though 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!
