An investigation of requirements traceability practices in software companies in Malaysia

Requirement traceability (RT) is one of the critical activity of good requirements management and an important part of development projects. At the same time, it improves the quality of software products. Nevertheless, industrial practitioners are challenged by this lack of guidance or results which...

Full description

Saved in:

Bibliographic Details
Main Author:	Dahr, Jasim Mohammed
Format:	Thesis
Language:	eng eng
Published:	2016
Subjects:	QA75 Electronic computers Computer science
Online Access:	https://etd.uum.edu.my/6531/1/s814911_01.pdf https://etd.uum.edu.my/6531/2/s814911_02.pdf
Tags:	Add Tag No Tags, Be the first to tag this record!

id	my-uum-etd.6531
record_format	uketd_dc
institution	Universiti Utara Malaysia
collection	UUM ETD
language	eng eng
advisor	Omar, Mazni
topic	QA75 Electronic computers Computer science
spellingShingle	QA75 Electronic computers Computer science Dahr, Jasim Mohammed An investigation of requirements traceability practices in software companies in Malaysia
description	Requirement traceability (RT) is one of the critical activity of good requirements management and an important part of development projects. At the same time, it improves the quality of software products. Nevertheless, industrial practitioners are challenged by this lack of guidance or results which serve as a rule or guide in establishing effective traceability in their projects. The outcome of this is that practitioners are ill-informed as to the best or most efficient means of accomplishing their tasks, such as found in software companies. Notwithstanding the lack of guidance, there are a number of commonly accepted practices which can guide industrial practitioners with respect to trace the requirements in their projects. This study aims to determine the practices of RT through conducting a systematic literature review. Also, this study conducted a survey for investigating the use of RT practices in the software companies at northern region of Malaysia. Finally, a series of interviews with practitioners were carried out to know the reasons that influence on the use of these practices in software development. The findings showed that majority software companies do not use traceability practices for tracing requirements due to financial issues and the lack of knowledge of these practices. This study presented empirical evidence about the use of RT practices among software companies. Thus, the findings of this study can assist practitioners to select RT practices, and also enables researchers to find gaps and pointers for future study in this study domain.
format	Thesis
qualification_name	masters
qualification_level	Master's degree
author	Dahr, Jasim Mohammed
author_facet	Dahr, Jasim Mohammed
author_sort	Dahr, Jasim Mohammed
title	An investigation of requirements traceability practices in software companies in Malaysia
title_short	An investigation of requirements traceability practices in software companies in Malaysia
title_full	An investigation of requirements traceability practices in software companies in Malaysia
title_fullStr	An investigation of requirements traceability practices in software companies in Malaysia
title_full_unstemmed	An investigation of requirements traceability practices in software companies in Malaysia
title_sort	investigation of requirements traceability practices in software companies in malaysia
granting_institution	Universiti Utara Malaysia
granting_department	Awang Had Salleh Graduate School of Arts & Sciences
publishDate	2016
url	https://etd.uum.edu.my/6531/1/s814911_01.pdf https://etd.uum.edu.my/6531/2/s814911_02.pdf
_version_	1747828085896511488
spelling	my-uum-etd.65312021-04-05T02:10:49Z An investigation of requirements traceability practices in software companies in Malaysia 2016 Dahr, Jasim Mohammed Omar, Mazni Awang Had Salleh Graduate School of Arts & Sciences Awang Had Salleh Graduate School of Arts and Sciences QA75 Electronic computers. Computer science Requirement traceability (RT) is one of the critical activity of good requirements management and an important part of development projects. At the same time, it improves the quality of software products. Nevertheless, industrial practitioners are challenged by this lack of guidance or results which serve as a rule or guide in establishing effective traceability in their projects. The outcome of this is that practitioners are ill-informed as to the best or most efficient means of accomplishing their tasks, such as found in software companies. Notwithstanding the lack of guidance, there are a number of commonly accepted practices which can guide industrial practitioners with respect to trace the requirements in their projects. This study aims to determine the practices of RT through conducting a systematic literature review. Also, this study conducted a survey for investigating the use of RT practices in the software companies at northern region of Malaysia. Finally, a series of interviews with practitioners were carried out to know the reasons that influence on the use of these practices in software development. The findings showed that majority software companies do not use traceability practices for tracing requirements due to financial issues and the lack of knowledge of these practices. This study presented empirical evidence about the use of RT practices among software companies. Thus, the findings of this study can assist practitioners to select RT practices, and also enables researchers to find gaps and pointers for future study in this study domain. 2016 Thesis https://etd.uum.edu.my/6531/ https://etd.uum.edu.my/6531/1/s814911_01.pdf text eng public https://etd.uum.edu.my/6531/2/s814911_02.pdf text eng public masters masters Universiti Utara Malaysia Aartsengel, A. Van, Kurtoglu, S., Lean, T., Sigma, S., & Methodology, S. (2013). Handbook on Continuous Improvement Transformation. http://doi.org/10.1007/978-3-642-35901-9 Abbors, F., Trusçan, D., & Lilius, J. (2009). Tracing requirements in a model-based testing approach. In Advances in System Testing and Validation Lifecycle, 2009. VALID’09. First International Conference on (pp. 123–128). IEEE. Abdalla, M., Bourse, F., De Caro, A., & Pointcheval, D. (2015). Simple functional encryption schemes for inner products. In Public-Key Cryptography--PKC 2015 (pp. 733–751). Springer. Ackroyd, S. (1992). Data collection in context. Longman Group United Kingdom. Agarwal, M., & Gael, S. (2014). Expert System and it ’ s Requirement Engineering Process. Ahmad, A., & Ghazali, M. A. (2007). Documenting requirements traceability information for small projects. In Multitopic Conference, 2007. INMIC 2007. IEEE International (pp. 1–5). IEEE. Aizenbud-Reshef, N., Nolan, B. T., Rubin, J., & Shaham-Gafni, Y. (2006). Model traceability. IBM Systems Journal, 45(3), 515–526. Alghazzawi, D. M., Siddiqui, S. T., Bokhari, M. U., & Hamatta, H. S. A. (2014). Selecting Appropriate Requirements Management Tool for Developing Secure Enterprises Software. International Journal of Information Technology and Computer Science, 6(4), 49–55. http://doi.org/10.5815/ijitcs.2014.04.06 Ali, N. (2010). Traceability Improvement for Software Miniaturization. Ali, N., Guéhéneuc, Y.-G., & Antoniol, G. (2012). Factors impacting the inputs of traceability recovery approaches. In Software and Systems Traceability (pp. 99–127). Springer. Ali, N., Gueneuc, Y.-G., & Antoniol, G. (2013). Trustrace: Mining software repositories to improve the accuracy of requirement traceability links. Software Engineering, IEEE Transactions on, 39(5), 725–741. Ali, N., Sharafi, Z., Guéhéneuc, Y.-G., & Antoniol, G. (2015). An empirical study on the importance of source code entities for requirements traceability. Empirical Software Engineering, 20(2), 442–478. Arkley, P., Mason, P., & Riddle, S. (2002). Position paper: Enabling traceability. In Proceedings of the 1st International Workshop on Traceability in Emerging Forms of Software Engineering, Edinburgh, Scotland (September 2002) (pp. 61–65). Citeseer. Arkley, P., & Riddle, S. (2005). Overcoming the traceability benefit problem. In 13th IEEE International Conference on Requirements Engineering (RE’05) (pp. 385–389). IEEE. Athira, B., & Samuel, P. (2011). Traceability Matrix for Regression Testing in Distributed Software Development. In Advances in Computing and Communications (pp. 80–87). Springer. Atieno, O. (2009). An analysis of the strengths and limitations of qualitative and quantitative research paradigms. Problems of Education in the 21st Century, 13(1), 13–38. Attarha, M., & Modiri, N. (2011). Focusing on the importance and the role of requirement engineering. The 4th International Conference on Interaction Sciences, 181–184. Auerbach, C., & Silverstein, L. B. (2003). Qualitative data: An introduction to coding and analysis. NYU press. Azhar, D., Mendes, E., & Riddle, P. (2012). A systematic review of web resource estimation. In Proceedings of the 8th International Conference on Predictive Models in Software Engineering (pp. 49–58). ACM. Bacchelli, A., Lanza, M., & Robbes, R. (2010). Linking e-mails and source code artifacts. In Proceedings of the 32nd ACM/IEEE International Conference on Software Engineering-Volume 1 (pp. 375–384). ACM. Balvanes, M., & Caputi, P. (2001). Introduction to quantitative research methods. London: Sage Publications. Bano, M., Imtiaz, S., Ikram, N., Niazi, M., & Usman, M. (2012). Causes of Requirement Change – A Systematic Literature Review, 22–31. Bashir, M. F., & Qadir, M. A. (2006). Traceability techniques: A critical study. 10th IEEE International Multitopic Conference 2006, INMIC, 265–268. http://doi.org/10.1109/INMIC.2006.358175 Basit, T. (2003). Manual or electronic? The role of coding in qualitative data analysis. Educational Research, 45(2), 143–154. Bauer, M. W., & Gaskell, G. (2000). Qualitative researching with text, image and sound: A practical handbook for social research. Sage. Blaauboer, F. A. (2006). Deciding to adopt traceability in practice: influencing this decision. Blaauboer, F., Sikkel, K., & Aydin, M. N. (2007). Deciding to adopt requirements traceability in practice. Lecture Notes in Computer Science (including Subseries Lecture Notes in Artificial Intelligence and Lecture Notes in Bioinformatics), 4495 LNCS, 294–308. Retrieved from http://www.scopus.com/inward/record.url?eid=2-s2.0-38149045785&partnerID=tZOtx3y1 Bonaccorsi, A., Giannangeli, S., & Rossi, C. (2006). Entry strategies under competing standards: Hybrid business models in the open source software industry. Management Science, 52(7), 1085–1098. Borges, R. V., Garcez, A. d’Avila, Lamb, L. C., & Nuseibeh, B. (2011). Learning to adapt requirements specifications of evolving systems: (NIER track). 2011 33rd International Conference on Software Engineering (ICSE), 856–859. http://doi.org/10.1145/1985793.1985924 Bouillon, E., Mäder, P., & Philippow, I. (2013). A survey on usage scenarios for requirements traceability in practice. In Requirements Engineering: Foundation for Software Quality (pp. 158–173). Springer. Burnay, C., Jureta, I., & Faulkner, S. (2015). Towards a Model of Topic Relevance during requirements elicitation-Preliminary results. In Research Challenges in Information Science (RCIS), 2015 IEEE 9th International Conference on (pp. 151–158). IEEE. Burns, N., & Grove, S. K. (2003). Understanding nursing research (3rd Ed.). Philadelphia. Saunders. Casey, V., & Mc Caffery, F. (2011). Med-Trace: traceability assessment method for medical device software development. Chakraborty, A., Baowaly, M. K., Arefin, A., & Bahar, A. N. (2012). The role of requirement engineering in software development life cycle. Journal of Emerging Trends in Computing and Information Sciences, 3(5), 723–729. Chaos, E. (2001). The Standish Group International. Inc. Charreire, S., & Durieux, F. (2001). Exploring and testing. RA. Thietart et Al.(a Cura Di), Doing Management Research: A Comprehensive Guide, London: Sage. Chen, X., Hosking, J., & Grundy, J. (2011). A combination approach for enhancing automated traceability:(NIER track). In Software Engineering (ICSE), 2011 33rd International Conference on (pp. 912–915). IEEE. Cheng, B. H. C., & Atlee, J. M. (2007). Research directions in requirements engineering. In 2007 Future of Software Engineering (pp. 285–303). IEEE Computer Society. Chisaka, C., & Vakalisa, N. C. G. (2000). Gathering and analysis of data using qualitative methods in Education. Gauteng: Rand Afrikaans University. Clark, V. L. P., & Creswell, J. W. (2014). Understanding research: A consumer’s guide. Pearson Higher Ed. Cleland-Huang, J. (2005). Toward improved traceability of non-functional requirements. In Proceedings of the 3rd international workshop on Traceability in emerging forms of software engineering (pp. 14–19). ACM. Cleland-Huang, J. (2006). Just enough requirements traceability. In Computer Software and Applications Conference, 2006. COMPSAC’06. 30th Annual International (Vol. 1, pp. 41–42). IEEE. Cleland-Huang, J., Chang, C. K., & Christensen, M. (2003). Event-based traceability for managing evolutionary change. Software Engineering, IEEE Transactions on, 29(9), 796–810. Cleland-Huang, J., Chang, C. K., Sethi, G., Javvaji, K., Hu, H., & Xia, J. (2002). Automating speculative queries through event-based requirements traceability. In Requirements Engineering, 2002. Proceedings. IEEE Joint International Conference on (pp. 289–296). IEEE. Cleland-Huang, J., Czauderna, A., Dekhtyar, A., Gotel, O., Hayes, J. H., Keenan, E., … Shin, Y. (2011). Grand challenges, benchmarks, and TraceLab: developing infrastructure for the software traceability research community. In Proceedings of the 6th international workshop on traceability in emerging forms of software engineering (pp. 17–23). ACM. Cleland-huang, J., Gotel, O., Hayes, J. H., Mäder, P., Zisman, A., & Keyes, M. (2014). Software Traceability : Trends and Future Directions. Proceedings of the on Future of Software Engineering (FOSE’14), 55–69. Cleland-Huang, J., Hayes, J. H., & Domel, J. M. (2009). Model-based traceability. In Proceedings of the 2009 ICSE Workshop on Traceability in Emerging Forms of Software Engineering (pp. 6–10). IEEE Computer Society. Cleland-huang, J., Hayes, J. H., & Domel, J. M. (2009). Model-Based Traceability School of Computing. Management, Copyright, 6–10. http://doi.org/10.1109/TEFSE.2009.5069575 Cleland-Huang, J., & Schmelzer, D. (2003). Dynamically tracing non-functional requirements through design pattern invariants. In Workshop on Traceability in Emerging Forms of Software Engineering, in conjunction with IEEE International Conference on Automated Software Engineering (Vol. 10). Cleland-Huang, J., Settimi, R., BenKhadra, O., Berezhanskaya, E., & Christina, S. (2005). Goal-centric traceability for managing non-functional requirements. In Proceedings of the 27th international conference on Software engineering (pp. 362–371). ACM. Coakes, S. J., & Steed, L. (2009). SPSS: Analysis without anguish using SPSS version 14.0 for Windows. John Wiley & Sons, Inc. Creswell, J. W. (2013). Research design: Qualitative, quantitative, and mixed methods approaches. Sage publications. Cuddeback, D., Dekhtyar, A., & Hayes, J. H. (2010). Automated requirements traceability: The study of human analysts. In Requirements Engineering Conference (RE), 2010 18th IEEE International (pp. 231–240). IEEE. Cysneiros, L. M. (2007). Evaluating the Effectiveness of Using Catalogues to Elicit Non-Functional Requirements. In WER (pp. 107–115). da Silva, A. R. (2014). Quality of requirements specifications: a preliminary overview of an automatic validation approach. In Proceedings of the 29th Annual ACM Symposium on Applied Computing (pp. 1021–1022). ACM. De Lucia, A., Fasano, F., & Oliveto, R. (2008). Traceability management for impact analysis. In Frontiers of Software Maintenance, 2008. FoSM 2008. (pp. 21–30). IEEE. De Lucia, A., Marcus, A., Oliveto, R., & Poshyvanyk, D. (2012). Information retrieval methods for automated traceability recovery. In Software and systems traceability (pp. 71–98). Springer. Dick, a J. J. (2012). Evidence-based development - coupling structured argumentation with requirements development. System Safety, Incorporating the Cyber Security Conference 2012, 7th IET International Conference on, 1–5. http://doi.org/10.1049/cp.2012.1498 Diev, S. (2007). Requirements development as a modeling activity. ACM SIGSOFT Software Engineering Notes, 32(2), 1–3. Dybä, T., Kitchenham, B., & Jorgensen, M. (2005). Evidence-based software engineering for practitioners. Software, IEEE, 22(1), 58–65. Egyed, A., & Grunbacher, P. (2002). Automating requirements traceability: Beyond the record & replay paradigm. In Automated Software Engineering, 2002. Proceedings. ASE 2002. 17th IEEE International Conference on (pp. 163–171). IEEE. Egyed, A., Grünbacher, P., Heindl, M., & Biffl, S. (2009). Value-based requirements traceability: Lessons learned. In Design requirements engineering: a ten-year perspective (pp. 240–257). Springer. Elliott Sr, R. A., & Allen, E. B. (2013). A methodology for creating an IEEE standard 830-1998 software requirements specification document. Journal of Computing Sciences in Colleges, 29(2), 123–131. Fatwanto, A. (2013). Software requirements specification analysis using natural language processing technique. 2013 International Conference on QiR, 105–110. http://doi.org/10.1109/QiR.2013.6632546 Felderer, M., & Beer, A. (2013). Using defect taxonomies for requirements validation in industrial projects. 2013 21st IEEE International Requirements Engineering Conference, RE 2013 - Proceedings, 296–301. http://doi.org/10.1109/RE.2013.6636733 Ferreira, D., & da Silva, A. R. (2008). A requirements specification case study with ProjectIT-studio/requirements. In Proceedings of the 2008 ACM symposium on Applied computing (pp. 656–657). ACM. Fontana, A., & Frey, J. H. (2005). The Interview: From Neutral Stance To Political Involvement. In the book of The Sage of Handbook of Qualitative Research. United Kingdom: Sage Publications, Inc. Fricker, S. A., Grau, R., & Zwingli, A. (2015). Requirements Engineering : Best Practice Requirements Engineering State-of-Art. Goknil, A., Kurtev, I., van den Berg, K., & Spijkerman, W. (2014). Change impact analysis for requirements: A metamodeling approach. Information and Software Technology, 56(8), 950–972. http://doi.org/10.1016/j.infsof.2014.03.002 Gotel, O. C., & Finkelstein, A. C. W. (1994). An Analysis of the Requirements Traceability Problem Imperial College of Science , Technology & Medicine Department of Computing , 180 Queen ’ s Gate, 94–101. Gotel, O. C. Z., & Finkelstein, A. C. W. (1994). An analysis of the requirements traceability problem. In Requirements Engineering, 1994., Proceedings of the First International Conference on (pp. 94–101). IEEE. Gotel, O., Cleland-Huang, J., Hayes, J. H., Zisman, A., Egyed, A., Grünbacher, P., … Maletic, J. (2012). The grand challenge of traceability (v1. 0). In Software and Systems Traceability (pp. 343–409). Springer. Gough, D., Oliver, S., & Thomas, J. (2012). An introduction to systematic reviews. Sage. Han, K., Youn, J., & Cho, J. (2014). A Functional Requirement Traceability Management Methodology for Model-based Testing Framework of Automotive Embedded System, (c), 46–51. Hannay, J. E., Sjøberg, D. I. K., & Dybå, T. (2007). A systematic review of theory use in software engineering experiments. Software Engineering, IEEE Transactions on, 33(2), 87–107. Harfoushi, O., Fawwaz, B. A., Obiedat, R., Faris, H., & Al-Sayyed, R. (2012). Usability Assessment of the Government Web Services in the Hashemite Kingdom of Jordan. Journal of American Science, 8(12), 12. Haron, A. (2012). Understanding the Requirement Engineering for Organization : The Challenges, 561–567. Hassnain, M. (2015). A Comparative Study on Traceability Approaches in Software development Life Cycle. ITEE Journal Information Technology & Electrical Engineering, (2), 4. Hayes, J. H., Dekhtyar, A., Sundaram, S. K., Holbrook, E. A., Vadlamudi, S., & April, A. (2007). REquirements TRacing On target (RETRO): improving software maintenance through traceability recovery. Innovations in Systems and Software Engineering, 3(3), 193–202. Heindl, M., & Biffl, S. (2005). A case study on value-based requirements tracing. In Proceedings of the 10th European software engineering conference held jointly with 13th ACM SIGSOFT international symposium on Foundations of software engineering (pp. 60–69). ACM. Hill, R. (1998). What sample size is “enough” in internet survey research. Interpersonal Computing and Technology: An Electronic Journal for the 21st Century, 6(3-4), 1–12. Hong, Y., Kim, M., & Lee, S.-W. (2010). Requirements management tool with evolving traceability for heterogeneous artifacts in the entire life cycle. In Software Engineering Research, Management and Applications (SERA), 2010 Eighth ACIS International Conference on (pp. 248–255). IEEE. Huang, R., Berenbach, B., & Clark, S. (2007). Best practices for automated traceability. Jaber, K., Sharif, B., & Liu, C. (2013). A study on the effect of traceability links in software maintenance. Access, IEEE, 1, 726–741. Javed, M. A., & Zdun, U. (2014). A systematic literature review of traceability approaches between software architecture and source code. In Proceedings of the 18th International Conference on Evaluation and Assessment in Software Engineering (p. 16). ACM. Jiang, L., Eberlein, A., Far, B. H., & Mousavi, M. (2008). A methodology for the selection of requirements engineering techniques. Software & Systems Modeling, 7(3), 303–328. Juergens, E., Deissenboeck, F., Feilkas, M., Hummel, B., Schaetz, B., Wagner, S., … Streit, J. (2010). Can clone detection support quality assessments of requirements specifications? In Proceedings of the 32nd ACM/IEEE International Conference on Software Engineering-Volume 2 (pp. 79–88). ACM. Kang, S., Kim, J., Kang, S., & Eom, S. (2014). A Formal Representation of Platform Feature-to-Requirement Traceability for Software Product Line Development. 2014 IEEE 38th Annual Computer Software and Applications Conference, 211–218. http://doi.org/10.1109/COMPSAC.2014.29 Katta, V., & Stålhane, T. (2014). Survey Protocol : Traceability during Development of Systems with Safety and Security Implications - Importance , Tools , and Challenges. Khan, K., Kumar, P. V. V., Ahmad, A., Riaz, T., Anwer, W., Suleman, M., … Chaitanya, a. V. K. (2011). Requirement Development Life Cycle: The Industry Practices. 2011 Ninth International Conference on Software Engineering Research, Management and Applications, 12–16. http://doi.org/10.1109/SERA.2011.38 Khan, K., Kunz, R., Kleijnen, J., & Antes, G. (2011). Systematic reviews to support evidence-based medicine. CRC Press. Khan, M. N. A., Khalid, M., & ul Haq, S. (2013). Review of requirements management issues in software development. International Journal of Modern Education and Computer Science (IJMECS), 5(1), 21. Kirova, V., Kirby, N., Kothari, D., & Childress, G. (2008). Effective requirements traceability: Models, tools, and practices. Bell Labs Technical Journal, 12(4), 143–157. Kitchenham, B. A., Dyba, T., & Jorgensen, M. (2004). Evidence-based software engineering. In Proceedings of the 26th international conference on software engineering (pp. 273–281). IEEE Computer Society. Kitchenham, B., & Charters, S. (n.d.). Guidelines for performing systematic literature reviews in software engineering. 2007. URL Http://www. Dur. Ac. uk/ebse/resources/Systematic-Reviews-5-8. Pdf. Klimpke, L., & Hildenbrand, T. (2009). Towards end-to-end traceability: Insights and implications from five case studies. In Software Engineering Advances, 2009. ICSEA’09. Fourth International Conference on (pp. 465–470). IEEE. Kong, L., & Yuan, T. (2009). Extension Features-Driven Use Case Model for requirement traceability. In Computer Science & Education, 2009. ICCSE’09. 4th International Conference on (pp. 866–870). IEEE. Kothari, C. R. (2009). Research methodology: Methods and techniques New Delhi: New Age International Publishers. ISBN 978-81-224-15222-3. Kumar, R. (2011). Research methodology: A step-by-step guide for Beginners (3rd ed.). Lago, P., Muccini, H., & van Vliet, H. (2009). A scoped approach to traceability management. Journal of Systems and Software, 82(1), 168–182. http://doi.org/10.1016/j.jss.2008.08.026 Laplante, P. A. (2013). Requirements engineering for software and systems. CRC Press. Lin, J., Lin, C. C., Cleland-Huang, J., Settimi, R., Amaya, J., Bedford, G., … Zou, X. (2006). Poirot: A distributed tool supporting enterprise-wide automated traceability. In Requirements Engineering, 14th IEEE International Conference (pp. 363–364). IEEE. Mader, P., & Egyed, A. (2012). Assessing the effect of requirements traceability for software maintenance. In Software Maintenance (ICSM), 2012 28th IEEE International Conference on (pp. 171–180). IEEE. Mäder, P., & Egyed, A. (2014). Do developers benefit from requirements traceability when evolving and maintaining a software system? Empirical Software Engineering, 1–29. Mäder, P., & Gotel, O. (2012). Towards automated traceability maintenance. Journal of Systems and Software, 85(10), 2205–2227. Mäder, P., Gotel, O., Kuschke, T., & Philippow, I. (2008). traceMaintainer-Automated Traceability Maintenance. In International Requirements Engineering, 2008. RE’08. 16th IEEE (pp. 329–330). IEEE. Mader, P., Gotel, O., & Philippow, I. (2008). Rule-based maintenance of post-requirements traceability relations. In International Requirements Engineering, 2008. RE’08. 16th IEEE (pp. 23–32). IEEE. Mäder, P., Gotel, O., & Philippow, I. (2009a). Motivation matters in the traceability trenches. In Requirements Engineering Conference, 2009. RE’09. 17th IEEE International (pp. 143–148). IEEE. Mäder, P., Gotel, O., & Philippow, I. (2009b). Semi-automated traceability maintenance: An architectural overview of traceMAINTAINER. In Software Engineering-Companion Volume, 2009. ICSE-Companion 2009. 31st International Conference on (pp. 425–426). IEEE. Mäder, P., Gotel, O., & Philippow, I. (2009c). traceMAINTAINER: A Tool for the Semi-automated Maintenance of Model Traceability. Submitted), Enschede, Netherlands (June 2009). Mader, P., Jones, P. L., Zhang, Y., & Cleland-Huang, J. (2013). Strategic traceability for safety-critical projects. Software, IEEE, 30(3), 58–66. Mahmoud, A. (2015). An information theoretic approach for extracting and tracing non-functional requirements. In Requirements Engineering Conference (RE), 2015 IEEE 23rd International (pp. 36–45). IEEE. Maletic, J. I., Munson, E. V, Marcus, A., & Nguyen, T. N. (2003). Using a hypertext model for traceability link conformance analysis. In Proc. of the Int. Workshop on Traceability in Emerging Forms of Software Engineering (pp. 47–54). Malhotra, N. K. (2008). Marketing research: An applied orientation, 5/e. Pearson Education India. Manapian, A., & Prompoon, N. (2014). Software time estimation model for requirements change based on software prototype profiles using an analogy estimation method. In Computer Science and Engineering Conference (ICSEC), 2014 International (pp. 366–371). IEEE. Marnewick, A. (2014). The effect of requirements engineering on the success of system implementation: a comparative case study. Marshall, C., & Rossman, G. B. (1999). Designing qualitative research. Sage publications. Miles, M. B., & Huberman, A. M. (1994). Qualitative data analysis: An expanded sourcebook. Sage. Mirakhorli, M., & Cleland-Huang, J. (2012). Tracing non-functional requirements. In Software and Systems Traceability (pp. 299–320). Springer. Mohebzada, J. G., Ruhe, G., & Eberlein, A. (2012). Systematic Mapping of Recommendation Systems for Requirements Engineering, 200–209. Morckos, M. (2011). Requirements Traceability. Report for School of Computer Science, University of Waterloo, Waterloo. Muijs, D. (2010). Doing quantitative research in education with SPSS. Sage. Murta, L. G. P., Van Der Hoek, A., & Werner, C. M. L. (2006). ArchTrace: policy-based support for managing evolving architecture-to-implementation traceability links. In Automated Software Engineering, 2006. ASE’06. 21st IEEE/ACM International Conference on (pp. 135–144). IEEE. Murta, L. G. P., van der Hoek, A., & Werner, C. M. L. (2008). Continuous and automated evolution of architecture-to-implementation traceability links. Automated Software Engineering, 15(1), 75–107. Nair, S., De La Vara, J. L., & Sen, S. (2013). A review of traceability research at the requirements engineering conferencere@21. 2013 21st IEEE International Requirements Engineering Conference, RE 2013 - Proceedings, 222–229. http://doi.org/10.1109/RE.2013.6636722 Naz, H., Motla, Y. H., Asghar, S., Abbas, M. A., & Khatoon, A. (2013). Effective usage of AI technique for requirement change management practices. 2013 5th International Conference on Computer Science and Information Technology, CSIT 2013 - Proceedings, 121–125. http://doi.org/10.1109/CSIT.2013.6588769 Niessink, F., & Van Vliet, H. (1998). Two case studies in measuring software maintenance effort. In Software Maintenance, 1998. Proceedings., International Conference on (pp. 76–85). IEEE. Noor, N. M. (2011). Writing Research and Thesis Proposals: Guidelines and Examples. Pusat Penerbitan Universiti Teknologi Mara. O’Connor, A. M., Anderson, K. M., Goodell, C. K., & Sargeant, J. M. (2014). Conducting systematic reviews of intervention questions I: Writing the review protocol, formulating the question and searching the literature. Zoonoses and Public Health, 61(S1), 28–38. Ohashi, K., Kurihara, H., Tananaka, Y., & Yamamoto, R. (2011). A means of establishing traceability based on a UML model in business application development. In Requirements Engineering Conference (RE), 2011 19th IEEE International (pp. 279–284). IEEE. Omoronyia, I., Sindre, G., Biffl, S., & Stålhane, T. (2011). Understanding Architectural Elements from Requirements Traceability Networks. In Relating Software Requirements and Architectures (pp. 61–83). Springer. Ooi, S. M., Lim, R., & Lim, C. C. (2014). An integrated system for end-to-end traceability and requirements test coverage. In Software Engineering and Service Science (ICSESS), 2014 5th IEEE International Conference on (pp. 45–48). IEEE. Ozkaya, I., & Akin, Ö. (2007). Tool support for computer-aided requirement traceability in architectural design: The case of DesignTrack. Automation in Construction, 16(5), 674–684. Pandanaboyana, S., Sridharan, S., Yannelli, J., & Hayes, J. H. (2013). REquirements TRacing On target (RETRO) enhanced with an automated thesaurus builder: An empirical study. In Traceability in Emerging Forms of Software Engineering (TEFSE), 2013 International Workshop on (pp. 61–67). IEEE. Pandey, D., & Suman, U. (2012). The Usefulness of RE Practices in S/W Development. Journal of Global Research in Computer Science, 3(9), 56–69. Pandey, D., Suman, U., & Ramani, A. K. (2010). An effective requirement engineering process model for software development and requirements management. In Advances in Recent Technologies in Communication and Computing (ARTCom), 2010 International Conference on (pp. 287–291). IEEE. PC, A., & Prabhu, B. (2012). Integrating Requirements Engineering and User Experience Design in Product Life Cycle Management, 12–17. Petticrew, M., & Roberts, H. (2008). Systematic reviews in the social sciences: A practical guide. John Wiley & Sons. Pinheiro, F. A. C. (2004). Requirements traceability. In Perspectives on software requirements (pp. 91–113). Springer. Raja, U. A. (2009). Empirical studies of requirements validation techniques. 2009 2nd International Conference on Computer, Control and Communication, IC4 2009. http://doi.org/10.1109/IC4.2009.4909209 Ramesh, B., & Jarke, M. (2001). Toward reference models for requirements traceability. Software Engineering, IEEE Transactions on, 27(1), 58–93. Ramesh, B., Stubbs, C., Powers, T., & Edwards, M. (1997). Requirements traceability : Theory and practice, 3, 397–415. Regan, G., McCaffery, F., McDaid, K., & Flood, D. (2012). The barriers to traceability and their potential solutions: towards a reference framework. In Software Engineering and Advanced Applications (SEAA), 2012 38th EUROMICRO Conference on (pp. 319–322). IEEE. Regan, G., McCaffery, F., McDaid, K., & Flood, D. (2014). The Development and Validation of a Traceability Assessment Model. In Software Process Improvement and Capability Determination (pp. 72–83). Springer. Rempel, P., Mader, P., & Kuschke, T. (2013). An empirical study on project-specific traceability strategies. 2013 21st IEEE International Requirements Engineering Conference, RE 2013 - Proceedings, 195–204. http://doi.org/10.1109/RE.2013.6636719 Richards, L., & Morse, J. M. (2012). Readme first for a user’s guide to qualitative methods. Sage. Rikhari, P., & Kumar, A. (2012). Validating the Change Management Process for Managing Changing Requirements with the help of a Real Life Project. International Journal of Computer Applications, 58(7). Rochimah, S., Wan Kadir, W. M. N., & Abdullah, A. H. (2007). An Evaluation of Traceability Approaches to Support Software Evolution. International Conference on Software Engineering Advances (ICSEA 2007), (October), 19–19. http://doi.org/10.1109/ICSEA.2007.17 Rosmadi, N. A., Ahmad, S., & Abdullah, N. (2015). The Relevance of Software Requirement Defect Management to Improve Requirements and Product Quality: A Systematic Literature Review. In Pattern Analysis, Intelligent Security and the Internet of Things (pp. 95–106). Springer. Sadiq, M., & Jain, S. K. (2014). Stakeholder identification method in goal oriented requirements elicitation process. In Requirements Prioritization and Communication (RePriCo), 2014 IEEE 5th International Workshop on (pp. 25–33). IEEE. Saiedian, H., Kannenberg, A., & Morozov, S. (2013). A streamlined, cost-effective database approach to manage requirements traceability. Software Quality Journal, 21(1), 23–38. Saldaña, J. (2015). The coding manual for qualitative researchers. Sage. Salvador, C., Nakasone, A., & Pow-Sang, J. A. (2014). A systematic review of usability techniques in agile methodologies. In Proceedings of the 7th Euro American Conference on Telematics and Information Systems (p. 17). ACM. Sarkan, H. M., Ahmad, T. P. S., & Bakar, A. A. (2011). Using JIRA and Redmine in requirement development for agile methodology. In Software Engineering (MySEC), 2011 5th Malaysian Conference in (pp. 408–413). IEEE. Schwarz, H., Ebert, J., & Winter, A. (2010a). Graph-based traceability: A comprehensive approach. Software and Systems Modeling, 9(4), 473–492. http://doi.org/10.1007/s10270-009-0141-4 Schwarz, H., Ebert, J., & Winter, A. (2010b). Graph-based traceability: a comprehensive approach. Software & Systems Modeling, 9(4), 473–492. Sekaran, U., & Bougie, R. (2010). Research methods for business: A skill building approach. Wiley. London. Shahid, M., Ibrahim, S., & Mahrin, M. N. (2011). An evaluation of requirements management and traceability tools. World Academy of Science, Engineering and Technology, 78(6), 596–601. Retrieved from http://www.scopus.com/inward/record.url?eid=2-s2.0-84855217455&partnerID=40&md5=63ec72af99df5960c8e026199d2ddf0f Shahid, M., Ibrahim, S., & Mahrin, M. N. (2011). An Evaluation of Requirements Management and Traceability Tools. World Academy of Science, Engineering and Technology, WASET. Sharma, R., Bhatia, J., & Biswas, K. K. (2014). Machine learning for constituency test of coordinating conjunctions in requirements specifications. Proceedings of the 3rd International Workshop on Realizing Artificial Intelligence Synergies in Software Engineering - RAISE 2014, 25–31. http://doi.org/10.1145/2593801.2593806 Sharma, S., & Pandey, S. K. (2014). Requirements elicitation: Issues and challenges. In Computing for Sustainable Global Development (INDIACom), 2014 International Conference on (pp. 151–155). IEEE. Sherba, S. A., Anderson, K. M., & Faisal, M. (2003). A framework for mapping traceability relationships. In Proceedings of the 2nd International Workshop on Traceability in Emerging Forms of Software Engineering (pp. 32–39). Shubhamangala, B. R., Rao, L. M., Dakshinamurthy, A., & Singh, C. G. L. (2012). Ability based domain specific training: a pragmatic solution to poor requirement engineering in CMM level 5 companies. In Computer Science and Automation Engineering (CSAE), 2012 IEEE International Conference on (Vol. 3, pp. 459–464). IEEE. Silva Souza, V. E., Lapouchnian, A., Robinson, W. N., & Mylopoulos, J. (2011). Awareness requirements for adaptive systems. In Proceedings of the 6th international symposium on Software engineering for adaptive and self-managing systems (pp. 60–69). ACM. Smith, A. M. (2012). Research Methodology: A Step-by-step Guide for Beginners. Churchill Livingstone. Solemon, B., Sahibuddin, S., & Ghani, A. A. A. (2010). Adoption of requirements engineering practices in Malaysian software development companies. In Advances in Software Engineering (pp. 141–150). Springer. Soonsongtanee, S., & Limpiyakorn, Y. (2010). Enhancement of requirements traceability with state diagrams. In Computer Engineering and Technology (ICCET), 2010 2nd International Conference on (Vol. 2, pp. V2–248). IEEE. Spanoudakis, G., & Zisman, A. (2005). Software traceability: a roadmap. Handbook of Software Engineering and Knowledge Engineering, 3, 395–428. Spanoudakis, G., Zisman, A., Pérez-Minana, E., & Krause, P. (2004). Rule-based generation of requirements traceability relations. Journal of Systems and Software, 72(2), 105–127. Speziale, H., & Carpenter, D. R. (2003). Qualitative research in nursing: Advancing the humanistic imperative. New York. Harper and Row. Stallinger, F., Neumann, R., Schossleitner, R., & Zeilinger, R. (2011). Linking software life cycle activities with product strategy and economics: Extending ISO/IEC 12207 with product management best practices. In Software Process Improvement and Capability Determination (pp. 157–168). Springer. Sutcliffe, A., & Sawyer, P. (2013). Requirements elicitation: Towards the unknown unknowns. 2013 21st IEEE International Requirements Engineering Conference, RE 2013 - Proceedings, 92–104. http://doi.org/10.1109/RE.2013.6636709 Thomas, S. W., Adams, B., Hassan, A. E., & Blostein, D. (2014). Studying software evolution using topic models. Science of Computer Programming, 80, 457–479. Torkar, R., Gorschek, T., Feldt, R., Svahnberg, M., Raja, U. A., & Kamran, K. (2012). Requirements traceability: a systematic review and industry case study. International Journal of Software Engineering and Knowledge Engineering, 22(03), 385–433. Vagias, W. M. (2006). Likert-type scale response anchors. Clemson International Institute for Tourism & Research Development, Department of Parks, Recreation and Tourism Management. Clemson University. Wen, B., Luo, Z., & Liang, P. (2012). Distributed and Collaborative Requirements Elicitation based on Social Intelligence. In Web Information Systems and Applications Conference (WISA), 2012 Ninth (pp. 127–130). IEEE. Wiegers, K., & Beatty, J. (2013). Software requirements. Pearson Education. Wiegers, K. E. (2000). When Telepathy Won’t Do: Requirements Engineering Key Practices. Cutter IT Journal, 13(5), 9–15. Willig, C., & Stainton-Rogers, W. (2007). The SAGE handbook of qualitative research in psychology. Sage. Winkler, S., & Pilgrim, J. (2010). A survey of traceability in requirements engineering and model-driven development. Software and Systems Modeling (SoSyM), 9(4), 529–565. Winkler, S., & von Pilgrim, J. (2010). A survey of traceability in requirements engineering and model-driven development. Software & Systems Modeling, 9(4), 529–565. http://doi.org/10.1007/s10270-009-0145-0 Yousuf, F., Zaman, Z., & Ikram, N. (2008). Requirements validation techniques in GSD: A survey. IEEE INMIC 2008: 12th IEEE International Multitopic Conference - Conference Proceedings, 553–557. http://doi.org/10.1109/INMIC.2008.4777800 Yozgyur, K. (2014). A proposal for a requirements elicitation tool to increase stakeholder involvement. In Software Engineering and Service Science (ICSESS), 2014 5th IEEE International Conference on (pp. 145–148). IEEE. Zaib, A., Chauhan, M., & Sirshar, M. (2015). A Review Analysis on Non-Functional Requirements and Causes of Failure of Projects. Zainol, A., & Mansoor, S. (2011). An investigation of a requirements management tool elements. 2011 IEEE Conference on Open Systems, ICOS 2011, 59–64. http://doi.org/10.1109/ICOS.2011.6079304 Zhang, Z. (2007). Effective requirements development-A comparison of requirements elicitation techniques. Software Quality Management XV: Software Quality in the Knowledge Society, E. Berki, J. Nummenmaa, I. Sunley, M. Ross and G. Staples (Ed.) British Computer Society, 225–240. Zhou, J. (2014a). Requirements Development and Management of Embedded Real-Time Systems, 479–484. Zhou, J. (2014b). Requirements development and management of embedded real-time systems. In Requirements Engineering Conference (RE), 2014 IEEE 22nd International (pp. 479–484). IEEE. Zikmund, W. G. (2003). Sample designs and sampling procedures. Business Research Methods, 7, 368–400. Zisman, A. (2012). Using rules for traceability creation. In Software and Systems Traceability (pp. 147–170). Springer. Zou, X., Settimi, R., & Cleland-Huang, J. (2010). Improving automated requirements trace retrieval: a study of term-based enhancement methods. Empirical Software Engineering, 15(2), 119–146.

An investigation of requirements traceability practices in software companies in Malaysia

Similar Items