A Detailed Phasewise Study on Software Metrics : A Systematic Literature Review

Authors

  • Ausaf Ahmad  Department of Computer Science, Aligarh Muslim University, Aligarh, Uttar Pradesh, India
  • Tamanna Siddiqui  Department of Computer Science, Aligarh Muslim University, Aligarh, Uttar Pradesh, India
  • Najeeb Ahmad Khan  SRB International Private Limited, Noida, Uttar Pradesh, India

Keywords:

Software Development Lifecycle, Systematic Phase, IEEExplore

Abstract

As we all aware that the measurement becomes an essential part of all engineering fashion and software development lifecycle is no exception. Software metric applied to create quantitative/qualitative decisions regarding development process and product as well as in risk assessment. The verities of software metrics have been developed that have utilized by different project personnel at different phase of software development to fulfill the objective in an effective way. In this paper, we discuss about software measurement and metrics along with their standard role in the software development. A systematic phase wise studies on the metrics used in different phase of software development lifecycle have been carried out.

References

  1. Lyu, M.R. (Revised 2005). Handbook of Software Reliability Engineering. IEEE Computer Society Press, California.
  2. Fenton, N.; Bieman, J. (2014).Software Metrics a Rigorous and Practical Approach.3rd edition, CRC press.
  3. Lima, P., Guerra, E., Meirelles, P., Kanashiro, L., Silva, H., &Silveira, F. F. (2018). A Metrics Suite for code annotation assessment. Journal of Systems and Software, vol. 137,pp. 163-183.
  4. Padhy, Neelamadhab, Satapathy, S., and Singh, R.P., (2018).State-of-the-art object-oriented metrics and its reusability: a decade review.In Smart Computing and Informatics, pp. 431-441. Springer
  5. Scotto, M.; Sillitti, A., Succi, G., &Vernazza, T. (2004, March). A relational approach to software metrics. In Proceedings of the 2004 ACM symposium on Applied computing. pp. 1536-1540.
  6. Gomez, O., Oktaba, H., Piattini, M., &García, F. (2006, September). A systematic review measurement in software engineering: State-of-the-art in measures. In International Conference on Software and Data Technologies (pp. 165-176).Springer, Berlin, Heidelberg.
  7. Unterkalmsteiner, M.; Gorschek, T.; Islam, A. K. M. M.; Cheng, C.K.; Permadi, R. B.; Feldt, R. (2012). A Systematic review measurement in Evaluation and Measurement of Software Process Improvement—A Systematic Literature Review, IEEE Transactions on Software, 38(2), 10.1109/TSE.2011.26.
  8. Kitchenham, B. (2010). What's up with software metrics?-A preliminary mapping study. Journal of systems and software, 83(1), 37-51.
  9. Brereton, P., Kitchenham, B. A., Budgen, D., Turner, M., & Khalil, M. (2007). Lessons from applying the systematic literature review process within the software engineering domain. Journal of systems and software, 80(4), 571-583.
  10. Siddiqui, T., & Ahmad, A., (2018) . “Data Mining Tools and Techniques for Mining Software Repositories: A Systematic Review”. In: Aggarwal V., Bhatnagar V., Mishra D. (eds) Big Data Analytics. Advances in Intelligent Systems and Computing, vol 654. Pp. 717-726 Springer, Singapore.
  11. Siddiqui, T., Ahmad , A., (2018) Complexity Clarification through Code Metrics. Proceedings of the 12th INDIACom, pp. 3746-3749.
  12. Keele, S. (2007).Guidelines for performing systematic literature reviews in software engineering. In Technical report, Ver. 2.3 EBSE Technical Report. EBSE.sn.
  13. Kitchenham, B., Brereton, O. P., Budgen, D., Turner, M., Bailey, J., & Linkman, S. (2009). Systematic literature reviews in software engineering-a systematic literature review. Information and software technology, 51(1), 7-15.
  14. Unterkalmsteiner, M., Gorschek, T., Islam, A. M., Cheng, C. K., Permadi, R. B., &Feldt, R. (2012 b). Evaluation and measurement of software process improvement—a systematic literature review. IEEE Transactions on Software Engineering, 38(2), 398-424.
  15. Nuseibeh, B., & Easterbrook, S. (2000, May). Requirements engineering: A roadmap. In Proceedings of the Conference on the Future of Software Engineering (pp. 35-46).
  16. Davis, A. M. (1993). Software requirements: objects, functions, and states. Prentice-Hall, Inc.
  17. Zave, P., & Jackson, M. (1997).Four dark corners of requirements engineering.ACM transactions on Software Engineering and Methodology (TOSEM), 6(1), 1-30.
  18. Bokhari, M. U., & Siddiqui, S. T. (2011, March). Metrics for Requirements Engineering and Automated Requirements Tools. In Proceedings of the 5th National Conference.
  19. Soren Petersen, Design Metrics -- Is It Possible to Optimize Design for Innovation?, available at http://www.huffingtonpost.in/entry/design-metrics-is-it-poss_b_1411593.
  20. Wikipedia of Requirements analysis http://en.wikipedia.org/wiki/Requirements_analysis.Retrived 2018.
  21. Ralph, P., & Wand, Y. (2009).A proposal for a formal definition of the design concept. Design requirements engineering: A ten-year perspective, 14, 103-136.
  22. Freeman, P., & Hart, D. (2004).A science of design for software-intensive systems. Communications of the ACM, 47(8), 19-21.
  23. Booch, G.; (2004). Object-Oriented Analysis and Design with Applications (3rd Ed.). MA, USA: Addison Wesley. ISBN 0-201-89551-X. Retrieved 30 January 2015.
  24. Kafura, D., & Reddy, G. R. (1987).The use of software complexity metrics in software maintenance. IEEE Transactions on Software Engineering, (3), 335-343.
  25. Omarsson, O.T. (2017). Assessment Methods When Choosing a Software Architecture Alternative Software Maintainability Prediction. University of Gothenburg Gothenburg, Sweden. https://quandarypeak.com/2015/02/measuring-software-maintainability/.
  26. Gulechha, L.; Software Testing Metrics, available at: https://www.stickyminds.com/article/white-paper-software-testing-metrics.
  27. Ahamed S.S. (2009): Studying The Feasibility and Importance of Software Testing: An Analysis. International Journal of Engineering Science and Technology, 1(3), pp.119-128.
  28. Catal, C., &Diri, B. (2009). A systematic review of software fault prediction studies. Expert systems with applications, 36(4), 7346
  29. Cyclomatic complexity available at https://en.wikipedia.org/wiki/Cyclomatic_complexity.
  30. Ebert, C., Dumke, R., Bundschuh, M., &Schmietendorf, A. (2005). Best Practices in Software Measurement: How to use metrics to improve project and process performance. Springer Science & Business Media.
  31. http://www.informit.com/articles/article.aspx?p=30306&seqNum=3.
  32. https://en.wikipedia.org/wiki/Halstead_complexity_measures retrived october,2016.
  33. Jayanthi,B.; Kumari k. (2014): Brief study on Software quality metrics and software complexity metrics in Web application. International Journal of Engineering Sciences & Research Technology, 3(12) pp. 441-444.
  34. Kafura, D., & Reddy, G. R. (1987).The use of software complexity metrics in software maintenance. IEEE Transactions on Software Engineering, (3), 335-343.
  35. Khan,A. A.; Mahmood, A.; Amralla, S.M.; Mirza, T.H. (2016): Comparison of Software Complexity Metrics. International Journal of Computing and Network Technology, 4(1), pp. 19-26.
  36. Kushwaha, D. S., &Misra, A. K. (2006). Improved cognitive information complexity measure: a metric that establishes program comprehension effort. ACM SIGSOFT Software Engineering Notes, 31(5), pp. 1-7.
  37. Misra, S. (2006).A complexity measure based on cognitive weights.International Journal of Theoretical and Applied Computer Sciences, 1(1). Pp. 1-10.
  38. Moore, J. W. (1998). Software engineering standards. John Wiley & Sons, Inc..
  39. Nirpal, P. B., & Kale, K. V. (2011).A brief overview of software testing metrics. International Journal on Computer Science and Engineering (IJCSE), 3(1), 204-211.
  40. Shao, J., & Wang, Y. (2003). A new measure of software complexity based on cognitive weights. Canadian Journal of Electrical and Computer Engineering, 28(2), 69-74.
  41. Siddiqui, T., Wani, M. A., & Khan, N. A. (2011).Efficiency Metrics. BVICAM's International Journal of Information Technology, 3(2), pp. 61-65.
  42. Artemev, Vasilii, Vladimir Ivanov, Manuel Mazzara, Alan Rogers, Alberto Sillitti, Giancarlo Succi, and Eugene Zouev(2017). "An architecture for non-invasive software measurement." In International Andrei Ershov Memorial Conference on Perspectives of System Informatics, pp. 1-11. Springer, Cham,.
  43. O'Regan, Gerard.(2017). "Software Metrics and Problem-Solving." In Concise Guide to Software Engineering, pp. 139-170. Springer,
  44. Arar, O.F. and Ayan, K., (2016).Deriving thresholds of software metrics to predict faults on open source software: Replicated case studies.Expert Systems with Applications, 61, pp.106-121.
  45. Toure, F., Badri, M., &Lamontagne, L. (2018).Predicting different levels of the unit testing effort of classes using source code metrics: a multiple case study on open-source software. Innovations in Systems and Software Engineering, Vol. 14(1), pp. 15-46.
  46. Gasparic, M., & Janes, A. (2016). What recommendation systems for software engineering recommend: A systematic literature review. Journal of Systems and Software, 113, 101-113.

Downloads

Published

2018-04-30

Issue

Section

Research Articles

How to Cite

[1]
Ausaf Ahmad, Tamanna Siddiqui, Najeeb Ahmad Khan, " A Detailed Phasewise Study on Software Metrics : A Systematic Literature Review , IInternational Journal of Scientific Research in Computer Science, Engineering and Information Technology(IJSRCSEIT), ISSN : 2456-3307, Volume 3, Issue 3, pp.1696-1705, March-April-2018.