No abstract

Abstract

Defining organization-specific process standards by integrating, harmonizing, and standardizing heterogeneous and often implicit processes is an important task, especially for large development organizations. On the one hand, such a standard must be generic enough to cover all of the organization's development activities; on the other hand, it must be as detailed and precise as possible to support employees' daily work. Today, organizations typically maintain and advance a plethora of individual processes, each addressing specific problems. This requires enormous effort, which could be spent more efficiently. This article introduces an approach to developing a Software Process Line that, similar to a Software Product Line, promises to reduce the complexity and thus, the effort required for managing the processes of a software organization. We propose as majors steps Scoping, Modeling, and Architecting the Software Process Line, and describe in detail the Scoping approach werecommend, based on an analysis 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, it discusses the approach, and related work, conclusions, and an outlook on future work are presented

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.

With increasing process maturity of the software-developing companies, an increasing interest in standardized processes can be observed. Company-specific standards are often derived from reference standards such as ISO/IEC 12207 or the German V-Modell XT. Developing and deploying a (new) company-wide standard is a challenging task with many obstacles. Many efforts in defining and deploying standard processes in a company do not result in sufficient adherence between the defined and the lived (i.e., the enacted) process. Such situations have severe consequences, e.g., it is not possible to measure processes. Published experience with process definition and deployment projects is often anecdotal or incomplete. This paper describes the adaptation of a generic process standard to an organization and its deployment to daily practice. In this article, the approach taken for adapting and deploying the V-Modell XT in the data processing department of the German Josef Witt GmbH is described. Additionally, effort data and lessons learned with respect to these activities are given. Finally, effects visible so far are sketched