Page History

...

• M1

  • Modeling team The info-model plan is established. The model planning follows a template that is worked. For example in R6 (Frankfurt) it was here: ONAP R6 Modeling High Level Requirements.
    • #1: MODELING REQUIREMENTS - A description of the modeling requirements are given in more detail.
    • #2: Use Cases Relevance USE CASE RELEVANCE - The relevance use cases are identified and Use Case teams can give more detailed explanation for use case requirements and how they tie to the high-level requirements. This allows for experts in Info-model team to identify what fields of existing info model could be enhanced and become aware of where the impacts are. 
    • #3: Impacted Projects IMPACTED PROJECTS - The impacted projects (e.g. SO, VID, SDC etc) are identified and how they tie to the high level modeling requirements
    • #4: Overlapping proposals OVERLAPPING PROPOSALS - Overlapping proposals from different use cases or forward looking work (FLW) are identified.
    • #5: Model Reuse MODEL REUSE - During this time, overlap from different proposals that are evaluated can also lead to identifying where model reuse can occur.
    • #6: Owner OWNER - The owner(s) for the item are identified
    • #7 Priority PRIORITY - A priority is identified for the info model requirements. A suggested High/Medium/Low is sufficient at this stage.
    • #8 Lower priority LOWER PRIORITY - Lower priority requirements are generally considered as "nice to haves".
    • #8 Documentation after implemented DOCUMENTATION AFTER IMPLEMENTATION - When the model plan is established, modeling requirements documentation after implemented can be worked on.
    • #9 FORWARD LOOKING WORK (FLW) - FLW is another class of requirements which are intended to recognize future needs. This is separate from the ASAMI stereotype view "Experimental" because you can get consensus from the modeling team and the PTL.
      
  • Use Case Txeveloped.
  • Architecture uxn be known.
  • PTL- Hixl

  • 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

...