Nicholas J. Di Liberto 20 June 2011 Integrating MBSE into a Multi-Disciplinary Engineering Environment: A Test Engineering Perspective Nicholas J. Di Liberto 20 June 2011

MBSE and Test Provides Early Confidence in Test Approach Requirements Design Integrate Test Test bookends the program Starts with determining how the requirements will be evaluated Ends with evaluating the requirement to verify the system design and implementation Model driven engineering helps reduce risk Test program can be dynamically updated as the design matures (both at the system and lower levels) Using performance/functional design models, test approaches can be evaluated prior to hardware availability

A Good Test Approach Shows Total Impact of Any Change Traceability There should be a reason for everything in a test approach Requirements, integration steps, test environment should all trace back to a customer need/requirement Ability to be understood by many different stakeholders There are many stakeholders on a program, each with their own wants out of the tests Program Office worries about cost and schedule System Architects and System IT&E, worry about technical compliance Customers worry about system compliance and verification Being able to provide answers to everyone is a daunting task Especially trying to sync all those documents Need to coordinate with Fred Simpson, to make sure this consistent with current I&T thoughts.

Model Driven Test Links Requirements, Design, Performance and Back Test Design Models Adding to the system descriptive models… Test Flows Test Set/Environments Test Procedures Using the system model as the foundation Performance/Functional Modeling Utilizing existing design models to… Determine system behavior Understand interfaces Red line test procedures Traceability Tracing those elements back to the requirements, test cases, and use cases

Obstacles to Model Driven Testing Can Be Overcome Test Model System Design SysML Software Design UML Hardware Models ADS ModSim System Performance Model Matlab Simulink, Excel Requirement Model Doors Every discipline has it own set of tools Being able to leverage them in test is difficult, but achievable Managing the model requires a disciplined program Responsibilities, and ownership need to be developed early, and maintained throughout the program life cycle

As systems get more complex, test follows suit Model Based Test Approaches for a Program Reduces Risk and Increases Confidence As systems get more complex, test follows suit By using already developed models and adding to them, the test approach can adapt with the system design System and low level design models are increasing in fidelity Allowing for them to stand in for the hardware Every element in a test approach can be traced back to a “why”… a requirement Providing rational for the need for each part Providing greater visibility to see the impact of any change