MetaProPOS: A Meta-Process Patterns Ontology for Software Development Communities

A Semantic Approach for Automatic Structuring and Analysis of Software Process Patterns

“…As consequence to the huge proliferation of the process patterns practice, these latters are being used in an informal manner, through traditional textbooks or better with modest hypertext systems providing weak semantic relationships. In addition to the huge number of process patterns that are available in books or Web-based resources [3], they significantly differ in format, coverage, scope, architecture and terminology used [1].…”

“…The lack of architectural consent means that different process pattern descriptions have been proposed using disparate architectures. In fact, when comparing the eleven selected works from the literature, we identified eleven different pattern description facets, namely: identification, classification, problem, context, solution, role, artifact, relationship, guidance, management and evaluation [1]. In addition, these are differently covered by process patterns descriptions and most of them pay more attention to the four main facets: context, solution, problem and relationships of a pattern.…”

“…To overcome the afore mentioned lacks, a first step was to create a unified conceptualization of process patterns. Thus, mappings efforts [1] were necessary to achieve this goal leading to a process patterns' meta-model unifying patterns knowledge representations. In this latter, we consider a process pattern information description from six facets: [13] The identification facet encapsulates a set of properties identifying a pattern such as pattern name, author(s), keywords, pattern's classification (type, category, abstraction level, and aspect) as well as pattern origin (project and participants) and pattern artifacts (used and/or produced).…”

“…In this context, many formalisms and languages have been proposed to describe software process patterns. This multiplicity makes capitalization and/or reuse of process patterns, difficult to be achieved [1].…”

Knowledge Support for Software Processes

“…The informal knowledge resource is consulted by Domain Specialist who resolves various tasks to achieve goals of the formal conceptualization activity (Scacchi, 1997), (Uschold, 1998) (Dufresne, 2003), -the situation is depicted in picture 2.17 and identified as a Semantic Gap -a loss of captured detail or information -that is caused by transformation of the process representation to respective process models with informal (and often also ad-hoc) terminology resource used as a middleware between process representation (as it appears in an organization) and final model (Jlaiel, 2011), (Samuel, 2015).…”