Proposed M3 Checklist modeling updates discussion
Please provide comments on this wiki page by 7 DEC 2018
Draft of the recommended new "Practice Area" for Information and Data Modeling for the M3 Deliverables for API Freeze Milestone Checklist Template.
Practice Area | Checkpoint | Yes/No | Evidences | How to? |
---|---|---|---|---|
Information and Data Modeling | Has the Project team completed Use Cases and Feature Requirements demonstrating an existing Use Case that describe the information exchanges among ONAP Components? | YES/NO | If Yes, please provide link to the specific Use Cases / Feature Requirements and associated Sequence Diagrams. | Describe the interactions and behavior of each Information Exchange with Use Case / Feature Requirements and Sequence Diagrams. |
Has the Project team completed a Data Model for all Shared Information (e.g., APIs, API Payload, Shared Design Model)? | YES/NO | If Yes, please provide link to the Data Model. | Data Models (e.g., JSON, YANG, etc.) that define the data exchanged or shared. | |
Has the Project team mapped the data elements in the Data Models into the ONAP Common Information Model? | YES/NO | If Yes, please provide link to the Data Element Mapping. | Mapping to understand how the data elements relate to the ONAP Common Information Model. (see: Modeling sub-committee) | |
Has the Project team reviewed the Data Models and Use Case artifacts with the Modeling Sub-Committee? | YES/NO | If Yes, please provide link to the review findings. | Modeling walkthrough to understand how each project contributes to the ONAP Common Information Model. Modeling Sub-Committee to organize the walkthrough | |
Is there a plan to address the findings of the Information / Data Modeling review? | YES/NO | If Yes, please provide link to the plan. | The plan could be as simple as a Jira issue to track the resolution of findings or a documented plan within the wiki. |