1 Introduction
2 Requirements of the Information Model
2.1 Guideline for Using OpenModelAttributes
2.2 Requirements of Defining the Classes
A Class in ONAP shall have the following properties:
- Name: in alignment with IISOMI TR 514, Name follows Upper Camel Case style (UCC). Each class in the model has a unique name.
- Example: Qualified Name: Common::Location::ObjectClasses::Place
- Documentation: in alignment with IISOMI TR 514, Contains a short definition. The documentation is carried in the “Applied comments” field in Papyrus; i.e., the “Owned comments” field shall not be used. The complete documentation should be written in a single comment; i.e., at most one “Applied comment”.
- Example: .....
- Superclass(es): in alignment with IISOMI TR 514, Inheritance and multiple inheritance may be used to deal with shared properties.
- Example: Parent class: RootEntity
- TBV: is multiple inheritance supported in ONAP ?
- Applied Steoreotypes: Following stereotypes needs to be identified
- Example:
- Experimental
- OpenModelClass
support: MANDATORY
- Reference: From TMF SID
- Example:
- Abstract : in alignemnt with IISOMI TR 514, Indicates if the object class can be instantiated or is just used for inheritance; i.e., abstract classes will not be instantiated.
- Example: .
Following properties are not mandatory in ONAP:
- Is Leaf : Indicates that the object class must not be extended (Is Leaf = true); default = false