Criteria for Evaluating a Software Systems Model

This study paper addresses questions frequently asked by organizations transitioning to digital engineering. These organizations are involved in the acquisition or development of large-scale systems that integrate hardware, software, and human-executed subsystems. Their questions pertain to the development, analysis, acquisition, review, and validation of models for these systems and delivering digital artifacts. These artifacts form a “digital thread” – an interconnected chain of models that covers all lifecycle phases. The digital thread serves as basis for system analysis, implementation, integration, verification, validation, accreditation and deployment of product systems. The organizations that face the challenges of transition include government acquisition entities, prime contractors, suppliers, and qualification and accreditation authorities.

Digital engineering for physical aspects of systems utilizes computer-aided design, engineering, and manufacturing tools. Use of such digital tools has demonstrated significant value across all industries for many years. Achieving similar success in systems where hardware-software integration is predominant, known as cyber-physical systems (CPS), remains challenging. The development of such systems has faced difficulties in creating and effectively using model-based engineering artifacts. The specific questions we hear include:

• Why do we receive models from suppliers that don’t really address our acquisition needs?
• How do we create and deliver models that satisfy our business drivers?
• How do we create models for CPS that provide analytic results in the same way that models of purely physical systems support analysis?
• How can we use models to support early lifecycle decision-making or tradeoffs in the areas of functionality, safety and security?