Towards Employing Metrics in Measuring the Quality of Software Safety Critical Systems and Managing their Development
-
2018-12-09 https://doi.org/10.14419/ijet.v7i4.31.23356 -
Safety Critical Systems, Quality Management, Quality Metrics -
Abstract
Failures in safety critical systems have a high impact on the environment in which they are used. For that, developers usually follow specific development standards and techniques to avoid and reduce failures in such systems. Developers have to build safety critical systems considering the quality, complexity, and size factors in all the development phases beginning with the requirement gathering and ending with the maintenance and verification. In this paper, some quality models and some metrics for measuring the quality, complexity, and size of systems are explored. The metrics are classified to the development phases so that the classification indicates the degree of metrics usage in measuring the quality, complexity, and size factors in relation to the development phases. We are now working on relating the studied metrics in this paper with their impact on the development of the software safety critical system. We expect to use these metrics in the management of the development phases and processes of software safety critical systems so that a decision making could be performed based on the measurements of these metrics.
Â
Â
-
References
[1] M. Rausand, Reliability of safety-critical systems: theory and applications. John Wiley & Sons, 2014.
[2] L. E. G. Martins and T. Gorschek, “Requirements engineering for safety-critical systems: A systematic literature review,†Information and software technology, vol. 75, pp. 71–89, 2016.
[3] E. S. Grant, V. K. Jackson, and S. A. Clachar, “Towards a formal approach to validating and verifying functional design for complex safety critical systems,†GSTF Journal on Computing (JoC), vol. 2, no. 1, 2018.
[4] Iso and I. Std, “9126 software product evaluation–quality characteristics and guidelines for their use,†ISO/IEC Standard, vol. 9126, 2001.
[5] N. Bevan, “Quality in use: Meeting user needs for quality,†Journal of systems and software, vol. 49, no. 1, pp. 89–96, 1999.
[6] N. Silva and M. Vieira, “Towards making safety-critical systems safer: Learning from mistakes,†in Software Reliability Engineering Work shops (ISSREW), 2014 IEEE International Symposium, pp. 162–167, IEEE, 2014.
[7] R. S. Pressman, Software engineering: a practitioner’s approach. Pal- grave Macmillan, 2005.
[8] R. Singh, “A systematic approach to software safety,†in Software Engineering Conference, 1999.(APSEC’99) Proceedings. Sixth Asia Pacific, pp. 420–423, IEEE, 1999.
[9] S. R. Chidamber and C. F. Kemerer, “A metrics suite for object oriented design,†IEEE Transactions on software engineering, vol. 20, no. 6, pp. 476–493, 1994.
[10] S. R. Chidamber and C. F. Kemerer, “Towards a metrics suite for object oriented designâ€, vol. 26. ACM, 1991.
[11] S. R. Chidamber and C. F. Kemerer, “Moose: Metrics for object oriented software engineering,†in Workshop on Processes and Metrics for Object Oriented Software Development, OOPSLA, vol. 93, 1993.
[12] R. Harrison, S. Counsell, and R. Nithi, “An overview of object-oriented design metrics,†in Software Technology and Engineering Practice, 1997. Proceedings., Eighth IEEE International Workshop on incorporating Computer Aided Software Engineering, pp. 230–235, IEEE, 1997.
[13] F. B. Abreu,“Design metrics for oo software system,†in ECOOP ‘95, Quantitative Methods Workshop, 1995.
[14] F. B. Abreu, M. Goula˜o, and R. Esteves, “Toward the design quality evaluation of object-oriented software systems,†in Proceedings of the 5th International Conference on Software Quality, Austin, Texas, USA, pp. 44–57, 1995.
[15] M. Lorenz and J. Kidd, Object-oriented software metrics: a practical guide. Prentice-Hall, Inc., 1994.
[16] J. Bansiya and C. G. Davis, “A hierarchical model for object-oriented design quality assessment,†IEEE Transactions on software engineering, vol. 28, no. 1, pp. 4–17, 2002.
[17] J. Bansiya, A hierarchical model for quality assessment of object- oriented designs. The University of Alabama in Huntsville, 1997.
[18] T. J. McCabe, “A complexity measure,†IEEE Transactions on software Engineering, no. 4, pp. 308–320, 1976.
[19] J. P. Kearney, R. L. Sedlmeyer, W. B. Thompson, M. A. Gray, and M. A. Adler, “Software complexity measurement,†Communications of the ACM, vol. 29, no. 11, pp. 1044–1050, 1986.
[20] J. Albrecht, “Measuring application development productivity,†in Proc. of the Joint SHARE/GUIDE/IBM Application Development Symposium, pp. 83–92, 1979.
[21] J. Albrecht and J. E. Gaffney, “Software function, source lines of code, and development effort prediction: a software science validation,†IEEE transactions on software engineering, no. 6, pp. 639–648, 1983.
[22] D. R. Jeffery, G. C. Low, and M. Barnes, “A comparison of function point counting techniques,†IEEE Transactions on Software Engineering, vol. 19, no. 5, pp. 529–532, 1993.
[23] S. M. Henry, Information flow metrics for the evaluation of operating systems’ structure. PhD thesis, 1979.
[24] S. Henry and D. Kafura, “Software structure metrics based on in- formation flow,†IEEE transactions on Software Engineering, no. 5, pp. 510–518, 1981.
[25] R. Rask, P. Laamanen, and K. Lyyttinen, “Simulation and comparison of albrecht’s function point and demarco’s function bang metrics in a case environment,†IEEE Transactions on Software Engineering, vol. 19, no. 7, pp. 661–671, 1993.
[26] G. E. Stark, “Measurements for managing software maintenance.,†in icsm, p. 152, 1996.
[27] V. R. Basili and H. D. Rombach, “Tailoring the software process to project goals and environments,†in Proceedings of the 9th inter- national conference on Software Engineering, pp. 345–357, IEEE Computer Society Press, 1987.
-
Downloads
-
How to Cite
Din, J., Din, R., Yah Jusoh, Y., & Basheer Jasser, M. (2018). Towards Employing Metrics in Measuring the Quality of Software Safety Critical Systems and Managing their Development. International Journal of Engineering & Technology, 7(4.31), 135-139. https://doi.org/10.14419/ijet.v7i4.31.23356Received date: 2018-12-07
Accepted date: 2018-12-07
Published date: 2018-12-09