The overall objective for SAVI Version 1.0 is to develop capabilities to a level that the Virtual Integration Process (VIP) could be incorporated with manageable risk in a system development program.
Safety analyses, simple fit, and elementary behavior patterns were primary thrusts for SAVI Version 1.0A and Version 1.0B, but Version 1.0C (AFE 61s2) considers integration of a more complete behavior-based example WBS system and extends behavior analyses to more realistic wheel braking systems development.
Version 1.0C also extends “fit” analysis techniques to include consistency checking for wiring harness design and improved automation in assessing wiring harness anomalies early in the design cycle.
Task 1
Provide model translation and data exchange capabilities for the SAVI VIP that facilitates safety, “fit”, and behavioral information exchange to underpin the architectural analysis of and consistency checking between differing model types and all actors in the VIP. The models should include all types of models for these three capabilities with special emphasis on two-way translation between SysML and AADL architectural models. Data exchange should be based on ISO 10303-239, Product Life Cycle Support (PLCS).
Deliverables
- A revision of the document describing the SAVI DEX structure and methods to integrate data exchange capability within the SAVI MR/DEL, including descriptions of translations to/from the baseline toolsets and the DEX specification language and security practices used to guard against violation of intellectual property concerns of each actor in the VIP.
- A video demonstration of how the SAVI DEL underpins consistency checking and protects sensitive data both internal to the VIP and external to the development process, while facilitating flow of necessary information between actors (OEMs, suppliers, and regulatory agencies).
- An assessment of the demonstration of Share-A-space capability to support the Pin 1 Fit Use Case scenario and its expected capability to support behavioral Use Case demonstrations will be part of the document revision. Any gaps in capability will be identified.
- Use case and scenario description, DARPA translator features list, gap/needs analysis, translator feature development plan (tasks, resources, timeline), a demonstration and report, and (as time and resources allow) a revised SysML-AADL translator that allows verified two-way translation between AADL and SysML models used in the SAVI VIP will also be described in the document revision of subtask a. Any code developed will available to all SAVI participants.
- Continue development of guidance intended to lead to a standard for the SAVI VIP. A list of topics should be created in appendix A that addresses model translation. This appendix should include a summary, along with guidelines for each topic and explanatory notes for each topic. Topics that are to be analyzed during AFE 61s2 should be documented as fully as possible to provide guidance for other users who wish to perform model translation and model exchange.
Task 2
Expand VIP “fit” analysis capabilities to include wiring harness interconnect.
Deliverables
- Wiring harness consistency checking use case and scenario description.
- List of model types.
- Business Object Model (BOM).
- Map of BOM to MoSSEC.
- Wiring harness consistency checking rule, or algorithm.
- Continue development of guidance intended to lead to a standard for the SAVI VIP. A list of topics should be created in appendix C that addresses fit analysis capabilities. This appendix should include a summary, along with guidelines for each topic and explanatory notes for each topic. Topics that are to be analyzed during AFE 61s2 should be documented as fully as possible to provide guidance for other users who wish to perform fit analyses on other models.
Task 3
Expand behavioral consistency checks for the SAVI VIP
Deliverables
- Narrated video demonstration of behavioral analysis capability and consistency checking of the extended WBS (including antiskid/autobraking) using the SAVI VIP.
- A report documenting impacts of increased complexity (reliability of the antiskid system, for example) on consistency checking, on the PSSA, and on the predictions of this added complexity with specific use cases patterned after conventional (hydromechanical) and newer (electromechanical) WBS designs.
- Show the pressure drops in hydraulic power circuits and voltage drops in the hydraulic and electrical power distribution branches and the impact on the PSSA of this added complexity for each of these more complete sets of models.
- Record the transient behavior of the power-up events for both hydraulic and electrical power to the WBS, along with behavior during typical failure conditions to help identify potential controlling software anomalies.
- Record predicted stopping distances for these modeled wheel braking systems and compare these predictions with results from similar WBS implementations or actual measure stopping distances.
- Document methods, procedures, and results of performing the extended WBS behavioral analyses above, including development of any constraint algorithms used to implement the antiskid operation and added interface consistency checks.
- Continue development of guidance intended to lead to a standard for the SAVI VIP. A list of topics should be created in appendix D that addresses behavior characteristics. This appendix should include a summary, along with guidelines for each topic and explanatory notes for each topic. Topics that are to be analyzed during AFE 61s2 should be documented as fully as possible to provide guidance for other users who wish to perform behavioral consistency checks.
Task 4
Manage SAVI Version 1.0C Development
Deliverables
- Video demonstrations, as spelled out within the three primary task statements, will be collected and uploaded to an appropriate internet site to serve the purposes of both the participating members and to publicize selected features of the SAVI approach.
- A plan for ensuring credible demonstration of security during the last phase (2016) of SAVI Version 1.0 development.
- The goal of the outreach effort is to attract at least 3 new members during 2015.