Origins and Consequences of Misunderstood/Slipped Requirements on Large Scale Software Projects

Authors

  • Adeel Ashraf UMT Lahore
  • Hina Alam Department of Informatics and Systems, University of Management and Technology Lahore, Pakistan
  • Shahid Mahmood Awan Department of Computer Science, University of Management and Technology Lahore, Pakistan

DOI:

https://doi.org/10.21015/vtse.v9i4.879

Abstract

Requirement engineering is the first and foremost phase of a software development life cycle. Making mistakes during this process has enormous negative impact on all underlying activities of software development. Defects discovered when a system is deployed cost fifty to two hundred times more than defects discovered during software elicitation phase. In this research paper causes of missed requirements have been identified by literature review and supported by interviews and surveys from leading software industry professionals. In total, sixteen factors of missed requirements have been identified and divided into three categories namely; User factors, Analyst factors, and Common Factors. Understanding of these factors will aid in developing software with complete requirements and thus achieving customer satisfaction level and to avoid wastage of effort and poor quality software.

References

REFRENCES

. Al-Ani, Ban, and H. Keith Edwards. "A comparative empirical study of communication in distributed and collocated development teams." 2008 IEEE International Conference on Global Software Engineering. IEEE, 2008. DOI: https://doi.org/10.1109/ICGSE.2008.9

. A. J. Coffey and P. A. Atkinson, “Making Sense of Qualitative Data: Complementary Research Strategies”, Sage Publications, Inc, 1996.

. Bill Curtis, Herb Krasner, and Neil Iscoe. 1988. A field study of the software design process for large systems. Commun. ACM 31, 11 (Nov. 1988), 1268–1287. DOI:https://doi.org/10.1145/50087.50089 DOI: https://doi.org/10.1145/50087.50089

. J. Kotlarsky and I. Oshri. “Social ties, knowledge sharing and successful collaboration in globally distributed system development projects.” Eur Journal of Inf Systems, vol. 14, Mar. 2005, pp. 37-48, doi: 10.1057/palgrave.ejis.3000520. DOI: https://doi.org/10.1057/palgrave.ejis.3000520

. A. Piri, "Challenges of Globally Distributed Software Development - Analysis of Problems Related to Social Processes and Group Relations", Proc IEEE Int Conf on Global Software Engineering, Sep. 2008,pp. 264-268, doi: 10.1109/ICGSE.2008.33. DOI: https://doi.org/10.1109/ICGSE.2008.33

. B. Lutz, "Linguistic Challenges in Global Software Development: Lessons Learned in an Int. SW Development Division,", Proc. Int. Conf. on Global Software Engineering, Jul. 2009, pp. 249-253, doi: 10.1109/ICGSE.2009.33 DOI: https://doi.org/10.1109/ICGSE.2009.33

. T. Niinimaki, A. Piri, C. Lassenius and M. Paasivaara, "Reflecting the Choice and Usage of Communication Tools in GSD Projects with Media Synchronicity Theory" Proc. IEEE Int. Conf. on Global Software Engineering, Sep. 2010, pp. 312, doi: 10.1109/ICGSE.2010.11 DOI: https://doi.org/10.1109/ICGSE.2010.11

. Karl Wiegers and Joy Beatty. “Software Requirements Engineering”, 2nd Edition.

. E. Bjarnason, K. Wnuk and B. Regnell, "Requirements are slipping through the gaps — A case study on causes & effects of communication gaps in large-scale software development," 2011 IEEE 19th International Requirements Engineering Conference, Trento, 2011, pp. 37-46. DOI: https://doi.org/10.1109/RE.2011.6051639

. Firesmith, Donald. "Prioritizing Requirements." Journal of Object Technology 3.8 ,2004, 35-48. DOI: https://doi.org/10.5381/jot.2004.3.8.c4

. https://docs.google.com/a/umt.edu.pk/forms/d/1JYA0U73hx8ZASOfsZ0-5PInVSfSz609xyskx_1MP-9c

. Pohl, Klaus, “Requirements EngineeringFundamentals, Principles, and Techniques” 2016, 3rd Edition.

. Bjarnason, E., Runeson, P., Borg, M. et al. ,“Challenges and practices in aligning requirements with verification and validation: a case study of six companies.” ,2014, Empir Software Eng 19, 1809–1855 https://doi.org/10.1007/s10664-013-9263-y DOI: https://doi.org/10.1007/s10664-013-9263-y

. Bjarnason, E., Wnuk, K., & Regnell, B., “Are you biting off more than you can chew? A case study on causes and effects of overscoping in large-scale software engineering”. 2018, 54(10), 1107-1124. DOI: https://doi.org/10.1016/j.infsof.2012.04.006

. Raees, M. S., & Ashraf, M. A., “Effects of Refactoring and Design Patterns on The Software Source Code Quality: An Empirical Assessment”. 2018, VAWKUM Transactions on Computer Sciences, 6(1), 48-54.

Downloads

Published

2021-12-31

How to Cite

Ashraf, A., Alam, H., & Awan, S. M. (2021). Origins and Consequences of Misunderstood/Slipped Requirements on Large Scale Software Projects. VFAST Transactions on Software Engineering, 9(4), 62–67. https://doi.org/10.21015/vtse.v9i4.879

Issue

Vol. 9 No. 4 (2021): October-December

Section

Articles

License

Authors who publish with this journal agree to the following terms:

  1. Authors retain copyright and grant the journal right of first publication with the work simultaneously licensed under a Creative Commons Attribution License (CC-By) that allows others to share the work with an acknowledgment of the work's authorship and initial publication in this journal.
  2. Authors are able to enter into separate, additional contractual arrangements for the non-exclusive distribution of the journal's published version of the work (e.g., post it to an institutional repository or publish it in a book), with an acknowledgement of its initial publication in this journal.
  3. Authors are permitted and encouraged to post their work online (e.g., in institutional repositories or on their website) prior to and during the submission process, as it can lead to productive exchanges, as well as earlier and greater citation of published work (See The Effect of Open Access).

                                      

This work is licensed under a Creative Commons Attribution  License CC BY