Versions Compared

Old Version 19

changes.mady.by.user Benjamin Cheung

Saved on

compared with

New Version 20

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.
      • DISCUSSION INFO MODEL - 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 refinement.
      • INFORMATION MODEL REVIEW - After the information model is refined, it will undergo review by the modeling sub-committee. 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 - it is a approved & The information model for the release is approved after it has been review by the modeling sub-committee. However, There is a Note: even after the freeze, but 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
    • Components (PTL) Engagement - Platform Teams review Model impacts

  • M3

    • API Freeze

    • Add “Infomodel Final”

    • Add “Data Model Freeze” (Approval)

    • 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

...