Review of Requirements Management Issues in Software Development

Full Text (PDF, 223KB), PP.21-27

Views: 0 Downloads: 0


M. N. A. Khan 1,* Muhammad Khalid 1 Sami Ulhaq 1

1. Department of Computing Shaheed Zulfikar Ali Bhutto Institute of Science and Technology (SZABIST), Islamabad, Pakistan

* Corresponding author.


Received: 23 Oct. 2012 / Revised: 5 Nov. 2012 / Accepted: 4 Dec. 2012 / Published: 8 Jan. 2013

Index Terms

Requirements Engineering, Requirements Management, Extreme Programming, Software Engineering


A requirement is a capability to which a product or service should conform to. A meticulous consideration to requirements engineering acts as a backbone of software projects. Ambiguous and unrealistic requirements are major source of failure in the software-intensive systems. Requirements engineering processes are complex as most of the requirements engineering documentation is written in natural languages which are less formal and often distract the designers and developers. Requirements management is a continuous process throughout the project lifecycle and relates to documenting, analyzing, tracing and prioritizing requirements and then finally controlling changes. The main issues related to requirements management are usually social, political and cultural. Software requirement engineers who gather the requirements generally consider that such issues are beyond the scope of their profession as they deem them within the project management ambit. In this study, we highlight the management issues that arise in the requirements engineering process and explore the possibilities to tackle them amicably. The study is supplemented with a critical review of the existing methodologies for resolving and managing software requirements.

Cite This Paper

Muhammad Naeem Ahmed Khan, Muhammad Khalid, Sami ul Haq, "Review of Requirements Management Issues in Software Development", International Journal of Modern Education and Computer Science (IJMECS), vol.5, no.1, pp.21-27, 2013. DOI:10.5815/ijmecs.2013.01.03


[1]R. R. Young, The Requirements Engineering Handbook, ARTECH HOUSE, INC. 685 Canton Street Norwood, MA 02062, 2004.
[2]G. Kotonya and I. Sommerville, Requirements Engineering: Processes and Techniques, Chichester, UK: John Wiley & Sons, 1998.
[3]I. Sommerville and P. Sawyer, Requirements Engineering: A Good Practice Guide, New York: John Wiley & Sons, 1997.
[4]K. E. Wiegers, Software Requirements, 2nd ed., Redmond, W A: Microsoft Press, 2003.
[5]F. W. Beichter, O. Herzog and H. Petzsch, “SLAN-4 A Software Specification and Design Language”, IEEE Transaction on Software Engineering, Volume 10, Number 1, pp 155-162, 1994.
[6]P. B. Crossby, Quality is Free, New York: McGraw-Hill, 1979.
[7]J. M. Juran and F. M. Gryna, Quality planning and analysis: From product development through usage, McGraw-Hill, New York, 1970.
[8]D. Mishra, A. Mishra and A. Yazici, “Successful Requirement Elicitation by Combining Requirement Engineering Techniques”, International Conference on the Applications of Digital Information and Web Technologies (ICADIWT'08), pp. 258-263, 2008.
[9]B. Zagajsek, K. Separovic and Z. Car, “Requirements Management Process Model for Software Development Based on Legacy System Functionalities”, 9th International Conference on Telecommunications (ConTEL 2007) pp. 115 - 122, 13-15 June 2007.
[10]D. Pandey, U. Suman and A. K. Ramani, “An Effective Requirement Engineering Process Model for Software Development and Requirements Management”, International Conference on Advances in Recent Technologies in Communication and Computing (ARTCom, 2010), pp. 287 - 291, 16-17 October 2010.
[11]J. Cheng and Q. Liu, “Using Stakeholder Analysis for Improving Statechart Merging in Software Requirement Management”, The 9th International Conference for Young Computer Scientists (ICYCS, 2008), pp. 1217 - 1222, School of Software, Tsinghua University, Beijing, China, 18-21 November 2008.
[12]C-W Lu, W. C. Chu and C-H Chang, “A Model-based Object-oriented Approach to Requirement Engineering (MORE)”, 31st Annual International Computer Software and Applications Conference (COMPSAC 2007), Hsiuping Institute of Technology, Taichung, Volume 1, pp. 153 - 156, 24-27 July 2007.
[13]X. Jiang, “Modeling and Application of Requirements Engineering Process Metamodel”, IEEE International Symposium on Knowledge Acquisition and Modeling Workshop (KAM Workshop, 2008), Department of Commanding Communication, PLA Commanding Communication Academy, Wuhan, China, pp. 998 - 1001, 21-22 December 2008.
[14]G. Lu and F. Yuan, “Comparison of Requirement Items based on the Requirements Change Management System of QONE”, Second World Congress on Software Engineering (WCSE), Institute of Computer Technology, Chinese Academy of Science, Beijing, China Volume 2, pp. 211 - 215, 19-20 December 2010.
[15]V. Pavanasam, C. Subramaniam, T. Srinivasan, J. K. Jain, “Membrane Computing Model for Software Requirement Engineering”, Second International Conference on Computer and Network Technology (ICCNT), Sathyabama University, Chennai, India, pp. 487 - 491, 23-25 April 2010.
[16]E-S Lee and J-M Bae, “Design Opportunity Tree for Requirement Management and Software Process Improvement”, International Conference on Multimedia and Ubiquitous Engineering (MUE'07), Soongsil University, Seoul, pp. 395 - 400, 26-28 April 2007..
[17]M. F. Tchidi and Z. He, “The Requirements Engineering Process Model Based on Design for Six Sigma”, The 2nd IEEE International Conference on Information Management and Engineering (ICIME, 2010), Tianjin University, Tianjin, China, pp. 287 - 290, 16-18 April 2010.
[18]T. Schummer and S. Lukosch, “Supporting the Social Practices of Distributed Pair Programming”, In Groupware: Design, Implementation, and Use, volume 5411/2008 of Lecture Notes in Computer Science, pages 83–98. Springer, Berlin / Heidelberg, March 2008.
[19]C. Murphy, D. Phung and G. Kaiser, “A Distance Learning Approach to Teaching eXtreme Programming”, ITiCSE, June 30-July 2, 2008, Madrid, Spain. ACM. 2008.