Length: 3 Days
Print Friendly, PDF & Email

Agile Systems Engineering Workshop with MBSE and SysML Training by Tonex

Creativity Hacks Workshop Training by Tonex

Agile Systems Engineering Workshop with MBSE and SysML is a 3-day innovative workshop with a vision of combining Agile, modern systems engineering , MBSE and SysML. Participants will learn how to work high level users and customers need, create use cases, model system specification, model requirements, structure, behavior and traceability.  Non-functional requirements such as usability, safety, security, reliability, and performance of systems are also discussed in an agile engineering context with MBSE and SysML.

The workshop incorporates agile methodologies, system thinking, model-based systems engineering (MBSE) and System Modelling Language (SysML) to define the properties of a complex system throughout s the lifecycle of systems development, including ConOps, use cases, requirements, analysis, architecture design, verification, validation, operation, maintenance and sustainability.

LEARNING OBJECTIVES

Upon completion of this hands-on course, the participants will:

  • Learn about the general concepts of systems engineering
  • Discuss the general systems engineering process components and their relationships with each other.
  • Learn the key similarities and difference between traditional systems engineering, MBSE and Agile
  • Conduct the practices of Agile system requirements analysis, physical solution development, logical candidate solution development, trade-off studies evaluation, and design iteration
  • Discuss the principles and key approaches of engineering management in a systems project framework
  • Describe how MBSE and SysML language and diagrams/models are related to Agile
  • Analyze and create SysML diagrams for a complex spacecraft system and system of Systems (SoS) development, engineering project or mission
  • Learn how to create models in a SysML including packages, requirements, structure, behavior and parametrics diagrams and constructs,
  • Develop SysML activity models that are executable
  • Analyze and construct SysML models with calculations and execute parametric simulations.

WHO SHOULD ATTEND

This course is designed for systems engineers, hardware, software and firmware design engineers, software developers, system and software architect, modelers, managers, and employees with little or no Agile, MBSE and SysML experience. Tonex is the industry leader in Agile systems engineering, model-based systems engineering (MBSE) and SysML and has extensive in space application and systems engineering architecting and modeling.

METHOD OF LEARNING

The class consists of theory and practical workshops creating SysML diagrams using Modelio open source tool.

COURSE MATERIAL, TOOLS AND GUIDES

  • Course Student Guide
  • Exercises and Workshops Guide
  • Training Resources: Best Practices, Lessons Learned, Stories, Guides, Handbooks, Templates, Examples, Tools
  • Cheat Sheets
  • Organizational examples of common problems

COURSE SCHEDULE/OUTLINE

Session 1 (3 hours)

Introduction to Systems Engineering

  • Systems configuration
  • Describing the problem
  • Solutions domain: main ideas, relationships, data types and work products, MBSE
  • OCD/CONOPS/OSD/ADD issues
  • Architectural configurations
  • How problem definition can relate to stakeholder satisfaction
  • Systems of systems engineering
  • Waterfall, incremental, evolutionary and spiral models
  • What are agile, lean and concurrent/simultaneous engineering?
  • Systems Engineering Processes

Fundamentals of Agile Development

  • Agile environment and systems engineering
  • Agile values and philosophies
  • Scrum, XP, and Lean software development
  • Agile teams
  • Tailored methods and processes to deliver incremental capabilities
  • Disciplined approach to coordinating parallel requirements elaboration and prioritization
  • Agile technical development, operations, and sustainment activities.

Session 2 (3 hours)

Agile Principals

  • Ongoing adding value
  • An operating system is the main measure index of progress
  • Changing requirements are always welcome
  • Frequently provision of working system
  • Collaboration between the business professionals and developers
  • Inspired and empowered professionals
  • Face-to-face communication
  • Stimulating the sustainable development
  • Encouraging the technical excellence
  • Simplicity
  • Impact of self-organizing Teams on architectures, requirements and designs

Model Based Engineering

  • Main systems engineering actions
  • Systems engineering data
  • Systems engineering lifecycle
  • Model-based systems engineering (MBSE)

Agile Methods and Models

  • The agile manifesto
  • Advantages of agile methods
  • Agile applications in systems engineering
  • Best practices for ASE
  • The synergy of agile MBSE process

Session 3 (3 hours)

Overview of MBSE (Model Based Systems Engineering) and SysML

  • MBSE (Model Based Systems Engineering) Overview
  • How is MBSE different than traditional Systems Engineering?
  • Overview of Systems Modeling Language (SysML)?
  • SysML and MBSE
  • 4 Pillars of SysML
  • Modeling with SysML
  • SysML Diagrams
  • Package diagram
  • Requirement diagram
  • Use Case diagram
  • Block Definition diagram
  • Internal Block diagram
  • Activity diagram
  • Sequence diagram
  • State Machine diagram
  • Parametric diagram

HANDS-ON ACTIVITIES

Session 4 (3 hours)

Agile System Engineering with MBSE  and SysML

  • Agile System Requirements Evaluation
  • Agile Systems Architectural Evaluation
  • Agile Systems Architectural Design
  • Downstream Systems Engineering Applications
  • Context Diagram (ibd or bdd)
  • Use Case Diagrams
  • Requirements Diagrams
  • Modeling System Objectives
  • Stakeholders Requirements
  • System Requirements
  • Functional Requirements
  • Non-Functional Requirements (NFR)
  • Structure
  • Interfaces
  • Part Catalogs
  • Behavior
  • Analysis
  • Testing and Simulation
  • Verification
  • Validation
  • Integration

Workshop 1: Creating SysML Diagrams for a Spacecraft SoS

  • Blocks and Block Definition Diagrams
  • Packages and Use Cases
  • Requirements and Sequence Diagrams
  • Analysis Parametric Diagrams
  • Activities and Activity Diagrams
  • Internal Block Diagrams
  • State Machines and Advanced Interactions

Session 5 (3 hours)

Workshop 2: Model Creation Process and Guidance

  • Model Organization
  • Planning Artifacts
  • Mission & System Specification and Design Process
  • Spacecraft Mission Context
  • Model Organization
  • Requirements
  • Derived Mission Requirements
  • Spacecraft SoS
  • Ground Station
  • Launch Vehicle
  • Launch Operations Facility
  • Supporting Elements (Interface Definition)
  • Command and Control (C2)

Session 6 (3 hours)

Workshop 3: Creating Custom Libraries and Stereotypes

  • Profile
  • Failure modes
  • Hardware
  • Software
  • Firmware
  • Mechanical
  • Orbit
  • Subsystems
  • Test component
  • Verification objectives

Workshop 4: Architecting Spacecraft SoS with MBSE and SysML

Creating Model Organization

  • Mission User Requirements
  • Mission ConOps
  • Mission Requirements
  • Mission & System Specification and Design Process
  • Spacecraft Mission Context
  • Structure
  • System of Systems (SoS), Systems and Subsystems
  • Behavior
  • Orbit Analysis
  • Launch Vehicles
  • Orbit Requirements
  • Revisit Time
  • Interface Definitions
  • Signal Definitions
  • Operational Use Cases
  • Modeling the Behavior
  • Analysis of the Models
  • Models to Support Specifications, Integration and Testing

Request More Information

Please enter contact information followed by your questions, comments and/or request(s):
  • Please complete the following form and a Tonex Training Specialist will contact you as soon as is possible.

    * Indicates required fields

  • This field is for validation purposes and should be left unchanged.

Request More Information

  • Please complete the following form and a Tonex Training Specialist will contact you as soon as is possible.

    * Indicates required fields

  • This field is for validation purposes and should be left unchanged.