Course Outline
Introduction
- Application of the Systems Development Life Cycle (SDLC) integrated with the Harmony Process (IBM/Telelogic)
- Overview of UML/SysML diagrams utilized for requirements acquisition, system analysis, and design within the Systems Engineering domain
- Implementation of a framework-based methodology for requirements capture, system analysis, and design
Acquiring Requirements and Converting Them into System Specifications
- Establishing traceability between business and system requirements through SysML requirement diagrams
- Defining the system scope by specifying functions and the use cases that invoke them
- Modeling the System Life Cycle to manage state transitions and function triggers
- Developing test cases based on scenarios that implement Use Cases and System Functions
- Case Study: Modeling the System Scope and function utilization derived from established requirements
Converting System Specifications into Design-Level Components
- Modeling the System Block Diagram and refining it through internal blocks
- Detailing the Communication Architecture between subsystems 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 decisions
- 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
- Procedural steps for requirement analysis and system specification in systems engineering
- Maintaining traceability between requirements and software artifacts
- System Integration and Acceptance testing of requirements
Note: The aforementioned training and mentoring sessions are delivered interactively using Requirement Engineering and Modeling tools, such as Enterprise Architect (EA), to ensure robust traceability between requirements and underlying solutions for government operations. Concepts are first illustrated through foundational examples, followed by the application of solution drafts to specific organizational challenges. Following this session, continuous support is available to review and validate solutions as required.
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 fundamental understanding of the software development lifecycle (SDLC) and systems engineering lifecycle concepts (e.g., V-Model, Agile/Iterative delivery).
- Familiarity with requirements engineering concepts, including functional versus non-functional requirements, constraints, and verification.
Technical & Modeling Concepts:
- Basic knowledge of Object-Oriented Analysis and Design (OOAD) principles, such as classes, instances, inheritance, composition, and interfaces.
- Prior exposure to basic visual diagrams (such as flowcharts or basic UML) is advantageous, though 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!
