Abstract—There are two methods that are used to translate the customer requirements into software specification. First one is the Quality Function Deployment (QFD) and the second approach to the identification of software specification comes from the software engineering. Software requirements stipulate what must be accomplished, transformed, produced or provided. It is well documented that requirement engineering saves money. In this paper we have used the Web Surveys approach to elicit the software requirements for a railway projects. In this paper we have also added threat during software requirements elicitation and prioritization.
Index Terms—Software, QFP, Elicitation, and Prioritizationof Software Requirements.
Mohd. Sadiq is with the Jamia Millia Islamia (A Central University), NewDelhi-25, India. (Phone: 09891667600; email: firstname.lastname@example.org).
Javed Ahmad, Guest Lecturer in Computer Engineering, is with the JamiaMillia Islamia (A Central University), New Delhi-25, India. (Phone:09891667600; email: email@example.com).
Abdul Rahman , R. Suman, Shweta Khandelwal are M.Tech. scholarswith the Department of Computer science Engineering, AFSET, Dhauj, Faridabad, Haryana, India. (Phone: +91 9313569986; email:firstname.lastname@example.org, email@example.com,firstname.lastname@example.org).
Cite: Mohd. Sadiq, Javed Ahmad, Abdul Rahman, R. Suman and Shweta Khandelwal, "More on Adding Threat during Software Requirements Elicitation and Prioritization," International Journal of Engineering and Technology vol. 2, no. 3, pp. 286-290, 2010.