Verification and Validation (V&V) of System Behavior Specifications
Systems Engineering and Systems Management Transformation
Report Number: SERC-2018-TR-116
Publication Date: 2018-10-31
Project: Verification and Validation (V&V) of System Behavior Specifications
Dr. Kristin Giammarco
Dr. Mark Blackburn
This technical report summarizes the accomplishments for Research Task RT-176 – Verification and Validation (V&V) of System Behavior Specifications.
The NAVAIR workforce has a need for Model Centric Systems Engineering (MCSE) methods, processes and tools (MPTs) capable of assessing the goodness of system behavior specifications and other requirements earlier in the lifecycle of a system. In particular, the NAVAIR Systems Engineering Transformation (SET) initiative aims to leverage and extend existing research in the area of MPTs for performing early V&V of requirements and architecture models managed within its organization, and to educate its workforce in the use of automated tools for conducting early and continuous V&V across the entire lifecycle. Several Unmanned Aerial Vehicle (UAV) system models have been developed for use as a case study to test new and improved MPTs that have been developed as a result of this task. These MPTs are expected to apply to other systems in many domains throughout DOD and other government agencies.
The objectives of this work are aligned to NAVAIR SET tasks as follows:
Model-based V&V Demo (Task Lead: Kristin Giammarco)
• Formalize UAV behavior specifications into MBSE architecture tool(s)
– using Monterey Phoenix for comprehensive use case scenario generation
– Core Value Proposition: Manual drawing of a limited set of use cases is replaced with automatic and comprehensive scenario generation, enabling humans to spend more time on requirements analysis and V&V tasks that cannot be automated. Correction of errors in system behavior is then done much earlier.
• Demonstrate use of the UAV behavior model for early V&V analysis of requirements
– using MP to expose positive and negative system behaviors permitted by the design
– Core Value Proposition: Requirements gaps are identified and fixed early (before contracting), through inspection of a comprehensive set of use case scenarios.
• Formalize patterns of common design flaws or other model properties
– using MP event grammar to store system behavior templates
– Core Value Propositions: Save money by eliminating error-prone, labor-intensive, and expensive manual checking, and provide specification for testing contracted models for presence or absence of wanted and unwanted system behaviors discovered during early model-based V&V.
Training Content Development and Delivery (Task Lead: Ron Carlson)
The mission of this task is to create a full modeling methodology training curriculum. Training materials were developed to teach the NAVAIR workforce the necessary skills to perform in a model centric environment.
The goals of this task were to create an acquisition workforce transformed to understand and value model-based methods as well as be trained in model-based collaboration and technical review methods.
The objectives of this task were to create a series of classes and workshops that will be available as needed by the workforce.
Specific tasks for FY18 included:
1. Creation of a workshop that will serve as a kick-off for a program office to start a program as a model based project. This workshop will provide an overview of the processes, methods and tools needed in order to create a model based acquisition program. This workshop will cover the program from conception to approximately source selection.
2. Creation of course objectives for three courses:
a. Basics of SysML. A course on the basics of SysML.
b. Intermediate SysML. A course that will introduce how to develop models using SysML and MagicDraw Cameo.
c. Advanced SysML. A course that goes further than the basics of SysML and delves deeper into the use of the Cameo tool to create architectures.
3. Creation of the Basics of SysML course.
Coaching & Mentoring (Task Lead: Kristin Giammarco)
• Create a catalog of typical architecture model views for behavior containing good practices (patterns*), poor practices (anti-patterns†), and pattern / anti-pattern examples.
– See Appendix E for this catalog.
• Provide ongoing mentoring and coaching support as needed on pilot projects.