Conceptual Modeling: How to Connect Architecture Overview and Design Details?

Transcription

1 Conceptual Modeling: How to Connect Architecture Overview and Design Details? by Gerrit Muller USN-NISE, TNO-ESI Abstract Today s Smart systems are highly complex, due to the dynamic interactions between systems and the context, and the dynamic behavior within the system. The architecting challenge is to have overview facilitating reasoning, communication, and decision making. At the same time, details may disrupt expected behavior. Hence, architects and designers need a connection between overview and details. We will discuss application of architecture overviews in various complex systems. 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 The Problem: The Coming Software Apocalypse The Solution: A3 Architecture Overviews Principle: Three Main Views Example: Visualizations Principle: Multiple Abstraction Levels Example: Dynamic A3s The Challenges: Pitfalls and Dilemmas Conclusions and Questions

2 The Coming Software Apocalypse? The problem is that we are attempting to build systems that are beyond our ability to intellectually manage. (Nancy Leveson) "Software failures are failures of understanding, and of imagination" The Atlantic The Coming Software Apocalypse "Really he was interested in how people see and understand systems as he puts it, in the visual representation of dynamic behavior. (Bret Victor) 09/saving-the-world-from-code/540393/ James Somers Sep 26, Gerrit Muller CMCAODapocalypse

3 How to Architect Smart Systems? Smart Systems: interoperating with many systems data from everywhere Somers solution: replace code by models use formal methods intelligence, learning autonomous, automated, remote Dumb Stakeholders? who can intellectually manage them? who can understand their construction? who can imagine their interactions? how to visualize dynamic behavior? This presentation s solution: create Architecture Overviews in digestable nuggets static, dynamic, and qualities at various abstraction levels 3 Gerrit Muller CMCAODsmartSolutions

4 Figure of Contents TM The Problem: The Coming Software Apocalypse The Solution: A3 Architecture Overviews Principle: Three Main Views Example: Visualizations Principle: Multiple Abstraction Levels Example: Dynamic A3s The Challenges: Pitfalls and Dilemmas Conclusions and Questions 4 Gerrit Muller CMCAODlogo

5 The Solution: A3 Architecture Overviews 420 mm legend quality attributes 297 mm dynamic behavior visual aids notes parts source: PhD thesis Daniel Borches 5 Gerrit Muller CMCAODa3ao

6 Main Principles of A3 Architecture Overviews A3 Space limitation show essentials Show multiple views: Parts Dynamic behavior Quality attributes (and quantify!) Visualize Use visual aids Structure of A3s: multiple abstraction levels 6 Gerrit Muller CMCAODprinciples

7 Parts + Dynamic Behavior + Quality Attributes The Problem: The Coming Software Apocalypse The Solution: A3 Architecture Overviews Principle: Three Main Views Example: Visualizations Principle: Multiple Abstraction Levels Example: Dynamic A3s The Challenges: Pitfalls and Dilemmas Conclusions and Questions 7 Gerrit Muller CMCAODlogoMainViews

8 Dominating Mindset: Parts (static) Master Gateway ECU drivetrain engine ECU GPS ECU camera Coop driving system From: A reference architecture for cooperative driving by Sagar Behere, Martin Törngren, De-Jiu Chen parts prime interest of organization 8 Gerrit Muller CMCAODparts

9 Interaction Causing Emerging Dynamic Behavior get external data get goal trajectory get sensor get sensor data data transform transform into image into image fuse sensor images detect objects classify objects update world model analyze situation determine next step get GPS data get v, a calculate GPS location estimate location update location location objects world model dynamic behavior functionality interact parts prime interest of organization 9 Gerrit Muller CMCAODpartsDynamics

10 Prime Customer Interest: Key Performance Throughput Response Time Accuracy prime system responsibility quality attributes prime interest of customer Image Quality Reliability Safety Security results in dynamic behavior functionality interact Sensitivity Specificity... enose Sensitivity vs Specificity from: uploads/2017/07/poster-ers-2016.pdf parts prime interest of organization 10 Gerrit Muller CMCAODpartsDynamicsQualities

11 Example of Visualizations for Early Validation The Problem: The Coming Software Apocalypse The Solution: A3 Architecture Overviews Principle: Three Main Views Example: Visualizations Principle: Multiple Abstraction Levels Example: Dynamic A3s The Challenges: Pitfalls and Dilemmas Conclusions and Questions 11 Gerrit Muller CMCAODlogoExampleVisualizations

12 Example A3 Transit to Operation from: Kristian Frøvold, Applying A3 reports for early validation and optimization of stakeholder communication in development projects, INCOSE 2017 in Adelaide, Australia 12 Gerrit Muller CMCAODfrovoldA3

13 Findings A3 for Validation Too little knowledge about the function and why it existed within the project Not optimal market focus, and story the project was based on Easy and fast method to collect, document and share information from peoples head Developing the function through common understanding/agreement We were able to document and agree on important statements like needs, key drivers and market Bridges development with sales and marketing, and experienced operators (internal + external) People will have to consider the operational view and not only the technical perspective Everybody was able to work with the same tool Different focus Cross-fertilization Low effort training and implementation costs Broader involvement of stakeholders The stakeholders saw advantages of model based communication Easy to provide feedback Many new and improved requirements were collected and reported Gives the developers a clearer picture of what to make, a good overview of the function Piece of the puzzle May not cover all paths to validation failure 13 Gerrit Muller CMCAODfrovoldFindings

14 Multiple Abstraction Levels The Problem: The Coming Software Apocalypse The Solution: A3 Architecture Overviews Principle: Three Main Views Example: Visualizations Example: Dynamic A3s The Challenges: Pitfalls and Dilemmas Conclusions and Questions Principle: Multiple Abstraction Levels 14 Gerrit Muller CMCAODlogoLevels

15 Level of Abstraction Single System 10 0 number of details system requirements multidisciplinary design static system definition monodisciplinary 15 Gerrit Muller RAPpyramid

16 From system to Product Family or Portfolio number of details system system portfolio systems multidisciplinary monodisciplinary increase multidisciplinary monodisciplinary Gerrit Muller DRALpyramidGrowth

17 Product Family in Context number of details enterprise context enterprise stakeholders systems multidisciplinary design 10 9 parts, connections, lines of code 17 Gerrit Muller RAPdiabolo

18 Engineering 10 0 number of details system requirements multi-disciplinary design 10 7 static system definition mono-disciplinary Capturing all information that is required for: logistics, manufacturing, legislation, maintenance, life cycle support, Engineering 18 Gerrit Muller LAWFengineering

19 Design 10 0 number of details from needs and requirements to design: decomposition, interface definition, allocation, system concept selection, technology choices requirements multi-disciplinary design 10 7 static system definition mono-disciplinary Design anticipating engineering needs and constraints 19 Gerrit Muller LAWFdesign

20 Architecting number of details enterprise context enterprise stakeholders systems multidisciplinary design parts, connections, lines of code Architecting: realization and design choices in context some context details are essential some technical details are essential 20 Gerrit Muller LAWFdiabolo

21 Architecture Overviews at Multiple Levels number of details top-level A3 society enterprises enterprise stakeholders quality A3s processes systems aspect A3s multi-disciplinary design parts, connections, lines of code 21 Gerrit Muller IASAdiaboloA3

22 Example of Dynamic A3s The Problem: The Coming Software Apocalypse The Solution: A3 Architecture Overviews Principle: Three Main Views Example: Visualizations Principle: Multiple Abstraction Levels Example: Dynamic A3s The Challenges: Pitfalls and Dilemmas Conclusions and Questions 22 Gerrit Muller CMCAODlogoExampleDynamicA3s

23 Example Dynamic A3s for Gas Turbines from Vickram Singh, Knowledge Capture, Cross Boundary Communication and Early Validation with Dynamic A3 Architectures, INCOSE 2013 in Philadelphia, 23 Gerrit Muller CMCAODsinghA3Structure

24 A3 Luboil System Gas Turbine from Vickram Singh, Knowledge Capture, Cross Boundary Communication and Early Validation with Dynamic A3 Architectures, INCOSE 2013 in Philadelphia, 24 Gerrit Muller CMCAODsinghA3

25 Early Validation with Dynamic A3 Detect 8 missing parameters (sensors, control settings, and mechanical components) Gave engineers what and how, and they started to ask why Finalize design and approval in only two revisions! from Vickram Singh, Knowledge Capture, Cross Boundary Communication and Early Validation with Dynamic A3 Architectures, INCOSE 2013 in Philadelphia, 25 Gerrit Muller CMCAODsinghPIDchanges

26 Pitfalls, Dilemmas, Conclusions, and Questions The Problem: The Coming Software Apocalypse The Solution: A3 Architecture Overviews Principle: Three Main Views Example: Visualizations Principle: Multiple Abstraction Levels Example: Dynamic A3s Conclusions and Questions The Challenges: Pitfalls and Dilemmas 26 Gerrit Muller CMCAODlogoChallenges

27 Typical Pitfalls and Dilemmas when Making A3AOs Lack of context understanding: customer context life cycle context Staying superficial Lack of dynamic behavior understanding Lack of quality attributes understanding Short-term orientation No sense-of-urgency Drowning in multitude of options Too few perspectives; one-dimensional thinking 27 Gerrit Muller CMCAODdilemmas

28 Conclusions, and Questions The Problem: The Coming Software Apocalypse The Solution: A3 Architecture Overviews Principle: Three Main Views Example: Visualizations Principle: Multiple Abstraction Levels Example: Dynamic A3s The Challenges: Pitfalls and Dilemmas Conclusions and Questions 28 Gerrit Muller CMCAODlogoFinal

29 Conclusions and Questions? A3AOs are: practical powerful means to create overview cope with complexity However, A3AOs require: architecting competence visualization skills conceptual modeling competence zoom in, zoom out agility many viewpoints capacity Questions? 29 Gerrit Muller CMCAODconclusions