Model-Based Conceptual Design through to system implementation

Transcription

1 Australian Systems Engineering Workshop October 2015, Sydney, NSW, Australia Model-Based Conceptual Design through to system implementation Lessons from a structured yet agile approach Presenter: Matthew Wylie Senior Systems Engineer, Shoal Engineering Pty Ltd ASEW 2015 MBCD through to system implementation 1

2 Presentation overview Background Conceptual design using model-based methods Software development using Agile MBCD and Agile Flexibility and Traceability Lessons learnt Further development and future applications Conclusions Questions ASEW 2015 MBCD through to system implementation 2

3 Background ange safety planning MBCD using WSAF Agile Scrum Example US military range safety trace Deterministic trace Source: ASEW 2015 MBCD through to system implementation 3

4 Model-based Conceptual Design (MBCD) IT 1 IT 2 IT 3 IT n 2 4 weeks MBCD workflow Planning Scope Engagement Tasks Deliverables Develop knowledge model Engage stakeholders un workshops isk and issues management Develop operational concept Develop specifications Develop test concept eview eview meetings Produce knowledge model outputs Stakeholder feedback equirements ASEW 2015 MBCD through to system implementation 4

5 Model-based Conceptual Design (MBCD) Critical Issue [Critical Issue] generates addressed by Needs Single Statement of User Need [equirement] refines Policy and egulation Source [Document] documents guides Solution Constraint [equirement] System equirements refined by verified by verified by [Verfication equirement] verified by Need [equirement] Solution- Independent Constraint [Guidance] Functional equirement [equirement] Non-Functional equirement [equirement] Interface equirement [equirement] refined by refined by composed of [Architecture] composed of specified by specified by specified by [ Task] basis of [System Mission] Capability Node [Performer] built from [Performer] performs performs Decomposed by Scenario [ Activity] decomposed by [ Activity] achieved by inputs/ outputs/ triggered by exhibits results in MOE [Performance Characteristic] enabled by enabled by decomposed by enabled by System Function [Function] inputs/ outputs/ triggered by exhibits performs MOP [Performance Characteristic] exhibits Sub-System/ Component [Component] augmented by connects built from built from Capability System [Component] joins [Interface] comprised of joins External System [Component] [ Item] enabled by [Item] transfers decomposed by [Link] connects Architecture Behaviour Functional Design System Architecture A rearranged sub-set of the key elements diagram from the WSAF reference model v1.5.1 ASEW 2015 MBCD through to system implementation 5

6 4.1 Execution cue Prepare to execute 4.2 Mission manoeuvre command Manoeuvre 4.3 Situation awareness picture Threat denial command Weapon system picture Deny threat 4.4 Initiate weapon payload elease payload Deliver payload Payload support data 4.5 Initiate weapon payload Payload command Weapon system picture Payload status Payload support requirement Support weapon payload 4.6 Complete execution Date: Tuesday, 17 October 2006 Number: 4 Author: Name: Delivery platform state Threat denial requirements Payload detonation Payload status report Execution complete Kevin Execute LP LP Decision requirement 1.1 Consult with customer isk statement High level question 1.2 Question scenario Question operational context Deconstruct question Identified functions elevant PerfChar 1.3 Develop study plan Additions to WSAF structure Problem definition loop 1.4 New questions Insufficient information and/or resources to answer questions accurately Study plan Define fidelity requirements O Insufficient definition Sufficient definition Fidelity requirement document LE O LP 1.5 Acquire models and data O Final agreed study plan 4.1 System information Insufficient resources Accreditation report Sufficient resources Qualified models Execution cue Prepare to execute LE 4.2 Mission manoeuvre command O Manoeuvre LP 4.3 Situation awareness picture Threat denial command Weapon system picture Deny threat WSAF update Perform studies eport to customer Initiate weapon payload elease payload Deliver payload Payload support data 4.5 Initiate weapon payload Payload command Weapon system picture Payload status Payload support requirement Support weapon payload 4.6 Complete execution Date: Tuesday, 17 October 2006 Number: 4 Author: Name: Delivery platform state Threat denial requirements Payload detonation Payload status report Execution complete Kevin Execute Components of WSAF Capability Skilled people Support (training and facilities) Probability of kill PerformanceCh... based on Accuracy of terminal guidance PerformanceCh... based on Probability of mid-course navi... PerformanceCh... Desk officer / IPT Experts Document map / Template COE tool Description: decomposed by: decomposes: exhibits: Function: 4 Execute This is the main action function in the mission. In strike it involves transit of the delivery platform to the release zone and flight of the weapon from release to impact, together with the associated support functions. This is generally the principal of interest to WSD, in particular the deliver payload sub-function which covers the flight of the weapon from launch to impact at the target. Function: 4.1 Prepare to execute Function: 4.2 Manoeuvre Function: 4.3 Deny threat Function: 4.4 Deliver payload Function: 4.5 Support weapon payload Function: 4.6 Complete execution Function: 0 Weapon System Mission PerformanceCharacteristic: Communications survivability PerformanceCharacteristic: Execution flexibility PerformanceCharacteristic: Execution time PerformanceCharacteristic: Off task endurance PerformanceCharacteristic: Platform survivability PerformanceCharacteristic: Probability of successful execution PerformanceCharacteristic: Strike range PerformanceCharacteristic: Time over target area Mission Op Tasks (Objectives) assigned to (Task) Organisation responsible for Library of projects performs Node connected to Needline ( Connectivity) Performance Characteristic (MOE) exhibits Need Activity in/output basis of implements implements Function in/output scoped by Performance Characteristic (MOP) exhibits performed by (Data) transferred transfers Information Item by based on Probability of target acquisitio... PerformanceCh... based on Simultaneous time on target PerformanceCh... based on Terminal effectiveness PerformanceCh... based on Weapon survivability PerformanceCh... basis of Probability of successful execu... PerformanceCh exhibited by Deliver payload Function Enterprise domain System domain Analysis Context domain Guidance (Op System Policy and refined by refined by Constraints Constraints Doctrine) eference Model results in Study scoped by Question specifies defines Study Component Plan connected to constrains Analysis Links Fidelity equirement comprises of Existing corporate and capability documentation Diagram courtesy DSTO Scripts DCP capability documentation and other reports Process exhibits Exchange Characteristics generates exhibits [Critical ] Issues Enterprise interfaces (External) Interfaces ASEW 2015 MBCD through to system implementation 6

7 Example Views System hierarchy System connectivity ASEW 2015 MBCD through to system implementation 7

8 One model many views Conceptual design using MBSE ASEW 2015 MBCD through to system implementation 8

9 Conceptual design using MBSE Same data different views ASEW 2015 MBCD through to system implementation 9

10 Traceability Example traceability path Strategic Guidance activity needs Functions Functional equirements efined requirements Software components Planning Doctrine Guides Initial planning esults in Defined user type roles Basis of Determine user type Specified by... User type selection efined by Set user type restrictions Specifies Set user permissions Model-based conceptual design Software development ASEW 2015 MBCD through to system implementation 10

11 Wider traceability view Traceability Needs System equirements Critical Issue [Critical Issue] generates addressed by Single Statement of User Need [equirement] refines Policy and egulation Source [Document] documents guides Solution Constraint [equirement] refined by verified by verified by [Verfication equirement] verified by Need [equirement] Solution- Independent Constraint [Guidance] Functional equirement [equirement] Non-Functional equirement [equirement] Interface equirement [equirement] refined by refined by composed of [Architecture] composed of specified by specified by specified by [ Task] basis of [System Mission] Capability Node [Performer] built from [Performer] performs performs Decomposed by Scenario [ Activity] decomposed by [ Activity] achieved by inputs/ outputs/ triggered by exhibits results in MOE [Performance Characteristic] enabled by enabled by decomposed by enabled by System Function [Function] inputs/ outputs/ triggered by exhibits performs MOP [Performance Characteristic] exhibits Sub-System/ Component [Component] augmented by connects built from built from Capability System [Component] joins [Interface] comprised of joins External System [Component] [ Item] enabled by [Item] transfers Architecture decomposed by [Link] Behaviour Functional Design System Architecture A sub-set of the key elements diagram from the WSAF reference model v1.5.1 connects ASEW 2015 MBCD through to system implementation 11

12 Software development using Agile Scrum Sprint 1 Sprint 2 Sprint 3 Sprint n 2 4 weeks equirements Sprint workflow Planning Sprint planning meeting Stories Prioritisation Sprint Develop software Verification eview Sprint review meeting Scrum roles Scrum master Developers Product owner Product backlog Sprint backlog Daily scrum Functioning software product Changes / enhancements Project team Stakeholders Users ASEW 2015 MBCD through to system implementation 12

13 Software development using Agile Scrum Manifesto for Agile Software Development We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value: Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation esponding to change over following a plan That is, while there is value in the items on the right, we value the items on the left more. Source: ASEW 2015 MBCD through to system implementation 13

14 MBCD and Agile Leveraging MBCD traceability in Agile development Prioritisation Model can identify requirements to be implemented to provide specific functionality or meet specific needs. esponding to change Allows informed assessment of the impact and suitability of proposed design changes resulting from early customer assessments of the product. Focus on function ich functional models help define the what Software development effort can focus on the how educes uncertainty for the software developers ASEW 2015 MBCD through to system implementation 14

15 MBCD and Agile Model-based conceptual design Strategy System Software development Strategic Guidance Document Scenario Top-Level Need Function equirement Software development environment constraints documents decomposes refines decomposes refines Specifies Guidance element guides Vignette Consolidated Need basis of Function specified by equirement Specifies Software component documents decomposed by refined by decomposed by Specifies Documented SME Guidance Activity results in Need Function efined by equirement ASEW 2015 MBCD through to system implementation 15

16 Wider traceability view (WSAF subset) MBCD and Agile Needs System equirements Critical Issue [Critical Issue] generates addressed by Single Statement of User Need [equirement] refines Policy and egulation Source [Document] documents guides Solution Constraint [equirement] refined by verified by verified by [Verfication equirement] verified by Need [equirement] Solution- Independent Constraint [Guidance] Functional equirement [equirement] Non-Functional equirement [equirement] Interface equirement [equirement] refined by refined by composed of [Architecture] composed of specified by specified by specified by [ Task] basis of [System Mission] Capability Node [Performer] built from [Performer] performs performs Decomposed by Scenario [ Activity] decomposed by [ Activity] achieved by inputs/ outputs/ triggered by exhibits results in MOE [Performance Characteristic] enabled by enabled by decomposed by enabled by System Function [Function] inputs/ outputs/ triggered by exhibits performs MOP [Performance Characteristic] exhibits Sub-System/ Component [Component] augmented by connects built from built from Capability System [Component] joins [Interface] comprised of joins External System [Component] [ Item] enabled by [Item] transfers Architecture decomposed by [Link] Behaviour Functional Design System Architecture A sub-set of the key elements diagram from the WSAF reference model v1.5.1 connects ASEW 2015 MBCD through to system implementation 16

17 Functional models Why are they important? Level 1 Hazard mitigation Construct range Geometry safety checks Level 2 Danger area 1 safety Define danger areas Danger areas safety measures Level 3 Occupancy warning Plot danger area 1 Check danger area 1 But what is the required functional sequence? Occupancy warning Plot danger area 1 Check danger area 1 Check danger area 1 Plot danger area 1 Occupancy warning Plot danger area 1 Check danger area 1 Occupancy warning ASEW 2015 MBCD through to system implementation 17

18 Functional Model ASEW 2015 MBCD through to system implementation 18

19 Lessons learnt equirements derived from functional models are easily transitioned into the software development space. MBCD processes have a natural synergy with software development processes. MBCD is capable of supporting the flexible nature of Agile development by providing clear traceability back to user needs. Involvement of the development team in the MBCD process beneficial. Software architecture and components were not modelled in detail potential enhancement. ASEW 2015 MBCD through to system implementation 19

20 Further development and future applications Further exploit synergies between MBCD and Software Development. Close the distinction between conceptual design phase and software development phase. Integrate MBCD solution system definition process and software architecting / planning process. ASEW 2015 MBCD through to system implementation 20

21 Project process enhancements Existing process IT 1 IT 2 IT 3 Sprint 1 Sprint 2 Sprint 3 Sprint 4 Sprint 5 MBCD workflow Sprint workflow Planning Develop knowledge model Outputs eview Stakeholder feedback equirements Product backlog Planning Sprint eview Sprint backlog Daily scrum Functioning software product Changes / enhancements esource allocation MBCD team Software development team ASEW 2015 MBCD through to system implementation 21

22 Project process enhancements Enhanced process IT 1 IT 2 IT 3 Sprint 1 Sprint 2 Sprint 3 Sprint 4 Sprint 5 MBCD workflow Sprint workflow Planning Develop knowledge model Outputs eview Stakeholder feedback equirements Product backlog Planning Sprint eview Sprint backlog Daily scrum Functioning software product Changes / enhancements esource allocation MBCD team Software development team ASEW 2015 MBCD through to system implementation 22

23 Project process enhancements Agile for MBCD IT 1 IT 2 IT 3 Sprint 1 Sprint 2 Sprint 3 Sprint 4 Sprint 5 MBCD Sprint workflow Software dev. Sprint workflow Planning MBCD Sprint eview Planning Sprint eview Work packages / deliverables Sprint backlog Daily scrum Knowledge model outputs Feedback / Changes equirements Product backlog Sprint backlog Daily scrum Functioning software product Changes / enhancements esource allocation MBCD team Software development team ASEW 2015 MBCD through to system implementation 23

24 Project process enhancements Fully integrated agile development IT 1 IT 2 / Sprint 1 IT 3 / Sprint 2 Sprint 3 Sprint 4 Sprint 5 Integrated MBCD / Software sprint Planning Sprint eview Product backlog Sprint backlog Daily scrum Knowledge model / software products Feedback / changes / enhancements equirements esource allocation MBCD team Software development team ASEW 2015 MBCD through to system implementation 24

25 Project process enhancements Potential modelling enhancements Model-based conceptual design Software development Strategy Strategic Guidance Document documents Guidance element guides Scenario decomposes Vignette Top-Level Need refines Consolidated Need basis of Function decomposes Function System specified by equirement Model software support elements refines equirement Specifies Model software constraints in greater detail Software development environment constraints Specifies Software component documents Documented SME Guidance decomposed by Activity results in refined by Need decomposed by Function efined by Model Software Components, interfaces and links Specifies equirement Model User Stories link to Functions ASEW 2015 MBCD through to system implementation 25

26 MBCD can deliver a robust software system specification and support an Agile Scrum implementation Conclusions The synergies between MBCD and Agile Scrum methods were successfully leveraged in range safety software development Potential further enhancements of the MBCD / Agile approach have been identified ASEW 2015 MBCD through to system implementation 26

27 Acknowledgements ASEW 2015 MBCD through to system implementation 27

28 Questions? ASEW 2015 MBCD through to system implementation 28

29 PO Box 3005 Port Adelaide SA 5015 Tel: support@shoalgroup.com ASEW 2015 MBCD through to system implementation 29