CFP last date
20 May 2024
Call for Paper
June Edition
IJCA solicits high quality original research papers for the upcoming June edition of the journal. The last date of research paper submission is 20 May 2024

Submit your paper
Know more
The week's pick
Responsive image
Enhancing Privacy Preservation: Multi-Attribute Protection with P-Sensitive K-Anonymity

Twinkle Patel Kiran Amin
Random Articles
Reseach Article

Classification of Software Requirement Errors: A Critical Review

by Pawan Kumar Chaurasia, R.A. Khan
journal cover thumbnail

International Journal of Computer Applications
Foundation of Computer Science (FCS), NY, USA
Volume 132 - Number 7
Year of Publication: 2015
Authors: Pawan Kumar Chaurasia, R.A. Khan
10.5120/ijca2015907465

Pawan Kumar Chaurasia, R.A. Khan . Classification of Software Requirement Errors: A Critical Review. International Journal of Computer Applications. 132, 7 ( December 2015), 9-14. DOI=10.5120/ijca2015907465

@article{ 10.5120/ijca2015907465,
author = { Pawan Kumar Chaurasia, R.A. Khan },
title = { Classification of Software Requirement Errors: A Critical Review },
journal = { International Journal of Computer Applications },
issue_date = { December 2015 },
volume = { 132 },
number = { 7 },
month = { December },
year = { 2015 },
issn = { 0975-8887 },
pages = { 9-14 },
numpages = {9},
url = { https://ijcaonline.org/archives/volume132/number7/23604-2015907465/ },
doi = { 10.5120/ijca2015907465 },
publisher = {Foundation of Computer Science (FCS), NY, USA},
address = {New York, USA}
}
%0 Journal Article
%1 2024-02-06T23:28:30.074873+05:30
%A Pawan Kumar Chaurasia
%A R.A. Khan
%T Classification of Software Requirement Errors: A Critical Review
%J International Journal of Computer Applications
%@ 0975-8887
%V 132
%N 7
%P 9-14
%D 2015
%I Foundation of Computer Science (FCS), NY, USA
Abstract

From last three decades various tools, techniques and methods are developed by researchers. The objective of research is to optimize the error and improve the quality of the software. During development of software, various errors are introduced by the developer at various phases of software development life cycle (SDLC). It is difficult to identify all the errors of the software by the developer of different phases. Various methodologies are proposed and implemented by the researcher to identify the errors. The objective of this paper is to review and develop taxonomy of requirement errors, prepare a list of requirement errors for the analysis. Conclusions are listed on software requirement errors at last. The list of requirement errors may support the researchers to improve their work in a systematic way and classify all requirement errors to increase the software quality.

References
  1. Nikora, A. P.; Lyu, M. R. Software reliability measurement experience. Handbook of Software Reliability Engineering, Lyu, M. R. Ed.;McGraw-Hill: New York, 1996; 255–301.
  2. P. Fusaro, F. Lanubile, G. Visaggio, A replicated experiment to assess requirements inspection techniques, Journal of Empirical Software Engineering 2(1) (1997) 39–57.
  3. F. Lanubile, F. Shull, V.R. Basili, Experimenting with error abstraction in requirements documents, in: Proceedings of Fifth International Software Metrics Symposium, METRICS’98, IEEE Computer Society, Bethesda, MD, 1998, pp. 114–121.
  4. S. Basu, N. Ebrahimi, Estimating the number of undetected errors: Bayesian model selection, in: Proceedings of the Ninth International Symposium on Software Reliability Engineering, IEEE Computer Society, Paderborn, Germany,1998, pp. 22–31.
  5. D.N. Card, Learning from our mistakes with defect causal analysis, IEEE Software 15 (1) (1998) 56–63.
  6. R.B. Grady, Software failure analysis for high-return process improvement, Hewlett–Packard Journal 47 (4) (1996) 15–24.
  7. J. Jacobs, J.V. Moll, P. Krause, R. Kusters, J. Trienekens, A. Brombacher, Exploring defect causes in products developed by virtual teams, Journal of Information and Software Technology 47 (6) (2005) 399–410.
  8. R.G. Mays, C.L. Jones, G.J. Holloway, D.P. Studinski, Experiences with defect prevention, IBM Systems Journal 29 (1) (1990) 4–32.
  9. T. Nakashima, M. Oyama, H. Hisada, N. Ishii, Analysis of software bug causes and its prevention, Journal of Information and Software Technology 41 (15) (1999) 1059–1068.
  10. Bhandari, M. Halliday, E. Tarver, D. Brown, J. Chaar, R. Chillarege, A case study of software process improvement during development, IEEE Transactions on Software Engineering 19 (12) (1993) 1157–1170.
  11. S. Beecham, T. Hall, C. Britton, M. Cottee, A. Rainer, Using an expert panel to validate a requirements process improvement model, The Journal of Systems and Software 76 (3) (2005) 251–275.
  12. G.J. Browne, V. Ramesh, Improving information requirements determination: a cognitive perspective, Journal of Information and Management 39 (8) (2002) 625–645.
  13. C. Debou, A.K. Combelles, Linking software process improvement to business strategies: experiences from industry, Journal of Software Process: Improvement and Practice 5 (1) (2000) 55–64.
  14. M.R. Endsley, Situation awareness and human error: designing to support human performance, in: Proceedings of the High Consequence Systems Surety Conference, SA Technologies, Albuquerque, NM, 1999, pp. 2–9.
  15. D.A. Norman, Design rules based on analyses of human error, Communications of the ACM 26 (4) (1983) 254–258.
  16. D.A. Norman, Steps towards a cognitive engineering: design rules based on analyses of human error, Communications of the ACM 26 (4) (1981) 254–258.
  17. C. Trevor, S. Jim, C. Judith, K. Brain, Human Error in Software generation Process, University of Technology, Loughborough, England, 1994.
  18. Endres, An analysis of errors and their causes in system programs, IEEE Transactions on Software Engineering 1 (2) (1975) 140–149.
  19. T.E. Bell, T.A. Thayer, Software requirements: are they really a problem?, in: Proceedings of Second International Conference on Software Engineering, IEEE Computer Society Press, Los Alamitos, CA, 1976, pp 61–68.
  20. T. Berling, T. Thelin, A case study of reading techniques in a software company, in: Proceedings of the 2004 International Symposium on Empirical Software Engineering (ISESE’04), IEEE Computer Society, 2004, pp. 229–238.
  21. B. Freimut, C. Denger, M. Ketterer, An industrial case study of implementing and validating defect classification for process improvement and quality management, in: Proceedings of the 11th IEEE International Software Metrics Symposium, IEEE Press, 2005.
  22. P.C. Cacciabue, A methodology of human factors analysis for systems engineering: theory and applications, IEEE Transactions on System, Man and Cybernetics – Part A: Systems and Humans 27 (3) (1997) 325–329.
  23. Endres, An analysis of errors and their causes in system programs, IEEE Transactions on Software Engineering 1 (2) (1975) 140–149.
  24. S.H. Kan, V.R. Basili, L.N. Shapiro, Software quality: an overview from the perspective of total quality management, IBM Systems Journal 33 (1) (1994) 4–19.
  25. D. Batra, Cognitive complexity in Data modelling: causes and recommendations, Requirements Engineering Journal 12 (4) (2007) 231–244.
  26. K. Sasao, J. Reason, Team errors: definition and taxonomy, Journal of Reliability Engineering and System Safety 65 (1) (1999) 1–9.
  27. D.A. Gaitros, Common errors in large software development projects, The Journal of Defense Software Engineering 12 (6) (2004) 21–25.
  28. J. Galliers, S. Minocha, A. Sutcliffe, A causal model of human error for safety critical user interface design, ACM Transactions on Computer–Human Interaction 5 (3) (1998) 756–769.
  29. J. Coughlan, D.R. Macredie, Effective communication in requirements elicitation: a comparison of methodologies, Requirements Engineering Journal 7 (2) (2002) 47–60.
  30. P. K Chaurasia, Software Reliability Chain Model, International Journal of Software and Web Services (IJSWS), Vol 1, Issue 8, pp 46-50.
  31. R.R. Lutz, Analyzing software requirements errors in safety-critical, embedded systems, in: Proceedings of the IEEE International Symposium on Requirements Engineering, IEEE Computer Society Press, San Diego, CA, USA, 1993, pp. 126–133.
  32. S. Sakthivel, A survey of requirement verification techniques, Journal of Information Technology 6 (2) (1991) 68–79.
  33. B. Cheng, R. Jeffrey, Comparing inspection strategies for software requirement inspections, in: Proceedings of the 1996 Australian Software Engineering Conference, IEEE Computer Society, Melbourne, Australia, 1996, pp. 203–211.
  34. P.M. Fitts, R.E. Jones, Analysis of factors contributing to 460 ‘pilot error’ experiences in operating aircrafts control, in: Proceedings of Selected Papers on Human Factors in the Design and Use of Control Systems, Dover Publications Inc., New York, 1961, pp. 332–358.
  35. A.J. Ko, B.A. Myers, Development and evaluation of a model of programming errors, in: Proceedings of IEEE Symposium on Human Centric Computing Languages and Environments, IEEE Computer Society, 2003, pp. 7–14.
  36. Swain, H. Guttman, Handbook of Human Reliability Analysis with Emphasis on Nuclear Power Plant Applications, Nuclear Regulatory Commission, Washington, DC, 1983.
  37. P. K Chaurasia, How Accountability Improves Software Reliability?, International Journal of Computer Science and Technology (IJCSET), Vol 5, Issue 9, pp 868-871.
  38. S.T. Shorrock, B. Kirwan, Development and application of a human error identification tool for air traffic control, Journal of Applied Ergonomics 33 (4) (2002) 319–336.
Index Terms

Computer Science
Information Sciences

Keywords

Software Quality Systematic Review Error Fault Failure Reliability.

Powered by PhDFocusTM