Abstract
SPEM (Software Process Engineering Metamodel Specification) is the software processes modeling standard defined by OMG (Object Management Group). However, the process enactment support provided by this standard has many deficiencies. Therefore, the main objective of this paper is to propose a language for software process enactment based upon SPEM 2.0 concepts. First, we will present a critical analysis of the SPEM standard approach for enactment. Then, we will present xSPIDER_ML, an enactment language, and describe its structure, components and associated rules. In order to evaluate the proposed language, a case study is performed through a RUP (Rational Unified Process) process instantiation. The language presented in this paper is part of a support set of tools for flexible software process enactment. Additionally, this set of tools is in compliance with software process quality models.
Highlights
Software process is the main object of study in Software Engineering and can be defined as the set of activities that aims to build software from a set of requirements [1]
SPEM (Software Process Engineering Metamodel Specification) is the software processes modeling standard defined by OMG (Object Management Group)
The main objective of this paper is to propose a language for software process enactment based upon SPEM 2.0 concepts
Summary
Software process is the main object of study in Software Engineering and can be defined as the set of activities that aims to build software from a set of requirements [1]. Its main objective is to provide organizations with the means to define a conceptual framework It does so providing the concepts necessary for modeling, interactions, documentation, management and presentation of their methods and development processes [2]. After the mapping with project plans, these can be instantiated through planning tools where resources can be allocated Despite this approach being very useful for project planning, it does not meet the process enactment requirements that are: automatic changes in the tasks for responsible roles; automatic artifact forwarding; automatic control of the state of work products after each activity; among other features [7]. In order to address these deficiencies in the standard, there are some studies that propose to automate the enactment of software processes modeled using SPEM notations These studies are presented in the following subsection
Sign-in/Register to view highlights & summary Sign-in/Register to access full text options 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a call
