Agile Systems Engineering Training Bootcamp

Agile Systems Engineering Training Bootcamp by Tonex

First and foremost, the primary benefit of agile methods to systems engineering is quality improvement.

You might say, Agile systems engineering mantra is: The best way not to have defects in your system is to not put defects in your system.

In Agile systems engineering you find that through the application of agile practices of modeling, continuous execution, continuous integration and continuous customer involvement, you can proceed with a much higher assurance that you are creating the right system to meet the needs in the right way.

Traditional engineering where you have a big design up front and big bang integration at the end cause all kinds of problems that can largely be avoided through the judicious use of agile methods, ensuring that your systems engineering specifications are correct right now, even if they are incomplete.

Another major benefit of Agile systems engineering is the reduction of rework. Big design up front means that an untested architecture is used as the scaffolding for design engineering. If later work finds that scaffolding lacking, then significant rework is required because of the baked-in dependencies.

Agile’s incremental delivery removes most of this problem because the architecture is continuously being exercised to uncover defects and problems leading to their early discovery and repair.

Analysts are quick to point out yet another key advantage to Agile system engineering: The fact that organizations can deliver executable specifications means that you can exercise them early in either simulated or actual customer environments.

In other words, Agile methods reduce the ”air gap” between requirements as-stated and functionality as-needed through early demonstration of validity.

In an Agile environment, systems engineering requires tailored methods and processes to deliver incremental capabilities, and therefore demands a disciplined approach to coordinating parallel requirements elaboration and prioritization, technical development, operations, and sustainment activities.

Agile systems engineers play an essential role in operational, technical, and programmatic integration, as expressed in the core Agile software development tenet of active collaboration among developers, users, and other stakeholders.

Program leaders must encourage systems engineers to engage developers, testers, users, and other stakeholders in their disciplined engineering processes.

To enable faster, smaller capability deliveries, Agile development requires proactive integration among enterprise architectures, platform architectures, and related development efforts, where each of the stakeholder groups are contributing concerns and opportunities from their constituency for the good of the successful release and system delivery.

Agile Systems Engineering Training Course Description

Agile Systems Engineering Training covers the application of Agile environment in systems engineering. Agile systems engineering  training provides you with proven practices to help to collaborate effectively in a team through applying Agile development approaches.

You will learn how to provide high-quality and valuable working environment while accommodating changing requirements. The Agile systems engineering hands-on bootcamp goes beyond just coding practices, providing you with skills that will empower the Agile principles.

Learn about the notions, principles, and framework of Agile software development to implement your plans for incorporating Agile approaches into your organization. Agile Systems Engineering Training bootcamp will cover the techniques, skills, and tools that help you build your Agile discipline.

Learn About:

• Systems and systems engineering
• Components and principals of systems engineering
• What is Agile?
• User stories vs. requirements
• Systems engineering and team collaboration
• Evolving design
• Requirements and their value
• Verification and validation process
• Collaboration with Agile stakeholders
• Elements of an Agile environment
• Agile principals
• Agile version of V-model diagram
• Lean SE vs. Agile
• User stories
• The Agile frameworks
• ASE ontology
• Use Case scenarios
• Agile development bases
• Automated verification
• Constructing automation & ongoing integration
• Version control methods
• Collaborative process development
• Test-driven process
• Clean coding
• Individual efficiency
• Requirements alteration
• Developer testing best practices
• Operational Test and Evaluation (OT&E)
• Agile OT&E
• Agile OT&E applied to System of Systems (SoS)

Why Should You Choose TONEX for You ASE Training?

• Our instructors have extensive experience in systems engineering and Agile environment
• Our training covers both theoretical and practical aspects of ASE
• You will get to experience what you are taught with real-world projects via several labs, group activities, and hands-on workshops
• You will have fun while learning

Audience

Agile Systems Engineering Training Bootcamp is a 4-day course designed for:

• Product manager
• Project manager
• R&D manager
• Engineering manager
• Systems engineer
• Capability developer
• Business and systems analyst
• System designer
• Enterprise architect
• Software systems engineer
• Software and hardware engineers
• Design engineer
• Project and product engineers
• Industrial engineer

Learning Objectives

Upon the completion of Agile Systems Engineering Training Bootcamp, the attendees are able to:

• 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, and Agile
• Discuss the relationship between developers as supplier, developer as creator and developer as acquirer, and to position their own roles, and those of their internal and external customers and suppliers within this framework
• 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
• Demonstrate the capability of modifying the application of the Agile systems engineering methods to various application scenarios
• Use individual efficiency practices to get things done
• Develop automated tests to make sure of software code proper function
• Generate code using Test-Driven Development to ensure testability
• Develop clean code to facilitate maintenance and prevent rework
• Approximate tasks with higher accuracy and negotiate realistic commitments

Course Outline

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

• Systems engineering principles
• Concepts of system
• Systems engineering components
• Requirements analysis
• Physical solution development
• MBSE
• How to evaluate trade studies
• System components description
• System integration
• Verification and validation process
• Engineering management
• Work product characteristics
• Traceability of requirements
• Design traceability
• Test traceability

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.

Building Automation, Automated Testing, and Ongoing Integration

• Enhancing value with automated testing
• Testing structures
• Unit test designs
• Automated build scripting
• Permanent integration set-up
• Critical strategies for continuous integration

Agile Principals Overview

• 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

An Introduction to SysML

• Airborne SysML
• UML extensions
• Organizing the models
• Negligible SysML profile

ASE Stakeholders Requirements

• Goals and objectives
• The stakeholder requirements workload
• Recognizing the stakeholders
• Developing the stakeholders requirements
• Modeling the stakeholder Use Cases scenarios
• Validation plan development

Agile System Requirements Evaluation

• Goals and objectives
• The systems requirements workload
• System Use Cases determination
• Use cases evaluation
• Logical data plan development
• Dependability evaluation

Agile Systems Architectural Evaluation

• Goals and objectives
• Architecture analysis workload
• Analysis methods
• The key systems functions
• Generating candidate solutions
• Performing architectural trade study
• Translating the solutions into the systems configuration

Agile Systems Architectural Design

• Goals and objectives
• Architectural design tasks
• Subsystems determination
• Assigning systems requirements to subsystems
• Assigning Use Cases to subsystems
• Logical data plan development
• Generating control laws
• Dependability analysis

Downstream Systems Engineering Applications

• The handoff to downstream engineering activities
• Subsystem specification data
• Developing the shared model
• Subsystem physical interfaces
• Assigning requirements to engineering models

TONEX Hands-On Case Study Sample

Suppose that the hotel reservation system need to allow the users to make reservations along with confirmation of payment.

• Use Case: the user makes a room reservation
• Actor: the user
• Success Guarantee: Room was reserved; credit card was charged and confirmation payment was received
• Main Scenario:
  • Looking for discounted rooms
  • Room was found
  • Save the selection option
  • The user chooses her/his payment type
  • The user enters credit card number, expiration date, name
  • The hotel system validates and approves the card
  • The hotel system charges credit card
  • The hotel system provides the confirmation number

Agile Systems Engineering Training Bootcamp