MBSE & Verification 2 nd Workshop

1. MBSE & Verification2nd Workshop Christopher Laing 11 April 2017

2. Model-Based Systems Engineering Model-Based Systems Engineering  (INCOSE) is the formalized application of modeling to support system requirements, design, analysis, verification and validation activities beginning in the conceptual design phase and continuing throughout development and later life cycle phases. Model (INCOSE) is an approximation, representation, or idealization of selected aspects of the structure, behavior, operation, or other characteristics of a real-world process, concept, or system

3. Verification ISO 15288: “The purpose of the Verification process is to provide objective evidence that a system or system element fulfils its specified requirements and characteristics” ► “Build the thing right” • Transverse verification occurs throughout project • For every step, we can verify: • That the work has been done correctly • That the work will lead to the right result

4. Purpose of Research • How the application of modelling could produce better transversal verification outcomes? • Better coverage? • Faster with less cost? • Risk and error reduction? • 1st Step: AFIS workshop and literature review to determine: • What can be verified • How it can be verified • How MBSE verification fits into the system development process • 2nd Step: Industrial feedback through AFIS community: • How useful are the techniques? • How and when can they be applied cost-effectively? • How can transverse verification be used to optimize and link these activities

5. Purpose of Presentation • Present a global view of model supported verification from the last 7 years of INCOSE publications (2010-2017) • View encompasses many industries and is not specific to any one company • Solicit your feedback: • Identify new areas of interest • Identify key subjects to explore further

6. 1 MBSE & Verification Needs Problem Space Model Define Stakeholder Requirements Needs Perform System Validation Stakeholder Requirements What Verification Items Black Box System Model Define System Requirements System Requirements Perform System Verification Test Model Structural Architecture Model Functional Architecture Model Define Architecture System ElementRequirements REUSE LIBRARY How Verification Items Perform System Integration Physical Architecture Model Integration Model Domain Model Multiphysical Model MiscView Mech View ELN View S/W View Develop Component Implementation

7. MBSE & Verification 1.1 Verify All Stakeholder Needs are identified Needs 1.1 Verify All Stakeholder Needs are identified 1.2 Verify Stakeholder Reqts are correct Problem Space Model Define Stakeholder Requirements Needs Perform System Validation Stakeholder Requirements 2.1 Verify black box fulfils stakeholder expectations 2.2 Verify System Reqts are correct What 2.3 Verify Reqt Specification Verification Items Black Box System Model Define System Requirements System Requirements Perform System Verification Test Model 6.2 Verify virtual system fulfils System Reqts 3.3; 4.3; 5.3 Verify System Element Reqts are derived correctly 3.5; 4.5 Verify Correctness of Model 2.4 Verify Reqts can be verified correctly Structural Architecture Model Functional Architecture Model Define Architecture 3.1; 4.1; 5.2 Verify Architecture fulfils System Reqts System ElementRequirements REUSE LIBRARY How Verification Items 3.2; 4.2; 5.4 Verify Element Reqt Specification Perform System Integration Physical Architecture Model 6.3 Verify virtual elements fulfils System Element Reqts Integration Model 5.5 Verify System Induced Reqts are managed 3.4; 4.4; 5.6 Verify that elements can be integrated Domain Model Multiphysical Model MiscView Mech View ELN View S/W View 6.1 Reverify previous steps with updated values 5.1 Verify Physical Architecture fulfils stakeholder expectations Develop Component Implementation

8. Ex Stakeholder Needs Definition • Validation 1. Define Stakeholder Requirements System Requirements Definition • Verification • Architecture Defintion • Integration • In your experience: • Are originating needs (emails, verbal correspondence, etc) captured in a database? (circle) yesno • Can model collaboration improve needs elicitation? (circle) 012345 • Which Stakeholder Reqts can be defined with Model-Based methods? (check) • For this activity, which Model-Based techniques are utilized by your organization? • What Non Model-Based methods must be used? (QFD,VOC, etc)? • Implementation Architecture Definition No Improvement Large Improvement • Functional • Performance • Interface • Safety • Constraints • Standards • "Ilities"* • ___________ *“Ilities”: Dependability, Transportability, Storability, Producibility, Maintainability, Disposability, etc

9. 2 1. Define Stakeholder Requirements Stakeholder Needs Definition • Validation System Requirements Definition • Verification Import Originating Needs • Architecture Defintion • Integration • Implementation • Verification Examples: • Model Collaboration: • Stakeholder needs are elicited with models: • Use cases diagrams [3] • Mockups/Previous Project Models [5] • Traceability • Originating needs can be traced to Stakeholder Reqts [1] • Rational for Reqts captured [1] • MOEs are linked to dependent Reqts Needs Stakeholders 1.1 Verify All Stakeholder Needs are identified Problem Space Model 1.2 Verify Stakeholder Reqts are correct Needs Use Cases REUSE LIBRARY MOEs* Stakeholder Requirements Sequence Diagrams Activity Diagrams State Machine Diagrams Previous Models Requirements Capture and Trace Needs, Stakeholder Requirements and MOES Elicit and Analyze Needs *MOE-Measure of Efficiency: “Mission level performance requirements that reflect value to the customer and other stakeholders” [2]

10. Needs 1.2 Verify Stakeholder Reqts are correct 1.1 Verify All Stakeholder Needs are identified Problem Space Model Define Stakeholder Requirements Needs Perform System Validation Stakeholder Requirements What Verification Items Black Box System Model Define System Requirements System Requirements Perform System Verification Test Model Structural Architecture Model Functional Architecture Model Define Architecture Architecture Definition System ElementRequirements REUSE LIBRARY How Verification Items Perform System Integration Physical Architecture Model Integration Model Multiphysical Model Domain Model MiscView Mech View ELN View S/W View Develop Component Implementation

11. 3 Stakeholder Needs Definition • Validation 1. Define Stakeholder Requirements System Requirements Definition • Verification • Architecture Defintion • Integration • Implementation • In your experience: • Are originating needs (emails, verbal correspondence, etc) captured in a database? (circle) yesno • Can model collaboration improve needs elicitation? (circle) 012345 • Which Stakeholder Reqts can be defined with Model-Based methods? (check) • For this activity, which Model-Based techniques are utilized by your organization? • What Non Model-Based methods must be used? (QFD,VOC, etc)? Architecture Definition No Improvement Large Improvement • Functional • Performance • Interface • Safety • Constraints • Standards • "Ilities"* • ___________ *“Ilities”: Dependability, Transportability, Storability, Producibility, Maintainability, Disposability, etc

12. 4 2. Define System Requirements Stakeholder Needs Definition • Validation • Verification • Examples: • Model Collaboration • Walkthrough black box with stakeholders [16] • Traceability • Ensure no gaps between levels [1] • Identify unstable reqts [2] • Identify high impact reqts [2] • Connect Constraints to reqt rationale [2] • Black Box Simulation • Black Box (Behavioral) Modeling [8] • Model-in-the-Loop Testing [15] • Fault Analysis [2] [8] • Verification Planning: • Verification Items [2] • Test Model* [17] System Requirements Definition • Verification Needs • Architecture Defintion • Integration • Implementation Stakeholder Requirements MOEs Stakeholders Needs Use Cases Problem Space Model 2.1 Verify black box fulfils stakeholder expectations 2.2 Verify System Reqts are correct Architecture Definition Activity Diagrams Sequence Diagrams State Machine Diagrams System Use Cases REUSE LIBRARY Verification Items SystemRequirements Black Box System Model 2.4 Verify Reqts can be verified correctly Test Model 2.3 Verify Reqt Specification Scenarios Test Environment Capture and Trace System Requirements Verification Planning Use Case Analysis and Functional Flow Block Diagrams Requirements *Test Model or Model-Based Testing: Model capable of generating test cases (17)

13. Test Model Formalized Scenarios Formalized Requirements Formalized Models Test Model Code Generator Automated Testing Virtual Testing with simulation Test Plans

14. Needs Problem Space Model 2.2 Verify System Reqts are correct Define Stakeholder Requirements Needs Perform System Validation Stakeholder Requirements 2.1 Verify black box fulfils stakeholder expectations What Verification Items Black Box System Model Define System Requirements System Requirements Perform System Verification 2.3 Verify Reqt Specification Test Model Structural Architecture Model Functional Architecture Model Define Architecture 2.4 Verify Reqts can be verified correctly System ElementRequirements REUSE LIBRARY How Verification Items Perform System Integration Physical Architecture Model Integration Model Multiphysical Model Domain Model MiscView Mech View ELN View S/W View Develop Component Implementation

15. 5 Stakeholder Needs Definition • Validation System Requirements Definition • Verification 2. Define System Requirements • Architecture Defintion • Integration • Implementation • In your experience: • Could black box simulation be effective for early verification (Effort vs Return on Investment)? 012345 • Does increasing traceability also increase the effort to manage models: 012345 • Which System Reqts can be defined with Model-Based methods? (check) • For this activity, which Model-Based techniques are utilized by your organization? • What Non Model-Based methods must be used? Not Effective Very Effective Architecture Definition No Increase High Increase • Functional • Performance • Interface • Safety • Constraints • Standards • "Ilities"* • ___________ *“Ilities”: Dependability, Transportability, Storability, Producibility, Maintainability, Disposability, etc

16. 6

17. 7 Verification Brainstorming 1. Define Stakeholder Requirements 2. Define System Requirements • What Model-Based techniques can support: • What Model-Based techniques can support: 2.1 Verify black box fulfils stakeholder expectations 1.1 Verify All Stakeholder Needs are identified 1.2 Verify Stakeholder Reqts are correct 2.2 Verify System Reqts are correct Architecture Definition 2.3 Verify Reqt Specification 2.4 Verify Reqts can be verified correctly

18. Stakeholder Needs Definition • Validation System Requirements Definition • Verification Define Architecture Architecture Defintion • Integration • Implementation Structural Architecture Model Functional Architecture Model OOSEM “Logical Architecture” Physical Architecture Model

19. 3. Define Functional Architecture Ex: Circuit Breaker System Requirement: Protect on over current Performance Requirement: In less than 10ms Circuit Breaker F1: Measure Current F2: Compare F3: Open Electrical Network Electrical Network Functional Reqt 3 Performance Reqt: In less than 2ms Functional Reqt 2 Performance Reqt: In less than 5ms Functional Reqt 1 Performance Reqt: In less than 3ms

20. 8 3. Define Functional Architecture Stakeholder Needs Definition • Validation System Requirements Definition • Verification • Verification • Examples: • Executable Architecture • Verify functional and dysfunctional flow [7] [8] [9] • Verify external interfaces [20] • Verify virtual HMI* [24] • Traceability • Trace links between Performance Reqts, Functional Reqts, and Constraints [9] • Integration Planning • Creation of verification items for each System Element Reqt [1] • Create integration schedule in Integration Model [21] • Model Checking • Formal Methods [26] Needs Architecture Defintion • Integration • Implementation Stakeholder Requirements System Use Cases SystemRequirements Black Box System Model 3.1 Verify Functinal Architecture fulfils System Reqts Architecture Definition 3.5 Verify Correctness of Model 3.3 Verify System Element Reqts are derived correctly Functions REUSE LIBRARY Functions Functions Functions System ElementRequirements Verification Items Functions Functions Functions Interfaces Integration Model 3.4 Verify that elements can be integrated Functional Architecture Model 3.2 Verify Element Reqt Specification Functions Requirements Functional Blocks Capture and Trace System Element Requirements Integration Planning Functional Decomposition *HMI – Human Machine Interface (How a user interacts with the system of interest)

21. 7. Integration – Integration Model • Rational for useage: • Project Management • Improved Scheduling • Teams share information • Result Management • Automatic documentation [21] A. Salado, “5.5. 2 Efficient and Effective Systems Integration and Verification Planning Using a Model-Centric Environment,” in INCOSE International Symposium, 2013, vol. 23, pp. 1159–1173.

22. Needs Problem Space Model Define Stakeholder Requirements Needs Perform System Validation Stakeholder Requirements What Verification Items 3.1 Verify Functinal Architecture fulfils System Reqts Black Box System Model Define System Requirements System Requirements Perform System Verification Test Model 3.5 Verify Correctness of Model 3.3 Verify System Element Reqts are derived correctly Structural Architecture Model Functional Architecture Model Define Architecture Architecture Definition System ElementRequirements REUSE LIBRARY How Verification Items 3.2 Verify Element Reqt Specification Perform System Integration Physical Architecture Model Integration Model 3.4 Verify that elements can be integrated Multiphysical Model Domain Model MiscView Mech View ELN View S/W View Develop Component Implementation

23. 9 Stakeholder Needs Definition • Validation 3. Define Functional Architecture System Requirements Definition • Verification Architecture Defintion • Integration • In your experience: • Could functional architecture simulation be effective for early verification (Effort vs Return on Investment)? 012345 • Is Model Checking a value adding activity? (circle) 012345 • Which reqts are refined during the decomposition of the functional architecture? (Check) • For this activity, which Model-Based techniques are utilized by your organization? • What Non Model-Based methods must be used? • Implementation Not Effective Very Effective Low ROI High ROI • Functional • Performance • Interface • Safety • Constraints • Standards • "Ilities"* • ___________ *“Ilities”: Dependability, Transportability, Storability, Producibility, Maintainability, Disposability, etc

24. 4. Define Structural Architecture Ex: Circuit Breaker Functional Reqt 1 Performance Reqt: In less than 3ms Functional Reqt 2 Performance Reqt: In less than 5ms Functional Reqt 3 Performance Reqt: In less than 2ms Sub System 2 Sub System 1 I sample Electrical Network Electrical Network Circuit Breaker

25. Ex: Parameter* Analysis Reqt: Electrical resistance must be less than .2 mΩ Electric Network <<Constraint>> Total Resistance =function of (A,V,T,X) A Current Sub Systems Sub Systems X V Other Constraints Voltage T Physical Environment Temperature *Parameter - A numerical or other measurable factor forming one of a set that defines a system or sets the conditions of its operation (Oxford Dictionary)

26. 10 4. Define Structural Architecture Stakeholder Needs Definition • Validation System Requirements Definition • Verification • Verification • Examples: • Executable Architecture • Verify functional and dysfunctional flow [9] [8] [7] • Verify Interfaces • Verify Global Performance Values (MOEs) [7] • Traceability • Manage requirement specification to structural elements • Integration Planning • Creation of verification items for each System Element Reqt [1] • Create integration schedule in Integration Model [21] • Model Checking • Formal Methods [26] Needs Architecture Defintion • Integration • Implementation Functions Functions Stakeholder Requirements Functions Functions Functions Functions Functions Interfaces Functional Architecture Model SystemRequirements 4.1 Verify Structural Architecture fulfils System Reqts 4.5 Verify Correctness of Model Architecture Definition 4.3 Verify System Element Reqts are derived correctly Functions Subsystem Functions REUSE LIBRARY System ElementRequirements Verification Items Subsystem Interfaces Integration Model 4.4 Verify that elements can be integrated Structural Architecture Model 4.2 Verify Element Reqt Specification Requirements Structural Blocks Capture and Trace System Element Requirements Integration Planning Logical Allocation

27. 4. Define Structural Architecture Needs Problem Space Model Define Stakeholder Requirements Needs Perform System Validation Stakeholder Requirements 4.1 Verify Structural Architecture fulfils System Reqts What Verification Items Black Box System Model Define System Requirements System Requirements Perform System Verification Test Model 4.5 Verify Correctness of Model 4.3 Verify System Element Reqts are derived correctly Structural Architecture Model Functional Architecture Model Define Architecture Architecture Definition System ElementRequirements REUSE LIBRARY How Verification Items 4.2 Verify Element Reqt Specification Perform System Integration Physical Architecture Model 4.4 Verify that elements can be integrated Integration Model Multiphysical Model Domain Model MiscView Mech View ELN View S/W View Develop Component Implementation

28. 11 Stakeholder Needs Definition • Validation 4. Define Structural Architecture System Requirements Definition • Verification Architecture Defintion • Integration • Implementation • In your experience: • Could structural architecture simulation be effective for early verification (Effort vs Return on Investment)? (circle) 012345 • Could parameter analysis be effective for early verification (Effort vs Return on Investment)? (circle) 012345 • Which types of reqts can be refined with a structural architecture model? (Check) • For this activity, which Model-Based techniques are utilized by your organization? • What Non Model-Based methods must be used? Not Effective Very Effective Not Effective Very Effective • Functional • Performance • Interface • Safety • Constraints • Standards • "Ilities"* • ___________ *“Ilities”: Dependability, Transportability, Storability, Producibility, Maintainability, Disposability, etc

29. 12 Verification Brainstorming 3. Define Functional Architecture 4. Define Structural Architecture • What Model-Based techniques can support: • What Model-Based techniques can support: 3.1 Verify Functinal Architecture fulfils System Reqts 4.1 Verify Structural Architecture fulfils System Reqts 4.2 Verify Element Reqt Specification 3.2 Verify Element Reqt Specification 4.3 Verify System Element Reqts are derived correctly 3.3 Verify System Element Reqts are derived correctly 3.4 Verify that elements can be integrated 4.4 Verify that elements can be integrated 3.5 Verify Correctness of Model 4.5 Verify Correctness of Model

30. Ex: Circuit Breaker Physical Architecture Functional Reqt 1 Performance Reqt: In less than 3ms Functional Reqt 2 Performance Reqt: In less than 5ms Functional Reqt 3 Performance Reqt: In less than 2ms Electronic Protection unit Electronic Current sensor I sample Electrical Network Electrical Network Circuit Breaker Induced Reqt 1 Temp<70C Induced Reqt 2 125A MAX Induced Reqt 3 10V MAX Induced Reqt 4 125A MAX

31. 13 5. Define Physical Architecture Stakeholder Needs Definition • Validation • Verification • Example: • Model Collaboration • Architecture viewpoints provide means for stakeholder and domain collaboration [2] • Executable Architecture • Verification of MOEs[7] • Update previous models with data from physical components [7] • Traceability • Management of induced functional requirements [10] • Integration Planning • Creation of verification items for each System Element Reqt [1] • Create integration schedule in Integration Model [21] System Requirements Definition • Verification Needs Architecture Defintion • Integration Functions Logical Block • Implementation Functions Stakeholder Requirements Stakeholders Logical Block Interfaces 5.1 Verify Physical Architecture fulfils stakeholder expectations Structural Architecture Model SystemRequirements 5.2 Verify Physical Architecture fulfils System Reqts Architecture Definition 5.3 Verify System Element Reqts are derived correctly Physical Architecture Model Functions REUSE LIBRARY Functions Functions Physical Block System ElementRequirements Verification Items Functions Functions Functions Interfaces Integration Model 5.4 Verify Element Reqt Specification 5.6 Verify that elements can be integrated 5.5 Verify System Induced Reqts are managed Physcial Blocks Mech View ELN View S/W View MiscView Architecture Views Requirements Capture and Trace System Element Requirements Integration Planning Technological Choices

32. 5. Define Physical Architecture Needs Problem Space Model Define Stakeholder Requirements Needs Perform System Validation Stakeholder Requirements What Verification Items Black Box System Model Define System Requirements System Requirements Perform System Verification 5.2 Verify Physical Architecture fulfils System Reqts Test Model 5.3 Verify System Element Reqts are derived correctly 5.1 Verify Physical Architecture fulfils stakeholder expectations Structural Architecture Model Functional Architecture Model Define Architecture System ElementRequirements 5.4 Verify Element Reqt Specification REUSE LIBRARY How Verification Items Perform System Integration Physical Architecture Model Integration Model 5.5 Verify System Induced Reqts are managed 5.6 Verify that elements can be integrated Multiphysical Model Domain Model MiscView Mech View ELN View S/W View Develop Component Implementation

33. 14 Stakeholder Needs Definition • Validation 5. Define Physical Architecture System Requirements Definition • Verification Architecture Defintion • Integration • In your experience: • Is a single, up-to-date architecture model sufficient for all domain engineering comunication. (Circle) 012345 • Could parameter analysis performed with information supplied from domain engineers be effective for early verification (Effort vs Return on Investment)? (circle) 012345 • Which types of reqts could be suitable for early verification with a physical architecture model? (Check) • For this activity, which Model-Based techniques are utilized by your organization? • What Non Model-Based methods must be used? • Implementation 0% Sufficient 100% Sufficient Not Effective Very Effective • Functional • Performance • Interface • Safety • Constraints • Standards • "Ilities"* • ___________ *“Ilities”: Dependability, Transportability, Storability, Producibility, Maintainability, Disposability, etc

34. 15 6. Domain Modeling Stakeholder Needs Definition • Validation System Requirements Definition • Verification Physical Architecture Model Needs Architecture Defintion • Integration • Verification • Examples: • Model Updates • Update architecture with more accurate data/test results [7] • Multiphysics Modeling • Virtually verify System Requirements • Hardware/Software co-design [27] • Cyber-Physcial Systems [25] • Physical Systems [25] • Domain Model • Verify against System Element Requirements Functions • Implementation Functions Functions Physical Constituent Part Stakeholder Requirements Functions Functions Functions Interfaces 6.1 Reverify previous steps with updated values SystemRequirements 6.2 Verify virtual system fulfils System Reqts Architecture Definition Multiphysics Model REUSE LIBRARY System ElementRequirements Domain Model Domain Modeling 6.3 Verify virtual elements fulfils System Element Reqts Previous Models Trace System Element Requirements Modeling of physical systems and components

35. 6. Domain Modeling Needs Problem Space Model Define Stakeholder Requirements Needs Perform System Validation Stakeholder Requirements What Verification Items Black Box System Model Define System Requirements System Requirements Perform System Verification Test Model 6.2 Verify virtual system fulfils System Reqts Structural Architecture Model Functional Architecture Model Define Architecture Architecture Definition System ElementRequirements REUSE LIBRARY How Verification Items Perform System Integration Physical Architecture Model 6.3 Verify virtual elements fulfils System Element Reqts Integration Model Multiphysical Model Domain Model MiscView Mech View ELN View S/W View 6.1 Reverify previous steps with updated values Develop Component Implementation

36. 16 6. Domain Modeling Stakeholder Needs Definition • Validation System Requirements Definition • Verification Architecture Defintion • Integration • In your experience: • Which types of models are utilized? (circle) MultiphysicsDomain _________ _________ • What level of virtual verification is necessary before going to implementation phase (Verified percent of Functional, Performance, and Constraint reqts)? (Circle)012345 • Which types of reqts could be suitable for virtual verification by domain modeling? (Check) • For this activity, which Model-Based techniques are utilized by your organization? • What Non Model-Based methods must be used? • Implementation 100% Verified 0% Verified • Functional • Performance • Interface • Safety • Constraints • Standards • "Ilities"* • ___________ *“Ilities”: Dependability, Transportability, Storability, Producibility, Maintainability, Disposability, etc

37. Verification Brainstorming 17 5. Define Physical Architecture 6. Domain Modeling • What Model-Based techniques can support: • What Model-Based techniques can support: 5.1 Verify Physical Architecture fulfils stakeholder expectations 6.2 Verify virtual system fulfils System Reqts 6.3 Verify virtual elements fulfils System Element Reqts 5.2 Verify Physical Architecture fulfils System Reqts 5.3 Verify System Element Reqts are derived correctly 5.4 Verify Element Reqt Specification 5.5 Verify System Induced Reqts are managed 5.6 Verify that elements can be integrated

38. 18 • Verification • Examples: • Test model [17] • Automatic test generation • Automated testing • Simulated or real environment • Increase coverage (Test all scenarios) • Reuse of tests [22] • Documentation • Management of results [21] • Automatic output for compliance documentation [23] • Integration Model • Automatic generation of test results [21] • Share up-to-date data between teams [21] • Management of open items [21] • Reuse of tests, procedures, or scripts from common projects [22] Stakeholder Needs Definition • Validation 7. Perform Integration & 8. Perform Verification System Requirements Definition Verification Architecture Defintion Integration Needs 8.1 Verify that Verification has been performed correctly • Implementation Stakeholder Requirements Black Box System Model SystemRequiremens Verification Items Perform System Verification Test Model Architecture Definition Verification REUSE LIBRARY System ElementRequirements Verification Items Perform System Integration 7.1 Verify that Integration has been performed correctly Integration Model* Tests Integrate

39. 8. Verification - Test Reuse Define System Requirements Black Box Testing* Test Model Code Generation Compare Result Requirement Specification Hardware-in-the-Loop Testing Test Scripts Verification *Or Model-in-the-Loop testing

40. 19 Stakeholder Needs Definition • Validation 8. Perform Verification 7. Perform Integration System Requirements Definition Verification Architecture Defintion Integration • In your experience: • For this activity, which Model-Based techniques are utilized by your organization? • What Non Model-Based methods must be used? • In your experience: • For this activity, which Model-Based techniques are utilized by your organization? • What Non Model-Based methods must be used? • Implementation Verification Brainstorming • What Model-Based techniques can support: • What Model-Based techniques can support: 8.1 Verify that Verification has been performed correctly 7.1 Verify that Integration has been performed correctly

41. 20 Stakeholder Needs Definition • Validation System Requirements Definition • Verification • Architecture Defintion • Integration • Implementation MBSE & Verification 2nd Workshop April 11, 2017 Name:________________________________________ Company:_____________________________________ Function:______________________________________ Email:_________________________________________ Page 41

42. Thank you for your participation. Christopher Laing 11 April 2017

43. References [1] N. Kass and J. Kolozs, “Getting Started with MBSE in Product Development,” INCOSE Int. Symp., vol. 26, no. 1, pp. 526–541, Jul. 2016. [2] S. Friedenthal, A. Moore, and R. Steiner, A Practical Guide to SysML: The Systems Modeling Language. Morgan Kaufmann, 2014. [3] M. Waite and P. Logan, “Model based user needs analysis,” in Systems Engineering and Test and Evaluation Conference (SETE2011), Canberra, 2011, vol. 7. [4] S. R. Hirshorn, L. D. Voss, and L. K. Bromley, “NASA Systems Engineering Handbook,” Feb. 2017. [5] B. Stalsberg and G. Muller, “Increasing the value of model-assisted communication: Modeling for understanding, exploration and verification in production line design projects,” in Proceedings of the INCOSE, 2014. [6] P. Petrinca, M. Gammaldi, and L. Tirone, “5.5. 1 A SysML-based Approach for the Specification of Complex Systems,” in INCOSE International Symposium, 2012, vol. 22, pp. 713–786. [7] E. A. Bjorkman, S. Sarkani, and T. A. Mazzuchi, “Using model-based systems engineering as a framework for improving test and evaluation activities,” Syst. Eng., vol. 16, no. 3, pp. 346–362, 2013. [8] C. Seidner, J.-P. Lerat, and O. H. Roux, “5.4. 1 Simulation and Verification of [Dys] functional Behavior Models: Model Checking for SE,” in INCOSE International Symposium, 2010, vol. 20, pp. 681–693. [9] Y. Bijan, J. Yu, H. Graves, J. Stracener, and T. Woods, “6.6. 1 Using MBSE with SysML Parametrics to Perform Requirements Analysis,” in INCOSE International Symposium, 2011, vol. 21, pp. 769–782. [10] F. Caron, “6.5. 1 A collaborative process based on systems engineering and mechatronics methods,” in INCOSE International Symposium, 2012, vol. 22, pp. 829–849. [11] F. Caron, “Leveraging tradeoff, bridging the gap among disciplines,” in INCOSE International Symposium, 2016, vol. 26, pp. 2407–2428. [12] G. Bleakley, A. Lapping, and A. Whitfield, “6.6. 2 Determining the right solution using SysML and model based systems engineering (MBSE) for trade studies,” in INCOSE International Symposium, 2011, vol. 21, pp. 783–795. [13] D. D. Walden, G. J. Roedler, K. Forsberg, R. D. Hamelin, and T. M. Shortell, Systems engineering handbook: A guide for system life cycle processes and activities. 2015. [14] “System Engineering Fundamentals,” DEFENSE ACQUISITION UNIV FT BELVOIR VA, DEFENSE ACQUISITION UNIV FT BELVOIR VA, Jan. 2001. [15] H. Shokry and M. Hinchey, “Model-Based Verification of Embedded Software.,” IEEE Comput., vol. 42, no. 4, pp. 53–59, 2009. [16] P. Chabout, “Personal Interview,” 27-Mar-2017. [17] J. Tretmans, F. Prester, P. Helle, and W. Schamai, “Model-Based Testing 2010: Short Abstracts,” Electron. Notes Theor. Comput. Sci., vol. 264, no. 3, pp. 85–99, 2010. [18] G. J. Roedler and C. Jones, “Technical Measurement. A Collaborative Project of PSM, INCOSE, and Industry,” Dec. 2005. [19] L. Murphy and P. Collopy, “A work-centered perspective on research needs for systems engineering with models,” Procedia Comput. Sci., vol. 8, pp. 315–320, 2012. [20] R. S. Carson and B. J. Sheeley, “2.5. 1 Functional Architecture as the Core of Model-Based Systems Engineering,” in INCOSE International Symposium, 2013, vol. 23, pp. 29–45. [21] A. Salado, “5.5. 2 Efficient and Effective Systems Integration and Verification Planning Using a Model-Centric Environment,” in INCOSE International Symposium, 2013, vol. 23, pp. 1159– 1173. [22] D. Cook and W. D. Schindel, “Utilizing MBSE Patterns to Accelerate System Verification,” in INCOSE International Symposium, 2015, vol. 25, pp. 1085–1100. [23] J. Dean, C. Henderson, and J. Gardner, “Model-Based Systems Engineering as an Enabler for Regulatory Design Compliance,” in INCOSE International Symposium, 2012, vol. 22, pp. 2266– 2278. [24] H. Gopinathan, A. Tocci, F. Ciambra, and D. Frisoni, “3.6.1 Rapid prototyping and validation of Human factors model in a Model Based Naval Systems Engineering Application,” INCOSE Int. Symp., vol. 22, no. 1, pp. 448–460, Jul. 2012. [25] W. Schamai, P. Helle, N. Albarello, L. Buffoni, and P. Fritzson, “Towards the Automation of Model‐Based Design Verification,” INCOSE Int. Symp., vol. 26, no. 1, pp. 585–599, Jul. 2016. [26 ]C. Baier, J.-P. Katoen, and K. G. Larsen, Principles of Model Checking. MIT Press, 2008. [27] J. Teich, “Hardware/software codesign: The past, the present, and predicting the future,” Proc. IEEE, vol. 100, no. SpecialCentennial Issue, pp. 1411–1430, 2012.

44. Appendix

45. EX: As-is and To-be Models To-be As-is S. Friedenthal, A. Moore, and R. Steiner, A Practical Guide to SysML: The Systems Modeling Language. Morgan Kaufmann, 2014. And Existing product mockups or virtual models

46. Black Box (Behavioral) Model Stakeholder Needs Definition • Validation System Requirements Definition • Verification • Architecture Defintion • Integration • Implementation Time Specification Functions State Description C. Seidner, J.-P. Lerat, and O. H. Roux, “5.4. 1 Simulation and Verification of [Dys] functional Behavior Models: Model Checking for SE,” in INCOSE International Symposium, 2010, vol. 20, pp. 681–693.

47. S. Friedenthal, A. Moore, and R. Steiner, A Practical Guide to SysML: The Systems Modeling Language. Morgan Kaufmann, 2014.

48. EX: Verify expected values of Global Performance [7] Requirement: Plane must loiter for 6 hours Values in System Model Analysis Architecture Definition Performance requirement [9] Y. Bijan, J. Yu, H. Graves, J. Stracener, and T. Woods, “6.6. 1 Using MBSE with SysML Parametrics to Perform Requirements Analysis,” in INCOSE International Symposium, 2011, vol. 21, pp. 769–782.

49. EX: Management of TPMs Stakeholder Needs Definition • Validation System Requirements Definition • Verification Architecture Defintion • Integration • Implementation Architecture Definition [7] E. A. Bjorkman, S. Sarkani, and T. A. Mazzuchi, “Using model-based systems engineering as a framework for improving test and evaluation activities,” Syst. Eng., vol. 16, no. 3, pp. 346–362, 2013.

50. Ex: MOE, MOP, TPM MOE Customer Wants <5 L/100km MOPs Total Weight Drag Engine Trade-offs - System Efficiency Emissions TPMs Power Trade-offs – System Elements