Requirements for Extremely Complex Systems
Download as PPTX, PDF1 like731 views
The document discusses the complexities involved in the requirements for extremely complex systems, highlighting the interdependency of levels within these systems and the critical nature of precise requirements to avoid safety and financial risks. It addresses the challenges of managing vast numbers of requirements and the necessity for clear documentation, modeling, and traceability to ensure successful system design and implementation. Additionally, it contrasts traditional and agile approaches to requirements management, emphasizing the importance of adaptability and structured analysis.
Requirements for Extremely Complex Systems
- 1. David Hetherington 2/13/2016 Product Camp Austin 16 - Requirements for Extremely Complex Systems 1
- 2. 2/13/2016 Product Camp Austin 16 - Requirements for Extremely Complex Systems 2
- 3. 2/13/2016 Product Camp Austin 16 - Requirements for Extremely Complex Systems 3 Multiple Levels Each Level is a “System” in its own right. Requirements at any level affect all the levels below.
- 4. 2/13/2016 Product Camp Austin 16 - Requirements for Extremely Complex Systems 4 Mission-Critical “Five Nines” Availability Required Multiple Suppliers Software/Requirements mistakes can kill people Safety-Critical Tower of Babel Software/Requirements mistakes can cause huge financial losses High Stakes
- 5. 2/13/2016 Product Camp Austin 16 - Requirements for Extremely Complex Systems 5
- 6. 2/13/2016 Product Camp Austin 16 - Requirements for Extremely Complex Systems 6 http://www.omgwiki.org/MBSE/lib/exe/fetch.php? media=mbse:03-2013_incose_mbse_workshop- ford_automotive_complexity_v4.0-davey.pdf Presentation of Christopher Davey at the INCOSE International Workshop MBSE Workshop January 26th-28th, 2013 A luxury car can have more than 100 onboard computers Many “requirements” need multiple onboard computers to cooperate with each other in a tightly choreographed dance.
- 7. 2/13/2016 Product Camp Austin 16 - Requirements for Extremely Complex Systems 7 http://www.omgwiki.org/MBSE/lib/exe/fetch.php? media=mbse:03-2013_incose_mbse_workshop- ford_automotive_complexity_v4.0-davey.pdf Presentation of Christopher Davey at the INCOSE International Workshop MBSE Workshop January 26th-28th, 2013 Working out all that choreography produces 450,000 requirements.
- 8. 2/13/2016 Product Camp Austin 16 - Requirements for Extremely Complex Systems 8
- 9. Stage 1 Stage 3Stage 2
- 10. Skilled Professionals Hate “Bureaucracy” “Tell Me What You Need” “I’ll Make it Happen!” Not Scalable
- 12. 2/13/2016 Product Camp Austin 16 - Requirements for Extremely Complex Systems 12
- 14. V0.4 – 3 January 2016Copyright© 2016 - Confidential 14 Euro Norm (2007) Something Else (1982) 3rd Item (1967) …Shall be compliant with XYZ Sections 3.4 and 7.8 …as laid out in Table x31.2 in… Untangling this sort of mess leaves a spider web that does not fit neatly in a traceability matrix.
- 15. V0.4 – 3 January 2016Copyright© 2016 - Confidential 15 Some Standard “…shall automatically stop at pedestrian crossings if pedestrians are present.” So…what does this standard actually require? A lot of analysis and interpretation will be required!
- 16. 2/13/2016 Product Camp Austin 16 - Requirements for Extremely Complex Systems 16
- 17. 2/13/2016 Product Camp Austin 16 - Requirements for Extremely Complex Systems 17
- 18. Semi-Automated document input Drag-and-drop Easy output of Word documents Good traceability functions 2/13/2016 Product Camp Austin 16 - Requirements for Extremely Complex Systems 18 Strengths Weaknesses Text-only is cumbersome “A picture is worth a thousand words” Requirements reviews are painful Hard to link to other tools
- 19. 2/13/2016 Product Camp Austin 16 - Requirements for Extremely Complex Systems 19
- 20. The Database Keeps Track of the Relationships Structure Requirements Behavior
- 21. “Model-Based Systems Engineering” is the More Formal Term. Simple Diagrams Different Diagrams for Different Stakeholders As Many Diagrams as Needed One Concept per Diagram Model Database Consolidates Information Structure View Plumbing View Software View
- 23. 2/13/2016 Product Camp Austin 16 - Requirements for Extremely Complex Systems 23
- 24. 2/13/2016 Product Camp Austin 16 - Requirements for Extremely Complex Systems 24
- 25. 2/13/2016 Product Camp Austin 16 - Requirements for Extremely Complex Systems 25
- 26. 2/13/2016 Product Camp Austin 16 - Requirements for Extremely Complex Systems 26
- 27. 2/13/2016 Product Camp Austin 16 - Requirements for Extremely Complex Systems 27
- 28. 2/13/2016 Product Camp Austin 16 - Requirements for Extremely Complex Systems 28
- 29. 2/13/2016 Product Camp Austin 16 - Requirements for Extremely Complex Systems 29
- 30. 2/13/2016 Product Camp Austin 16 - Requirements for Extremely Complex Systems 30 Animation by Kalia Pickett
- 31. 2/13/2016 Product Camp Austin 16 - Requirements for Extremely Complex Systems 31 If a careless mistake in your requirements, coding, or verification can incinerate a crew of 150 people, it is immoral to “blow off the documentation”…
- 32. 2/13/2016 Product Camp Austin 16 - Requirements for Extremely Complex Systems 32
- 33. V0.4 – 3 January 2016Copyright© 2016 - Confidential 33 Requirements Requirements Requirements Pictures Pictures Pictures Pictures Pictures PowerPoint Compiler Product
- 34. V0.4 – 3 January 2016Copyright© 2016 - Confidential 34 Wants range to be > 1km Marketing Vertical beam pattern? Antenna Guy Transmit Power? Radio How big is the test track? Test Facility FFT range bins? Digital Message format? Firmware Power Dissipation? Thermal Package Design? Mechanical “Make it 1000m” “Seems to be1000m” “2048 point FFT” “Rent an airport” “20 watt radio” “Need a big fan”
- 35. V0.4 – 3 January 2016Copyright© 2016 - Confidential 35 Wants range to be > 1km Marketing Vertical beam pattern? Antenna Guy Transmit Power? Radio How big is the test track? Test Facility FFT range bins? Digital Message format? Firmware Power Dissipation? Thermal Package Design? Mechanical Range = 182m System Model
- 36. 2/13/2016 Product Camp Austin 16 - Requirements for Extremely Complex Systems 36
- 37. Illusion of predictability Elaboration too early Long periods without working code 2/13/2016 Product Camp Austin 16 - Requirements for Extremely Complex Systems 37 Traditional Side Agile Side Moaning about “Waterfall” Skipping the documentation Flexible definition of “done”
- 38. Precision Accountability Project Scale 2/13/2016 Product Camp Austin 16 - Requirements for Extremely Complex Systems 38 Traditional Side Agile Side Frequent checkpoints reduce risk Efficient management of uncertainty Superior team throughput
- 39. 2/13/2016 Product Camp Austin 16 - Requirements for Extremely Complex Systems 39 Collect lots of requirements documents Make beautiful “Logical” architecture model Elaborate 20 levels of logical architecture and increasingly detailed requirements Publish voluminous specifications based on above Attempt to “allocate” logical architecture to real world subsystems Discover that nothing works Blame the tools!!
- 40. 2/13/2016 Product Camp Austin 16 - Requirements for Extremely Complex Systems 40 Existing System Model (Existing) Requirements Reverse Engineer Elaborate And Allocate Gaps Model (New) Try for Fit? Agile Process New System
- 41. 2/13/2016 Product Camp Austin 16 - Requirements for Extremely Complex Systems 41
- 42. David Hetherington ◦ LinkedIn: https://www.linkedin.com/in/djhetherington ◦ GitHub: https://github.com/DavidHetherington ◦ Dave’s “Minimal SaaS” Demo: http://cities.asattepress.com/ 2/13/2016 Product Camp Austin 16 - Requirements for Extremely Complex Systems 42