A New Standard for Quality Requirements

Bøegh, Jørgen

doi:10.1109/ms.2008.30

Cited by 65 publications

(46 citation statements)

References 1 publication

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…LSPCM is partly based on the ISO/IEC 14598 and ISO 9126 standards and can therefore be compared with these and the newer ISO/IEC 25000 (Software product Requirements and evaluation -SQuaRE) that combines and relates the two previous standards. In contrast to [3] and [7] application of LSPCM is more efficient and can also be used to assess more common information system development. A more detailed comparison of LSPCM and existing IV&V approaches can be found in Section V.…”

Section: Lspcmmentioning

confidence: 99%

“…Assessment of the software development process is intensively studied in the literature including, e.g., [8], [16], [7]. Assessment of software artifacts by thirdparty assessors is known as independent verification and validation or IV&V [3].…”

Section: Related Workmentioning

confidence: 99%

“…Popular approaches to requirements quality assessment include checklists and questionnaires originating from requirements engineering books [18], [19], [20], or guidelines and standards [7], [21], [22], [23], [24]. Thus, the theory of writing high quality requirements is well-established.…”

Section: Related Workmentioning

confidence: 99%

See 2 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: Lspcmmentioning

confidence: 99%

Section: Related Workmentioning

confidence: 99%

See 1 more Smart Citation

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

“…An ontology provides a common vocabulary for specifying requirements for a family of applications in the domain. Another research issue is the identification and specification of requirements and their quality properties [3,7,29,35,39], to establish the goals to be attained by a quality software product. In Chirinos et al [8], a conceptual model is proposed to identify quality requirements for software products (RECLAMO), based on the quality views of ISO/IEC 9126-1 [23], presented in Figure 1.…”

Section: Introductionmentioning

confidence: 99%

REquirements, Aspects and Software Quality: the REASQ model.

Castillo¹,

Losavio²,

Matteo³

et al. 2010

JOT

Self Cite

View full text Add to dashboard Cite

Object-oriented analysis and design have been more concerned with system functionality, neglecting non-functional aspects; the result is code which is tangled and difficult to maintain, contradicting main principles of object orientation. Aspect Oriented Software Development (AOSD) proposes the early specification of non-functional requirements. However, a standard and homogenous vision of the AOSD terminology is still missing. The goal of this work is to integrate AOSD concepts, classic requirements engineering notions, and the new standard ISO/IEC 25030 on software quality requirements.The main result of this study is the REASQ (REquirements, Aspects and Software Quality) conceptual model, expressed in UML. All the modelling concepts are formalized into three related ontologies, representing the ambits of aspect-orientation, software quality and requirements engineering. The ontologies can be used as an umbrella to specify quality requirements in aspect-oriented engineering processes.

show abstract

“…Non-functional requirements relate to "how" functions are performed such as performance requirements, specific quality requirements, and constraints (Azuma, 2004;Boegh, 2008;Glinz, 2008;ISO/IEC, 2007). Examples of non-functional (quality-based) requirements include using a content management system for easy content update by a novice user, using radio-buttons for choice selection and a user-interface with "sleek, modern graphics related to motorcycles and cars" for a race-car import company website.…”

Section: Requirementsmentioning

confidence: 99%

Eliciting User Requirements Using Appreciative Inquiry

Gonzales¹

View full text Add to dashboard Cite

A New Standard for Quality Requirements

Cited by 65 publications

References 1 publication

Requirements Certification for Offshoring Using LSPCM

Requirements Certification for Offshoring Using LSPCM

REquirements, Aspects and Software Quality: the REASQ model.

Eliciting User Requirements Using Appreciative Inquiry

Contact Info

Product

Resources

About