Development of Non-functional Requirements for Decision Support Systems

Decision Support System (DSS) are interactive software systems that are built to assist the management of an organization in the decision making process when faced with nonroutine problems in a specific application domain. Non-functional requirements (NFRs) for a DSS deal with the desirable qualities and restrictions that the DSS functionalities must satisfy. Unlike the functional requirements, which are tangible functionalities provided by the DSS, NFRs are often hidden and transparent to DSS users but affect the quality of the provided functionalities. NFRs are often overlooked or added later to the system in an ad hoc manner, leading to a poor overall quality of the system. In this paper, we discuss the development of NFRs as part of the requirements engineering phase of the system development life cycle of DSSs. To help eliciting NFRs, we provide a comprehensive taxonomy of NFRs for DSSs.

Authors:



References:
[1] R. Sprague, "A framework for the development of decision support
systems", MIS Quarterly, Vol. 4, Number 4, December 1980.
[2] L. Chung, B.A. Nixon, E. Yu, J. Mylopoulos, Non-Functional
Requirements in Software Engineering, Kluwer Academic Publishers,
Dordrecht, 2000.
[3] H. Becha and D. Amyot, "Non-functional properties in service oriented
architecture - A consumer-s perspective", to appear in the Journal of
Software, 2012.
[4] G. Booch, I. Jacobson and J. Rumbaugh, The UML User Guide,
Addison-Wesley, 1999.
[5] ITU-T, Recommendation Z.150, User Requirements Notation (URN) -
Language Requirements and Framework, Geneva, 2003.
[6] S. Robertson and J. Robertson, Mastering the Requirements Process,
Addison-Wesley, 1999.
[7] K. Saleh, Software Engineering, J. Ross Publishing, USA, 2009.
[8] K. Saleh and A. Al-Zarouni, "Capturing non-functional requirements
using the user requirement notation", Proceedings of the International
Research Conference on Innovations in Information Technology (IIT
2004), Dubai, Oct 2004, pp. 222-230.