The following process are copied from Proposed ONAP Release Process Updates for Information and Data Modeling

Only modeling subcommittee related process are listed below:

•  

  • M0 (Gather info and input high level requirements)

  • Modeling team - At MO the Modeling S/C does MODEL PLANNING. The planning develops into “High Level Info-model Requirements”.  ONAP R7 Modeling High Level Requirements

  • These High level info-model requirements fall into 3 categories:
    
    

    • #1: NEW USE CASES

    • #2: REFINING EXISTING MODEL

    • #3: FORWARD LOOKING WORK (FLW) .

•  

  • M1 (Deadline for high level requirements )

  • Modeling team  

  • #1: USE CASE TEAM SYNC - The Use Case teams need to engage the Modeling Sub-committee to make the team aware of potential model impacts arising from their use cases. The modeling team should also become aware of those at a high-level what impacts a use case might have to the release information model.  ONAP R7 Modeling High Level Requirements

  • #2: Start Info Model discussion in RM weekly meeting call.

  • #3 Use case design team will create DM internallly. Once finished they can apply for joint review asap.

  • #4：DM (design time DM ): jointly reviewed by SDC and modeling subcommittee

•  

  • M2. (Model Freeze for IM) == follow model subcommitee procedure for freeze (final call and polling)

    • MODELING SUBCOMMITTEE -

    • For the RELEASE Information Model these are the activities that the Modeling sub-committee is engaged in leading up to M2.

      • IM FREEZE - Each model proposal will be reviewed and refined during RM weekly meeting call. After concensus is reached, final call for approval polling will be launched.

      • For IM model still not reach consensus/not yet approved will be postponed to next release.

      • DM (design time DM): jointly reviewed by SDC and modeling subcommittee

•  

  • M3 ( IM final and DM model freeze) DM need to be viewed jointed by SDC and modeling subcommittee

    • M3 MODELING SUBCOMMITTEE ACTIVITIES -

      • IM: Refine clean model and continue disucssing unapproved IM 

      • DM FREEZE: Each model proposal will be reviwed and refined finally by SDC/Modeling subcommttee. After concensus is reached, final call for approval polling will be launched. 

      • M3 CHECKLIST - The M3 check list modeling updates discussion is used by the modeling sub-committee. It is used as a vehicle to engage the Use Case (project teams) and reconcile the Use Case Teams with the modeling S/C team's work. See also the Use Case Team Engagement (section below). The Check list can be found here: Proposed M3 Checklist modeling updates discussion

•  

  • M4 ( IM & DM documentataion)

  • RC0/RC1/RC2 (Discuss next release model plan)

Final achievement in modeling subcommittee:

• Information Model Artifact Contains

  • Classes

  • Relationships with Multiplicity

  • Important Attributes with Multiplicity 

  • Definitions

  • Data Types 

  • Feed to Data Dictionary

  • Tooling - Papyrus with GitHub

• Component Data Model Artifacts (Implementation Specific)

  • Component Data Model

    • Contains objects, attributes, & relationships (more detail than information model)

  • Mapping to Information Model

  • Feed to Data Dictionary?

• API Artifacts

  • API Model

  • Mapping to Information Model