Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

2.3 Requirements of Defining the Associations


  • Name: in alignment with IISOMI TR 514, Name follows Upper Camel Case (UCC) style and is unique across all relationship names defined in the whole model.
    The format for associations is "<Class1Name><VerbPhrase><Class2Name>" where the verb phrase creates a sequence that is readable and meaningful. In case of a long class name, it is also allowed to use a short form of the name.
    •  Example:
  • Documentation: in alignment with IISOMI TR 514, it 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”.
  • Type: in alignment with IISOMI TR 514,The following types are used: simple association, composition association, aggregation, association, generalization, dependency, usage dependency, abstraction dependency, realization dependency.


Following properties are optional in ONAP: 

  • Direction/Navigable in Papyrus

2.4 Requirements of Defining the Data Types

...