A Comparative Analysis between BPMN and SPEM Modeling Standards in the Software Processes Context

Abstract

The main objective of this paper is to analyze the representativeness of the SPEM (Software Process Engineering Metamodel Specification) and the BPMN (Business Process Modeling Notation) standards in the software processes modeling context. To perform this analysis, it was adopted a standard structure to define a software process based upon a process ontology. Then, the SPEM and BPMN standards notations and their semantically corresponding elements in the default process were identified. This mapping also includes components of the CMMI-DEV (Capability Maturity Model Integration for Development) and MR-MPS (Reference Model for Software Process Improvement) quality models. This was necessary to assist in the mapping evaluation through a case study which models the best practices of these quality models. Finally, we carried out an analysis of these standards through specific characteristics considered necessary to model and to represent software processes.

Practical Experiences in the Use of Pattern-Recognition Strategies to Transform Software Project Plans into Software Business Processes of Information Technology Companies

“…ITCs as many other organizations are introducing the BPM approach for improving [43][44][45]53] their software business processes, which means a key factor to become more competitive. As previously mentioned, processes have different perspectives or dimensions.…”

“…In order to manage the software lifecycle, business experts use General Process Modeling Languages (GPMLs) [43][44][45], such as Petri Nets, Business Process Execution Language (BPEL), Business Process Model and Notation (BPMN) [46], and Event-Driven Process Chain (EPC) or Unified Modeling Language Activity Diagrams (UML AD) [37], together with other specific Software Process Modeling Languages (SPMLs), such as Software and Systems Process Engineering Metamodel (SPEM [47][48][49]), Software Engineering Metamodel for Development Methodologies [50], and Essence-Kernel And Language For Software Engineering Methods (Essence [51,52]). Besides, we have taken into account NDTQ-Framework [30], because it is used in our case study: AQUA-WS Project [29].…”

“…Besides, we have taken into account NDTQ-Framework [30], because it is used in our case study: AQUA-WS Project [29]. Bonnet et al [53] consider BPMN as the process modeling leading standard between users and business experts, which is increasingly being utilized in the software field [43][44][45].…”

Definition of processes for MDE-based migrations

“…This is an important issue because in the software domain, SPEM is more expressive than BPMN. As can be seen in [20], to represent software procedures in BPMN we have Text Annotations while in SPEM we can use a range of elements such as Guidance, Guideline, ToolMentor, Template or Checklist. In the same way, to represent stakeholers involved in a process software, SPEM has the RoleUse and RoleDefinition elements which are more detailed for the software context than their equivalents in BPMN (Pool and Lane elements).…”

Mining software development process variations

“…Among the existing process modeling languages, we can stand out two that have raised the attention of both practitioners and researchers for modeling software development processes [20] and are supported by several tools [11]: SPEM (Software Process Engineering Metamodel Specification) and BPMN (Business Process Model and Notation).…”