Open Access Open Access  Restricted Access Subscription or Fee Access

Negotiation of Requirements and Requirements Prioritization

Rajeshkumar Myilsamy


The purpose of this paper is to bring to the notice of the readers the problem of decision making and requirements prioritisation in the requirements analysis phase. The success or failure of a new system depends on the ever changing and sometimes annoying task of requirements definition. During the development of large systems such as incrementally developed system, there are different versions of the software which are released over a large period of time depending on the customer and business needs. In such an environment, there are more customer requirements which need to be implemented than the available resources and budget. Each customer has different concerns and expectations from the system. When the customer expectations are high, timelines are short, and resources are limited, the developers want to make sure the product contains the most essential requirements. In a scenario where there are many requirements and multiple customers involved, there is a need for a process which can take care of the individual needs of the customers and at the same time create a win-win situation for all customers.


Re-engineering, Requirements Analysis, Requirements Prioritisation, Negotiation Techniques

Full Text:


References, Different types of Software Development lifecycles. Available from: . [15 February 2010]

Alliance Business & Information Solutions, Off the Shelf Packages. Available from: <>. [20 February 2010]

Solomon, Michael G. 2006, ―Project Management Framework Fundamentals‖ in PMP Exam Cram: project Management Professional, 4th Edition, USA.

Baar, Bas De 2006, Using Stakeholder Analysis in Software Project Management. Available from: <>. [1 March 2010].

ZD Net, Introduction to Requirements: Critical details that make or break a project. Available from: . [3 April 2010].

IEEE-STD 610.12-1990, ―Standard Glossary of Software Engineering Terminology‖, 1990, Institute of Electrical and Electronics Engineers.

Regnell, B., Brinkkemper, S. 2005, ―Market-Driven Requirements Engineering for Software Products‖ in Engineering and Managing Software Requirements, Springer-Verlag, Berlin, pp. 287-308.

Data & Analysis Centre for Software, Requirements Trade-offs/Negotiation. Available from: <>. [5 Dec 2009].

Davis, Alan M. 2003, 'The Art of Requirements Triage', in IEEE Xplore, vol. 36, Issue. 3, pp. 42-49. Available from:. [13 March 2010]

Brooks, F.P. (1987). Essence and Accidents of Software Engineering, IEEE Computer, Vol. April 1987, pp. 10-19.

Data & Analysis Centre for Software, Manage Requirements. Available from: <>. [10 Dec 2009].

Simon, H.A (1960), The New Science of Management Decisions, PreciseHall, NJ, USA.

Wiegers, K. (2003), Software Requirements, 2nd Edition, Microsoft Press, Redmond, WA.

Evans R, Park S, Alberts H (1997), ―Decisions not requirements: Decision-centered engineering of computer-based Systems in Proceedings of International Conference on Engineering and Computer-Based Systems”, pp.435-442.

Carlshamre, Pär 2001, A usability perspective on requirements engineering: from methodology to product development. Available from: < > [2 January 2010].

Rexfelt, O., Rosenblad, E. 2005, ―The progress of user requirements through a software development project‖, International Journal of Industrial Ergonomics, vol. 36, 2006, pp. 73-81. Available from: Science Direct. [17 February 2010].

Cooper, R.G., Kleinschmidt, E.J. 2000 ―New product performance: what distinguishes the star products‖, Australian Journal of Management, vol. 25 (1),pp. 17–46.

Wiegers, Karl E., First Things First: Prioritising Requirements. Available from: < > [6 March 2010].

Kononya, G., Sommerville I (1998), Requirements Engineering Processes and Techniques, Wiley, Chichester, UK.

Ngo-The, A. , Ruhe, G. 2005, ―Decision Support in Requirements Engineering‖ in Engineering and Managing Software Requirements, Springer-Verlag, Berlin, pp. 267-286.


  • There are currently no refbacks.

Creative Commons License
This work is licensed under a Creative Commons Attribution 3.0 License.