The Experts below are selected from a list of 2676 Experts worldwide ranked by ideXlab platform
Adam Kolawa - One of the best experts on this subject based on the ideXlab platform.
-
Automated Defect Prevention: Best Practices in Software Management - Principles of Automated Defect Prevention
Automated Defect Prevention, 2007Co-Authors: Dorota Huizinga, Adam KolawaAbstract:This chapter contains sections titled: Introduction Defect Prevention: Definition and Benefits Historical Perspective: Defect Analysis and Prevention in the Auto Industry??-??What Happened to Deming? Principles of Automated Defect Prevention Automated Defect Prevention-Based Software Development Process Model Examples Acronyms Glossary References Exercises
-
Automated Defect Prevention: Best Practices in Software Management
Automated Defect Prevention: Best Practices in Software Management, 2007Co-Authors: Dorota Huizinga, Adam KolawaAbstract:This book describes an approach to software management based on establishing an infrastructure that serves as the foundation for the project. This infrastructure defines people roles, necessary technology, and interactions between people and technology. This infrastructure automates repetitive tasks, organizes project activities, tracks project status, and seamlessly collects project data to provide measures necessary for decision making. Most importantly, this infrastructure sustains and facilitates the improvement of human-defined processes.The methodology described in the book, which is called Automated Defect Prevention (ADP) stands out from the current software landscape as a result of two unique features: its comprehensive approach to Defect Prevention, and its far-reaching emphasis on automation. ADP is a practical and thorough guide to implementing and managing software projects and processes. It is a set of best practices for software management through process improvement, which is achieved by the gradual automation of repetitive tasks supported and sustained by this flexible and adaptable infrastructure, an infrastructure that essentially forms a software production line.In defining the technology infrastructure, ADP describes necessary features rather than specific tools, thus remaining vendor neutral. Only a basic subset of features that are essential for building an effective infrastructure has been selected. Many existing commercial and non-commercial tools support these, as well as more advanced features. Appendix E contains such a list.
-
Principles of Automated Defect Prevention
Automated Defect Prevention: Best Practices in Software Management, 1Co-Authors: Dorota Huizinga, Adam KolawaAbstract:This chapter contains sections titled: Introduction Defect Prevention: Definition and Benefits Historical Perspective: Defect Analysis and Prevention in the Auto Industry��-��What Happened to Deming? Principles of Automated Defect Prevention Automated Defect Prevention-Based Software Development Process Model Examples Acronyms Glossary References Exercises
-
Testing and Defect Prevention
Automated Defect Prevention: Best Practices in Software Management, 1Co-Authors: Dorota Huizinga, Adam KolawaAbstract:This chapter contains sections titled: Introduction Best Practices for Testing and Code Review Defect Analysis and Prevention Policy for Use of Problem Tracking System Policy for Use of Regression Testing System Examples Acronyms Glossary References Exercises
-
The Case for Automated Defect Prevention
Automated Defect Prevention: Best Practices in Software Management, 1Co-Authors: Dorota Huizinga, Adam KolawaAbstract:This chapter contains sections titled: What Is ADP? What Are the Goals of ADP? How Is ADP Implemented? From the Waterfall to Modern Software Development Process Models Acronyms Glossary References Exercises
R. G. Mays - One of the best experts on this subject based on the ideXlab platform.
-
Experiences with Defect Prevention
IBM Systems Journal, 1990Co-Authors: R. G. Mays, C. L. Jones, G. J. Holloway, D. P. StudinskiAbstract:Defect Prevention is the process of improving quality and productivity by preventing the injection of Defects into a product. It consists of four elements integrated into the development process: (1) causal analysis meetings to identify the root cause of Defects and suggest preventive actions; (2) an action team to implement the preventive actions; (3) kickoff meetings to increase awareness of quality issues specific to each development stage; and (4) data collection and tracking of associated data. The Defect Prevention Process has been successfully implemented in a variety of organizations within IBM, some for more than six years. This paper discusses the steps needed to implement this process and the results that may be obtained. Data on quality, process costs, benefits, and practical experiences are also presented. Insights into the nature of programming errors and the application of this process to a variety of working environments are discussed.
-
Applications of Defect Prevention in software development
IEEE Journal on Selected Areas in Communications, 1990Co-Authors: R. G. MaysAbstract:A description is given of the Defect Prevention process. It consists of causal analysis meetings to identify the root causes of errors and suggest preventive actions, an action team that implements the preventive actions, stage kickoff meetings to provide feedback to developers at each stage of the development cycle, and data collection and tracking of associated data. Typical preventive actions include process changes (including common error lists, checklists, and other forms of feedback), new or improved tools, improved education, product changes, and improved communications among developers. The Defect Prevention process has been applied successfully in a number of software development organizations within IBM, with significant reduction in errors. The application of this process to different types of organizations involved in software development, including design, development, test, information development, planning and requirements, and human factors is described. For each type of organization, different processes, tools, and methodologies are used. It is shown that the Defect Prevention process can be applied to errors arising from each particular process.
T Gopalakrishnan R Nair - One of the best experts on this subject based on the ideXlab platform.
-
Defect Prevention approaches in medium scale it enterprises
arXiv: Software Engineering, 2010Co-Authors: T Gopalakrishnan R NairAbstract:The software industry is successful, if it can draw the complete attention of the customers towards it. This is achievable if the organization can produce a high quality product. To identify a product to be of high quality, it should be free of Defects, should be capable of producing expected results. It should be delivered in an estimated cost, time and be maintainable with minimum effort. Defect Prevention is the most critical but often neglected component of the software quality assurance in any project. If applied at all stages of software development, it can reduce the time, cost and resources required to engineer a high quality product.
-
effective Defect Prevention approach in software process for achieving better quality levels
arXiv: Software Engineering, 2010Co-Authors: V Suma, T Gopalakrishnan R NairAbstract:Defect Prevention is the most vital but habitually neglected facet of software quality assurance in any project. If functional at all stages of software development, it can condense the time, overheads and wherewithal entailed to engineer a high quality product. The key challenge of an IT industry is to engineer a software product with minimum post deployment Defects. This effort is an analysis based on data obtained for five selected projects from leading software companies of varying software production competence. The main aim of this paper is to provide information on various methods and practices supporting Defect detection and Prevention leading to thriving software generation. The Defect Prevention technique unearths 99% of Defects. Inspection is found to be an essential technique in generating ideal software generation in factories through enhanced methodologies of abetted and unaided inspection schedules. On an average 13 % to 15% of inspection and 25% - 30% of testing out of whole project effort time is required for 99% - 99.75% of Defect elimination. A comparison of the end results for the five selected projects between the companies is also brought about throwing light on the possibility of a particular company to position itself with an appropriate complementary ratio of inspection testing.
-
effective Defect Prevention approach in software process for achieving better quality levels
World Academy of Science Engineering and Technology International Journal of Social Behavioral Educational Economic Business and Industrial Engineerin, 2008Co-Authors: V Suma, T Gopalakrishnan R NairAbstract:Defect Prevention is the most vital but habitually neglected facet of software quality assurance in any project. If functional at all stages of software development, it can condense the time, overheads and wherewithal entailed to engineer a high quality product. The key challenge of an IT industry is to engineer a software product with minimum post deployment Defects. This effort is an analysis based on data obtained for five selected projects from leading software companies of varying software production competence. The main aim of this paper is to provide information on various methods and practices supporting Defect detection and Prevention leading to thriving software generation. The Defect Prevention technique unearths 99% of Defects. Inspection is found to be an essential technique in generating ideal software generation in factories through enhanced methodologies of abetted and unaided inspection schedules. On an average 13 % to 15% of inspection and 25% 30% of testing out of whole project effort time is required for 99% 99.75% of Defect elimination. A comparison of the end results for the five selected projects between the companies is also brought about throwing light on the possibility of a particular company to position itself with an appropriate complementary ratio of inspection testing. Keywords—Defect Detection and Prevention, Inspections, Software Engineering, Software Process, Testing.
-
Enhanced Approaches in Defect Detection and Prevention Strategies in Small and Medium Scale Industries
2008 The Third International Conference on Software Engineering Advances, 2008Co-Authors: V Suma, T Gopalakrishnan R NairAbstract:Advancement in fundamental engineering aspects of software development enables IT enterprises to develop a more cost effective and better quality product through aptly organized Defect detection and Prevention strategies. Software inspection has proved to be the most thriving and proficient technique for Defect detection and Prevention.The work analyzes data obtained for five different projects from progressive software company of varying software production capabilities. The Defect Prevention technique involves proactive, reactive and retrospective moves to uncover 70% of Defects during inspections and developer unit testing. The validation testing uncovers 29% of Defects. Inspection becomes imperative in creating much more ideal software in factories through enhanced methodologies of aided and unaided inspection schemes.
Mathieu Nayrolles - One of the best experts on this subject based on the ideXlab platform.
-
A Project on Software Defect Prevention at Commit-Time: A Success Story of University-Industry Research Collaboration
2018 IEEE ACM 5th International Workshop on Software Engineering Research and Industrial Practice (SER&IP), 2018Co-Authors: Wahab Hamou-lhadj, Mathieu NayrollesAbstract:In this talk, we describe a research collaboration project between Concordia University and Ubisoft. The project consists of investigating techniques for Defect Prevention at commit-time for increased software quality. The outcome of this project is a tool called CLEVER (Combining Levels of Bug Prevention and Resolution techniques) that uses machine learning to automatically detect coding Defects as programmers write code. The main novelty of CLEVER is that it relies on code matching techniques to detect coding mistakes based on a database of historical code Defects found in multiple related projects. The tool also proposes fixes based on known patterns.
-
SER&IP@ICSE - A project on software Defect Prevention at commit-time: a success story of university-industry research collaboration
Proceedings of the 5th International Workshop on Software Engineering Research and Industrial Practice - SER&IP '18, 2018Co-Authors: Wahab Hamou-lhadj, Mathieu NayrollesAbstract:In this talk, we describe a research collaboration project between Concordia University and Ubisoft. The project consists of investigating techniques for Defect Prevention at commit-time for increased software quality. The outcome of this project is a tool called CLEVER (Combining Levels of Bug Prevention and Resolution techniques) that uses machine learning to automatically detect coding Defects as programmers write code. The main novelty of CLEVER is that it relies on code matching techniques to detect coding mistakes based on a database of historical code Defects found in multiple related projects. The tool also proposes fixes based on known patterns.
Dorota Huizinga - One of the best experts on this subject based on the ideXlab platform.
-
Automated Defect Prevention: Best Practices in Software Management - Principles of Automated Defect Prevention
Automated Defect Prevention, 2007Co-Authors: Dorota Huizinga, Adam KolawaAbstract:This chapter contains sections titled: Introduction Defect Prevention: Definition and Benefits Historical Perspective: Defect Analysis and Prevention in the Auto Industry??-??What Happened to Deming? Principles of Automated Defect Prevention Automated Defect Prevention-Based Software Development Process Model Examples Acronyms Glossary References Exercises
-
Automated Defect Prevention: Best Practices in Software Management
Automated Defect Prevention: Best Practices in Software Management, 2007Co-Authors: Dorota Huizinga, Adam KolawaAbstract:This book describes an approach to software management based on establishing an infrastructure that serves as the foundation for the project. This infrastructure defines people roles, necessary technology, and interactions between people and technology. This infrastructure automates repetitive tasks, organizes project activities, tracks project status, and seamlessly collects project data to provide measures necessary for decision making. Most importantly, this infrastructure sustains and facilitates the improvement of human-defined processes.The methodology described in the book, which is called Automated Defect Prevention (ADP) stands out from the current software landscape as a result of two unique features: its comprehensive approach to Defect Prevention, and its far-reaching emphasis on automation. ADP is a practical and thorough guide to implementing and managing software projects and processes. It is a set of best practices for software management through process improvement, which is achieved by the gradual automation of repetitive tasks supported and sustained by this flexible and adaptable infrastructure, an infrastructure that essentially forms a software production line.In defining the technology infrastructure, ADP describes necessary features rather than specific tools, thus remaining vendor neutral. Only a basic subset of features that are essential for building an effective infrastructure has been selected. Many existing commercial and non-commercial tools support these, as well as more advanced features. Appendix E contains such a list.
-
Principles of Automated Defect Prevention
Automated Defect Prevention: Best Practices in Software Management, 1Co-Authors: Dorota Huizinga, Adam KolawaAbstract:This chapter contains sections titled: Introduction Defect Prevention: Definition and Benefits Historical Perspective: Defect Analysis and Prevention in the Auto Industry��-��What Happened to Deming? Principles of Automated Defect Prevention Automated Defect Prevention-Based Software Development Process Model Examples Acronyms Glossary References Exercises
-
Testing and Defect Prevention
Automated Defect Prevention: Best Practices in Software Management, 1Co-Authors: Dorota Huizinga, Adam KolawaAbstract:This chapter contains sections titled: Introduction Best Practices for Testing and Code Review Defect Analysis and Prevention Policy for Use of Problem Tracking System Policy for Use of Regression Testing System Examples Acronyms Glossary References Exercises
-
The Case for Automated Defect Prevention
Automated Defect Prevention: Best Practices in Software Management, 1Co-Authors: Dorota Huizinga, Adam KolawaAbstract:This chapter contains sections titled: What Is ADP? What Are the Goals of ADP? How Is ADP Implemented? From the Waterfall to Modern Software Development Process Models Acronyms Glossary References Exercises
