The week's pick
Random Articles
Reseach Article
Adding Threat during Software Requirements Elicitation and Prioritization
| International Journal of Computer Applications |
| Foundation of Computer Science (FCS), NY, USA |
| Volume 1 - Number 9 |
| Year of Publication: 2010 |
| Authors: Mohd. Sadiq, Mohd. Shahid, Shabbir Ahmad |
10.5120/200-339
|
Mohd. Sadiq, Mohd. Shahid, Shabbir Ahmad . Adding Threat during Software Requirements Elicitation and Prioritization. International Journal of Computer Applications. 1, 9 ( February 2010), 50-54. DOI=10.5120/200-339
Abstract
Requirements may be defined as a demand or need. In software engineering, a requirement is a description of what a system should do. System may have dozen to thousands of requirements. Software requirements stipulate what must be accomplished, transformed, produced or provided. In the field of software engineering researchers, academicians and scientist have developed many models and framework to elicit and prioritize the software requirements. It is well documented that requirement engineering saves money. There are several techniques to elicit the software requirements like JAD, misuse, RAD etc. In this paper we have used the JAD approach to elicit the software requirements. In this paper we have proposed a framework to elicit the software requirements and also to prioritize the software requirements. The proposed framework will rank the requirements by the relative level of threat associated with each requirement.
References
- 1. A.M. Hickey, A.M. Davis, "Elicitation Technique Selection: How Do Experts Do It?" Proceedings of the 11th IEEE International Requirements Engineering Conference, 2003.
- 2. Ann M. Hickey, Alan M. Davis, "Requirements Elicitation and Elicitation technique selection: A Model for Two knowledge-Intensive Software development Process", Proceedings of the 36th IEEE International Conference on System Sciences, 2002.
- 3. Beichter F. et al, " SLAN-4-A Software Specification and Design Language", IEEE Transaction on Software Engineering, SE- 10,2, 1994, pp 155-162.
- 4. Bruce White, "QFD for small business", Transaction from the 18 Symposium on QFD, 2006.
- 5. C.Kuloor, Armin Eberlein, "Requirements Engineering for Software Product Lines", The University of Calgary, Canada.
- 6. D. Firesmith, " Prioritizing Requirements", Journal of Object Technology, Volume 3, No.8, September 2004
- 7. Daya Gupta, Mohd Sadiq, "Software Risk Assessment and Estimation Model", International Conference on Computer Science and Information Technology, IEEE Computer Society, Singapore, 2008. pp 963-967
- 8. Gunnar Peterson, John Steven, "Defining Misuse within the Development Process", IEEE Security and Privacy, 2006.
- 9. http://en.wikipedia.org/wiki/Analytic_Hierarchy_Process
- 10. Ian Alexander, "Misuse Cases Help to Elicit Non-functional Requirements", Computing and Control Engineering 2003.
- 11. J. Karlsson, "Software Requirements Prioritizing", Proceedings of the International Conference on Requirement Engineering, 1996.
- 12. J. Karlsson, C. Wohlin, B. Regnell, "An Evaluation of Methods for Prioritizing Software Requirements", Elsvier Journal of Information and Software Technology, 1998, pp. 939-947.
- 13. J.J.Pauli, D.Xu, "Misuse Case-Based design and Analysis of secure Software Architecture", Proceedings of the IEEE International Conference on Information Technology: Coding and Computing (ITCC05), 2005.
- 14. LI Zong-yong, WANG Zhi-xue, YANG-ying, WU Yue, LIU Ying, " Towards multiple ontology Framework for Requirements Elicitation and Reuse", 31st IEEE Annual International Computer Software and Application Conference, 2007.
- 15. Mohd. Sadiq, Mohd. Shahid, "Elicitation and Prioritization of Software requirements", International Journal of Recent Trends in Engineering, Finland, 2009.
- 16. Mohd. Sadiq, Shabina Ghafir, Mohd. Shahid, "An Approach for Eliciting Software Requirements and its Prioritization using Analytic Hierarchy Process", IEEE International Conference on Advances in Recent Technologies in Communication and Computing, 2009, ACEEE annual world congress on Engineering and Technology , Kerala, India.
- 17. Mohd. Sadiq, Shabina Ghafir, Mohd. Shahid," A Framework to Prioritize the software Requirements using Quality Function Deployment", National Conference on Recent Development in Computing and its Application, 2009, organized by Jamia Hamdard, Delhi, India.
- 18. Nancy R. Mead, "Requirements Elicitation Introduction", Software Engineering Institute Carnegie Mellon University, 2008-2009.
- 19. P.Rajagopal, R.Lee, Thomas Ahlswede, Chia-Chu Chiang, D. Karolak, " A New Approach for Software Requirements Elicitation", Proceedings of the 6th IEEE International Conference on Software Engineering, Artificial Intelligence, Networking and Parallel/ Distributed Computing, 2005.
- 20. T. L. Saaty, "The Analytic Hierarchy process", New York, McGraw-Hill, 1980.
- 21. W.R. Friedrich, J. A. Van der Poll, "Towards a Methodology to Elicit Tacit Domain knowledge from Users", Interdisciplinary Journal of Information, Knowledge, and Management, Volume2, 2007.
- 22. Xiaoqing frank Liu, "Software Quality Development", IEEE Potentials, 2008.
- 23. Md. Rizwan Beg, Qamar Abbas, Ravi Prakash Verma, " An approach for Requirements Prioritization using B-Tree", IEEE First International Conference on Emerging Trends in Engineering and Technology 2008.
- 24. Nancy R. Mead, Dan Shoemaker, Jeffrey Ingalsbe, " Ensuring Cost Efficient and Secure Software through Student Case Studies in Risk and Requirements Prioritization", IEEE Proceedings of the 42 Hawaii International Conference on System Sciences-2009.
Index Terms
Keywords