2009Unpublished venueRequires access

A discussion on three critical issues for assuring quality of the users' requirements specification

Qilin Wu, Ming Ying, Jason Wang, Mingzhu Xie, Z. Chen, J. Chen

Open publisher page 2 citations

Abstract

The paper tries to step in a forbidden area of software engineering - to achieve the users' requirements specification of ideal quality in DIRPT (do it right the first time) way. The key idea happens to be a trilogy: modeling business relevant to the purpose of the software to be developed with a compact business model, defining a complete set of inhomogeneous users in conformity with the business model, and eliciting user's requirements by strictly adhering to correspondent user's definition. The result seems encouraging.

About this research paper

What this paper is about

The paper tries to step in a forbidden area of software engineering - to achieve the users' requirements specification of ideal quality in DIRPT (do it right the first time) way. The key idea happens to be a trilogy: modeling business relevant to the purpose of the software to be developed with a compact business model, defining a complete set of inhomogeneous users in conformity with the business model, and eliciting user's requirements by strictly adhering to correspondent user's definition. The result seems encouraging.

Why it matters

OpenAlex reports 2 citations for this work. Citation counts describe recorded attention and do not establish research quality.

Key contribution

A contribution statement is not available in the OpenAlex record.

Method / approach

Method details are not available in the OpenAlex metadata.

Main findings

Findings are not separately available in the OpenAlex metadata.

Limitations

Limitations are not available in the OpenAlex metadata.

Applications

Application details are not available in the OpenAlex metadata.

Available abstract

The paper tries to step in a forbidden area of software engineering - to achieve the users' requirements specification of ideal quality in DIRPT (do it right the first time) way. The key idea happens to be a trilogy: modeling business relevant to the purpose of the software to be developed with a compact business model, defining a complete set of inhomogeneous users in conformity with the business model, and eliciting user's requirements by strictly adhering to correspondent user's definition. The result seems encouraging.

Key concepts: Computer science, Business requirements, Software requirements specification, Key (lock), Quality (philosophy), Software engineering, Requirements engineering, Requirements analysis

Related papers

Back to paper searchBrowse research topicsOriginal source
A discussion on three critical issues for assuring quality of the users' requirements specification — Research Paper | ScholarLens