Defining Software Process Model Constraints With Rules Using Owl and SWRL

Abstract

The Software & Systems Process Engineering meta-model (SPEM) allows the modelling of software processes using OMG (Object Management Group) standards such as the MOF (Meta-Object Facility) and UML (Unified Modelling Language) making it possible to represent software processes using tools compliant with UML. Process definition encompasses both the static and dynamic structure of roles, tasks and work products together with imposed constraints on those elements. However, the latter requires support for constraint enforcement that is not always directly available in SPEM. Such constraint-checking behaviour could be used to detect possible mismatches between process definitions and the actual processes being carried out in the course of a project. This paper approaches the modelling of such constraints using the SWRL (Semantic Web Rule Language), which is a W3C recommendation. To do so, we need to first represent generic processes modelled with SPEM using an underlying ontology based on the OWL (Ontology Web Language) representation together with data derived from actual projects.

Formal modelling, knowledge representation and reasoning for design and development of user-centric pervasive software: a meta-review

“…However, such approaches do not exploit the full benefits of the abstraction. On the one hand, using UML, the UML meta-model and the Object Constraint Language (OMG, 2006) (OCL -used to increase expressivity of UML through allowing constraints to be defined) for ontology development is not preferable, since they do not offer automatic inference, and there is no notion of logic and formally defined semantics (Diouf et al, 2007;Noguera et al, 2010;Parreiras and Staab, 2010;Rodriguez et al, 2010). Available AI-based KR formalisms or logic programming languages (i.e., F-logic, OWL, etc.)…”

“…Therefore, design and development of full applications by employing ontologies throughout the whole software development cycle is not realised. One of the main concerns raised regarding the use of ontology as a central substance for MDD is that while UML provides means to specify dynamic behaviour of the system, current OWL-based approaches do not (Noguera et al, 2010;Parreiras and Staab, 2010;Rodriguez et al, 2010;Silva Parreiras et al, 2007). The ability to model dynamic behaviour of a system is crucial for the automated development of pervasive and adaptive systems and applications, since behavioural models (including constraints imposed) are central to the adaptation process.…”

“…In Rodriguez et al (2010) the authors present how processes modelled with SPEM (the Software & Systems Process Engineering meta-model of OMG (OMG, 2008) based MOF and UML) can be translated into an ontology to exploit the reasoning power of ontologies. The authors use Semantic Web Rule Language (SWRL, extends OWL with logic based rules, i.e., logic layer) to check project constraints and to assert new facts from existing data.…”

Verifying Service Choreography Model Based on Description Logic

“…Section 2 introduces the service choreography modeling framework, highlighting the metamodel of service choreography. Section 3 discusses CMV-DL further on model verification mechanism and UML-DL conversion and introduces the deductive reasoning rules specified in Semantic Web Rule Language (SWRL) [18]. Section 4 provides a case study to show the potential usage of CMV-DL.…”

OntoSoft: um processo de desenvolvimento ágil para software baseado em ontologia

“…Por exemplo, a catalogação de recursos ou de mapeamento de vocabulários de diferentes fontes de informação necessitam de definições precisas, ou caracterizações importantes que auxiliem na tomada de decisão dos termos para que possam ser utilizados em situações práticas. Nesse sentido, as ontologias permitem adicionar semântica aos dados de modo que diferentes componentes de software possam compartilhar informações de forma homogênea (RODRIGUEZ et al, 2010).…”