Versions Compared

Version Old Version 26 New Version 27
Changes made by

Benjamin Cheung

Benjamin Cheung

Saved on

Key

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

...

  • M2

    • Modeling SubCommittee -
    • For each contribution
      • PHASE 1: CONSIDERING - START: Input Contribution (verb Consider) END: Contribution in Discussion State
        • An individual model contribution is a model that will eventually be a part of the total release information model. It is generally a self-contained model which depicts a particular capability or function of the system. This contribution starts as a "input contribution" and undergoes consideration by the modeling sub-committee. Consideration means that the modeling S/C is entertains & assesses if the input contribution should be accepted into the current (or a future release) by weighing the contribution against its relevance and the available resources (modelers) in the release. If the team thinks that the contribution is not ready for the current release XYZ happensthat contribution will be put into a lower-priority and worked if there are no other contributions to be considered as they would take higher priority. Thus, the contribution would not necessarily be rejected, but would get attention as time allows.
      • PHASE 2a: REVIEW & REFINE - START: Contribution in Discussion State (verb Reviewing & Refine) END: Contribution in Discussion state
        • The contribution undergoes reviewing & refining during the discussion state. Reviewing & refining means that the modeling S/C is discussing the modeling, and updating the contribution based on feedback and comments from the modeling team. Each contribution can be reviewed and refined independently and concurrently with other contributions. Things in the discussion state are classes, attributes and relationships are tagged as IISOMI experimental.
      • PHASE 2b: APPROVING (FINAL CALL FOR COMMENTS & INITIATING POLLING) - START: Contribution in Discussion State (verb Approving/Poll) END: Contribution in Discussion state
        • (a) FINAL PRESENTATION - When the contribution has gotten to a point where the team feels that it can start to undergo the approval process, the contribution is brought one final time the modeling S/C for discussion and socialization.
        • (b) FINAL CALL FOR COMMENTS - After that, a final call for comments is issued by a sub-team lead to the modeling team whereby final thoughts & input can be given. This final call for comments signals that the discussion is wrapping up for this contribution and will so soon go to a poll.
        • (c) INITIATING POLL CREATED - After final call and no further outstanding comments exist, the contribution is brought to a poll by a sub-committee chair. A poll is created whereby modeling S/C members can give the contribution a vote of "yes" or "no". 
      • PHASE 3: APPROVING (FINAL) - START: Contribution in Discussion State Post-Poll (verb Approving) Contribution in Clean State
        • After the poll has concluded, the contribution has finished the approval process. The contribution is now considered to be in the clean state. The items that are in the IISOMI experimental state get promoted to a preliminary state. A gendoc is generated and put on the wiki page. The gendoc would be translated and published on the readthedocs site.

  • PHASE 6: Contribution Model (verb Conjoined) Information Model (Frozen)
    • REFINING RELEASE INFORMATION MODEL (Starting Point) - The release starts with a clean release 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 - In this phase, during the refining of the information model from the PREVIOUS release. Then contributions are considered (see above the process for handling each specific contribution). Potentially a snapshot of the papyrus model and posted into the current release..
    • DISCUSSION OF CONTRIBUTIONS - Next, each contribution is discussion and development (see above the process for handling each specific contribution) refining each of the contribution models 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 release information model is not separately tracked, composed, updated, or released in this period of time. But, rather, each individual contribution has its own Wiki. 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 describes the state of individual classes, attributes, and associations/relationships. IISOMI states are noted within the elements of the contribution. For example, a particular parameter might be in the experimental state while another class might be tagged as in the preliminary state. These preliminary and experimental are states that are mutually exclusive so you can't have a class/attributes with two different IISOMI states simultaneously. During the discussion phase, the elements of the contribution should be out of experimental state.   The exception is that there is a state of reference that can exist with other states. Some elements within the contribution could have different IISOMI states. The webpage for 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.
      • DELAYED THINGS - This may happen that are out of the control the modeling S/C. Use Cases get delayed, or a discussion can't wrap up. So, there could be a corner where for example one or more things (parameters/classes) in a contribution can't make the current release (it stay experimental), what would happen to the overall contribution or release information model (is it allowed to go clean). This would not stop the other parts of the contribution or the release information model from going to a clean state.  #@#
    • INFORMATION MODEL REVIEW - After the discussion information model has been refined, 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 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. Put into the information model for that release. Unfinished contributions are post-poned or discussed further.
  • 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.

...