ETP Schedule - INCOSE UK

About SE-Training

Systems Engineering and Project Management are core engineering disciplines used to enable the delivery of complex projects within schedule and cost expectations.

Delivering complex projects demands cross-functional engineering disciplines such as Systems Engineering, Project Management, Safety Engineering, Product Development and Design Thinking. SE-Training has been founded to offer specifically tailored solutions that support the drive, ambition and success in providing innovate and high-quality products and services.

There are a high number of engineering organisations based across Europe with diverse needs; SE-Training addresses these unique needs through expert project coaching, process development, enterprise organisational design & training courses provided by expert engineering professionals and academics.

Systems Architecting Course Objectives

- What is systems architecture and how does it differ from the system design?

- How does systems architecture relate to Systems and Holistic Thinking?

- What makes a good architecture: how many architectures do we need?

- What makes up a good architecture so important in the context of complex systems?

- Why are Interfaces such a fundamental concept in Systems Architectures?

- What is the relationship between the Operational Architecture and systems control?

- Can/should we develop the architectures for a system and its Digital Twin together?

- How does it help with decision making for an uncertain development environment?

- Why is it important to develop variants and provide variation points and how do they relate to the interfaces?

- What is a logical and repeatable methodology to develop architectures?

- How can we model the architectures? Do we need MBSE? Do we need tools?

- How can we ensure that the models are consistent and connected?

- Where can one customise the architectures?

- When is an agile approach permissible, when should you take extreme caution?

- How do architectures help developing the system for safety, reliability, availability, maintainability, and inspectability?

- Why is it important to separate the system’s (sometimes called “logical”) from the physical architectures?

- How do all architecture map to the others? Why is mapping a powerful mechanism in developing for complexity?

- What is the timing relationship between the various system (logical) architectures and the physical design?

Schedule

Day 1

09:00 - Introduction: Systems Thinking, Architectures and Architects
11:00 - Break
11:15 - Workshop: Context Analysis
12:15 - Lunch
13:00 - Operational Architecture
15:00 - Break
15:15 - Workshop: Operational Architecture

Day 2

09:00 - Functional Architecture
11:00 - Break
11:15 - Workshop: Functional Architecture
12:15 - Lunch
13:00 - Deriving Operational, Functional and Performance Requirements
15:00 - Break
15:15 - Workshop: Deriving Requirements and Verification Planning

Day 3

09:00 - Logical Architecture and Logical Interfaces
11:00 - Break
11:15 - Workshop: Logical Architecture and Logical Interfaces
12:15 - Lunch
13:00 - Physical Architecture, Integration and Physical Interfaces
15:00 - Break
15:15 - Workshop: Physical Architecture, Integration and Physical Interfaces

Trainer Bio:

Marco has had many roles in Systems Engineering: Professor at a technical university, Consultant, and Work in the development of complex systems for large scale research programmes and automotive innovation projects.

Professional Experience:

Professor of Systems Engineering at TH Ingolstadt
Management of projectglobe ltd, London, a consultancy specialising in the support of research driven industry (automotive and robotics) and publicly funded projects (nuclear fusion research).
Expert in model-based systems engineering and information modelling.
Head of development for CLOSE, a MBSE methodology based on a semantic graph that integrates Experimentable Digital Twins for reducing cycle times.
Inventor of a fractal data model that allows for unlimited scalability in managing complex information from any domain.

Course Description:

A three-day course in Systems Engineering activities across a full life cycle, covering: Introduction to Systems Engineering; Stakeholder Engagement; Context Diagrams; Life Cycle Concepts; Requirements Definition; Interfaces; Breakdown Structures; Concept Design; Trade-Offs and Design Decisions; Detailed Design; Assembly and Integration; Testing; Verification and Validation; the V model. This course is based on the book ‘Adventures in Systems Engineering’, published by INCOSE UK, and the content is taught through interactive, fantasy themed storytelling. Participants work in teams to define, design and deliver an imaginary rescue system over a simulated full life cycle, all the while journeying across an enchanted valley. Throughout the course, teams encounter engaging characters and scenarios that prompt them to perform Systems Engineering activities.

Part One: Definition

Module	Key Learning Points
Module 1: The Adventure Begins	Introduce the course style, format and trainer. What are the learning objectives. How to understand the course material.
Module 2: Introduction to Systems Engineering	Why do complex engineering projects need Systems Engineering. What are the definitions of a system and Systems Engineering. What are some Systems Engineering activities, who does them and when.
Module 3: Stakeholder Engagement	Why stakeholder engagement is important. How to engage with stakeholders effectively. What information can you reasonably expect to receive from an average stakeholder.
Module 4: Context Diagrams	What is a context diagram and what is it used for. How to draw a context diagram. What factors may be taken into account when defining system boundaries
Module 5: Life Cycle Concepts	Why it is important to consider the life cycle concept of a system from the outset. What does a basic, solution agnostic life cycle concept look like. How much time and effort goes into producing industry level life cycle concepts.
Module 6: Requirements Definition	What are requirements and why are they necessary. How to write basic requirements. What are the characteristics of good requirements What basic, additional information needs to be provided alongside requirement statements.
Module 7: Interfaces	What are interfaces and some different types of interfaces. Why is it necessary to identify and manage interfaces throughout a project. Understand that accommodations for interfaces need to be considered from the early stages of development to allow successful interactions with interfacing systems.

Part Two: Design

Module	Key Learning Points
Module 8: Breakdown Structures	What is a breakdown structure. Why is it necessary to consider a system in this way. How to consider different kinds of breakdowns (system and functional).
Module 9: Concept Design	How Systems Engineering activities in the definition phase provide strong foundations for concept design work. Understand that initial concept design can often help refine or add new knowledge to definition phase activities e.g., requirements definition.
Module 10: Trade-Offs and Design Decisions	What is a trade-off in terms of making engineering design decisions. What different factors are considered when making trade-offs and design decisions. Understand what role systems engineers play in trade-offs and design decisions.
Module 11: Detailed Design	Understand how systems engineers and designers work together and how a big picture view is beneficial to both during design activities. How Systems Engineering artefacts can be used to help with detailed design. How verification of a system starts early on by reviewing the design.

Part Three: Testing and Beyond

Module	Key Learning Points
Module 12: Assembly and Integration	What are the core definitions for activities in the build and integration phases of the life cycle. Understand the difference between assembly and integration.
Module 13: Testing	Why testing is conducted on a system. How systems engineers are involved in testing activities. Understand how a ‘big picture’ view is useful for testing related activities
Module 14: Verification and Validation	What is verification. What are the different methods of verifying a system. What is validation.
Module 15: Finale	Consolidate the learning from the entire course. What is the V model
Module 16: Reflection	What will participants take away from this course and into their day-to-day work. How can Systems Engineering be of benefit in the projects that participants work on.

Target Audience
The course is intended for participants who:

Work or aspire to work on complex technical projects, whether as engineers, designers, project managers, scientists, researchers, those in the procurement or sales team, analysts… etc. - anyone at all who works or will work on integrated projects and needs an appreciation of Systems Engineering.
Need to learn Systems Engineering techniques that they can take back to their desk and start using right away.
Are early career professionals, or university students, who will particularly appreciate the fantasy theme as a break from traditional engineering education methods (or indeed later career professionals without prior Systems Engineering knowledge who would also appreciate an engaging fantasy context).

Benefits
By the end of this course, participants will be able to answer the following questions:

What is Systems Engineering?
What are the benefits of Systems Engineering and why is it needed for complex projects? • How does Systems Engineering fit into a project life cycle?
What Systems Engineering techniques exist and how do I use them?
How can I apply basic Systems Engineering principles in my day-to-day work?
Where do I go for further information? Each of the Modules is also linked to a relevant competency area in the INCOSE Systems Engineering Competency Framework [INCOSE TP-2018-002-01.0]. This course contributes to building these selected competencies to between ‘awareness’ and ‘supervised practioner’ level - depending on the competency’s chosen indicators of knowledge and the depth of the matching Module.

Trainer Bio - Jessica Korzeniowska is a member of INCOSE and holds a Masters degree in Aeronautics and Astronautics from the University of Southampton where she specialised in spacecraft engineering. Since graduating in 2016 she has worked as a systems engineer in the space and nuclear fusion industries where she has seen first-hand the impact that MBSE can have on the toughest of technical challenges. In this time, she has also grown an international reputation for her award-winning Systems Engineering training programmes. In 2022 she was named as a finalist in the Top 50 Women in Engineering, placing her as one of the top 100 engineers in the U.K. Alongside her technical career, Jessica has worked extensively in outreach for many years from teaching science at American Summer Camp to launching a student-built rocket from an island in the Arctic Circle. Her first book,a fantasy themed adventure into Systems Engineering, was published in November 2023.

An Introduction to Systems Engineering with Requirements Writing Course
This course has been designed to provide a high-level foundation to the principles and practices of systems engineering. This course content is aligned with the INCOSE Systems Engineering Handbook V.4 and provides an introduction and overview of the processes required for successful systems engineering delivery on projects. Presented by highly experienced systems engineering instructors, the course examines the role and benefits of applying Systems Engineering principles within your organisation. We teach students how to define Systems Engineering, understand the approach and scope, and identify key systems engineering models. The creation of accurate requirements, traceable across the systems engineering life cycle, is critical for successful projects, which is why we have designed specialist modules which provide students with the techniques necessary for the creation of clear, concise, and correct requirements, independent of specific requirements management tools. Best practice is drawn from the INCOSE handbook and the INCOSE guide for writing requirements.

What you will learn:

A definition of systems engineering in accordance with the INCOSE Systems Engineering Handbook
An understanding of the systems engineering approach and scope
Key systems engineering models and details of each
How systems engineering methodology improves engineering programmes and how to apply these methods
The role of organisational stakeholders throughout the systems engineering life cycle, and the vital role each plays
The cost element of systems engineering

Specialist Requirements Writing Modules include:

Principles of requirements writing
Levels of requirement
Problem and solution domains
Needs v requirements
INCOSE Handbook / ISO 15288 Requirements Processes
Requirements structure
Requirements syntax
Statement rules
Vocabulary
Requirements review process
Baselining
Change control
Use of Artificial Intelligence to enhance requirements quality pre-review

Syllabus Main Points
All of the lessons within the course are supported by case histories, with many of the lessons supported by storyboard exercise and examples.

Lessons 1 and 2
Lessons 1 and 2 explore what we mean when we say ‘Systems Engineering’ and examine the major principles. Lesson 1 examines through-life processes. Key topics covered within Lesson 1 include user requirements, validation and verification, configuration control and design processes. For Lesson 2, we look at the through-life process and cover topics such as characteristics, decision gates, life cycle stages, life cycle comparisons, life cycle approaches, storyboard exercises and examples.

Lesson 3
Lesson 3 focuses on the pivotal role of Requirements Analysis, Capture, Writing and Management. During the lesson, we examine the concept plus the analysis process including input, controls, and outputs. These specialist modules teach around requirements process activities, how to carry out requirements analysis, characteristics of requirements statements, rules for writing requirements, requirements vocabulary and the use of requirements management systems. Students can expect to learn how to write clear, concise, and correct requirements on completion of these modules.

Lesson 4
Lesson 4 teaches about configuration management, change management and configuration control. Key topics include configuration management processes, baselines, change requests, configuration control, change control, configuration status and accounting. About SyntheSys provides defence systems, training, systems and software engineering and technical management services over a spectrum of different industry sectors. Along with distinct support and consultancy services, our innovative product range makes us first choice provider for both large and small organisations. Established in 1988, the company focus is on fusing technical expertise with intuitive software applications to solve common industry challenges. 90501TDS4002 www.synthesys.co.uk Syllabus Main Points DATASHEET.

Lesson 5
This lesson explores Test and Acceptance procedures including test categories, validation and verification, test cases and test scripts.

Who Benefits?

Mechanical Engineers
Project Managers
Test Engineers
Systems Developers
Personnel whose role heavily integrates with a software or systems development process
Suitable for engineers and non-engineers at all levels

Trainer Bio -
Mark Williamson, BSc (Hons), CSEP, MINCOSE.

Mark leads SyntheSys Technologies and is responsible for the delivery and support of Systems Engineering training and associated services. Mark has an engineering background with 23 years’ service in the Royal Air Force, working in management roles for airborne radar systems on a variety of aircrafts. He also served on software teams in both test and software maintenance roles. His systems engineering credentials have been recognised by International Council on Systems Engineering (INCOSE) Certified Systems Engineering Professional (CSEP) certification in 2013. He is now delivering Systems Engineering and CSEP preparation training to future candidates.

Endorsed Training Schedule

Modal header