Systems Architecting

Class Description

Date:  18 – 19 February 2025

Duration:  2 Days

Location:  Munich, Germany

PREREQUISITES FOR THIS COURSE:

• A solid understanding of what a system is and what it is that makes it different from a simple product.
• A healthy view on the Systems Engineering challenges associated with complexity.
• Experience in developing a system.

OR

• The 1-day SE-Training Systems Contextualisation Course

This 2 day intermediate level course covers the WHY, WHAT and HOW of Systems Architecting:

• Understanding the WHY: The need for employing architectures to help cope with the overwhelming nature of
  complexity.
• Explaining the WHAT: Architectures provide different system perspectives and are ideal entry points to effectively structure your information.
• Introducing one HOW: The OFLP Framework creates the Operational, Functional, Logical and Physical
  Architectures from their respective perspectives.
• Operational: Plan your Scenarios for efficiency and introduce fall-backs and variation points.
• Functional: Make your Capabilities effective, your Functions re-usable and your Performance robust.
• Logical: Structure your ideal System using logical reasoning over legacy or – worse – Conway’s law.
• Physical: Support Integration and Verifications of your real System long before buying the first part.

We will work out together why Architecting is the practical implementation of Systems Thinking, what each of these
individual Architectures adds to the Model, and how they connect to one another and relate to Requirements

The best way to learn this, it to actively develop all Architectures in a team with plenty of time for discussing
challenge, methodology, and its application to your own practical problems – and how it can help to reduce your
Requirements Engineering efforts by over 80%!

LEARNING OUTCOMES

• Why Systems Architecture is the logical implementation of Systems thinking and using Perspectives.
• What makes a good architecture and why having one is so important to solve a complex challenge.
• How Architectures help to develop for safety, reliability, availability, maintainability, and inspectability!
• Why a good Model is by definition correct, consistent, and fully traceable.
• What classes of Interfaces exist and why we want to actively create them – not having to search for them​.
• How much a solid Operational Architecture reduces your efforts in developing the Controls of your System.
• Which part of Requirements Engineering can be completely replaced by well-formed Architectures.
• The importance of having Variation Points in every level of your Architectures.
• Why it is better to record your decision making in the Architecture than in minutes or emails.
• How a robust Architecture Model can support agile Development.
• What the main skills of a senior Systems Architect are.

WHO SHOULD ATTEND?

Systems Engineers  |  Lead/Senior Engineers  |  Systems Analysts |  Systems Architects

COURSE PRESENTER

Marco Di Maio