Leading Systems Engineering Narratives Dieter Scheithauer Dr.-Ing., INCOSE ESEP 01.09.2014 Dieter Scheithauer, 2014.
Content Introduction Problem Processing The Systems Engineering Value Stream The System Life Cycle Concluding Remarks 01.09.2014 Leading Systems Engineering Narratives Dieter Scheithauer, 2014. 2
Content Introduction The Systems Engineering Challenge Narration Theory and the Human Mind Leading Systems Engineering Narratives Problem Processing The Systems Engineering Value Stream The System Life Cycle Concluding Remarks 01.09.2014 Leading Systems Engineering Narratives Dieter Scheithauer, 2014. 3
The Systems Engineering Challenge 01.09.2014 Leading Systems Engineering Narratives Dieter Scheithauer, 2014. 4
Complexity Considerations The complexity of the systems engineering challenge is constrained by the initial knowledge in the domain of system technologies the process capabilities of the systems engineering organisations involved The complexity of the systems engineering challenge is a function of the size and the diversity of the system under consideration the initial knowledge about the system compared to the final knowledge gained at the end of that system s life cycle the number and quality of design decisions to be taken explicitly or implicitly the sequence, number and quality of action driving decisions made explicitly Note, these influencing factors have multiple dependencies between them including the convolution of design decisions and action driving decisions 01.09.2014 Leading Systems Engineering Narratives Dieter Scheithauer, 2014. 5
Manage the Systems Engineering Process (and not only the solution) Example Find optimum switch-on/switch-off pattern for four lamps considering multiple, non-trivial criteria. (24)4 = 216 = 65536 possible ways to the final solution with three intermediate solutions 24 = 16 possible solutions 01.09.2014 Leading Systems Engineering Narratives Dieter Scheithauer, 2014. 6
Homo Narrans The expert s knowledge is not accessible at once For the response, the expert has to generate a narrative considering The relevance of information in the expert s field of knowledge The anticipated novice s knowledge about the subject including terminology and semantic patterns 01.09.2014 Leading Systems Engineering Narratives Dieter Scheithauer, 2014. 7
Narration Theory Basics (1) Narratives follow a basic sequential pattern Then and then and then and then and then The relation between particular statements and episodes ranges continuously from temporal relations to causal relations Narratives with more causal relations are better memorisable than more temporal relations Narratives re-use particular patterns known to the audience adoption to human attention levels satisfying existing expectations embedding the narrative in a cultural context 01.09.2014 Leading Systems Engineering Narratives Dieter Scheithauer, 2014. 8
Narration Theory Basics (2) No single sequential narrative can explain a complex domain of knowledge, or the whole world sufficiently Some episodes of a narrative may tell side stories about related information not in the main flow of the narrative However, such episodes cannot compensate for the dominating narration flow Reality is better approximates as a network of multiple interwoven narratives building a net with positive and negative feedback loops 01.09.2014 Leading Systems Engineering Narratives Dieter Scheithauer, 2014. 9
Thinking Fast and Slow Contemplative thinking Slow thinking helps us to differentiate and to make distinctions Inventing terminology and semantics Slow thinking is rational thinking performed mainly consciously Human real-time capability is based on fast thinking Re-using patterns learned before as postulated by behaviourism Utilising one s knowledge and experience that may be modelled as a network of narratives In complex environments with multiple stimuli, unique paths are followed in the brain for perceiving a situation and generating appropriate action 01.09.2014 Leading Systems Engineering Narratives Dieter Scheithauer, 2014. 10
Expert Knowledge and Intuition The Ten-Years-Rule according to D. Kahnemann When can you trust the intuition of a person? When this person has at least ten years of deep rooted experience in a domain e.g. when this person is an expert The relation to narration theory An expert has created a closed meshed network of many narratives applicable to the field of knowledge She/he will perceive a situation in a multi-faceted way to generate an appropriate responsive action At its best, innovative ideas and novel behaviour may result 01.09.2014 Leading Systems Engineering Narratives Dieter Scheithauer, 2014. 11
Conclusions for Systems Engineering Training All attempts to try to explain all facets of systems engineering in a single narrative are doomed to failure Not all narratives that may be told by an expert may be beneficial for a novice A selection of leading systems engineering narratives have to be selected to define an effective and efficient systems engineering training Starting from this basis, a novice has a smooth entry point to widen and deepen the systems engineering knowledge with minimising the likelihood of frustration, and finally, to become a true systems engineering expert too 01.09.2014 Leading Systems Engineering Narratives Dieter Scheithauer, 2014. 12
Leading Systems Engineering Narratives Problem Processing The individual in the engineering team Problem Processing Cycle from problem finding to decision making Creativity Theme-Centred Interaction Group Dynamics The Systems Engineering Value Stream Teams in an engineering organisation including external relations The V as overall systems engineering value stream Breakdown of the systems engineering process Development process activities Assurance process activities Management process activities The System Life Cycle Tasks and responsibilities of organisations along the system life cycle The life cycle as a system property The goal of system life cycle efficiency Variations in business models and the impact on defining system life cycle phases Business development Life cycle phase interfaces and overlaps 01.09.2014 Leading Systems Engineering Narratives Dieter Scheithauer, 2014. 13
Content Introduction Problem Processing Problem Finding Problem Understanding Problem Shaping Problem Solving Decision Making The Systems Engineering Value Stream The System Life Cycle Concluding Remarks 01.09.2014 Leading Systems Engineering Narratives Dieter Scheithauer, 2014. 14
Problem Processing Cycle Before making a sound and sustainable decision on a problem someone needs to understand the problem comprehensively, and must have found the problem in the first place 01.09.2014 Leading Systems Engineering Narratives Dieter Scheithauer, 2014. 15
Problem Finding Problem finding is the most ignored step in problem processing The acceptance of the unknown disturbs the sel-view of omnipotence In competitive environments, the concession of unknowns weakens the negotiating power But we just do not see what we do not see, and Sokrates word to know to know nothing is more than coquetry Problem finding demands creativity But problem finding is not a focus in creativity research Linguistic and semiotic research provide some hints 01.09.2014 Leading Systems Engineering Narratives Dieter Scheithauer, 2014. 16
Creativity Creativity research is performed in two directions Experimental research Solving given problems Assessing capability for individual self-expression Empirical research Evaluating the life of people widely accepted for being exceptionally creative Findings from experimental research Creativity is a personal trait Certain social environments are supporting creative behaviour Findings from empirical research Socially relevant innovations come from people with at least ten years of deep rooted experience in the particular domain The ten-years-rule again In families with acknowledged innovators, the number of members with certain psychical diseases is significantly higher compared with the average 01.09.2014 Leading Systems Engineering Narratives Dieter Scheithauer, 2014. 17
Theme-Centred Interaction Embedded in a wider context, all human communication is constraint by three factors I We Subject For maintaining the level of reasonability high, it is important to drive the communication towards the direction of the subject And note, disturbances have precedence for successful communication eventually 01.09.2014 Leading Systems Engineering Narratives Dieter Scheithauer, 2014. 18
Problem Understanding Problem understanding demands a careful investigation of the problem under various perspectives In systems engineering this normally leads to evaluations from multiple disciplines point of views Problem understanding works best without a bias from other constraints like budget, resources and time The results of this stage do not generate any firm commitments automatically 01.09.2014 Leading Systems Engineering Narratives Dieter Scheithauer, 2014. 19
Problem Shaping Problem shaping establishes a commitment with respect to the problem to be solved This may disregard some findings from the problem understanding stage To generate commitments within teams, a common understanding of the problem to be solved is required Otherwise, contributions to the solution may not fit It is important to get the commitment from all disciplines that may have a limited insight into the problem itself, but have to contribute to the solution 01.09.2014 Leading Systems Engineering Narratives Dieter Scheithauer, 2014. 20
Group Dynamics All four phases have to be run through satisfying individual team members Storming may be unsufficient due to Avoidance by team members in the course of feeling unsecure Suppression by individuals executing power Unsufficient storming impacts commitments in the norming stage leading to a demand to return to the storming stage, or internal Emigration or open team disintigration, usually when matters become critical and tough 01.09.2014 Leading Systems Engineering Narratives Dieter Scheithauer, 2014. 21
Problem Solving The term problem solving is many times used as a synonym of the whole problem processing cycle This indicates some ignorance of the need to find the problem first This also ignores a distinction regarding decision making that may take further constraints into account In problem solving the technical expertise of the engineers contributing to the solution is the dominating factor Systems engineering adds some principles applicable to this stage, e.g. proceeding top-down generating solution alternatives 01.09.2014 Leading Systems Engineering Narratives Dieter Scheithauer, 2014. 22
Decision Making The term decision making is also used many times as a synonym of the whole problem processing cycle Mainly from a management perspective This fuels sometimes over-confidence to make decisions without really understanding the problem and the solution alternatives Decision making is the selection of the most appropriate solution alternative A bias to find isolated self-contained solutions for each problem is a risk to avoid considering more basic root causes Commitment to the decision by the whole systems engineering team is important as the solution may cause further problems in future 01.09.2014 Leading Systems Engineering Narratives Dieter Scheithauer, 2014. 23
Content Introduction Problem Processing The Systems Engineering Value Stream The Overall Systems Engineering Value Stream The Basic V The Development V The Assurance V The Dynamic V Work Product Generation Sequences The System Life Cycle Concluding Remarks 01.09.2014 Leading Systems Engineering Narratives Dieter Scheithauer, 2014. 24
Top-Down Design and Bottom-Up Integration Stakeholder Needs and Stakeholder Satisfaction Vertical Dimension: System Architecture Horizontal Dimension: Logical Sequence 01.09.2014 Leading Systems Engineering Narratives Dieter Scheithauer, 2014. 25
Logical Sequence The left-to-right direction expresses the logical sequence Several iterations may be performed concurrently over the full V or parts of it The logical sequence may be executed iteratively 01.09.2014 Leading Systems Engineering Narratives Dieter Scheithauer, 2014. 26
System Architecture Abstract Systems are a result of the recursive architectural decomposition of the Overall System due to technical and organizational reasons Abstract Systems may have a corresponding physical representation The System Environment represents the part of the world considered relevant for the Overall System The Overall System comprises all items and services to be delivered to a customer The vertical dimension expresses the System Architecture System Elements on the Implementation Level represent all the supplies from other parties not concerned with achieving stakeholder satisfaction on the Overall System 01.09.2014 Leading Systems Engineering Narratives Dieter Scheithauer, 2014. 27
Stakeholder Needs and Stakeholder Satisfaction Stakeholder Needs exist in the Stakeholders Minds All Systems Engineers analysing the System Environment, or developing the Overall System or any Abstract System are concerned with satisfying the Stakeholder Needs on the Overall System The stakeholders who have to deal with the system in the utilisation phase will rate their satisfaction when they operate the overall system in its real environment 01.09.2014 Leading Systems Engineering Narratives Dieter Scheithauer, 2014. 28
The Development V From Stakeholder Needs to Stakeholder Requirements Requirement Cascade System Integration Cascade System Integration Preparation 01.09.2014 Leading Systems Engineering Narratives Dieter Scheithauer, 2014. 29
Assurance Activities Assurance activities need to be performed continuously over the whole value stream Only distinct assurance activities are shown in correspondence to the development activities Process assurance is not visualised at all 01.09.2014 Leading Systems Engineering Narratives Dieter Scheithauer, 2014. 30
Validation It can never been proven during development that all relevant Stakeholder Needs have been captured completely Validation is best performed progressively during the development Validation activities provide a proof either that the understanding of stakeholder needs is substantiated, or that unwanted effects are absent 01.09.2014 Leading Systems Engineering Narratives Dieter Scheithauer, 2014. 31
Verification Verification means to demonstrate that the integrated system satisfies its System Requirements Verification is not applicable for the System Environment as the System Requirements on the System Environment are out of the scope of the development of the Overall System Verification includes satisfying assurance objectives driven by resolving assumptions as these assurance objectives also contribute to verification 01.09.2014 Leading Systems Engineering Narratives Dieter Scheithauer, 2014. 32
Iterations Over the V Iterations are unavoidable when the initial knowledge is significantly below 100 percent of the final knowledge Iterations over the V are caused by performing systems engineering activities repeatedly in different system life cycle phases satisfying the same or different objectives with the main focus on problem finding in conceptual phases with the focus of system improvement when utilising the product applying incremental or evolutionary development philosophies incorporating lessons learned# Iterations of all kinds need to be properly managed to maintain high integrity 01.09.2014 Leading Systems Engineering Narratives Dieter Scheithauer, 2014. 33
Iterations Over a Single System Element on the Left or Right Leg of the V They enhance the maturity of integrated System Elements forwarded for the integration of the upper level System They enhance the maturity of Allocated Requirements forwarded to System Elements Improved maturity of the configuration baselines of every System reduces the load on the heavier change control over the System Architecture! 01.09.2014 Leading Systems Engineering Narratives Dieter Scheithauer, 2014. 34
Iterations Over Multiple System Elements on the Left or Right Leg of the V They enhance the maturity of a System Architecture before System Elements on the Implementation Level are procured from suppliers They improve the reactivity to cope with anomalies especially when System Integration is performed on various architectural levels concurrently 01.09.2014 Leading Systems Engineering Narratives Dieter Scheithauer, 2014. 35
Iterations Over the System Architecture on the Left and Right Leg of the V They are usually the most costly Preferably, they should be pre-planned Pure event-driven iterations should be avoided except when the implementation effort is quite low as for example for some software development activities 01.09.2014 Leading Systems Engineering Narratives Dieter Scheithauer, 2014. 36
Content Introduction Problem Processing The Systems Engineering Value Stream The System Life Cycle System Life Cycle as a System Property Structuring the System Life Cycle Concluding Remarks 01.09.2014 Leading Systems Engineering Narratives Dieter Scheithauer, 2014. 37
System Life Cycle as a System Property The recognition of the system life cycle is the constituting event for the systems engineering discipline The original context is characterised by systems featuring high risk long lifetimes huge budgets significant economic impact Initially, the focus in systems engineering was very much placed on structuring the system life cycle into phases From today s knowledge, it is fully justified to anticipate the existence of a system life cycle as a property of every system 01.09.2014 Leading Systems Engineering Narratives Dieter Scheithauer, 2014. 38
System Life Cycle Phase Models Today The discussions of appropriate life cycle phase models today are rare System life cycle considerations are primarily seen as a further facet of the systems engineering process fully blended into what is described by the systems engineering value stream narrative Current standards mention system life cycle stages with contradicting descriptions, most notably a standard model with six stages This ignorance hampers true system life cycle orientation with the focus on system life cycle efficiency instead of profit for the engineering, production and maintenance organisations sound considerations on the organisational issues applicable over the whole system life cycle the transfer of systems engineering into market-driven business domains 01.09.2014 Leading Systems Engineering Narratives Dieter Scheithauer, 2014. 39
Definition Criteria for Defining System Life Cycles From mass production to one-off solutions From movable products physical and immaterial to stationary infrastructure From sales orientation to providing systems as a service From short system lifetimes to long system lifetimes From low economic impact to high economic impact Business models and conventions in particular business sectors Varying legal obligations in certain product domains 01.09.2014 Leading Systems Engineering Narratives Dieter Scheithauer, 2014. 40
Content Introduction Problem Processing The Systems Engineering Value Stream The System Life Cycle Concluding Remarks 01.09.2014 Leading Systems Engineering Narratives Dieter Scheithauer, 2014. 41
Concluding Remarks Three leading systems engineering narratives are proposed to provide a sound introduction into systems engineering The problem processing narrative is in practice highly reentrant and may be applied on various levels of granularity to the other two narratives Segregating the systems engineering value stream narrative from the system life cycle narrative allows a recognition of the iterative nature of systems engineering The system life cycle narrative allows further considerations to enable the outreach of systems engineering into other product and application domains 01.09.2014 Leading Systems Engineering Narratives Dieter Scheithauer, 2014. 42
Thank You for your attention Dieter Scheithauer Dr.-Ing., INCOSE ESEP Breitensteinstr. 26 83727 Schliersee Germany Phone: +49 (0) 80 26-97 68 00 Fax: +49 (0) 80 26-97 67 99 Mobile: +49 (0) 170-23 50 23 4 dieter.scheithauer@hitseng.eu www.hitseng.eu 01.09.2014 Leading Systems Engineering Narratives Dieter Scheithauer, 2014. 43