National Aeronautics and Space Administration
Robert K. Crain 281.483.0922
1
A Process-based Data Architecture provides an understanding of what information is needed to
effectively execute the enterprise's business processes and provides a framework for effectively
managing the enterprise's information environment. It provides a representation of data artifacts and
data assets that classifies and defines all data entities, their attributes, and associations to facilitate
knowledge of how data is produced, managed, and shared in different contexts of use. The Data
Architecture provides identification, management, interoperability, and integration of information
across business or organizational elements needed to support Product Data Life-cycle Management
goals. It also ensure that data needed by programs and projects (e.g. for milestones, reviews, mission
operations, anomalies or investigations, decisions, and outcomes) are identified and managed to
provide traceability of data used in decision making.
The Data Architecture is the foundation for a solid Model-Based Systems Engineering (MBSE) approach.
A well-defined process-based data architecture will facilitate:
•
•
•
•
•
•
•
Standardization (definitions, concern viewpoints, etc.)
Discovering document based process flaws
Defining process compliance audits
Interoperability and data exchange
Data Integration
Application (Tool) Schema and Methodology development
IT Architecture requirements definition (Applications, platforms, MDM, etc.)
Robert K. Crain 281.483.0922
2
MBSE without a process-based Data Architecture is just a set of
random characters…..
–
–
–
–
–
–
What is MBSE?
Enterprise Architecture Components
10 step process Enterprise Architecture Definition
Tool Agnostic Data Architecture Definition
Data Architecture SE Vee Entity Relational Diagram (ERD)
Data Architecture Wiki (Reference)
Robert K. Crain 281.483.0922
3
MBSE without a process-based Data Architecture is just a set of
random characters…..
M
B
S
E
What is MBSE?
– Four letters that represents….
– Four Words that are comprised of even more letters
•
•
•
•
Model
Based
Systems
Engineering
– Which is represented as an acronym…
Robert K. Crain 281.483.0922
4
• In order for us to understand what MBSE is someone had to
A.
B.
C.
D.
E.
Define letters
Arrange those letters into words
Provide a definition of those words
Combine the words together to provide a specific meaning
Define the term acronym and how it is applied
M odel
B ased
S ystems
E ngineering
Robert K. Crain 281.483.0922
5
So, what is Mfano mifumo ya uhandisi ya msingi (MMUM)???
Model Based Systems Engineering (MBSE) translated into
Swahili.
Because we have the underlying definition of letters and
arranging those letters into words, which have definitions, they
can be translated into other languages.
Robert K. Crain 281.483.0922
6
•
•
•
•
•
•
Modelo de la ingeniería de sistemas basados
Modello base di sistemi di ingegneria
‫نموذج هندسة النظم القائمة‬
Μοντέλο που βασίζεται μηχανικής συστημάτων
基於模型的系統工程
Odelmay Asedbay Ystemssay Engineeringway
All of these examples follow the same underlying
“process” for creating an “architecture” to “model” words
that have meaning.
The same needs to be true with Model Based Systems
Engineering….
Robert K. Crain 281.483.0922
7
A rendering from one language into another
• Once we have defined what MBSE represents we can translate
it into many different “languages”
• The same is true with developing a tool agnostic, process
based Data Architecture
– Once it is defined it can be represented into many different
applications (languages) and translated in tool agnostic representation
for mapping and transformation
Robert K. Crain 281.483.0922
8
• Systems Engineering is Systems Engineering, the process
hasn’t changed significantly throughout the years.
• What is changing is the methodology for implementing the
processes.
Robert K. Crain 281.483.0922
9
• Document-centric
– Implementation of the Systems Engineering process using distributed
documents, often duplicating data
• Model/Data-centric
– Implementation of the Systems Engineering process using distributed
tools/applications, object-oriented, define once use many
A process based, tool agnostic, data architecture is the key to a
creating a sustainable, successful model-based methodology
for implementing the various systems engineering domains.
Robert K. Crain 281.483.0922
10
• Model Based Project Control
• Model Based Engineering
– Model Based Manufacturing and Operations
– Model Based Systems Engineering
– Model Based Design
Robert K. Crain 281.483.0922
11
SECURITY ARCHITECTURE
Architecture
BUSINESS (PROCESS) ARCHITECTURE
Focus
of this
Presentation
DATA ARCHITECTURE
APPLICATION ARCHITECTURE
TECHNOLOGY (IT) ARCHITECTURE
Description
Business
Mission Based Standards and Processes for meeting the Agency Vision
Data
Processed Based Data Model (Objects, Attributes, Associations, Audits)
Application
Enabling tools designed to perform domain specific functions
Technology
IT Networks and Infrastructure
Security
Application and Technology layer built in controls to protect data
Robert K. Crain 281.483.0922
12
Program Mgmt, Systems Engineering, Operations, PDLM, Enterprise Architecture
Number
NPR 2830.1
NPR 7120.9
NPR 7120.9 Handbook
NASA/SP-2010-3403
NASA/SP-2010-3404
NPR 7120.5
NPR 7120.5 Handbook
NPR 7120.7
NPR 7120.8
NPR 9420.1
NPR 7123.1
NPR 7123.1 Handbook
NPR 7150.2
NPR 7500.1
NPR 8000.4
NPR 8705.2
NPR 8705.5
NPR 8705.5 Guidebook
NPR 8705.6
NPR 8820.2
Process/Procedure Title
NASA Enterprise Architecture Procedures
NASA Product Data and Life-Cycle Management (PDLM) for Flight Programs and Projects
NASA PDLM Handbook
Schedule Management Handbook
Work Breakdown Structure (WBS) Handbook
NASA Space Flight Program and Project Management
NASA Space Flight Program and Project Management Handbook
NASA IT and Institutional Infrastructure Program and Project Management Requirements
NASA Research and Technology Program and Project Management Requirements
Budget Formulation
Systems Engineering
NASA Systems Engineering Handbook
NASA Software Engineering Requirements
NASA Technology Commercialization Process
Agency Risk Management Procedure Requirements
Human-Rating Requirements for Space Systems
Probabilistic Risk Assessment (PRA) Procedures
PRA Procedures Guide for NASA Managers and Practitioners
Safety and Mission Assurance (SMA) Audits, Reviews, and Assessments
Facility Project Requirements
Robert K. Crain 281.483.0922
13
•
•
•
•
•
Provides an understanding of what information is needed to effectively execute
the enterprise's business processes and provides a framework for effectively
managing the enterprise's information environment.
Links information behavior (i.e., accessing, using, and sharing data), information
management processes, and information support staff to other aspects of the
enterprise.
Provides a (process-based) representation of data artifacts and data assets that
classifies and defines all data entities, their attributes, and associations to facilitate
knowledge of how data is produced, managed, and shared in different contexts of
use.
Provides identification, management, interoperability, and integration of
information across business or organizational elements needed to support program
PDLM goals.
Ensure data needed by programs and projects (e.g., for milestones, reviews,
mission operations, and anomalies or investigations, decisions, and outcomes) are
identified and managed to provide traceability of data used in decision making.
Robert K. Crain 281.483.0922
14
Focus of this Presentation
Tool Agnostic Data Architecture
2
1
Business/
Process
Architecture
Definition
10
System
Definition
Define
System of
Interest
Architecture
Data
Architecture
Framework
Definition
Program Project Specific Tool/Application Development
4
5
Data Object
Application
Assignment
Application
Schema
Development
8
7
6
Data
Integration
Framework
Definition
Disparate
Data Object
Identification
Application
Methodology
Definition
3
Application
Architecture
Selection
Shared Data Integration Service
9
Technology
Architecture
Development
Robert K. Crain 281.483.0922
15
1- Business Architecture Definition
Based on the position of the system-of-interest within the hierarchy of the overall architecture determine the specific guiding Business
Architecture rules for Systems Engineering and Project Management process requirements. The Program/Project could adopt established
Agency standards, tailored Center standard, tailored Program/Project standards, or decide to create new standards that meet or exceed
the parent standard(s). For Programs/Projects these documents would be included as Applicable Documents in Systems Engineering
Management Plan (SEMP).
2- Data Architecture Framework Definition
Based on the Program/Project Business Architecture definition a Data Architecture “Framework” can be adopted, tailored or developed.
The Data Architecture “Framework” identifies the Data Objects, attributes, and associations (correspondence) applicable to
Program/Project. Existing DAFs can be tailored and expanded to add optional Center/program/project specific attributes and or
associations. Deviations/tailoring to the common model should be documented and well understood so the data can evidentially be
transformed for data exchange, integrated reports, audits, and metrics. Unique program/project specific additions should also be
documented in the Program/Project’s Data Architecture Dictionary. The resulting DAF should be documented/referenced in the in the
Systems Engineering Management Plan (SEMP).
3- Application Architecture Selection
Identify Authoritative Data Repository Application for Data Objects. Applications MUST be able to “expose” data to other Applications for
Data Integration. These applications are typically server-based, not desktop instances. Applications are typically related to a specific
Systems Engineering or Program Management function (i.e. Requirements Management, Risk Management, Schedule Management,
Budget Management, etc.).
4- Data Object to Application Assignment
The identified Data Objects, from the Data Architecture “Framework”, necessary to perform the Project Management and Systems
Engineering functions, per the Business Architecture, should be assigned to their authoritative repository (application). Typically
authoritative data objects reside in only one application.
Robert K. Crain 281.483.0922
16
5- Application Schema Development
Each application needs to incorporate the subset of the Data Architecture “Framework” based on the assignment of Data Objects to that
Authoritative Application. The Program/Project can take liberties with the Data Object names and attribute labels, however the underlining
definition must be maintained. An XML schema for the NASA Data Architecture Framework can be tailored and parsed, based on Program
and application specifications and used to establish the traceable Data Framework.
6- Application Methodology Development
A Methodology, how you implement the process, should be developed and documented for application’s function(s) based on the assigned
data object. In theory, there should not be duplications of implementations, multiple ways of capturing the same data. This methodology
needs to be governed to ensure the application’s model artifacts are consistent.
7- Disparate Data Objects Identification
An analysis of the Applications and their assigned Data Objects will result in the level of data disparity within the program/project. The
Program/Project should document anywhere there is an association between two data objects that are in different, disparate applications
8- Data Integration Framework Definition
The purpose of the Data Integration Framework (DIF) is to perform as middle-ware, which joins the disparate data object to maintain the
structure of the model. The DIF is the back-end Application-to-Application interface. The DIF front-end provides the user interface to record
the associations across data objects/applications and to generate user defined reports and analysis. The Data Integration Framework should
comply with the previously defined Data Architecture Framework to develop a Common Model. This common model will facilitate the
transformation of data from Application-to-Application and generating reports.
9- Technology Architecture Development
The Technology Architecture includes the Information Technology (IT) infrastructure, which includes the Data Integration Framework (DIF).
To be successful the Technology Architecture must have real-time, or near real-time, access to the exposed application data items.
10- Define the System of Interest Architecture
After the Business, Data, Application, and Technology Architectures have been defined the Model-Based Project Management and Systems
Engineering efforts can begin for the System-of-Interest Architecture. It is important for the System-of-interest to be modeled per the
described data architecture and application methodologies. Inter-application data items should be registered in the Data Integration
Framework to extend the data model from one application to the other application(s) within the Technology Architecture.
17
Robert K. Crain 281.483.0922
Modelo de la ingeniería
de sistemas basados
DOORS
基於模型的系統工程
Magic Draw
SysML
‫ن‬Μοντέλο που βασίζεται
μηχανικής συστημάτων
MS Project
Translation
Mapping
xsd
Data Architecture
xml
Odelmay Asedbay
Ystemssay Engineeringway
Cradle
Model Based
Systems Engineering
‫موذج هندسة النظم القائمة‬
Windchill
Robert K. Crain 281.483.0922
18
• Model/Data-centric
– Implementation of the Systems Engineering process using distributed
tools/applications, object-oriented, define once use many
– Based on a process-based Data Architecture
Robert K. Crain 281.483.0922
19
PRACA
You
Organization
Requirements
Support Equipment H/W S/W
Schedule
Results
Verification
Configuration CAD
GMIP
Test Execution
Work Breakdown Structure
Waiver
Facility
Budget
Test Procedure Document
Deviation Variance
Robert K. Crain 281.483.0922
Interfaces
Product Under Test
20
Data Objects
• A data object is a logical cluster of attributes in a data set
that relate to a common business process.
Robert K. Crain 281.483.0922
21
Data Object metadata
– Attributes
–
A quality or characteristic inherent in or associated with a business process
– String
– Fixed-String (16/60/256/etc.)
– Enumeration (Category)
» Single Pick (sp)
» Multiple Pick (mp)
–
Boolean/File
– Date (MM/DD/YYYY)
– Association
• Definition of relationships between Data Objects
– Bi or Uni-Directional semantics
– From/To, Parent/Child hierarchy
– Audits/Metrics
• Measurements of Process Compliance
• Quality of Data
• Measurement of Goals
Robert K. Crain 281.483.0922
22
Data Object Associations (ex. Requirement Data Object )
•
Definition of relationships between Data Objects
Robert K. Crain 281.483.0922
23
Graphical Representation of the Requirement Data Object Association rules.
Robert K. Crain 281.483.0922
24
Used for standardized Life-cycle maturation, Configuration Control levels,
data source identification, attribute formatting, etc.
• Inherited by all Data Objects
Robert K. Crain 281.483.0922
25
Metadata about the Data Object (Requirement example)
• Unique to the Data Object
Robert K. Crain 281.483.0922
26
Measurement, Data Quality, and Process Audits (ex. Requirement Data Object)
Robert K. Crain 281.483.0922
27
Numerous “Rabbit
Holes” to venture
down depending on
stakeholder’s
concern
Verified
By
Requirement Data
Object Peacock Chart
integrated with the
Verification Data
Object Peacock Chart
Data Objects and
Semantics provide
the logic for
navigating the Data
Architecture Model
Robert K. Crain 281.483.0922
28
Standard Systems Engineering Vee process executed
• Left to Right
• Top to Bottom
• Recursive for each Architecture Level
29
Robert K. Crain 281.483.0922
Realized By
SE Data Architecture
Process Data Model
Tracked
For
RESULT
Closed By
Class
Guides
NGO
Refined By
Measured
By
Performs
OBJECTIVE
Modeled By
MOE
Performs
Measured
By
OPERATION
Related
To
Monitored
By
FUNCTION
Basis Of
Analyzed By
Specifies
Controlled By
Allocated
ARCHITECTURE
To
Basis
Of
REQUIREMENT
Verified By
Causes
RISK
Causes
VERIFICATION
Causes
Detailed By
Studied By
CIL
PRACA
CAD
Related
To
Tracked
For
Resolved
By
HAZARD
CONTROL
Related
To
RESULT
Closed By
Closes
ANALYSIS
RESULT
Closes
Performed
During
RESULT
Closed By
Studied By
TBX
Related
To
Studied By
DVO
Generates
FMEA
Closed By
Studied By
SUPPORT
PRODUCT
References
Analyzed By
Assigned
To
Maintained
By
Produces
Built From
Monitored By
TPM
References
ARCHITECTURE
Provides
Specified
By
Basis
Of
Constrained
By
Satisfied By
LCC
Joined Thru
CAPABILITY
Modeled By
Maintained
By
Achieved
By
INTERFACE
Performs
Results In
MOP
MISSION
Manifested
Supported
MISSIONBy
Applicable
O&M
REQUIREMENT
Requires
ASSET
GMIP
SCHEDULE
Inspected By
Generates
Documented By
DOCUMENT
VARIANCE
Deviation/Waiver
Causes
Run During
Related 281.483.0922
To
Robert K. Crain
30
Process Driven
Model-Based Domains
Identify “Mission-Based” Business Processes to derive the Data Architecture.
•
•
•
•
Data Objects
Data Attributes
Data Associations
Audits
Robert K. Crain 281.483.0922
31
Examine Official Process Documents and derive Data Objects, Attributes, and Associations
Systems Engineering
Process
32
Robert K. Crain 281.483.0922
Process Based Data Objects
Associations Identified
Examine Process Based Data Objects and Derive Associations and Semantics
MBSE Approach provides ability to capture and formalize relationships between Data Objects that already exist in “real world” practice.
Robert K. Crain 281.483.0922
33
https://nasa-ice.nasa.gov/confluence/pages/viewpage.action?pageId=9732
Currently Hosted In NASA ICE (Integrated Collaborative Environment)
Robert K. Crain 281.483.0922
34
Detailed Process
Procedures
Data Arch.
Definition
Currently there are 53
defined Data Objects classes
with 70+ defined types
Robert K. Crain 281.483.0922
35
The Data Architecture is the foundation for a solid ModelBased Systems Engineering (MBSE) approach. A well-defined
process-based data architecture will facilitate:
•
•
•
•
•
•
•
•
Standardization (definitions, stakeholder concerns, viewpoints, etc.)
Identification of Document-based process flaws
Process compliance audits
Interoperability and data exchange between applications/tools
Data Integration
Application (Tool) Schema and Methodology development
Definition of IT requirements
More detailed, integrable Data Delivery Requirements (DRDs)
Ontology is tool agnostic and represents standard relationship represented in a
document-centric environment. (Ex. Verifications verify Requirements which specify an
Architecture used to achieve a Mission that is guided by NGOs and Objectives)
Robert K. Crain 281.483.0922
36
BACK-UP
Robert K. Crain 281.483.0922
37
• The purpose of the Model Based Systems Engineering & Integration
Wiki is to:
– Provide an Integrated model for the components of
• NPR 7123.1 – NASA Systems Engineering Processes and Requirements
• NPR 7120.5 – NASA Space Flight Program and Project Management
Requirements
• NPR 7120.9 - NASA Product Data and Life-Cycle Management (PDLM) for Flight
Programs and Projects
– Provide a Tool agnostic, common Architecture Framework used as an
integration point for distributed data
• Definition of Technical data structure
– Data Objects
– Attributes
– Associations
– Provide standardized processes and procedures for implementing Systems
Engineering and Project Control using the defined Data Architecture
– Provide standardized metrics and audits
– Provide a common framework for Data/Configuration Management
Robert K. Crain 281.483.0922
38
Used for standardized Life-cycle maturation, Configuration Control levels,
data source identification, attribute formatting, etc.
• Inherited by all Data Objects
Robert K. Crain 281.483.0922
39
Data Object Associations (ex. Requirement Data Object )
•
Definition of relationships between Data Objects
Robert K. Crain 281.483.0922
40
Graphical Representation of the Requirement Data Object Association rules.
Robert K. Crain 281.483.0922
41
Robert K. Crain 281.483.0922
42
Hyperlink to Data Object
Definition (Attributes,
Associations, Audits, etc.)
Hyperlink to detailed
step-by-step directions to
establish Data
Architecture model
Robert K. Crain 281.483.0922
43
WBS Dictionary
1st Level WBS
WBS
Decomposed
By
2nd Level WBS
Charging Level
Cost Charge
Number
Associated Cost
and Schedule
Controls, basis
of EVM
WBS
Decomposed
By
Decomposed
By
WBS
WBS
Controlled
By
Decomposed
By
Decomposed
By
Decomposed
By
WORK
PACKAGE
WORK
PACKAGE
WORK
PACKAGE
Controlled
By
Controlled
By
COST
SCHEDULE
Robert K. Crain 281.483.0922
COST
44
URL
https://nasa-ice.nasa.gov/confluence/pages/viewpage.action?pageId=9732
Please contact me if you require access
robert.k.crain@nasa.gov
Robert K. Crain 281.483.0922
45