Course Outline
Introduction
- The System Development Life Cycle within the Harmony Process framework (IBM/Telelogic)
- An overview of UML and SysML diagrams applied to requirements gathering, system analysis, and design in the System Engineering domain
- Establishing a methodology-based framework for requirement collection, system analysis, and design
Requirements Gathering and System Specification Transformation
- Ensuring traceability of business and system requirements using SysML requirement diagrams
- Defining the system scope, comprising functions and the use cases that invoke them
- Modeling the system life cycle to orchestrate state transitions where functions are triggered
- 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 derived from requirements
Transforming System Specifications into Design-Level Components
- Modeling the system Block Diagram and refining it with internal blocks
- Defining 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 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
- 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 artifacts
- 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 guarantee robust traceability between requirements and underlying solutions. Concepts are first introduced through basic examples, followed by the development of solution drafts tailored to your specific challenges. Following this session, we can provide further support by reviewing and validating your solutions according to your needs.
Requirements
Professional Experience:
- Minimum of two years of hands-on 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, such as the V-Model and Agile or iterative delivery methods.
- Knowledge of requirements engineering principles, including the distinction between functional and non-functional requirements, constraints, and verification processes.
Technical & Modeling Concepts:
- Foundational understanding of Object-Oriented Analysis and Design (OOAD) principles, covering classes, instances, inheritance, composition, and interfaces.
- Familiarity with basic visual diagrams, such as flowcharts or introductory UML, is advantageous; however, prior 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!
