Scoping Software Process Models - Initial Concepts and Experience from Defining Space Standards

Abstract

Abstract. Defining process standards by integrating, harmonizing, and standardizing heterogeneous and often implicit processes is an important task, especially for large development organizations. However, many challenges exist, such as limiting the scope of process standards, coping with different levels of process model abstraction, and identifying relevant process variabilities to be included in the standard. On the one hand, eliminating process variability by building more abstract models with higher degrees of interpretation has many disadvantages, such as less control over the process. Integrating all kinds of variability, on the other hand, leads to high process deployment costs. This article describes requirements and concepts for determining the scope of process standards based on a characterization of the potential products to be produced in the future, the projects expected for the future, and the respective process capabilities needed. In addition, the article sketches experience from determining the scope of space process standards for satellite software development. Finally, related work with respect to process model scoping, conclusions, and an outlook on future work are presented.

Turning Method Engineering Support into Reality

“…For instance, we are planning the integration of a process engine such as Activiti [1]. Furthermore, we are concerning with one of the big challenges of ME [2], which deals with the variability of methods at modeling level and runtime. Providing support to variability will allow stakeholders to dynamically adapt methods and their supporting tools to changes that occur during method execution.…”

An MDE approach to software process tailoring

“…The context of the software process has gained importance, but it has been usually represented informally. Armbrust et al [2] define three dimensions to define the characteristics in the SPrL scope definition: product, project and process. The COCOMO II model [6] defines a set of attributes and dimensions to estimate a project, that are useful for representing context models too.…”

Micro process analysis of maintenance effort: an open source software case study using metrics based on program slicing

“…Yoo suggested a model that combined CMMI and ISO models. Armbrust took a different approach by treating software as manufacturing product lines, creating easier processes, however, making the processes systematic and generic. Unlike these approaches, we use the data mined from software repositories for our assessment.…”