Requirement engineering: The emerging wisdom [Guest Editor's introduction]

Siddiqi, Jawed I. A.

doi:10.1109/ms.1996.506458

Cited by 104 publications

(45 citation statements)

References 8 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…Yet there has been little progress to date, either theoretical or practical, on the mechanisms for prioritizing software requirements [2]. In a review of the state of the practice in requirements engineering, Lubars et al [3] found that many organizations believe that it is important to assign priorities to requirements and to make decisions about them according to rational, quantitative data.…”

Section: Motivationmentioning

confidence: 99%

An evaluation of methods for prioritizing software requirements

Karlsson¹,

Wohlin²,

Regnell³

1998

Information and Software Technology

320

266

View full text Add to dashboard Cite

This article describes an evaluation of six different methods for prioritizing software requirements. Based on the quality requirements for a telephony system, the authors individually used all six methods on separate occasions to prioritize the requirements. The methods were then characterized according to a number of criteria from a user's perspective. We found the analytic hierarchy process to be the most promising method, although it may be problematic to scale-up. In an industrial follow-up study we used the analytic hierarchy process to further investigate its applicability. We found that the process is demanding but worth the effort because of its ability to provide reliable results, promote knowledge transfer and create consensus among project members. ᭧ 1998 Elsevier Science B.V.

show abstract

Section: Motivationmentioning

confidence: 99%

An evaluation of methods for prioritizing software requirements

Karlsson¹,

Wohlin²,

Regnell³

1998

Information and Software Technology

320

266

View full text Add to dashboard Cite

show abstract

“…Traditionally, RE assumes an objective reality [21,20,84,62,87,4,52,77,90,67]. An objective reality is a reality that is assumed to exist independently of any observer.…”

Section: Traditional Rementioning

confidence: 99%

Requirements engineering for organizational transformation

Ramos

Berry

Carvalho

2005

Information and Software Technology

View full text Add to dashboard Cite

Traditional approaches to requirements elicitation stress systematic and rational analysis and representation of organizational context and system requirements. This paper argues that the introduction of any computer-based system to an organization transforms the organization and changes the work patterns of the system's users in the organization. These changes interact with the users' values and beliefs and trigger emotional responses which are sometimes directed against the computerbased system and its proponents. The paper debunks myths about how smoothly such organizational transformations take place, describes case studies showing how organizational transformation really takes place, and introduces and confirms by case studies some guidelines for eliciting requirements and the relevant emotional issues for a computer-based system that is being introduced into an organization to change its work patterns.

show abstract

“…Requirements engineering (RE) is generally accepted to be the most critical and complex process within the development of embedded systems, see, for example, [4,5,6]. One reason for this is that in requirements engineering the most diverse set of product demands from the most diverse set of stakeholders has to be considered, making the requirements engineering process both multidisciplinary and complex.…”

Section: Introductionmentioning

confidence: 99%