Experiences on Analysis of Requirements Quality

Heck, Petra; Parviainen, Päivi

doi:10.1109/icsea.2008.32

Cited by 7 publications

(6 citation statements)

References 11 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…While LSPCM as presented in [4], [5] covers all types of software artifacts, so far for offshoring only requirements have been considered. As the future work we plan to apply LSPCM to additional software artifacts used at hand-over moments in the offshoring projects, e.g., high-level design and code.…”

Section: Discussionmentioning

confidence: 99%

“…The emphasis is on the quality of the product, not the process or people. In this section we briefly review LSPCM-the reader is referred to [4], [5] for further details of the model. The complete model is described in [6].…”

Section: Lspcmmentioning

confidence: 99%

“…While LSPCM has been successfully applied in the past to assess quality of user requirements [4], it had yet to be applied to offshored development. To assess the applicability of LSPCM to offshored development we have used it in a number of comparable case studies; industrial offshored software development projects which are discussed in Sections III-A through III-C. Involved development teams were comparable, the requirements effort ratio was similar, and also the software itself had an average complexity for all 3 cases.…”

Section: Case Studiesmentioning

confidence: 99%

“…LSPCM, LaQuSo Software Product Certification Model, is a software product certification model introduced in [4] and further developed in [5]. The emphasis is on the quality of the product, not the process or people.…”

Section: Lspcmmentioning

confidence: 99%

“…To support our claim we did a postmortem analysis on the requirements of three offshoring projects which were not deployed yet and for two first cases predicted their successfulness using LSPCM [4], [5]. Section II describes more details about LSPCM.…”

Section: Introductionmentioning

confidence: 99%

See 4 more Smart Citations

Requirements Certification for Offshoring Using LSPCM

Serebrenik

Mishra

Delissen

et al. 2010

2010 Seventh International Conference on the Quality of Information and Communications Technology

View full text Add to dashboard Cite

Abstract-Requirements hand-over is a common practice in software development offshoring. Cultural and geographical distance between the outsourcer and supplier, and the differences in development practices hinder the communication and lead to the misinterpretation of the original set of requirements.In this article we advocate requirements quality certification using LSPCM as a prerequisite for requirements hand-over. LSPCM stands for LaQuSo Software Product Certification Model that can be applied by non-experienced IT assessors to verify software artifacts in order to contribute to the successfulness of the project. To support our claim we have analyzed requirements of three offshoring projects using LSPCM. Application of LSPCM revealed severe flaws in one of the projects. The responsible project leader confirmed later that the development significantly exceeded time and budget. In the other project no major flaws were detected by LSPCM and it was confirmed that the implementation was delivered within time and budget.Application of LSPCM to the projects above also allowed us to refine the model for requirements hand-over in software development offshoring.

show abstract

Section: Discussionmentioning

confidence: 99%

Section: Lspcmmentioning

confidence: 99%

Section: Case Studiesmentioning

confidence: 99%

Section: Lspcmmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

See 3 more Smart Citations

Requirements Certification for Offshoring Using LSPCM

Serebrenik

Mishra

Delissen

et al. 2010

2010 Seventh International Conference on the Quality of Information and Communications Technology

View full text Add to dashboard Cite

show abstract

7.7.3 The Requirements Engineering Process Design for Six Sigma

Yurt

Brouse

2012

INCOSE International Symp

View full text Add to dashboard Cite

Many software projects continue to be over budget, over schedule, and fail despite the tools created for managing the life cycle and the continuous improvement efforts. A great number of the problems in systems development projects is caused by poor requirements management processes. The failure to understand the reasons behind the low quality requirements, to understand the relationship between the quality of requirements and requirements engineering process, and to take no actions for increasing the quality of requirements by eliminating the causes behind those effects result in increased cost, low reliability and maintainability, and a system that does not meet the stakeholders' requirements. The aim of this research, the Requirements Engineering Process Design for Six Sigma (REDFSS), is to improve the quality of requirements using Six Sigma methodology along with a set of metrics and tools to identify the low quality requirements and offer corrective actions to overcome the quality issues and identify and eliminate the causes for defects and help requirements engineers to make better judgments.

show abstract