| Latest revision |
Your text |
| Line 35: |
Line 35: |
| | In the following example diagram (Figure 1) the package represents an Environmental research infrastructure. The infrastructure contains five objects which are all communities and each community is linked to a community objective. | | In the following example diagram (Figure 1) the package represents an Environmental research infrastructure. The infrastructure contains five objects which are all communities and each community is linked to a community objective. |
| | | | |
| − | [[File:SVCommunities.png|none]] | + | [[File:SVCommunities.png|frame|Figure 1 Example of a community diagram|none]] |
| − | <div style='margin-left: 420px;'>Figure 1 Example of a community diagram</div>
| |
| | | | |
| | == <span style="color: #BBCE00">Community Roles</span> == | | == <span style="color: #BBCE00">Community Roles</span> == |
| − |
| |
| − | SV Roles are represented using a class diagram with packages and classes
| |
| − |
| |
| − | {| class="wikitable sortable" style="width: 85%;"
| |
| − | |+ Table 2 Notation for role diagrams
| |
| − | |-
| |
| − | ! style="padding: 7px"| <span style="color: #BBCE00">'''Figure'''</span>
| |
| − | ! <span style="color: #BBCE00">'''Description'''</span>
| |
| − | |-
| |
| − | | style="background-color:#ffffff;"| [[File:UML_Package.png]]
| |
| − | | style="background-color:#ffffff;"| A Package, in UML notation, is a grouping element. Package is used "to group elements, and to provide a namespace for the grouped elements".
| |
| − |
| |
| − | A package may contain other packages, thus providing for a hierarchical organization of packages.
| |
| − |
| |
| − | Classes, objects, use cases, components, nodes, node instances etc. can all be organized as packages, enabling a manageable organization of the elements of UML models.
| |
| − | |-
| |
| − | | style="background-color:#ffffff;"| [[File:UML_Class.png]]
| |
| − | | style="background-color:#ffffff;"| Classes are used to represent roles in the RM.
| |
| − |
| |
| − | Classes can have additional compartments to express properties (called attributes) and behaviours (called methods). Omitting the compartments means that the behaviour and attributes are undefined at the time of building the diagram.
| |
| − |
| |
| − | Name tag indicates the name of the class. Typically, classes are named using no spaces and starting each word that makes up the name, i.e., camelcase.
| |
| − |
| |
| − | The stereotype indicates the namespace where the class is grouped. Sometimes the stereotype can be an image. The image can be used in place of the figure. For ODP, the stereotype for role is a mask:
| |
| − |
| |
| − | [[File:Enterprise-Role.jpg|right]]
| |
| − | |}
| |
| − |
| |
| − | In the example diagram the package represents the data curation community. The community contains eight role classes. The ENVRI RM provides a detailed description of each role in text.
| |
| − |
| |
| − | [[File:SVCurationCommunityRoles_2.png|none]]
| |
| − | <div style='margin-left: 250px;'>Figure 2 Example of a SV Role diagram</div>
| |
| − |
| |
| − | == <span style="color: #BBCE00">Community Behaviours</span> ==
| |
| − |
| |
| − | SV Behaviours are represented using an activity diagram with packages and activities
| |
| − |
| |
| − | {| class="wikitable sortable" style="width: 85%;"
| |
| − | |+ Table 3 Notation for behaviour diagrams
| |
| − | |-
| |
| − | ! style="padding: 7px"| <span style="color: #BBCE00">'''Figure'''</span>
| |
| − | ! <span style="color: #BBCE00">'''Description'''</span>
| |
| − | |-
| |
| − | | style="background-color:#ffffff;"| [[File:UML_Package.png]]
| |
| − | | style="background-color:#ffffff;"| A Package, in UML notation, is a grouping element. Package is used "to group elements, and to provide a namespace for the grouped elements".
| |
| − |
| |
| − | A package may contain other packages, thus providing for a hierarchical organization of packages.
| |
| − |
| |
| − | Classes, objects, use cases, components, nodes, node instances etc. can all be organized as packages, enabling a manageable organization of the elements of UML models.
| |
| − | |-
| |
| − | | style="background-color:#ffffff;"| [[File:UML_Activity.png]]
| |
| − | | style="background-color:#ffffff;"| Activities are used to represent behaviours in the RM.
| |
| − |
| |
| − | Name tag indicates the name of the behaviour. Behaviours are named using a short phrase that describes the event or action being represented.
| |
| − |
| |
| − | The small decoration in the activity indicates that the activity is complex and can be subdivided into smaller tasks.
| |
| − |
| |
| − | A stereotype can be used to indicate the namespace where the activity is grouped. Sometimes the stereotype can be an image. The stereotype image can be used in place of the figure. For ODP, the stereotype for behaviour is process icon:
| |
| − |
| |
| − | [[File:Enterprise-Process.jpg|right]]
| |
| − | |}
| |
| − |
| |
| − | [[File:SVAcquisitionCommunityBehaviours_2.png|none]]
| |
| − | <div style='margin-left: 120px;'>Figure 3 Example of a SV Behaviour diagram</div>
| |
| − |
| |
| − | In the example diagram the package represents a community, data acquisition. The community implements four basic behaviours. The RM also provides a detailed description of each behaviour in text.
| |
| | [[Category:Appendix C Notation]] | | [[Category:Appendix C Notation]] |
