Continuing Professional Development for Aerospace D6 : Foundations of Systems Engineering June/July 2005

1. Continuing Professional Development for AerospaceD6 : Foundations of Systems EngineeringJune/July 2005

2. Introduction to SE • A Systems Engineering example • The development of this module • An exercise in requirements capture • Systems engineering, the discipline

3. D6 as an application of SE System Features Stakeholders industry CPDA evaluation delegates staff INCOSE Detailed needs hard to pin down innovative Formative feedback Goals? Iterative process Learning about Systems Engineering Making money Split delivery Getting the qualification Multi-disciplinary Increasing SE Skill base Coordination CMS/web site

4. System Features D6 Plan Support Staff evaluation Venue innovative Teaching Staff Formative feedback Iterative process Syllabus Course structure Split delivery Timetable Assessment Multi-disciplinary Coordination Teaching material CMS/web site

5. D6 in Operation June / July 2005 Stakeholder D6 Plan industry CPDA delegates staff Delegates INCOSE Fitness

6. The Venue • Coffee ad lib • Lunch is a finger buffet • Dinner on Tuesday and Thursday nights • 2 breakout rooms along the corridor • Fire drill • Anything else we should know?

7. The teaching staff • A multi-disciplinary team of staff • Chris Wallace : Software Engineer • Ian Beeson : Systems Analyst • Terry Winnington : Engineering Project Management • Julian Webb : Aerospace Software • Andy Gillies : Requirements Engineering • Paul Head : Quality

8. The course structure Timing: • 3 days foundations • 2 weeks for work on first part of assignment and reflection • you to reflect on SE practices in your workplace • us to develop special topics based on your needs • 2 days consolidation, special topics • 2 weeks – formative feedback on draft of assignment • 6 weeks – hand in of completed assignment

10. D6 in Context • ‘Foundations of Systems Engineering’ is a foundation module in a developing strand of modules which expand the Systems Engineering discipline. • Related modules are • Requirements engineering (planned) • Project management • Aerospace Lifecycle and Cost Modelling • The Aerospace Design Process: From Concept to Compliance • CPDA as a system-of-systems – each exists independently, but addition benefits accrue when they are integrated

11. Reflection • Prescription • What we hold to be best practice • ‘Espoused Theory’ (Argyris and Schon, 1974) • Description • What we do in practice • ‘Theory-in-Action’ • Closing the gap

12. Introductions • Goal: to increase level of comfort in the group • Goal: to gather individual goals, requirements and constraints for this module • Goal: to gain practical experience in requirements capture • Process • In pairs: • Each to interview the other to capture a couple of requirements for the D6 module: e.g. • I want to learn about X • My employer would like me to develop skill Y • Submit a written, attributed copy of these requirements • In the whole group: • Introduce your partner to the group

13. Systems Engineering : the Discipline • What is Systems Engineering? • How to become a Systems Engineer? • How to improve engineering practice through the application of Systems Engineering? • Where is the Systems Engineering discipline going?

14. What is Systems Engineering? • History • Top-down Definition • Bottom-up usage • Comparison with other disciplines

15. History • Some kind of System engineering capability cannot be a modern invention, witness great civil engineering projects such as the Pyramids • Explicit SE can be traced to the development of telephone communication systems (INCOSE, 2005) • WW2 increased complexity and urgency of systems development and SE concepts developed alongside Operations Research • 50’s cold war systems and 60’s space race • Impact of software and communications technologies • ’00 increased cost and time-to-market pressure at the same time as increases in scale • Major project failures continue despite advances in SE theory

16. Definitions - system • 1. A system is a complex set of dissimilar elements or parts so connected or related as to form an organic whole. • 2 The whole is greater in some sense than the sum of the parts, that is the system has properties beyond those of the parts. Indeed the purpose of building systems is to gain those properties. (Eberhardt Rechtin,1991) • A collection of components organised to accomplish a specific function or set of functions (IEEE STD 610.12)

17. Definitions - system • An integrated set of elements that accomplish a defined objective. These elements include products (hardware, software, firmware), processes, people, information, techniques, facilities, services and other support elements (INCOSE,2004) • Examples: • Hardware / Software • A380 • Products / People • A380 + staff + passengers in flight • Products / Organisations • A380 + ground systems (ATC..) • Services • Aviation fuelling system • Processes • The A380 realization system at Airbus (Martin) • Systems Engineering process defined by ISO 13288 • Organisational learning and process improvement

18. Definitions : engineering • engineer: one who designs or makes or puts to practical use, engines or machinery of any type, including electrical; one who designs or constructs public works.. engineering: the art or profession of an engineer. (Chambers,1978) • The application of scientific principles to practical ends (Kossiakoff and Sweet, 2003)

19. Definitions : Systems Engineering • Systems Engineering is an organised method for decomposing a large problem into a series of smaller, hierarchically arranged problems and the integration of the solutions to these smaller problems into a solution for the large problem. (Grady, 1993) • An interdisciplinary approach and means to enable the realization of successful systems..(INCOSE,2004)

20. 3 Types of SE • SYSTEMS Engineering • Holistic (D6) • Discovery (Sheard) • External : the system in its context • Validation : building the right system • System understanding, Problem identification, solution finding, change processes • systems ENGINEERING • Systematic (D6) • Program SE (Sheard) • Internal : coordination of systems development • Verification : building the system right • systems engineering • approach (Sheard) • what every engineer should do • good practice : requirements before solution; customer-focus; multi-factor trade studies..

21. SYSTEMS engineering • Emphasis on • the nature of systems in general • General systems theory • Systems Thinking • socio-technical systems • the system in its operational context • problem identification and negotiation • emergent (holistic) properties of systems • system architecture

22. systems ENGINEERING • Emphasis on • Life cycle processes and their integration • Project and resource management • Trade studies, evaluation of alternative solutions though computer simulation and cost analysis • Multi-factor design optimisation • Tracking of changes in requirements through life cycle stages • Management of multiple stakeholder interests • Knowledge and data management • Cutting out steps in the life cycle though automation and model-driven development (CAD/CAM)

23. systems engineering • ‘Common sense’ joined-up thinking • Identify the problem before selecting a solution • Occam’s razor • “entities should not be multiplied without necessity” • Linear cause-effect analysis • Feedback loops • Pareto law – 80/20

24. Systems Engineering Roles • SE Roles (Sheard, 1996) • Requirements Owner • Systems Designer • Systems Analyst • Validation/Verification Engineer • Logistics/Operations Engineer • Glue among subsystems • Customer Interface • Technical Manager • Information Manager • Process Engineer • Coordinator • (as defined by job ads e.g. MCSE)

25. Comparison with other disciplines • Core engineering disciplines • Mechanical • Electrical • Civil • Software • Information Systems • … • Project Management • Business Management • Quality

26. Software and information engineering • Important in three ways: • as increasingly important components in mechanical systems – due to the complexity and customisation possible with software • as enabling technologies in the engineering process • for managing and communicating engineering data and documentation • for simulation and computation in solution analysis • for complex transformation – from design to machining instructions, from model to code • as a source of new approaches to systems engineering • spiral and iterative process models • new approaches to requirements analysis such as Use cases, scenarios • modelling languages – UML, SySML, XML

27. Becoming a Systems Engineer • Books and journals • Professional bodies • INCOSE: (4,800 in 2003) • National and International Conferences • Standards organisations (ISO, BS) • Domain specific • Royal Aeronautical Society • IEE • IEEE .. • Experience • The role of failure • ‘Walk the talk’