Versions Compared

Old Version 21

changes.mady.by.user Benjamin Cheung

Saved on

compared with

New Version 22

changes.mady.by.user Benjamin Cheung

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • M2

    • Modeling SubCommittee -
      • REFINING INFORMATION MODEL - The information model that has been scheduled for development from the model requirements planning is being developed and refined in this phase of work. The various models and components of the information model are discussed are refined week to week with input from model sub-committee members. Following IISOMI, The classes & attributes are all in experimental state. The model has been posted.
      • DISCUSSION INFO MODEL - During In this phase, during the refining of the info model by the modeling S/C the info model is called the "discussion model" in this phase. The graphics will indicate "discussion model" when they are under refinementinformation model by the Modeling Sub-committee (S/C) a given contribution is in "Discussion Information model" state. The proposed contribution would be put in the discussion section of the Modeling S/C wiki for a particular release. For example, for R6 (Frankfurt) for the service model there would be an input model, discussion model and a clean model sections. As the contribution is worked on, it would move from the input to the discussion to the clean model sections. The following key concepts will be used to describe how the contributions are handled and the various states that are used to track their development:
        • IISOMI STATES - The concept of IISOMI states describe the state of individual classes, attributes, and associations/relationships. For example, a particular parameter might be in the experimental state while another class might be tagged as preliminary. These preliminary and experimental are states that are mutually exclusive so you can't have a class/attributes with two different IISOMI states simultaneously. so if you are in discussion you must have all of the model be out of experimental state. IISOMI states within the contributions. Some elements within the contribution could have different IISOMI states. The link to the IISOMI states can be found at: Informal Inter-SDO Open Model Initiative (IISOMI)
        • CONTRIBUTIONS vs RELEASE - Parameter group (R7) refinements some things still as "preliminary" (accepted) but a few new ones are "experimental" than the contribution becomes clean. Just because the contribution is clean, does not mean the release has gone to clean.
        • MODELING S/C STATES - Input / Discussion / Clean states.
      • INFORMATION MODEL REVIEW - After the discussion information model is has been refined, it a particular contribution will undergo review by the modeling sub-committee et al. People can comment on the wiki and there will generally be a face-to-face discussion for the review as well. Objections and continued discussion can be accommodated for with further discussions and responses in the wiki page.
      • INFORMATION MODEL FREEZE - The information model for the release is approved after it has been review by the modeling sub-committee. Note: even after the freeze, some minor refinement can still occur (see the M3 activities).
      • CLEAN INFO MODEL - After review and info model freeze by the modeling S/C the info model is called the "clean model" in this phase. At this point, the Use Case teams that are developing the Data Model can be pretty certain that the information model will be usable as shown. The diagrams and model wiki pages will indicate that this is a clean model.
    • Architecture Engagement -
      • SYNC UP - Before M2, the architecture team is working to refine their Functional Architecture, the component architecture, and Architecture proposed enhancements.
    • Use Case Engagement -
      • DATA MODEL DEVELOPMENT - Discussion Info Model & Data model development with input from the Model S/C. Active discussion and interaction between Use Case Team and the Modeling S/C to make sure that the information model and the data model development are in lock-step.
      • DATA MODEL REVIEW - Reviews of Data Model with Project Teams. The Data Model is being reviewed by the Use Case Teams with inputs from the Modeling S/C
      • JOINT REVIEWS - The Data model should be reviewed with the Modeling S/C.
    • Components (PTL) Engagement - ONAP Platform Teams (A&AI, SO, SDC etc) review clean Information Model impacts for the release.
      • FEEDBACK - Component platform work can feedback to the Modeling S/C for updates to the information model during the refining the info model phase and should also provide input during the review. Modeling S/C should take into account component platform updates vis-a-vis the Use Case and modeling requirements for the release.

...