Video and Webinar Series

Systems Engineering: Managing System Complexity

Engineers use model-based systems engineering (MBSE) to manage system complexity, improve communication, and produce optimized system performance. Successful MBSE requires the synthesis of stakeholder requirements into architecture models to create intuitive system descriptions.

In this video series, we’ll cover what a product lifecycle looks like and introduce the systems engineering V-model. We’ll cover how trade studies and model-based systems engineering (MBSE) help to optimize system design, and we’ll look at the role that functional, logical, and physical architectures play in the early design process.

This series also covers the importance of requirements and how they are necessary for communicating exactly what needs to be designed. Finally, we’ll cover how systems engineering is responsible for ensuring that the right thing was built through system-level verification and validation.

Systems Engineering, Part 1: What Is Systems Engineering? This video presents a broad overview of how systems engineering helps you develop complex projects that meet program objectives in an efficient way.

Systems Engineering, Part 2: Towards a Model-Based Approach Learn how good engineering decisions can be made using experience, trade studies, and model-based engineering.

Systems Engineering, Part 3: The Benefits of Functional Architectures Learn how describing a system as a collection of its functions can help us navigate the early stages of a project and can provide a foundation from which we can develop models and perform trade studies.

Systems Engineering, Part 4: An Introduction to Requirements Get an introduction to an important tool in systems engineering: requirements. Learn about what they are and what makes a good requirement, and see how they contribute to the system design process.

Systems Engineering, Part 5: Some Benefits of Model-Based Systems Engineering Learn how model-based systems engineering (MBSE) can help you cut through the chaos of early systems development and get you from definition to execution more seamlessly.