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

Kuhrmann, Marco; Beecham, Sarah

doi:10.1145/2600821.2600839

Cited by 9 publications

(19 citation statements)

References 13 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…ArSPI Context. Our focus in this paper is the ArSPI artifact Actual Process, which is, together with an overall Vision and a set of Changes, the major input for an improvement project (iteration) [8]. An actual process has a variety of facets: it comprises a process specification, a process realization, and a process in use (Figure 1).…”

Section: Approachmentioning

confidence: 99%

“…Figure 2 shows an example of the stepwise created checklist. The checklist was generated from the ArSPI specification [6] and stepwise completed by the other material. Each (sub-)artifact and (sub-)activity is represented by a row of the spreadsheet.…”

Section: Step 1: the Process Checklistmentioning

confidence: 99%

“…To provide an initial application, we opted for the ArSPI model v0.9 [8] for the purpose of defining the requirements for the next version. The study was conducted as a controlled experiment in a Master's Thesis [5].…”

Section: Study Setupmentioning

confidence: 99%

“…The study was conducted as a controlled experiment in a Master's Thesis [5]. The student was provided with the specification of ArSPI [6], the process's realization as an EPF model, and the deployment package as HTML web-sites and document templates. CMMI v1.3 [2] was selected as an external reference.…”

Section: Study Setupmentioning

confidence: 99%

“…To overcome shortcomings associated with SPI, we recommended concentrating on the artifacts to be developed in SPI projects. For this, we developed a model for Artifact-based Software Process Improvement & Management (ArSPI; [8]). By relying on artifact models, this approach explicitly addresses process-model-related quality questions.…”

Section: Introductionmentioning

confidence: 99%

See 4 more Smart Citations

How do artifact models help direct SPI projects?

Kuhrmann

Richardson

2015

Proceedings of the 2015 International Conference on Software and System Process

Self Cite

View full text Add to dashboard Cite

To overcome shortcomings associated with software process improvement (SPI), we previously recommended that process engineers focus on the artifacts to be developed in SPI projects. These artifacts should define desired outcomes, rather than specific methods. During this prior research, we developed a model for Artifact-based Software Process Improvement & Management (ArSPI). We are now carrying out studies to confirm our claims that ArSPI will provide benefits such as quality assurance. In this paper, we report on an experimental setting in which we developed and analyzed a strategy to use artifact models to direct process model improvement. We analyzed a process specification, the realized model, and the generated electronic process guide. We used ArSPI v0.9 as our process model and the Capability Maturity Model Integration (CMMI) as an external reference to provide a set of overall improvement goals. We propose an effective approach to analyze and improve a process model. In addition, the analysis revealed issues with ArSPI realization, which will be corrected in the next major release.

show abstract

Section: Approachmentioning

confidence: 99%

Section: Step 1: the Process Checklistmentioning

confidence: 99%

Section: Study Setupmentioning

confidence: 99%

Section: Study Setupmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

See 3 more Smart Citations

How do artifact models help direct SPI projects?

Kuhrmann

Richardson

2015

Proceedings of the 2015 International Conference on Software and System Process

Self Cite

View full text Add to dashboard Cite

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 Case Study on Artefact-Based RE Improvement in Practice

Méndez

Wagner

2015

Product-Focused Software Process Improvement

View full text Add to dashboard Cite

Background: Most requirements engineering (RE) process improvement approaches are solution-driven and activity-based. They focus on the assessment of the RE of a company against an external norm of best practices. A consequence is that practitioners often have to rely on an improvement approach that skips a profound problem analysis and that results in an RE approach that might be alien to the organisational needs. Objective: In recent years, we have developed an RE improvement approach (called ArtREPI ) that guides a holistic RE improvement against individual goals of a company putting primary attention to the quality of the artefacts. In this paper, we aim at exploring ArtREPI's benefits and limitations. Method: We contribute an industrial evaluation of ArtREPI by relying on a case study research. Results: Our results suggest that ArtREPI is well-suited for the establishment of an RE that reflects a specific organisational culture but to some extent at the cost of efficiency resulting from intensive discussions on a terminology that suits all involved stakeholders. Conclusions: Our results reveal first benefits and limitations, but we can also conclude the need of longitudinal and independent investigations for which we herewith lay the foundation.

show abstract

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

Cited by 9 publications

References 13 publications

How do artifact models help direct SPI projects?

How do artifact models help direct SPI projects?

Crafting a software process improvement approach-a retrospective systematization

A Case Study on Artefact-Based RE Improvement in Practice

Contact Info

Product

Resources

About