Less Heavy Systems Engineering; How Much is Approriate?

Transcription

1 Less Heavy Systems Engineering; How Much is Approriate? by Gerrit Muller Buskerud University College Abstract Many companies are aware of opportunities to improve systems development, system integration and complex project execution. Conventional Systems Engineering from the military and aerospace domain, although perceived as useful, also tends to be seen as heavy in terms of process and artifacts. In this paper we explore alternative Systems Engineering approaches that are perceived as lighter. We also explore how much Systems Engineering is appropriate. Distribution This article or presentation is written as part of the Gaudí project. The Gaudí project philosophy is to improve by obtaining frequent feedback. Frequent feedback is pursued by an open creation process. This document is published as intermediate or nearly mature version to get feedback. Further distribution is allowed as long as the document remains complete and unchanged. status: preliminary draft

2 At the Beginning of this Century Spring 2000, preparing key-note for conference Let's go for Light Weight Processes You cannot be serious You do not want Light Weight Architecting Oh yes, absolutely, Light Weight Architecting is what we need Process Improvement Manager Architect 2 Gerrit Muller LHSEtriggerAnecdote

3 Architecture Weight weight(architecture) = weight(rule) all rules On/Off Rule Rule 1 Rule Kg Rule Rule Rule 1 1 Rule 1 n weight (rule) = f ( level of enforcement, scope (impact), size, guideline component single-line conditional rule product multi-line mandatory rule portfolio multi-page level of coupling or number of dependencies ) stand-alone builds on many rules low weight high 3 Gerrit Muller LWAarchitectureWeight

4 Effectiveness(Flexibility, Manageability) Effectiveness Flexibility Evolution Responsiveness market change technology change Manageability supply chain mass production long life times dependability very low low medium high very high process weight 4 Gerrit Muller BPCAeffectivenessCurves

5 Effectiveness Effectiveness = Flexibility W F * Manageability Effectiveness W F =0.3 W M =0.7 W M Effectiveness Flexibility Manageability very low low medium high very high process weight 5 Gerrit Muller BPCAeffectivenessFlexible

6 Light Weight How To weight(architecture) = all rules weight(rule) 2. Minimize the weight per rule 1. Reduce the rule set to the (business) essential Understand your customer your customer's customer etcetera 6 Gerrit Muller LWAlightWeightHow

7 Minimize Rule Weight weight(rule)= minimize number of mandatory rules f ( level of enforcement, empower, delegate scope (impact), minimize implementation details focus on essential concepts size, level of coupling or number of dependencies ) Apply design principles on architecture Multi-view architecting 7 Gerrit Muller LWAlightWeightRuleHow

8 Simplified Framework Effectiveness (Customer Value) Do the right things What methods increase (understanding of) Customer Value? What can you use in your own company to increase (understanding of) Customer Value? Efficiency (Effort, cost, and time per result) Do things right What methods improve the efficiency of the company? What can you use to improve the efficiency of your company? 8 Gerrit Muller LHSEsimplifiedFramework

9 Work Form for KSEE 2011 Effectiveness (Customer Value) Do the right things What can you use in your own company to increase (understanding of) Customer Value? Efficiency (Effort, cost, and time per result) Do things right What can you use to improve the efficiency of your company? Håkan Gustavsson Is it Lean or just common sense? Einar Jørgensen Globalising System Engineering and Lean Principles Odd Guldsten Complex power systems for offshore oil&gas topside installation John Bjarne Bye Lean Transformation Jon Wade Systems Engineering: At the Crossroads of Complexity Andreas Thorvaldsen Manufacturing Systems Modelling Kristian Frøvold Early Validation through the A3 method Gerrit Muller Less Heavy Systems Engineering; How Much is Appropriate? 9 Gerrit Muller LHSEformKSEE

10 Explanation of Work Form We expect that everyone fills in the form during or at the end of every presentation. The purpose is to stimulate you to reflect on possible value for your own company. We recommend to write down specific examples. The last presentation will look back at at all presentations. 10 Gerrit Muller LHSEworkFormExplanation

11 Time to Harvest! Figure Of Contents TM LEAN manufacturing 1 2 Knowledge Based Design A3 overviews A3 reports 4 User Stories ConOps Workflow Models 3 Less Heavy SE 5 6? How To 11 Gerrit Muller LHSEtimeToHarvest

12 LEAN Manufacturing strive for flow eliminate Toyota Production System (TPS) non-value-adding work overburden unevenness customer value empowerment continuous improvement evolved into LEAN manufacturing Just In Time autonomation result: organic flow manufacturing efficient, flexible, short cycle times A3 reports value stream mapping 12 Gerrit Muller LHSEleanManufacturing

13 Example of LEAN Manufacturing in Automotive work spot local stock scheduling white board One heart beat Every truck is unique Local scheduling Many practical local solution by Continuous Improvement 13 Gerrit Muller LHSEexampleAutomotiveLEANmanufacturing

14 Knowledge Based Design LEAN manufacturing 1 2 Knowledge Based Design A3 overviews A3 reports 4 User Stories ConOps Workflow Models 3 Less Heavy SE 5 6? How To 14 Gerrit Muller LHSElogoKBD

15 Knowledge Based Design LEAN manufacturing repeatable, production oriented inspires LEAN product development (LPD) creative, development oriented evolves into Knowledge Based Design a Norwegian variant of LPD improving efficiency by (re-)using knowledge 15 Gerrit Muller LHSEknowledgeBasedDesign

16 Example of LPD in Automotive all physical components of new truck design wall space full of schedules and visualizations development supported by team location tactile and visual support developers drive trucks themselves (customer understanding) 16 Gerrit Muller LHSEexampleAutomotiveLPD

17 Reflections on Knowledge Knowledge is abstract and intangible. is data in a computer knowledge? are text and figures in a book knowledge? Value is obtained when knowledge is applied properly. competence = knowledge + skills Humans need experience to develop skills. skills are practical, developed by doing Skills and experience are complementary to knowledge. 17 Gerrit Muller LHSEreflectionOnKnowledge

18 Level of Abstraction Single System 10 0 number of details system requirements multi-disciplinary design static system definition mono-disciplinary 18 Gerrit Muller RAPpyramid

19 From system to Product Family or Portfolio number of details system system portfolio systems multi-disciplinary mono-disciplinary increase multi-disciplinary mono-disciplinary Gerrit Muller DRALpyramidGrowth

20 Product Family in Context enterprise context enterprise number of details stakeholders systems multi-disciplinary design parts, connections, lines of code 20 Gerrit Muller RAPdiabolo

21 Knowledge at Multiple Levels number of details customer understanding knowledge construction knowledge fundamental knowledge 21 Gerrit Muller LHSEknowledgePyramids

22 Example of Fundamental Knowledge power a = asymptot = 12 linear behavior load 22 Gerrit Muller LHSEexampleFundamentalKnowledge

23 Example of Construction Knowledge source: Bjørnar Wiulsrød SESG presentation March SESG_Wiulsr%EF%BF%BDdA3overviews.pdf 23 Gerrit Muller LHSEexampleConstructionKnowledge

24 Customer Understanding LEAN manufacturing 1 2 Knowledge Based Design A3 overviews A3 reports 4 User Stories ConOps Workflow Models 3 Less Heavy SE 5 6? How To 24 Gerrit Muller LHSElogoUser

25 How well do Your Engineers Understand Your Customer? In every hand-over and every conversion knowledge is lost How much customer understanding needs validation is present at these levels? specification verification system design system test subsystem design subsystem test component design component test component realization 25 Gerrit Muller LHSEvModelCustomerKnowledge

26 Methods to Capture Customer Understanding User Stories Specific stories to explore specification and design. Contain social and environmental details to make engineers aware ConOps Concept of Operations, used in Defense Domain Factual description of Operational use, a.o. with scenarios Work Flows Systematic description of user operations. Annotated with Where, When, Who, What This is one class of methods, there are many more methods 26 Gerrit Muller LHSEcustomerMethods

27 Example of Customer Knowledge operations workflow geographical source: master project papers Kristian Frøvold and Martin Kruse 27 Gerrit Muller LHSEexampleCustomerKnowledge

28 A3 Overviews and A3 Reports LEAN manufacturing 1 2 Knowledge Based Design A3 overviews A3 reports 4 User Stories ConOps Workflow Models 3 Less Heavy SE 5 6? How To 28 Gerrit Muller LHSElogoA3

29 A3 Overview Fundamentals Legend Quantification of key parameters Functional View Visual aid Constraints Choices Physical View A3 Architecture Overviews Focusing architectural knowledge to support evolution of complex systems by: Daniel Borches and Maarten Bonnema, INCOSE Gerrit Muller LAWFexampleDDASoverview

30 A3 Overview Fundamentals (2) multiple related views quantifications one topic per A3 capture "hot" topics digestable (size limitation) source: PhD thesis Daniel Borches practical close to stakeholder experience 30 Gerrit Muller LAWFleanArchitecting

31 Evaluation of Conventional Design Spec Results of Questionnaire System Design Specification Source: PhD thesis Daniel Borches < 31 Gerrit Muller LHSEconventionalDesignSpec

32 Amount of Data per Medium #details in A3 100 to 1000 details/a How detailed is a good A3? systems #details in document 200 details/page 20 to 200 pages/doc multidisciplinary Report Spec 4000 to details/doc mono-disciplinary #details in "model-based" repositories large practically unlimited 32 Gerrit Muller LHSEdetailsPerDocument

33 Number of Conventional Documents 10 0 #details in document systems multidisciplinary We need about 1000 documents to describe detailed designs 200 details/page 20 to 200 pages/doc 4000 to details/doc mono-disciplinary In practice many more are needed, because of duplication and noise 33 Gerrit Muller LHSEnumberOfArtifacts

34 What If we Use A3s for all Detailed Designs? 10 0 #details in A3 systems We need about A3s to describe detailed designs 100 to 1000 details/a3 multidisciplinary In practice more are needed, because of duplication and noise mono-disciplinary Gerrit Muller LHSEnumberOfA3sDetailedDesign

35 What If we Use A3s for System Design? 10 0 #details in A3 systems multidisciplinary mono-disciplinary We need about 400 A3s to describe system design A3s are useful to focus on specific issues there might be many more focused A3s In practice some more are needed, because of duplication and noise 100 to 1000 details/a3 35 Gerrit Muller LHSEnumberOfA3s

36 Conclusions A3s We need documents and A3s and data bases We need to design documentation structure We need conventions for use naming, meta information, structure, storage A3s fit in broader context A3s are practical and work well 36 Gerrit Muller LHSEdocumentsConclusions

37 LEAN manufacturing 1 2 Knowledge Based Design A3 overviews A3 reports 4 User Stories ConOps Workflow Models 3 Less Heavy SE 5 6? How To 37 Gerrit Muller LHSElogoHowTo

38 Light Weight How To 1. Reduce the rule set to the (business) essential Understand your customer your customer's customer etcetera ConOps user stories work flows weight(architecture) = all rules minimize number of mandatory rules agile f ( level of enforcement, empower, delegate LEAN scope (impact), minimize implementation details focus on essential concepts A3 size, level of coupling or number of dependencies ) Apply design principles on architecture and documentation Multi-view architecting systems thinking A3 38 Gerrit Muller LHSEhowTo

39 ? 39 Gerrit Muller LHSElogoQuestionMark