Abstract

It is well known that software engineering suffer from various challenges. Moreover, numerous researchers found that project challenges have a negative effect on project time cost and user satisfaction. Additionally, Numerous Requirements Engineering (RE) methods have been proposed to improve the quality of requirements documents and to increase customer satisfaction about final product. Nevertheless, the choosing between various techniques may be confusing and puzzling. Therefore, this study aims to present, Literature review based study to link between RE challenges and available techniques to eliminate challenges using the utmost appropriate technique. Study conclusions are relevant for both industry and academic researchers in order to achieve effective software requirement engineering.

Keywords:

Comparison criteria, literature review based study, requirements engineering, software requirement, software requirement techniques,

References

1. Abran, A., J.W. Moore, P. Bourque and R. Dupuis, 2005. Software Requirements. Guide to the Software Engineering Body of Knowledge. Version 2004, IEEE Computer Society Press, Los Alamitos, California.
   
2. Aguilar, J.A., I. Garrigós, and J.N. Mazón, 2011. A goal-oriented approach for optimizing non-functional requirements in web applications. In: De Troyer, O. et al., (Eds.), ER 2011 Workshop. LNCS 6999, Springer-Verlag, Berlin, Heidelberg, pp: 14-23.
   CrossRef    
3. Alexander, I., 2003. Misuse cases: Use cases with hostile intent. IEEE Software, 20(1): 58-66.
   CrossRef    
4. Alexander, I.F., 2005. A taxonomy of stakeholders: Human roles in system development. Int. J. Technol. Hum. Interaction, 1(1): 23-59.
   CrossRef    
5. Baek, S.I., S.K. Paik and W.S. Yoo, 2009. Understanding key attributes in mobile service: Kano model approach. In: Smith, M.J. and G. Salvendy (Eds.), Human Interface, Part II, HCII 2009. LNCS 5618, Springer-Verlag, Berlin, Heidelberg, pp: 355-364.
   CrossRef    
6. Bailey, J.E. and S.W. Pearson, 1983. Development of a tool for measuring and analyzing computer user satisfaction. Manage. Sci., 29(5): 530-545.
   CrossRef    
7. Baroudi, J.J., M.H. Olson and B. Ives, 1986. An empirical study of the impact of user involvement on system usage and information satisfaction. Commun. ACM, 29(3): 232-238.
   CrossRef    
8. Becker, B.G., 1998. Visualizing decision table classifiers. Proceeding of IEEE Symposium on Information Visualization, pp: 102-105.
   CrossRef    
9. Benson, D.H., 1983. Field study of end-user computing: Findings and issues. MIS Quart., 7(4): 35-45.
   CrossRef    
10. Berander, P. and A. Andrews, 2005. Requirements prioritization. In: Aurum, A. and C. Wohlin, (Eds.), Engineering and Managing Software Requirements, Springer, Heidelberg, pp: 69-94.
    CrossRef    
11. Bourne, L., 2009. Stakeholder Relationship Management. Gower Publishing, USA.
    
12. Bourne, L., 2010. Using the Stakeholder Circle methodology for more effective stakeholder engagement of senior management. Proceeding of 7th Project Management National Benchmarking Forum PMI Chapter, Rio de Janeiro, Brazil.
    
13. Burke, L.A. and M.K. Miller, 2001. Phone interviewing as a means of data collection: Lessons learned and practical recommendations. Qual. Soc. Res., 2(2): Art. 7.
    
14. Cagiltay, N.E., G. Tokdemir, O. Kilic and D. Topalli, 2013. Performing and analyzing non-formal inspections of Entity Relationship Diagram (ERD). J. Syst. Software, 86: 2184-2195.
    CrossRef    
15. Carmel, E., R.D. Whitaker and J.F. George, 1993. PD and joint application design: A transatlantic comparison. Commun. ACM, 36(6): 40-48.
    CrossRef    
16. Carr, J.J., 2000. Requirements engineering and management: The key to designing quality complex systems. TQM Mag., 12(6): 400-407.
    CrossRef    
17. Chaudha, A., R. Jain, A.R. Singh and P.K. Mishra, 2010. Integration of Kano's Model into Quality Function Deployment (QFD). Int. J. Adv. Manuf. Tech., 53: 689-698.
    CrossRef    
18. Chen, T.Y., P.L. Poon, S.F. Tang, T.H. Tse and Y.T. Yu, 2006. Applying testing to requirements inspection for software quality assurance. Inform. Syst. Control J., Vol. 6.
    
19. Chung, L. and S. Supakkul, 2005. Representing NFRs and FRs: A goal-oriented and use case driven approach. In: Dosch, W., R.Y. Lee and C. Wu (Eds.), SERA 2004. LNCS 3647, Springer-Verlag, Berlin, Heidelberg, pp: 29-41.
    
20. Chung, L. and J.C. Sampaio do Prado Leite, 2009. On non-functional requirements in software engineering. In: Borgida, A.T. et al. (Eds.), Mylopoulos Festschrift. LNCS 5600, Springer-Verlag, Berlin, Heidelberg, pp: 363-379.
    CrossRef    
21. Cleuziou, G., L. Martin and C. Vrain, 2007. Structuring natural language data by learning rewriting rules. In: Muggleton, S., R. Otero and A. Tamaddoni-Nezhad (Eds.), ILP 2006. LNAI 4455, Springer-Verlag, Berlin, Heidelberg, pp: 125-138.
    CrossRef    
22. Cysneiros, L.M. and J.C. Sampaio do Prado Leite, 2004. Nonfunctional requirements: From elicitation to conceptual models. IEEE T. Software Eng., 30(5): 328-350.
    CrossRef    
23. Dai, J., W. Wang and Q. Xu, 2013. An uncertainty measure for incomplete decision tables and its applications. IEEE T. Cyb., 43(4): 1277-1289.
    
24. Davidson, E.J., 1999. Joint Application Design (JAD) in practice. J. Syst. Software, 45(3): 216-223.
    CrossRef    
25. Davison, R., 2000. The role of groupware in requirements specification. Group Decis. Negot., 9: 149-160.
    CrossRef    
26. Didar, Z. and G. Vincenzo, 2003. On the interplay between consistency, completeness, and correctness in requirements evolution. Inform. Software Tech., 45: 993-1009.
    CrossRef    
27. Didar Z. and C. Coulin, 2005. Requirements Elicitation: A Survey of Techniques, Approaches, and Tools. Maté, JL & Silva, A (Eds.), Idea Group, USA.
    
28. Duggan, E.W. and C.S. Thachenkary, 2003. Higher quality requirements: Supporting joint application development with the nominal group technique. Inform. Technol. Manag., 4: 391-408.
    CrossRef    
29. El-Attar, M. and J. Miller, 2007. Producing robust use case diagrams via reverse engineering of use case descriptions. Softw. Syst. Model., 7: 67-83.
    CrossRef    
30. Ferrari, A., S. Gnesi and G. Tolomei, 2013. Using clustering to improve the structure of natural language requirements documents. In: Doer, J. and A.L. Opdahl (Eds.), REFSQ 2013. LNCS 7830, Springer-Verlag, Berlin, Heidelberg, pp: 34-49.
    CrossRef    
31. Firesmith, D., 2003. Engineering security requirements. J. Object Technol., 2: 53-68.
    CrossRef    
32. Firesmith, D., 2004. Prioritizing requirements. J. Object Technol., 3(8): 35-47.
    CrossRef    
33. Firesmith, D., 2007. Common requirements problems, their negative consequences and the industry best practices to help solve them. J. Object Technol., 6(1): 17-33.
    CrossRef    
34. Fusaro, P., F. Lanubile and G. Visaggio, 1997. A replicated experiment to assess requirements inspection techniques. Empir. Softw. Eng., 2(1): 39-57.
    CrossRef    
35. García, J.D., J. Carretero, J. Maria Perez and F. García, 2004. A model for use case priorization using criticality analysis. In: Lagana, A. et al. (Eds.), ICCSA 2004. LNCS 3046, Springer-Verlag, Berlin, Heidelberg, pp: 496-505.
    CrossRef    
36. Génova1, G., J. Llorens, P. Metz, R. Prieto-Díaz and H. Astudillo, 2005. Open issues in industrial use case modeling. In: Jardim Nunes, N. et al. (Eds.), UML 2004 Satellite Activities. LNCS 3297, Springer-Verlag, Berlin, Heidelberg, pp: 52-61.
    
37. Giakoumakis, E.A. and G. Xylomenos, 1996. Evaluation and selection criteria for software requirements specification standards. Software Eng. J., 11(5): 307-319.
    CrossRef    
38. Glinz, M., 2007. On non-functional requirements. Proceeding of 15th IEEE International Requirements Engineering Conference, pp: 21-26.
    CrossRef    
39. Goguen, J.A. and C. Linde, 1992. Techniques for requirements elicitation. Proceeding of IEEE International Symposium on Requirements Engineering, pp: 152-164.
    CrossRef    
40. Grau, G. and X. Franch, 2007. A goal-oriented approach for the generation and evaluation of alternative architectures. In: Oquendo, F. (Ed.), ECSA 2007. LNCS 4758, Springer-Verlag, Berlin, Heidelberg, pp: 139-155.
    CrossRef    
41. He, L., J.C. Carver and R.B. Vaughn, 2008. Using inspections to teach requirements validation. CrossTalk: J. Defense Software Eng., 21(1).
    
42. Heninger, K.L., 1980. Specifying software requirements for complex systems: New techniques and their application. IEEE T. Software Eng., SE-6(1): 2-13.
    CrossRef    
43. Herrmann, T. and A. Nolte, 2010. The integration of collaborative process modeling and electronic brainstorming in co-located meetings. In: Kolfchoten, G., T. Herrmann and S. Lukosch (Eds.), CRIWG 2010. LNCS 6257, Springer-Verlag, Berlin, Heidelberg, pp: 145-160.
    CrossRef    
44. Huysmans, J., K. Dejaeger, C. Mues, J. Vanthienen and B. Baesens, 2011. An empirical evaluation of the comprehensibility of decision table, tree and rule based predictive models. Decis. Support Syst., 51: 141-154.
    CrossRef    
45. IEEE Computer Society, 1998. Recommended Practice for Software Requirements Specifications. IEEE Standard 830-1998, pp: 1-40.
    
46. Ives, B., M.H. Olson and J.J. Baroudi, 1983. The measurement of user information satisfaction. Commun. ACM, 26(10): 785-793.
    CrossRef    
47. Jiang, L., 2005. A framework for the requirements engineering process development. Ph.D. Thesis, University of Calgary Calgary, Alberta.
    
48. John, S. and P. Gunnar, 2006. Defining misuse within the development process. IEEE Secur. Priv., 4(6).
    
49. Juristo, N., A. Moreno and A. Silva, 2002. Is the European industry moving toward solving requirements engineering problems? IEEE Software, 19(6): 70-77.
    CrossRef    
50. Jurjens, J., 2002. UMLsec: Extending UML for secure systems development. In: Jezequel, J.M., H. Haussmann and S. Cook (Eds.), Proceeding of the Unified Modeling Language, 5th International Conference. LNCS 2460, Springer, Dresden, Germany, pp: 412-425.
    CrossRef    
51. Kamata, M.I. and T. Tamai, 2007. How does requirements quality relate to project success or failure? Proceeding of 15th IEEE International Requirements Engineering Conference (RE'07), pp: 69-78.
    CrossRef    PMid:17158865    
52. Kandt, R.K., 2003. Software quality improvement software requirements engineering: Practices and techniques. SQI Report R-3.
    
53. Kesh, S., 1995. Evaluating the quality of entity relationship models. Inform. Software Tech., 37(12): 681-689.
    CrossRef    
54. Kohavi, R. and S. Daniel, 1998. Targeting business users with decision table classiers. Proceeding of KDD-98.
    PMid:9663033    
55. Kotonya, G. and I. Sommerville, 1998. Requirements engineering: Processes and techniques. John Wiley and Sons, United Kingdom, pp: 5-282.
    
56. Lai, X., M. Xie and K.C. Tan, 2004. Optimizing product design using the kano model and QFD. Proceeding of IEEE International Engineering Management Conference, pp: 1085-1089.
    CrossRef    
57. Laitenberger, O., 2002. A Survey of Software Inspection Technologies. In: Chang, S.K. (Ed.), Handbook on Software Engineering and Knowledge Engineering. World Scientific, Singapore, pp: 517-556.
    CrossRef    
58. Laitenberger, O. and J.M. DeBaud, 2000. An encompassing life cycle centric survey of software inspection. J. Syst. Software, 50(1): 5-31.
    CrossRef    
59. Lehtola, L., M. Kauppinen and S. Kujala, 2004. Requirements prioritization challenges in practice. In: Bomarius, F. and H. Iida (Eds.), PROFES 2004. LNCS 3009, Springer-Verlag, Berlin, Heidelberg, pp: 497-508.
    CrossRef    
60. Litchfield, R.C., 2008. Brainstorming rules as assigned goals: Does brainstorming really improve idea quantity? Motiv. Emotion, 33: 25-31.
    CrossRef    
61. Lloyd, W.J., M.B. Rosson and J.D. Arthur, 2002. Effectiveness of elicitation techniques in distributed requirements engineering. Proceeding of the IEEE Joint International Conference on Requirements Engineering, pp: 311-318.
    CrossRef    
62. Lutz, R.R., 1993. Analyzing software requirements errors in safety-critical embedded systems. Proceeding of IEEE International Symposium on Requirements Engineering, pp: 126-133.
    
63. Mohd Kasirun, Z. and S.S. Salim, 2008. Focus group discussion model for requirements elicitation activity. Proceeding of International Conference on Computer and Electrical Engineering, pp: 102-105.
    CrossRef    
64. Nurmuliani, N., D. Zowghi and S.P. Williams, 2004. Using card sorting technique to classify requirements change. Proceeding of the 12th IEEE International Requirements Engineering Conference, pp: 240-248.
    CrossRef    
65. Nuseibeh, B. and S. Easterbrook, 2000. Requirements engineering: A roadmap. Proceeding of the Conference on the Future of Software Engineering (ICSE'00), pp: 35-46.
    CrossRef    
66. Ochoa, S., R. Alarcon and L. Guerrero, 2009. Understanding the relationship between requirements and context elements in mobile collaboration. In: Jacko, J.A. (Ed.), Human-Computer Interaction, Part III, HCII 2009. LNCS 5612, Springer-Verlag, Berlin, Heidelberg, pp: 67-76.
    CrossRef    
67. Opdahl, A.L. and G. Sindre, 2009. Experimental comparison of attack trees and misuse cases for security threat identification. Inform. Software Tech., 51(5): 946-932.
    CrossRef    
68. Opdenakker, R., 2006. Advantages and disadvantages of four interview techniques in qualitative research. Qual. Soc. Res., 7(4), Art. 11.
    
69. Porter, A.A., L.G. Jr. Votta and V.R. Basili, 1995. Comparing detection methods for software requirements inspections: A replicated experiment. IEEE T. Software Eng., 21(6): 563-575.
    CrossRef    
70. Ragone, A., K. Mirylenka, F. Casati and M. Marchese, 2013. On peer review in computer science: Analysis of its effectiveness and suggestions for improvement. Scientometrics, 97: 317-356.
    CrossRef    
71. Roman, G., 1985. A taxonomy of current issues in requirements engineering. Computer, 18(4): 14-23.
    CrossRef    
72. Saqi, S.B. and S. Ahmed, 2008. Requirements Validation Techniques practiced in industry: Studies of six companies. M.A. Thesis, Software Engineering, School of Engineering, Blekinge Institute of Technology, Sweden.
    
73. Sauerwein, E., F. Bailom, K. Matzler and H.H. Hinterhuber, 1996. The Kano model: How to delight your customers. Proceeding of International Working Seminar on Production Economics, pp: 313-327.
    
74. Scheinholtz, L.A. and I. Wilmont, 2011. Interview patterns for requirements elicitation. In: Berry, D. and X. Franch (Eds.), REFSQ 2011. LNCS 6606, Springer-Verlag, Berlin, Heidelberg, pp: 72-77.
    CrossRef    
75. Sendall, S., 2003. Requirements elicitation with use cases. Lecture Notes Comput. Sc., 2604: 203.
    CrossRef    
76. Siau, K. and L. Lee, 2004. Are use case and class diagrams complementary in requirements analysis? An experimental study on use case and class diagrams in UML. Requir. Eng., 9: 229-237.
    CrossRef    
77. Sindre, G. and A.L. Opdahl, 2004. Eliciting security requirements with misuse cases. Requir. Eng., 10: 34-44.
    CrossRef    
78. Singer, M., 2013. Validation in reading comprehension. Curr. Dir. Psychol. Sci., 22: 361-366.
    CrossRef    
79. Sneed, H.M. and C. Verhoef, 2013. Natural language requirement specification for web service testing. Proceeding of 15th IEEE International Symposium on Web Systems Evolution (WSE, 2013), pp: 5-14.
    CrossRef    
80. Sommerville, I., 2010. Software Engineering. 9th Edn., Addison-Wesley, ISBN 10: 0-13-703515-2.
    
81. Sommerville, I. and P. Sawyer, 1997. Requirements Engineering: A Good Practice Guide. John Wiley & Sons, New York.
    
82. Song, Y., M. Evans and E.K. Park, 1995. A comparative analysis of entity-relationship diagrams1. J. Comput. Software Eng., 3(4): 427-459.
    
83. Spencer, D., 2009. Card Sorting: Designing Usable Categories. Brooklyn, New York, USA.
    
84. Stellman, A. and J. Greene, 2005. Applied Software Project Management. O'Reilly Media Inc., USA, pp: 113.
    
85. Subramanian, G.H., J. Nosek, S.P. Raghunathan and S.S. Kanitkar, 1992. Comparison of the decision table and tree. Commun. ACM, 35(1): 89-94.
    CrossRef    
86. Tablan, V., D. Damljanovic and K. Bontcheva, 2008. A natural language query interface to structured information. Proceeding of the 5th European Semantic Web Conference on the Semantic Web: Research and Applications (ESWC'08), pp: 361-375.
    CrossRef    
87. Tøndel, I.A., J. Jensen and L. Røstad, 2010. Combining misuse cases with attack trees and security activity models. Proceeding of 10th International Conference on Availability, Reliability and Security (ARES, 2010), pp: 438-4445.
    CrossRef    
88. Ullah, S., M. Iqbal and A.M. Khan, 2011. A survey on issues in non-functional requirements elicitation. Proceeding of International Conference on Computer Networks and Information Technology (ICCNIT, 2011), pp: 333-340.
    CrossRef    
89. Umber, A. and I.S. Bajwa, 2011. Minimizing ambiguity in natural language software requirements specification. Proceeding of 6th International Conference on Digital Information Management (ICDIM, 2011), pp: 102-107.
    CrossRef    
90. Van Lamsweerde, A., 2001. Goal-oriented requirements engineering: A guided tour. Proceeding of 5th IEEE International Symposium on Requirements Engineering, pp: 249-262.
    
91. Von Dran, G.M., P. Zhang and R. Small, 1999. Quality websites: An application of the kano model to website design. Proceeding of the 5th Americas Conference on Information Systems (AMCIS'99), August 13-15.
    
92. Whittle, J., D. Wijesekera and M. Hartong, 2008. Executable misuse cases for modeling security concerns. Proceeding of 30th ACM/IEEE International Conference on Software Engineering (ICSE '08).
    CrossRef    
93. Wieringa, R., N. Maiden, N. Mead and C. Rolland, 2005. Requirements engineering paper classi?cation and evaluation criteria: A proposal and a discussion. Requir. Eng., 11: 102-107.
    CrossRef    
94. Wood, J.R. and L.E. Wood, 2008. Card sorting: Current practices and beyond. J. Usability Stud., 4(1): 1-6.
    
95. Xiong, W. and D. Litman, 2010. Identifying problem localization in peer-review feedback. In: Aleven, V., J. Kay and J. Mostow (Eds.), ITS 2010. Part II, LNCS 6095, Springer-Verlag, Berlin, Heidelberg, pp: 429-431.
    CrossRef    
96. Yeh, D., Y. Li and W. Chu, 2008. Extracting entity-relationship diagram from a table-based legacy database. J. Syst. Software, 81: 764-771.
    CrossRef    
97. Zave, P., 1997. Classification of research efforts in requirements engineering. ACM Comput. Surv., 29(4): 315-321.
    CrossRef    
98. Zowghi, D. and V. Gervasi, 2003. On the interplay between consistency, completeness, and correctness in requirements evolution, Inform. Software Tech., 45: 993-1009.
    CrossRef    

Competing interests

The authors have no competing interests.

Open Access Policy

This article is 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, provided you give appropriate credit to the original author(s) and the source, provide a link to the Creative Commons license, and indicate if changes were made.

Copyright

The authors have no competing interests.