...
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 and it's related runtime DM): jointly reviewed by SDC, A&AI 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 and it's related runtime DM): jointly reviewed by SDC, A&AI and modeling subcommittee
...