A Survey on the Application of the V-Modell XT in German Government Agencies

Kuhrmann, Marco; Lange, Christian; Schnackenburg, André

doi:10.1007/978-3-642-22206-1_5

Cited by 7 publications

(10 citation statements)

References 2 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…For instance, the German V-Modell XT implements a so-called "customercontractor-interface" (CC-interface; [4], [18]) in which, based on contracts, the interaction patterns of different project stakeholders are modeled. The CC-interface comprehends a number of quality gates to which certain artifacts are assigned.…”

Section: Fundamentals and Related Workmentioning

confidence: 99%

“…Hersleb and Mockus [22] investigated collaboration and communication patterns in distributed projects in general, whereby communication is a basic pillar of agile methods, which is hard to realize in distributed settings and, thus, often relies on tools [23]. Since tools need "data" to exchange, artifact models that precisely describe outcomes, which themselves are a means for communication, proved to be advantageous [18], even agile methods usually neither have a notion of artifact orientation nor underlying artifact models. A number of studies shows the feasibility of applying concrete artifact models in industrial settings, and the application of artifact models evidently provides significant improvements, e.g.…”

Section: Fundamentals and Related Workmentioning

confidence: 99%

“…Therefore, software processes such as the V-Modell XT implement an interface to couple projects by defining a set of shared quality gates to which certain artifacts (named "Work Products") are assigned [4]. Our field study on the application of the V-Modell XT [18] also investigates the effects of providing a well-defined interface between projects. The study shows that especially the clearness of communication benefits from such an instrument.…”

Section: ) Support For Customer-contractor-interfaces (Scaling and Hmentioning

confidence: 99%

“…A number of projects already implement the CC-interface concept as shown in a study (cf. [18]: 13 out of 29 investigated projects actively used the CC-interface while acting as client in a distributed setting). The example shows that the artifactbased process interface can be applied in such a setting while abstracting from concrete software processes.…”

Section: ) Support For Customer-contractor-interfaces (Scaling and Hmentioning

confidence: 99%

See 3 more Smart Citations

Towards Artifact Models as Process Interfaces in Distributed Software Projects

Kuhrmann

Fernández

Grober

2013

2013 IEEE 8th International Conference on Global Software Engineering

Self Cite

View full text Add to dashboard Cite

Much effort has been spent to investigate the organization of distributed teams and their collaboration patterns. It is, however, not fully understood to which extent and how agile software processes are feasible to support distributed software projects. Practices and challenges that arise from the demands for communication are often in scope of current research. Still, it remains unclear what is necessary to monitor a project and to track its progress from a management perspective. A solution is to monitor projects and their progress on basis of the current quality of the created artifacts according to a given reference model that defines the artifacts and their dependencies. In this paper, we present an artifact model for agile methods that results from of a systematic literature review. The contribution serves as an empirically grounded definition of process interfaces to coordinate projects and to define exchanged artifacts while abstracting from the diverse local software processes.

show abstract

Section: Fundamentals and Related Workmentioning

confidence: 99%

Section: Fundamentals and Related Workmentioning

confidence: 99%

Section: ) Support For Customer-contractor-interfaces (Scaling and Hmentioning

confidence: 99%

Section: ) Support For Customer-contractor-interfaces (Scaling and Hmentioning

confidence: 99%

See 2 more Smart Citations

Towards Artifact Models as Process Interfaces in Distributed Software Projects

Kuhrmann

Fernández

Grober

2013

2013 IEEE 8th International Conference on Global Software Engineering

Self Cite

View full text Add to dashboard Cite

show abstract

“…Experiences gathered during the development and continuous improvement of the V-Modell XT (the German standard software development process, [16]) and lab-based investigations showed taking an artifact approach can benefit process engineers in several ways. For example, the consistent terminology used in artifact modeling helps to avoid misunderstandings [11], artifacts support communication and data exchange [13], and artifacts are easier to evaluate in quality assurance than "performed" activities. A focus on artifacts gives process engineers the freedom to use those methods for artifact creation best serving the actual project context, e.g., creating text documents, or creating comprehensive models.…”

Section: Introductionmentioning

confidence: 99%

Artifact-based software process improvement and management: a method proposal

Kuhrmann¹,

Beecham

2014

Proceedings of the 2014 International Conference on Software and System Process

Self Cite

View full text Add to dashboard Cite

When it comes to software process improvement (SPI), process engineers look for SPI methods to support process analysis, design, realization, deployment, and management. Although a number of different SPI methods and models exist, process engineers tend to view these as too generic, too large, or a poor fit for the organization in which SPI is conducted. A strategy to overcome these shortcomings is to concentrate on the artifacts, which precisely define the desired outcomes, rather than on specific methods. In this paper, we present the Artifact-based Software Process Improvement & Management (ArSPI) model that provides a unified perspective on SPI and company-wide software process management (SPM), the required key artifacts, and the life cycle models. ArSPI is shown to be of practical support to industry who called for a practical way to define the interfaces between SPI projects. This paper concludes with an example of how ArSPI paved the way for several organizations through applying the model in real-world SPIprojects.

show abstract

Crafting a software process improvement approach-a retrospective systematization

Kuhrmann

2015

J. Softw. Evol. and Proc.

Self Cite

View full text Add to dashboard Cite

Structured approaches are beneficial for successful software process improvement (SPI). However, process engineers often struggle with standardized SPI methods, such as capability maturity model integration (CMMI) or International Organization for Standardization (ISO) 15504, and complain about too generic or voluminous approaches or methods that are alien to the organizations in which SPI is conducted. Therefore, process engineers need to customize existing SPI models or develop new approaches for companyspecific SPI programs. While conducting SPI in the context of the German V-Modell XT, we faced the need to develop a new method for artifact-based SPI. In the process, we found that the construction procedures of SPI models are barely documented, and thus, their successful adaptation solely depends on the process engineers' expertise. With this article, we aim to address this lack of support and provide a structured reflection on our experiences from creating and adopting the Artifact-based Software Process Improvement & Management (ArSPI) model. We present the steps of the construction procedure, the validation, and the dissemination of the model. Furthermore, we detail on the applied methods, the design decisions, and the challenges encountered. By providing a reference procedure and tested methods, we support process engineers with the creation and adoption of SPI approaches.

show abstract

A Survey on the Application of the V-Modell XT in German Government Agencies

Cited by 7 publications

References 2 publications

Towards Artifact Models as Process Interfaces in Distributed Software Projects

Towards Artifact Models as Process Interfaces in Distributed Software Projects

Artifact-based software process improvement and management: a method proposal

Crafting a software process improvement approach-a retrospective systematization

Contact Info

Product

Resources

About