...
- Tag components that are potentially impacted by an information model (IM) / data model (DM) concept and socialize the concept with that component team (M1)
- Note that Information Model Updates can be due to:
- Release / project specific needs
- Recognized 'future' needs
- Documenting existing models
- Note that Information Model Updates can be due to:
- The Modeling Subcommittee actively reviews component information flows, looking for I/Os being identified and related to the information model (M3)
- This is an opportunity to reconcile the IM/DM with the component model
- Require components to indicate that they comply with the IM/DM
- Require component teams to socialize their data model with the ONAP Modeling subcommittee (M2)
- Require Modeling subcommittee to sign off on component data models.
- Require component DM team to provide a DM document with rationalization to IM (M3)
- Alternative - Collaboratively rationalize
...