...
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”
- Modeling team has two categories of Modeling team does MODEL PLANNING. The planning develops into “High Level Info-model Requirements”. These High level info-model requirements fall into 3 categories:
- #1: NEW USE CASES - items from the expected Use Cases in the release (Scope of modeling, continuing, introducing, standards updates).
- #2 there : REFINING EXISTING MODEL - There are also Existing high level info-model requirements and the current release is focused on continuing or refining the model. Existing in a component that hasn't made it to the information model. Previously at design build-level that needs to be added into information model. For example, a need might have arisen in development but wasn't formalized. Long-lead, multi-release items might fall into this category. coded previously but no Use Case.
- #3: FORWARD LOOKING WORK - Forward thinking requirement. For example, suppose there were a very large use case/requirement or project that is expected to be worked on and also requirements that we know are comingcome down the pipe, but if no advanced modeling work were done on it, it wouldn't make the current release. Thus, a model might be proposed in advance of the actual use case/requirement.
- Use Case Team (evaluating U/C proposals) present presents their modeling needs. Each of the Use Case teams needs to come to the modeling S/C meetings to present their expected modeling needs and open a dialogue about potential model impacts so that they can be developed.
- Architecture understanding reference model. Modeling S/C members should be aware of any updates to the current release's reference model so that potential can be known.
- PTL- High level release scope from PTLs (understand from ONAP components what updates)
- PTL - Joint PTL sync meeting
M1
Project Planning / Functional Architecture Defined / Architecture Approved
Add “Infomodel Plan Established”
Note: Infomodel Updates Begin / Data Model Refinements Begin (M1.5)
- Note: Development Commitments for Infomodel Requirements?
M2
Functionality Freeze
Add “Infomodel Freeze” (Approval)
Add “Data Model Freeze” (Approval)
Note: Feed to Data Dictionary??
M3
API Freeze
Add “Infomodel Final”
Add “Component Data Model Final” (Approval – Design Level Compliance)
M4
Code Freeze
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
...