doi: 10.7763/IJET.2010.V2.135
More on Adding Threat during Software Requirements Elicitation and Prioritization
Mohd. Sadiq
1
,
Javed Ahmad
2
,
Abdul Rahman
2
,
R. Suman
2
,
Shweta Khandelwal
2
- 1 the Jamia Millia Islamia (A Central University), NewDelhi-25, India
- 2 the JamiaMillia Islamia (A Central University), New Delhi-25, India
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.
Keywords
- Software
- QFP
- Elicitation
- and Prioritizationof Software Requirements
How to 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. https://doi.org/ 10.7763/IJET.2010.V2.135
Copyright & License
Copyright © 2010 by the authors. This is an open access article distributed under the Creative Commons Attribution License which permits unrestricted use, distribution, and reproduction in any medium, provided the original work is properly cited (CC BY 4.0).