Low-Level Ontology Properties. With the term “low-level properties” we define the properties that cover the interactions among the different ontology classes, excluding Project and ActivityDiagram. We can further refine these properties in the ones defining the flow of activities in a diagram and the ones defining the relations among the rest elements (including implicitly derived elements, e.g. Action or Object). These properties are given in Table 3.2 and Table 3.3, respectively. Table 3.2 Low-level Properties of the Dynamic Ontology, for the Flow of a Diagram OWL Class Property OWL Class Activity activity_has_property Property Property is_property_of_activity Activity Transition has_source Activity, InitialActivity Activity, InitialActivity is_source_of Transition Transition has_target Activity, FinalActivity Activity, FinalActivity is_target_of Transition Transition has_condition GuardCondition GuardCondition is_condition_of Transition GuardCondition is_opposite_of GuardCondition As shown in Table 3.2, the different relations of ontology classes are actually forming the main flow as derived from diagram elements. Thus, Activity instances are connected with each other via instances of type Transition. Any Transition has a source and a target Activity (properties has_source and has_target, respectively), and it may also have a GuardCondition (property has_condition). Finally, any Activity is related to instances of type Property, while any GuardCondition has an opposite one, connected to each other via the bidirectional property is_opposite_of. This flow is also illustrated in Figure 3.2.
Low-Level Ontology Properties. The low-level properties are very important since they cover the main structure of the software project. The instances of the class Element along with these properties have to be as expressive as possible since they will be used to form the CIM of the project. The low-level properties of the aggregated ontology are shown in Table 5.2. Table 5.2 Low-level Properties of the Aggregated Ontology OWL Class Property OWL Class Resource has_activity Activity Activity is_activity_of Resource Resource has_property Property Property is_property_of Resource Resource has_representation Representation Representation is_representation_of Resource Activity has_action Action Action is_action_of Activity Activity has_condition Condition Property is_condition_of Activity Activity has_next_activity Activity Activity has_previous_activity Activity As shown in Table 5.2, the relations of the ontology classes are formed around two main subclasses, Resource and Activity. This is quite expected since these two elements form the basis of a RESTful system. Resources and the respective activities are prototyped by the S-CASE MDE engine. Any system Resource may be connected to instances of type Property and Activity, using the properties has_property/is_property_of and has_activity/is_activity_of respectively. The Representation of each Resource must also be connected to it (via the properties has_representation/ is_representation_of. Finally, class Activity is connected to instances of type Action (via the properties has_action/is_action_of) and of type Condition (via the properties has_condition/is_condition_of), since it is necessary to keep track of the CRUD verbs to be used as well as any conditions that have to be met in order for the activity to be valid. Transitions are handled using has_next_activity/ has_previous_activity. These low-level properties are also visualized in Figure 5.2, where it is clear that Resource and Activity have central roles in the aggregated ontology. Figure 5.2 Low-level Aggregated Ontology Properties
Low-Level Ontology Properties. With the term “low-level properties” we define the properties that cover the interactions among the different subclasses of ThingType and OperationType. These properties are given in Table 4. Table 4 Low-level properties of the ontology OWL Class Property OWL Class action acts_on object, property object, property receives_action action OperationType has_actor actor actor is_actor_of OperationType object has_goal goal goal is_goal_of object object has_source source source is_source_of object ThingType has_property property property is_property_of ThingType emergence occurs object object occured_by emergence ownership owns object object owned_by ownership
