SEBoK Part 1 Systems Engineering Body of Knowledge Introduction

1. SEBoK Part 1Systems Engineering Body of Knowledge Introduction Barry Boehm, Art Pyster BKCASE Workshop VI April 12, 2011

2. Outline • SEBoK Motivation, Context, Purpose, and Scope • Nature of Systems, Engineered Systems, and SE • SE and Other Engineering Disciplines • Short History of SE • Key SE Principles and Practices • SEBoK Origins, Users, and Use Cases • SEBoK Content and Organization • SEBoK Operational Concept and Next Steps • Backup: Detailed Tables, Definitions

3. SEBoK Purpose, Motivation, Context, and Scope • SEBoK Motivation and Context • Quantitative evidence of SE value • Proliferation of current definitions • Confusion in nature of SE services sought, bought, and taught • Rapidly evolving field • SEBoK Purpose • Provide evolvable baseline definition of the SEBoK • Inform SE practice, research, interactors, curriculum developers, certifiers, staffing • Scope: SE Boundary and Environment • Deals with Engineered Systems • Overlaps with system development, project management • Needs to integrate hardware, software, human factors engineering • Focus on domain-independent knowledge • Range from enterprises to subassemblies of components

4. Quantitative Evidence of SE Value

5. Systems, Engineered Systems, and SE • Natural Systems and Engineered Systems • Natural systems: Solar system, real number system • Not a concern of SEBoK, other than being external environments • Engineeredsystems: Technical or sociotechnical aggregations of physical, informational, and human elements that exhibit emergent properties not exhibited by the individual elements • Are created by and for people • Have a purpose, with multiple views • Satisfy key stakeholders’ value propositions • Have a life cycle and evolution dynamics • Have a boundary and an external environment • Are part of a system-of-interest hierarchy • SE (modified INCOSE; details in chart 18): • An interdisciplinary approach and means to enable the realization of successful systems. It focuses on holistically and concurrently understanding stakeholder needs; exploring opportunities; documenting requirements; and synthesizing, verifying, validating, and evolving solutions

6. Engineered Systems, Social Systems, and Natural Systems

7. SE, Systems Development, and Project Management * Software Development parts of Software Engineering

8. Comparison of SE and Other Engineering Disciplines • The intellectual content of most engineering disciplines is component-oriented, largely reductionist, and value-neutral • Ohm’s Law, Hooke’s Law, Newton’s Laws • The intellectual content of systems engineering is focused on: • How people and components can be combined into a cost-effective system • Holistic, opportunistic synthesis • Concurrent system definition, architecting, analysis, planning, evaluation, improvement • Cost-effectiveness in terms of value to stakeholders

9. SE Stakeholders and Use CasesFrom current Table 3 • Practicing SEs • Process engineers defining or implementing SE • Faculty members • GRCSE authors • Certifiers • Program managers, other engineers, developers, testers, researchers • SE managers, researchers • Customers of SE • Human resource development professionals • Non-technical managers • Attorneys, policy makers

10. History of SE: Challenge and Response • Early cities: Middle East, Egypt, Asia, Latin America • Early megacities, mobile cities: Roman Empire; Vitruvius • Industrial Revolution: transportation, mass production • World War II: Rapid, complex command-control, logistics • 1950s formalizations of SE, systems analysis • Warfield, Churchman-Ackoff-Arnoff, Goode-Machol, McKean, … • 1940s-1970s systems theories • Wiener, Forrester, Von Bertalanffy, Wymore, … • 1970s-1990s: Soft SE, systems architecting • Warfield, Checkland, Rechtin-Maier, … • 2000s: Exponential growth in systems complexity, proliferation of SE approaches

11. Key SE Principles and Practices • Start with Hitchins principles • Systems Approach “Consider System of Interest in context” • Synthesis “Bring parts together to create solutions” • Holism “Consider whole when making decisions” • Organism Analogy “Consider systems to have dynamic behaviour” • Adaptive Optimizing “Solve problems progressively over time” • Progressive Entropy Reduction “Continue to make systems work over time” • Progressive Satisfying “system success equals stakeholder success”

12. BKCASE Content and Organization • Part 1: Introduction (why?) • Part 2: Systems (what?) • Part 3: SE Processes (how, when, how much?) • Part 4: Implementing SE in Organizations (who, where) • Part 5: Implementation Examples

13. BKCASE Operational Concept and Evolution • SEBoK, GRCSE developed by SERC project • Graduate Reference Curriculum for SE • Convergence on hardcopy and softcopy versions (wikis?) • Transitioned to IEEE, INCOSE • Available free to all • Update processes negotiated with IEEE, INCOSE • Open to all, but with core editorial group

14. Backup charts

15. Table 1. SEBoK Purposes

18. Proposed Definitions • engineered system -- A technical or sociotechnical aggregation of physical, informational, and human elements that exhibit emergent properties not exhibited by the individual elements. Its characteristics include being created by and for people; having a purpose, with multiple views; satisfying key stakeholders’ value propositions; having a life cycle and evolution dynamics; having a boundary and an external environment; and being a part of a system-of-interest hierarchy. • natural system – a system whose elements, boundary, and relationships exist independently of human control. Examples: the real number system, the solar system, planetary atmosphere circulation systems. • social system – a system that includes humans as elements. • sociotechnical system – a system that is both an engineered system and a social system. • system – a set of system elements within a system boundary defined by a set of membership criteria, and a set of relationships satisfied by the elements within the boundary. • systems engineering-- An interdisciplinary approach and means to enable the realization of successful systems. It focuses on holistically and concurrently understanding stakeholder needs, exploring opportunities, documenting requirements, and synthesizing, verifying, and validating solutions while considering the complete problem: Performance and Mission Effectiveness; Verification and Validation; Development and Production; Training and Support; Operations and Maintenance; Disposal; Life Cycle Cost and Schedule Systems engineering integrates all the disciplines and specialty groups into a team effort forming a structured development process that proceeds from concept to production to operation for each evolutionary increment. Systems engineering considers both the business and the technical needs of all key stakeholders with the goal of providing a quality system that satisfactorily addresses the full set of stakeholder needs.