Proposed ONAP Process Improvements
No Modeling Presence
Add Modeling Swim Lane
Add Modeling Artifacts for appropriate milestones to Modeling Swim Lane
MO
Only Item in M0 timeframe is “Open Intent To Participate”
Add “High Level Infomodel Requirements”
M1
Project Planning / Functional Architecture Defined / Architecture Approved
Add “Infomodel Plan Established”
Note: Infomodel Updates Begin
Note: Data/ Data Model Refinements Begin (M1.5)
- Note: Development Commitments for Infomodel Requirements?
M2
Functionality Freeze
Add “Infomodel
Draft”Freeze” (Approval)
Add “Data Model
Draft”Freeze” (Approval)
Note: Feed to Data Dictionary??
M3
API Freeze
Add “Infomodel
Freeze” (Approval)Final”
Add
“Data“Component Data Model
Freeze”Final” (Approval – Design Level Compliance)
M4
Code Freeze
Add “Infomodel Final”
Add “Component Data Model Final”
- Add “API Final”
Kickoff Information Model Requirements for Next Release
RCx
Runtime Compliance
Observations
Establishes and Evolves a Common Model
Project (Component) Team Involvement in Modeling Solution
Governance of Common Model and Corresponding Component Models
- Update possible in M3 and M4 (bug fixes) per exception process
Artifacts
Information Model Artifact Contains
Classes
Relationships with Multiplicity
Important Attributes with Multiplicity
Definitions
Data Types
Feed to Data Dictionary
Tooling - Papyrus with GitHub
Component Data Model Artifacts (Implementation Specific)
Component Data Model
Contains objects, attributes, & relationships (more detail than information model)
Mapping to Information Model
Feed to Data Dictionary?
API Artifacts
API Model
Mapping to Information Model
...
Establishment and Evolution of a Common Model (Model Consistency)
Pivot Toward a Model Driven Design
Improve Data Quality
Establishment and Evolution of a Common Model (Model Consistency)
Pivot Toward a Model Driven Design
Improve Data Quality