Name | Purpose | Dates | Start / End Time | Tutor | Days |
Programme Introduction | To introduce the course delegates to the programme. To define the aims, outcomes and benefits together with expectations of commitment needed to successfully complete the programme | 15/04 | 1300 - 1700 | Stuart Burge | ½ day |
Systems Thinking | This is the foundation module that all the other modules will draw upon. A good grounding in Systems Thinking is essential if systems approaches are to be used to manage complexity. | 16/04 - 19/04 | 0830 - 1700 | Stuart Burge | 4 |
Systems Engineering and Lifecycle Management | The purpose of this module is to ensure that delegates have: A clear understanding of the overall programme and expectations for participation. A sound understanding of Systems Engineering and Lifecycle Management in terms of key concepts, principles and approaches to the design, development, operation and support of complex systems.
| 22/04- 24/04 | 0830 – 1700 | John Weaver | 3 |
SE Planning | No two projects are identical and there is a need to plan the engineering (including Systems Engineering) activity. While the overall project planning will be done by the Project Manager, it is essential that there is a significant input from the assigned Systems Engineer(s). The purpose of this module is to educate and train attendees in the concepts, principles and practice of planning an engineering project. | 25/04 & 26/04 | 0830 - 1700 | John Weaver | 2 |
Requirements Engineering and Management | The purpose of this module is to introduce the need to “engineer” requirements by applying a systematic approach to the gathering and analysis of requirements. | 29/04 - 03/05 | 0830 - 1700 | Keary Birch | 5 |
Team Working | The assigned Systems Engineer(s) to a project must work with engineers from many disciplines. It is therefore vital that they understand the dynamics of working in and with a team. The purpose of this module is to explain the philosophy of teamwork and provide understanding, skills and tools that will enable attendees to contribute effectively. | 07/05 & 08/05 | 0830 - 1700 | Andy Beaumont | 2 |
Safe System and Concept Design | Concept/Architectural Design is about identifying and exploring options to make the “big” decisions. It is at this point we have the opportunity to design in safety. This needs to be accomplished in a structured, rational way that is evidenced-based and thoroughly documented. Good Concept/Architectural design is not an accident or a lucky break but the logical consideration of the alternatives. | 09/05 & 10/05 | 0830 - 1700 | Stuart Burge | 2 |
| PROJECT WEEK | 13/05 - 17/05 | 0830 - 1700 | Keary Birch | 5 |
Detailed Design & Optimisation | Finding the target or nominal values for the system design parameters that deliver the best performance may sound like the “optimum design” but can result in sensitive designs that suffer excessive variation in performance, causing customer dissatisfaction. In Systems Engineering, the optimum design is the robust optimum. The best target values for the system design parameters that meet the customer requirements CONSISTENTLY, robust against the effects of variation. | 20/05 - 24/05 | 0830 - 1700 | Stuart Burge | 5 |
Integration and Verification and Validation | System integration is often accompanied by test and this module will provide the attendees with an understanding of the Systems Approach to integration and Verification and Validation (V&V). | 28/05 - 31/05 | 0830 - 1700 | John Weaver | 4 |
Interface Engineering and Sub-system Engineering | Most system problems happen at the interfaces and well-engineered and managed interfaces throughout the system’s development and service life are key success factors in any project. System integrators often rely on sub-contracts as well as their own capability to design and build the system’s subsystems. The purpose of this module is to educate and train attendees in the concepts, principles and practice of subsystem engineering and management. | 03/06 - 06/06 | 0830 - 1700 | Stuart Burge | 3 |
Facilitation Skills | Assigned Systems Engineer(s) to a project will have to facilitate engineers from many disciplines to undertake Systems Engineering tasks. Typically done as a workshop, it is important that is planned, prepared, conducted and concluded in a systematic and professional manner. This module will provide attendees an understanding and practice of the process of facilitation. | 06/06 & 07/06 | 0830 - 1700 | Andy Beaumont | 2 |
MBSE and SysML | The growing complexity of defence acquisition has led to the establishment of Architecture Frameworks. These provide a coherent set of rules and templates, known as Views, that when populated, provide a graphical and textual visualisation of the business area being investigated. The purpose of this module is to educate and train attendees in the concepts, principles and practice of Architecture Frameworks and its links with Model Based Systems Engineering. | 10/06 - 12/06 | 0830 - 1700 | John Weaver | 3 |
Communication Skills | The ability to communicate is vital to a Systems Engineer. This includes verbal, written and diagrammatic skills. The purpose of this module is to train attendees in the communication skills necessary for a successful Systems Engineer | 13/06 & 14/06 | 0830 - 1700 | Andy Beaumont | 2 |
| PROJECT WEEK and FINAL PRESENTATION | 17/06 - 21/06 | 0830 - 1700 | Stuart Burge | 5 |