1 min read

Abstract: Creating a Conceptual Data Model and Data Storage Plan

Abstract: Creating a Conceptual Data Model and Data Storage Plan

Abstract: "The Foundation for Digital Engineering: Creating a Conceptual Data Model (CDM) and Data Storage Plan (DSP)" discusses the crucial components of Digital Engineering (DE) – the Conceptual Data Model (CDM) and the Data Storage Plan (DSP). The CDM serves as a high-level data plan, illustrating data types, locations, and relationships, while the DSP builds upon it, defining numbering, naming, and labeling conventions for generating desired output products. The document outlines a structured approach for designing CDM and DSP to support Lifecycle Modeling Language (LML) and Innoslate-based DE efforts, which can be adapted to other modeling languages and tools.

The CDM development process involves five key steps: identifying data scope, data elements, data element classes, relationships, and project boundaries. It emphasizes the importance of clear boundaries and consistency in representation.

Similarly, the DSP encompasses documentation for data entry, data extraction, and schema modifications, providing a comprehensive guide for interacting with the digital engineering environment. It's structured around logical subsets of CDM data and ensures data consistency for generating output products.

The DSP development process involves identifying desired output products, establishing conventions for filtering, determining relationship targets, revisiting the CDM, and documenting output methods. These steps ensure that the DSP aligns with the intended DE goals.

The whitepaper stresses the need for periodic review and revision of CDM and DSP, particularly when data scope changes, to maintain data integrity. It advises creating prototypes to validate the DSP's effectiveness, as even minor changes can impact output products.

In conclusion, DE relies on well-designed and verified environments, with CDM and DSP playing critical roles in maintaining data integrity and facilitating the availability of output products.

Read the Whitepaper

 

Rethinking Requirements Derivation: Part 2

Rethinking Requirements Derivation: Part 2

By John Fitch, for Project Performance International (PPI) [Fitch, John. “Rethinking Requirements Derivation: Part 2.” PPI Systems Engineering...

Read More
Rethinking Requirements Derivation: Part 1

Rethinking Requirements Derivation: Part 1

By John Fitch, for Project Performance International (PPI) [Fitch, John. “Rethinking Requirements Derivation: Part 1.” PPI Systems Engineering...

Read More
MBSE: Alive & Well

MBSE: Alive & Well

This blog is in response to a Reddit post by Rhedogian, “Change My View: Model-Based Systems Engineering in 2024 is at best overhyped, or is at worst...

Read More