Proposing a Systematic Approach to Verify Software Requirements


Identifying stakeholder’s needs, eliciting, categorizing and translating them into specifications is the requirement analysis process. Requirement analysis can be a long and arduous process during which many delicate psychological skills are involved. For any software, it is important to identify all stakeholders, collect their requirements and ensure they understand the implications of the software. The gap between stakeholders’ vision of the proposed software and the analysis's depiction of that software is the cause of shortcomings in analysis. If the requirements specified by analysts can be tested against stakeholders' expectations, then this gap might be narrowed, and better solutions might be resulted. This paper discusses the impact of the activities of the analysis phase on the development process and on the software itself. It describes the development of the ReqVerifier tool and proposes a systematic approach on how to test software requirements and verify them against stakeholders’ vision in order to develop a good software requirement for a quality software.

Share and Cite:

Al-Khanjari, Z. (2014) Proposing a Systematic Approach to Verify Software Requirements. Journal of Software Engineering and Applications, 7, 218-224. doi: 10.4236/jsea.2014.74023.

Conflicts of Interest

The authors declare no conflicts of interest.


[1] Saeed, S., Khawaja, F.M. and Mahmood, Z. (2012) A Review of Software Quality Methodologies. In: Alsmadi, I., Ed., Advanced Automated Software Testing: Frameworks for Refined Practice, Information Science Reference, Hershey, 129-150.
[2] Alsmadi, I. and Saeed, S. (2013) A Software Development Process for Open Source and Open Competition Projects. International Journal of Business Information Systems, 12, 110-122.
[3] Beichter, F.W., Herzog, O. and Petzsch, H. (1994) SLAN-4 A Software Specification and Design Language. IEEE Transaction on Software Engineering, 10, 155-162.
[4] Pressman, R. (2001) Software Engineering: A Practitioner’s Approach. McGraw-Hill, New York.
[5] Christel, M. and Kang, K. (1992) Issues in Requirements Elicitation. Technical Report, CMU/SEI-92-TR-012, ESCTR-92-012.
[6] Alfeche, R. (1997) Requirements Engineering: A Good Practice Guide. John Wiley & Sons, Hoboken.
[7] Kotonya, G. and Sommerville, I. (1998) Requirements Engineering: Processes and Techniques. John Wiley & Sons, Chichester.
[8] Wiegers, K.E. (2003) Software Requirements. 2nd Edition, Microsoft Press, Redmond.
[9] Stellman, A. and Greene, J. (2005) Applied Software Project Management. O’REILLY, Sebastopol.
[10] Abran, A. and Moore, J. (2005) Chapter 2: Software Requirements. John Wiley & Sons, Hoboken.
[11] Gorschek, T., Garre, P., Larsson, S. and Wohlin, C. (2007) Industry Evaluation of the Requirements Abstraction Model. Requirements Engineering Journal, 12, 163-190.
[12] Zagajsek, B. Separovic, K. and Car, Z. (2007) Requirements Management Process Model for Software Development Based on Legacy System Functionalities. 9th International Conference on Telecommunications (ConTEL 2007), Zagreb, 13-15 June 2007, 115-122.
[13] Jiang, X. (2008) Modeling and Application of Requirements Engineering Process Metamodel. IEEE International Symposium on Knowledge Acquisition and Modeling Workshop (KAM Workshop, 2008). Wuhan, 21-22 December 2008, 998-1001.
[14] Cheng, J. and Liu, Q. (2008) Using Stakeholder Analysis for Improving State Chart Merging in Software Requirement Management. The 9th International Conference for Young Computer Scientists (ICYCS, 2008), Beijing, 18-21 November 2008, 1217-1222,
[15] Mishra, D., Mishra, A. and Yazici, A. (2008) Successful Requirement Elicitation by Combining Requirement Engineering Techniques. International Conference on the Applications of Digital Information and Web Technologies (ICADIWT’08), Ostrava, 4-6 August 2008, 258-263.
[16] Berkovich, M., Leimeister, J. and Krcmar, H. (2009) Suitability of Product Development Methods for Hybrid Products as Bundles of Classic Products, Software and Service Elements. Proceedings of the ASME 2009 International Design Engineering Technical Conferences & Computers and Information in Engineering Conference. IDETC/CIE 2009, 30 August-2 September 2009, San Diego, 885-894.
[17] Pandey, D., Suman, U. and Ramani, A. (2010) 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), Kottayam, 16-17 October 2010, 287-291.
[18] Pavanasam, V., Subramaniam, C., Srinivasan, T. and Jain, J. (2010) Membrane Computing Model for Software Requirement Engineering. 2nd International Conference on Computer and Network Technology (ICCNT), Chennai, 23-25 April 2010, 487-491.
[19] Torkar, R., Gorschek, T., Feldt, R., Svahnberg, M., Akbar Raja, U. and Kamran, K. (2012) Requirements Traceability: A Systematic Review and Industry Case Study. IJSEKE, 22, 1-49.
[20] Gorschek, T., Gomes, A., Pettersson, A. and Torkar, R. (2012) Introduction of a Process Maturity Model for Market-Driven Product Management and Requirements Engineering. Journal of Software: Evolution and Process, 24, 83-113.
[21] Khan, M., Khalid, M. and Haq, S. (2013) Review of Requirements Management Issues in Software Development. International Journal of Modern Education and Computer Science.
[22] Young, R. (2004) The Requirements Engineering Handbook. Artech house. Inc., Norwood.

Copyright © 2022 by authors and Scientific Research Publishing Inc.

Creative Commons License

This work and the related PDF file are licensed under a Creative Commons Attribution 4.0 International License.