Software development cycle is based on the software requirements. Requirement elicitation is first and most important activity in the requirement engineering. If the requirements are efficiently elicited and managed then the stakeholders application can be accomplished within time and budget. If the requirements are not complete, consistent and correct then projects fail because they not meet the user needs. Requirement is define as the needs of customer. Requirement elicitation techniques and tools are used for correct and complete requirement gathering. Many requirement elicitation techniques and tools are available. This study based on the understanding of requirement gathering techniques and tools. The paper also summarizes the comparison of the requirement elicitation techniques and software requirement tools. Comparison of requirement elicitation techniques and tools are based on the various parameters.
Published in | Software Engineering (Volume 3, Issue 2) |
DOI | 10.11648/j.se.20150302.11 |
Page(s) | 7-11 |
Creative Commons |
This is an Open Access article, distributed under the terms of the Creative Commons Attribution 4.0 International License (http://creativecommons.org/licenses/by/4.0/), which permits unrestricted use, distribution and reproduction in any medium or format, provided the original work is properly cited. |
Copyright |
Copyright © The Author(s), 2015. Published by Science Publishing Group |
Software Requirement Engineering, Requirement Elicitation, Requirement Tools
[1] | D. Duarte, C. Farinha, M. M. da silva, and A.R. da silva,“Collaborative Requirement Elicitation with visualization Techniques,” IEEE, pp. 343 - 348 2012 |
[2] | P. Zave, “Classification of Research Efforts in Requirements Engineering,” ACM Computing Surveys, vol.29, no. 44, pp. 315-321, 1997 |
[3] | C. M. Zapata, B. M. Losada and G. G. Calderón, “An approach for using procedure manuals as a source for Requirements Elicitation,” pp.1-8, 2012. |
[4] | S. Khan, A. B. Dulloo, and M. Verma, “Systematic Review of Requirement Elicitation Techniques,” vol. 4, no. 2, pp. 133–138, 2014. |
[5] | N. Mulla, and S. Girase, “Comparison of various Elicitation Techniques and Requirement Prioritisat ion Techniques,” IJERT,vol. 1, no. 3, pp. 1–8, 2012. |
[6] | T. U. Rehman, M. N. A. Khan, and N. Riaz, “Analysis of Requirement Engineering Processes, Tools/Techniques and Methodologies,” Int. J. Inf. Technol. Comput. Sci., vol. 5, no. 3, pp. 40–48, Feb. 2013 |
[7] | A. Amber, I. S. Bajwa, M.S. Naweed and T. Bashir, “Requirments Elicitation Methods,” MIMT , 2011. |
[8] | M. U. Bokhari and S. T. Siddiqui, “A Comparative Study of Software Requirements Tools for Secure Software Development,” vol. 2, no. 2, 2010. |
[9] | Y. Sharma, and A. K. Sharma, “Evaluation of the Software Requirement Tools,” vol. 3, no. 3, pp. 950–954, 2014. |
[10] | B. J. M. Abma, “Evaluation of requirements management tools with support for traceability-based change impact analysis,” 2009. |
[11] | http://www.componentsource.com/products /analyst-pro/index.html [access on 12-6-2014] |
[12] | M. U. Bokhari and S. T. Siddiqui, “A Comparative Study of Software Requirements Tools for Secure Software Development,” 2009. |
[13] | F. A. and R. Razali, “A Practical Guide to Requirements Elicitation Techniques Selection - An Empirical Study,” Middle-East J. Sci. Res., vol. 11, no. 8, p. 9, 2012. |
[14] | D. Zowghi and C. Coulin, “2 Requirements Elicitation: A Survey of Techniques, Approaches, and Tools,” pp.19-46, 2005. |
[15] | M. Asim and F. Sahar, “Advance Topics in Software Engineering Topic: Requirement Elicitation Techniques Case Study: Online Vehicle Trading Abstract :,” pp. 1–24. |
[16] | T. U. Rehman, M. N. A. Khan, and N. Riaz, “Analysis of Requirement Engineering Processes, Tools/Techniques and Methodologies,” Int. J. Inf. Technol. Comput. Sci., vol. 5, no. 3, pp. 40–48, Feb. 2013 |
[17] | L. Driscoll, “Introduction to Primary Research: Interviews Introduction to Primary Research: Observations, Surveys, and Interviews,” vol. 2, 2011. |
[18] | F. N. Ogwueleka, F. N. Ogwueleka “Requirement elicitation problems in software development - A case study of a GSM service provider,” vol. 1, no. 8, pp. 599–605, 2012. |
[19] | T. Tuunanen, “A New Perspective on Requirements Elicitation Methods” vol. 5, no. 3, pp. 45–62, 2003. |
[20] | Z. Zhang, “Effective Requirements Development - A Comparison of Requirements Elicitation techniques,” Tampere, Finland, INSPIRE, pp. 225–240, 2007. |
[21] | C. L. Paul, “Investigation of Applying the Delphi Method to a New Card Sorting Technique,” pp. 1–19, 2007. |
[22] | U. Sajjad, and M. Q. Hanif, “Issues and Challenges of Requirement Elicitation in Large Web Projects,” 2010. |
[23] | V. VandenAbeele, and B. Zaman “Laddering the User Experience !,”,2009 |
[24] | S. Arif., Q. Khan, and S.A.K. Gahyyur, “Requirements Engineering Processes, Tools/ Technologies & Methodologies,” IJRIC, vol. 2, no. 1, pp. 41-56, 2010 |
[25] | O. Tomico, E. Karapanos , P. Lévy , N. Mizutani, and T. Yamanaka, “The Repertory Grid Technique as a Method for the Study of Cultural Differences,”vol. 3, no. 3, 2009 |
[26] | S. Tiwari, S. S. Rathore, and A. Gupta, “Selecting Requirement Elicitation Techniques for Software Projects,” CONSEG, pp. 1 – 10, 2012. |
[27] | J. W. Creswell, “Qualitative, quantitative, and mixed methods approaches,” 2013 |
[28] | S. ARIF, Q. KHANS. A. K. Gahyyur, “Requirements Engineering Methodologies,” IJRIC, 2010. |
[29] | D. Zowghi and C. Coulin, “2 Requirements Elicitation: A Survey of Techniques, Approaches, and Tools,” pp.19-46, 2005 |
[30] | T. Keller, “Contextual Requirements Elicitation An Overview,” 2011. |
[31] | S. G. Gunda, “Requirements Engineering: Elicitation Techniques,” 2008. |
APA Style
Mateen Ahmed Abbasi, Javeria Jabeen, Yasir Hafeez, Dur-e-Benish Batool, Naila Fareen. (2015). Assessment of Requirement Elicitation Tools and Techniques by Various Parameters. Software Engineering, 3(2), 7-11. https://doi.org/10.11648/j.se.20150302.11
ACS Style
Mateen Ahmed Abbasi; Javeria Jabeen; Yasir Hafeez; Dur-e-Benish Batool; Naila Fareen. Assessment of Requirement Elicitation Tools and Techniques by Various Parameters. Softw. Eng. 2015, 3(2), 7-11. doi: 10.11648/j.se.20150302.11
@article{10.11648/j.se.20150302.11, author = {Mateen Ahmed Abbasi and Javeria Jabeen and Yasir Hafeez and Dur-e-Benish Batool and Naila Fareen}, title = {Assessment of Requirement Elicitation Tools and Techniques by Various Parameters}, journal = {Software Engineering}, volume = {3}, number = {2}, pages = {7-11}, doi = {10.11648/j.se.20150302.11}, url = {https://doi.org/10.11648/j.se.20150302.11}, eprint = {https://article.sciencepublishinggroup.com/pdf/10.11648.j.se.20150302.11}, abstract = {Software development cycle is based on the software requirements. Requirement elicitation is first and most important activity in the requirement engineering. If the requirements are efficiently elicited and managed then the stakeholders application can be accomplished within time and budget. If the requirements are not complete, consistent and correct then projects fail because they not meet the user needs. Requirement is define as the needs of customer. Requirement elicitation techniques and tools are used for correct and complete requirement gathering. Many requirement elicitation techniques and tools are available. This study based on the understanding of requirement gathering techniques and tools. The paper also summarizes the comparison of the requirement elicitation techniques and software requirement tools. Comparison of requirement elicitation techniques and tools are based on the various parameters.}, year = {2015} }
TY - JOUR T1 - Assessment of Requirement Elicitation Tools and Techniques by Various Parameters AU - Mateen Ahmed Abbasi AU - Javeria Jabeen AU - Yasir Hafeez AU - Dur-e-Benish Batool AU - Naila Fareen Y1 - 2015/07/09 PY - 2015 N1 - https://doi.org/10.11648/j.se.20150302.11 DO - 10.11648/j.se.20150302.11 T2 - Software Engineering JF - Software Engineering JO - Software Engineering SP - 7 EP - 11 PB - Science Publishing Group SN - 2376-8037 UR - https://doi.org/10.11648/j.se.20150302.11 AB - Software development cycle is based on the software requirements. Requirement elicitation is first and most important activity in the requirement engineering. If the requirements are efficiently elicited and managed then the stakeholders application can be accomplished within time and budget. If the requirements are not complete, consistent and correct then projects fail because they not meet the user needs. Requirement is define as the needs of customer. Requirement elicitation techniques and tools are used for correct and complete requirement gathering. Many requirement elicitation techniques and tools are available. This study based on the understanding of requirement gathering techniques and tools. The paper also summarizes the comparison of the requirement elicitation techniques and software requirement tools. Comparison of requirement elicitation techniques and tools are based on the various parameters. VL - 3 IS - 2 ER -