NOTE: Comments Due by 20 OCTOBER 2017.
This document specifies ONAP modeling design principles and guidelines for release 2+
The Principles section focuses on "what" foundations need to be followed as part of the ONAP Modeling effort, while the Guidelines section focuses on the plan for "how" to achieve the goals described in the Principles section and identifies best practices that may be applied.
Principles
1- Requirements driven and prioritization per release
2- Based on existing implementation and attempt to maintain backward compatibility
3- Keep the distinction and consistency between Information model and its data model representation(s).
a) DM does not need to match exactly the IM; DM can represent the semantics of the IM
b) DM are pruned and refactored from IM
c) Discuss extensibility guidelines to be progressed (TBD)
d) Apply IISOMI(Informal Inter-SDO Open Model Initiative) Approach (see diagram)
4- The Information Models and Data Models from this effort should be applied across ONAP projects.
5- The modeling team should not define the feature requirements, but take requiremetns derived from use cases or architecture as input.
Lingli Deng Moved from the Guidelines section to here.
6- Actively pursue participation from stakeholder projects in the modeling effort.
Lingli Deng Moved from the Guidelines section to here.
Guidelines
1- Initially focus on a Unified Information Model in UML and its TOSCA construct representation for Service and Resource, with an initial focus on the Service Descriptor and VNF Descriptor.
Lingli Deng We agreed on starting with modeling on Service and Resource, but not limited to SD and VNFD. Otherwise, it would prevent us from demonstrating hybrid scenarioes (as one of the requirements stated for R2 discussion list, which is not what we intended, at least not for my case I am afraid. Since we do not own the requirement, and we are waiting for the requirements to come, I suggest that we do not add extra limitation ourselves right now.
2- Use Eclipse Papyrus as the UML modeling tool for this activity
3- The model will support the ONAP VNF Requirements (e.g. scaling) and use the VNF Requirements as input. The modeling team should not define the feature requirements, but rather Information Model support for defined requirements
Lingli Deng Moved to Principles section.
4- Actively pursue participation from stakeholder projects in the modeling effort.
Lingli Deng Moved to Principles section.