Difference between revisions of "Notation of Information Viewpoint Models"
(→Information Object Instances) |
(→State Diagrams) |
||
Line 131: | Line 131: | ||
== <span style="color: #BBCE00">State Diagrams</span> == | == <span style="color: #BBCE00">State Diagrams</span> == | ||
− | IV Object instances can have different states during their lifespan. The basic information objects persistent data and metadata have specific sets of states associated to them. The state changes, together with the IV Activities can be used to model the behaviour of data as it is managed by the RI. For this we use a state machine diagram. The main components of state machine diagrams are activity frames, states, activities, and pseudo-states | + | IV Object instances can have different states during their lifespan. The basic information objects persistent data and metadata have specific sets of states associated to them. The state changes, together with the IV Activities can be used to model the behaviour of data as it is managed by the RI. For this we use a state machine diagram. The main components of state machine diagrams are activity frames, states, activities, and pseudo-states. |
+ | |||
+ | {| class="wikitable sortable" style="width: 85%;" | ||
+ | |+ Table 7 Notation for information object instances diagrams | ||
+ | |- | ||
+ | ! style="padding: 7px"| <span style="color: #BBCE00">'''Figure'''</span> | ||
+ | ! <span style="color: #BBCE00">'''Description'''</span> | ||
+ | |- | ||
+ | | style="background-color:#ffffff;"| [[File:UML_ActivityFrame.png]] | ||
+ | | style="background-color:#ffffff;"| Frames are used to indicate the information object instance being represented. | ||
+ | |||
+ | The name indicates the information object instance being modelled | ||
+ | |- | ||
+ | | style="background-color:#ffffff;"| [[File:UML_State.png]] | ||
+ | | style="background-color:#ffffff;"| States are used to represent the state of an information object resulting from the effects of an IV action | ||
+ | |||
+ | The name tag indicates the state reached by the information object | ||
+ | |||
+ | The small decoration in the box can be included to indicate that the state is complex and can be subdivided into sub-states | ||
+ | |- | ||
+ | | style="background-color:#ffffff;"| [[File:UML_Action.png]] | ||
+ | | style="background-color:#ffffff;"| The arcs connecting states represent information actions applied to objects at a given state. The arrow end indicates the resulting state, the undecorated end indicates the initial state | ||
+ | |- | ||
+ | | style="background-color:#ffffff;"| [[File:UML_StartPseudostate.png]] | ||
+ | | style="background-color:#ffffff;"| A filled circle is a pseudo-state, it can be used to model a start state or an intermediate connecting state | ||
+ | |- | ||
+ | | style="background-color:#ffffff;"| [[File:UML_StopPseudostate.png]] | ||
+ | | style="background-color:#ffffff;"| A circle with a smaller filled circle in the middle is a pseudo -state to model an end state | ||
+ | |- | ||
+ | | style="background-color:#ffffff;"| [[File:UML_DecisionPseudostate.png]] | ||
+ | | style="background-color:#ffffff;"| Decision pseudo-state, is used to model an exclusive fork in the execution of activities. It can also be used to model exclusive joins after forks. | ||
+ | |- | ||
+ | | style="background-color:#ffffff;"| [[File:UML_ForkJoinPseudostate.png]] | ||
+ | | style="background-color:#ffffff;"| Fork/merge pseudo-state, is used to model a forks and joints in the execution of activities. | ||
+ | |} | ||
+ | |||
+ | [[File:IVDataStates04-2.png|1200px|none]] | ||
+ | <div style='margin-left: 450px;'>Figure 7 Example of an IV Information Object Evolution diagram</div> | ||
+ | |||
+ | In the example diagram, five information object instances are presented. The possible transitions between states are indicated with arcs labelled using the names of IV actions. | ||
+ | |||
+ | == <span style="color: #BBCE00">Evolution of information objects</span> == | ||
+ | |||
+ | The evolution of information objects can also be represented using activity diagrams. Activity diagrams combine IV Object Instances and IV actions can also be combined into | ||
+ | |||
[[Category:Appendix C Notation]] | [[Category:Appendix C Notation]] |
Revision as of 23:00, 29 March 2020
Contents
Information Objects
IV Objects are represented using a class diagram.
In the example diagram the package represents the collection of all information objects described by the ENVRI RM. The stereotype for the package is invariant schemata, which indicates that these are the parts of the model that are stable. The main objects are persistent data and metadata. The RM also provides a detailed description of each object in the text.
Information Actions
IV Actions are represented using an activity diagram with packages and activities
In the example diagram the package represents the information action types described by the ENVRI RM. The stereotype for the package is invariant schemata, which indicates that these are the parts of the model that are stable. The RM also provides a detailed description of each action in text.
Information Object Instances
IV Objects instances are represented using an object diagram. The type of diagram is similar to the class diagram with the difference that the entities represented are objects not classes. Object instances have a specific state and this can change depending on the moment when the object is observed. Object instances are useful for representing the dynamic nature of the systems.
In the example diagram the package represents a collection of some information object instances. The stereotype for the package is dynamic schemata, which indicates that these are the parts of the model that can change depending on when the system is observed. The diagram presents four sample instances of persistent data objects and three examples of metadata objects. The diagram also includes the class definitions of persistent data and metadata objects for reference
State Diagrams
IV Object instances can have different states during their lifespan. The basic information objects persistent data and metadata have specific sets of states associated to them. The state changes, together with the IV Activities can be used to model the behaviour of data as it is managed by the RI. For this we use a state machine diagram. The main components of state machine diagrams are activity frames, states, activities, and pseudo-states.
In the example diagram, five information object instances are presented. The possible transitions between states are indicated with arcs labelled using the names of IV actions.
Evolution of information objects
The evolution of information objects can also be represented using activity diagrams. Activity diagrams combine IV Object Instances and IV actions can also be combined into