Linking the Static and Dynamic Ontologies Sample Clauses

Linking the Static and Dynamic Ontologies. ‌ The static ontology of deliverable 3.1 contains several classes that refer to the static view of the system. Among them, we focus on actions performed on objects and any properties of these objects. In the static ontology, these elements are represented by the OWL classes OperationType, object, and property. Concerning the dynamic elements of a software system, the corresponding ontology covers not only actions, objects, and properties, but also the conditions of actions. The corresponding OWL classes are Action, Object, Property, and GuardCondition. Apart from the above classes, we also keep track of the Project that is instantiated, as well as the instances of type Requirement and ActivityDiagram derived from the static and dynamic ontologies respectively. These three classes ensure that our ontologies are traceable and strongly linked to one another. The mapping of the static and the dynamic ontologies to the aggregated ontology is shown in Figure 5.3. As shown in this Figure, Requirement and ActivityDiagram are simply propagated to the aggregated ontology, while Project is used to ensure that the two ontology instantiation refer to the same project. Concept Project action emergence ownership state ThingType actor external_system system useractor object goal source theme property direction extent location manner modality time Concept Project ActivityDiagram Actor AnyActivity InitialActivity Activity FinalActivity Action Condition GuardCondition PreCondition PostCondition Object Property Transition Concept Project ActivityDiagram Element Representation InputRepresentation OutputRepresentation Activity Condition Resource Property OperationType Requirement Requirement FP7-ICT-610717