Details

Factors causing the low adoption of Software Inspection

Factors causing low adoption of software inspections

Knowledge - Products - Facts

Aug, 2012

Quoted text Reference
(inside the source document) 		Source document
As companies have begun to turn to distributed software development, meeting in a room has become impractical. Calefato, F., Lanubile, F., & Mallardo, T. (2007). A Controlled Experiment on the Effects of Synchronicity in Remote Inspection Meetings. First International Symposium on Empirical Software Engineering and Measurement (ESEM 2007), 473-475. Ieee. doi: 10.1109/ESEM.2007.61.
... the problem here is that not a lot of companies know how to use these things. Jones, Capers. “Interview." Computer Aid Inc. July 2005 Ebert, C., Stewart, R., & Priven, L. (2008). How to Avoid Software Inspection Failure and Achieve Ongoing Benefits. CrossTalk: The Journal for Defense Software Engineering, 23-27.
Lack of supportive SDLC infrastructure Ebert, C., Stewart, R., & Priven, L. (2008). How to Avoid Software Inspection Failure and Achieve Ongoing Benefits. CrossTalk: The Journal for Defense Software Engineering, 23-27.
Poor management understanding of the Inspection Process, its benefits, and their responsibilities Ebert, C., Stewart, R., & Priven, L. (2008). How to Avoid Software Inspection Failure and Achieve Ongoing Benefits. CrossTalk: The Journal for Defense Software Engineering, 23-27.
Poor management understanding of the Inspection Process, its benefits, and their responsibilities Ebert, C., Stewart, R., & Priven, L. (2008). How to Avoid Software Inspection Failure and Achieve Ongoing Benefits. CrossTalk: The Journal for Defense Software Engineering, 23-27.
Poor management understanding of the Inspection Process, its benefits, and their responsibilities Ebert, C., Stewart, R., & Priven, L. (2008). How to Avoid Software Inspection Failure and Achieve Ongoing Benefits. CrossTalk: The Journal for Defense Software Engineering, 23-27.
No computerized management-planning tools Ebert, C., Stewart, R., & Priven, L. (2008). How to Avoid Software Inspection Failure and Achieve Ongoing Benefits. CrossTalk: The Journal for Defense Software Engineering, 23-27.
Too little schedule time for inspections Ebert, C., Stewart, R., & Priven, L. (2008). How to Avoid Software Inspection Failure and Achieve Ongoing Benefits. CrossTalk: The Journal for Defense Software Engineering, 23-27.
No computerized inspector tools Ebert, C., Stewart, R., & Priven, L. (2008). How to Avoid Software Inspection Failure and Achieve Ongoing Benefits. CrossTalk: The Journal for Defense Software Engineering, 23-27.
Inadequate monitoring of inspection execution and tracking of results Ebert, C., Stewart, R., & Priven, L. (2008). How to Avoid Software Inspection Failure and Achieve Ongoing Benefits. CrossTalk: The Journal for Defense Software Engineering, 23-27.
Inadequate monitoring of inspection execution and tracking of results Ebert, C., Stewart, R., & Priven, L. (2008). How to Avoid Software Inspection Failure and Achieve Ongoing Benefits. CrossTalk: The Journal for Defense Software Engineering, 23-27.
Computerized tools… performing analysis to identify how future inspections can be improved. Ebert, C., Stewart, R., & Priven, L. (2008). How to Avoid Software Inspection Failure and Achieve Ongoing Benefits. CrossTalk: The Journal for Defense Software Engineering, 23-27.
Computerized tools… performing analysis to identify how future inspections can be improved. Ebert, C., Stewart, R., & Priven, L. (2008). How to Avoid Software Inspection Failure and Achieve Ongoing Benefits. CrossTalk: The Journal for Defense Software Engineering, 23-27.
No inspection facilitator/ project champion Ebert, C., Stewart, R., & Priven, L. (2008). How to Avoid Software Inspection Failure and Achieve Ongoing Benefits. CrossTalk: The Journal for Defense Software Engineering, 23-27.
Slow inspection implementation by project teams Ebert, C., Stewart, R., & Priven, L. (2008). How to Avoid Software Inspection Failure and Achieve Ongoing Benefits. CrossTalk: The Journal for Defense Software Engineering, 23-27.
No inspection process capture Ebert, C., Stewart, R., & Priven, L. (2008). How to Avoid Software Inspection Failure and Achieve Ongoing Benefits. CrossTalk: The Journal for Defense Software Engineering, 23-27.
Software inspection process should be made simple and easy to implement with limited resources to promote its use in small and medium size organizations Mishra, D., & Mishra, A. (2009). Simplified software inspection process in compliance with international standards. Computer Standards & Interfaces, 31(4), 763-771. Elsevier B.V. doi: 10.1016/j.csi.2008.09.018.
Software inspection process should be made simple and easy to implement with limited resources to promote its use in small and medium size organizations Mishra, D., & Mishra, A. (2009). Simplified software inspection process in compliance with international standards. Computer Standards & Interfaces, 31(4), 763-771. Elsevier B.V. doi: 10.1016/j.csi.2008.09.018.
...for others, inspections never succeeded aswell as expected, primarily because these organizations did not learn how to make inspections both effective and low cost. Ron Radice, High Quality Low Cost Software Inspections, Paradoxicon Publishing, Andover, MA, 2002. Mishra, D., & Mishra, A. (2009). Simplified software inspection process in compliance with international standards. Computer Standards & Interfaces, 31(4), 763-771. Elsevier B.V. doi: 10.1016/j.csi.2008.09.018.
...most of the organizations are not able to use inspections in software development process as these are too rigorous to follow… Mishra, D., & Mishra, A. (2009). Simplified software inspection process in compliance with international standards. Computer Standards & Interfaces, 31(4), 763-771. Elsevier B.V. doi: 10.1016/j.csi.2008.09.018.
...these evolutions in areas such as strongly typed languages, automated tools and improved testing environments, many defect groupings no longer exist. H. Siy and L. Votta. Does the modern code inspection have value? icsm, 00:281, 2001 Mcmeekin, D. A., Konsky, B. R. V., Chang, E., & Cooper, D. J. A. (n.d.). Checklist Based Reading ' s Influence on a Developer ' s Understanding. Communications.
It can even sometimes be difficult for projects to get the resources to keep a sufficient number of inspections in place at all… Shull, F., Feldmann, R. L., Seaman, C., Regardie, M., & Godfrey, S. (2010). Fully employing software inspections data. Innovations in Systems and Software Engineering. doi: 10.1007/s11334-010-0132-1.
There is a learning curve involved, meaning that it takes some time for developers to understand how to effectively find defects Shull, F., Feldmann, R. L., Seaman, C., Regardie, M., & Godfrey, S. (2010). Fully employing software inspections data. Innovations in Systems and Software Engineering. doi: 10.1007/s11334-010-0132-1.
It's hard to make connections between inspection effort and specific final product qualities… Denger, C., & Shull, F. (2007). A Practical Approach for Quality-Driven Inspections. IEEE Software, 24(2), 79-86. doi:10.1109/MS.2007.31
Largely dependent on individual experience Xu, B. (2010). Cost Efficient Software Review in an E-Business Software Development Project. 2010 International Conference on E-Business and E-Government, 2680-2683. Ieee. doi:10.1109/ICEE.2010.677
Current review processes face these obstacles due to their rigid and time consuming nature. Nazir, S., Fatima, N., & Malik, S. (2008). Effective Hybrid Review Process (EHRP). 2008 International Conference on Computer Science and Software Engineering, 763-771. Ieee. doi:10.1109/CSSE.2008.1417
...some engineers consider inspections to be uncreative work that adds costs. Komssi, M., Kauppinen, M., Pyhajarvi, M., Talvio, J., & Mannisto, T. (2010). Persuading Software Development Teams to Document Inspections: Success Factors and Challenges in Practice. 2010 18th IEEE International Requirements Engineering Conference, 283-288. Ieee. doi: 10.1109/RE.2010.40.
The reason may be that the original software inspection process, as described by Fagan [8], or its later variations are very rigorous Mishra, D., & Mishra, A. (2007). Efficient software review process for small and medium enterprises. Engineering and Technology, (4), 132 -142. doi:10.1049/iet-sen
...inspections are low tech and are not the most enjoyable engineering tasks... Radice, R. (2002). High Quality Low Cost Software Inspections. Andover: Paradoxicon Publishing. Poulin, L. (2003). High Quality , Low Cost Software Inspections. Quality, (January), 2003-2003.
...inspections are low tech and are not the most enjoyable engineering tasks... Radice, R. (2002). High Quality Low Cost Software Inspections. Andover: Paradoxicon Publishing. Poulin, L. (2003). High Quality , Low Cost Software Inspections. Quality, (January), 2003-2003.
...it is difficult to maintain the interest of software developers in performing inspections, even when management supports their usage Freimut B, Briand LC, Vollei F, “Determining Inspection Cost- Effectiveness by Combining Project Data and Expert Opinion," IEEE Transactions on Software Engineering 31, 12, 2005, 1074–1092. Komssi, M., Kauppinen, M., Pyhajarvi, M., Talvio, J., & Mannisto, T. (2010). Persuading Software Development Teams to Document Inspections: Success Factors and Challenges in Practice. 2010 18th IEEE International Requirements Engineering Conference, 283-288. Ieee. doi: 10.1109/RE.2010.40.
Inspections can be perceived as a heavyweight process that does not address the real issues of concern to the team Shull, F., Feldmann, R. L., Seaman, C., Regardie, M., & Godfrey, S. (2010). Fully employing software inspections data. Innovations in Systems and Software Engineering. doi: 10.1007/s11334-010-0132-1.
The failed applications of document inspections have typically not been reported. Komssi, M., Kauppinen, M., Pyhajarvi, M., Talvio, J., & Mannisto, T. (2010). Persuading Software Development Teams to Document Inspections: Success Factors and Challenges in Practice. 2010 18th IEEE International Requirements Engineering Conference, 283-288. Ieee. doi: 10.1109/RE.2010.40.
...bad previous experiences and a stagnant inspection process seemed to be the main reasons for the deterioration of the use of inspections or their bad quality... Grady RB, Van Slack T, “Key Lessons in Achieving Widespread Inspection Use," IEEE Software 11, 4, 1994, 46–57. Komssi, M., Kauppinen, M., Pyhajarvi, M., Talvio, J., & Mannisto, T. (2010). Persuading Software Development Teams to Document Inspections: Success Factors and Challenges in Practice. 2010 18th IEEE International Requirements Engineering Conference, 283-288. Ieee. doi: 10.1109/RE.2010.40.
...bad previous experiences and a stagnant inspection process seemed to be the main reasons for the deterioration of the use of inspections or their bad quality... Grady RB, Van Slack T, “Key Lessons in Achieving Widespread Inspection Use," IEEE Software 11, 4, 1994, 46–57. Komssi, M., Kauppinen, M., Pyhajarvi, M., Talvio, J., & Mannisto, T. (2010). Persuading Software Development Teams to Document Inspections: Success Factors and Challenges in Practice. 2010 18th IEEE International Requirements Engineering Conference, 283-288. Ieee. doi: 10.1109/RE.2010.40.
No post-class practitioner refresher Ebert, C., Stewart, R., & Priven, L. (2008). How to Avoid Software Inspection Failure and Achieve Ongoing Benefits. CrossTalk: The Journal for Defense Software Engineering, 23-27.
Technology transition/improvement is not easy Brykczynski, B., Meeson, R., & Wheeler, D. (1994). Software Inspection: Eliminating Software Defects. In Proceedings of the Sixth Annual Software Technology Conference. doi: 10.1.1.50.612.
Upfront cost Brykczynski, B., Meeson, R., & Wheeler, D. (1994). Software Inspection: Eliminating Software Defects. In Proceedings of the Sixth Annual Software Technology Conference. doi: 10.1.1.50.612.
Confusion with other review processes Brykczynski, B., Meeson, R., & Wheeler, D. (1994). Software Inspection: Eliminating Software Defects. In Proceedings of the Sixth Annual Software Technology Conference. doi: 10.1.1.50.612.
The alligator syndrome. An ongoing project that has many problems may not be receptive to introducing a new process. Brykczynski, B., Meeson, R., & Wheeler, D. (1994). Software Inspection: Eliminating Software Defects. In Proceedings of the Sixth Annual Software Technology Conference. doi: 10.1.1.50.612.
Bad prior experience. Brykczynski, B., Meeson, R., & Wheeler, D. (1994). Software Inspection: Eliminating Software Defects. In Proceedings of the Sixth Annual Software Technology Conference. doi: 10.1.1.50.612.
Improved quality not beneficial to the bottom line. For this particular product or set of products, quality is desired but is traded for other goals Brykczynski, B., Meeson, R., & Wheeler, D. (1994). Software Inspection: Eliminating Software Defects. In Proceedings of the Sixth Annual Software Technology Conference. doi: 10.1.1.50.612.
Inspections can be perceived as a heavyweight process that does not address the real issues of concern to the team Shull, F., Feldmann, R. L., Seaman, C., Regardie, M., & Godfrey, S. (2010). Fully employing software inspections data. Innovations in Systems and Software Engineering. doi: 10.1007/s11334-010-0132-1.
...upfront investment appears too large… Denger, C., & Shull, F. (2007). A Practical Approach for Quality-Driven Inspections. IEEE Software, 24(2), 79-86. doi:10.1109/MS.2007.31
Inspections are insufficiently tailored to a given context… Denger, C., & Shull, F. (2007). A Practical Approach for Quality-Driven Inspections. IEEE Software, 24(2), 79-86. doi:10.1109/MS.2007.31
Lack official review standards Xu, B. (2010). Cost Efficient Software Review in an E-Business Software Development Project. 2010 International Conference on E-Business and E-Government, 2680-2683. Ieee. doi:10.1109/ICEE.2010.677
Un-clear goal in practice Xu, B. (2010). Cost Efficient Software Review in an E-Business Software Development Project. 2010 International Conference on E-Business and E-Government, 2680-2683. Ieee. doi:10.1109/ICEE.2010.677
...some engineers consider inspections to be uncreative work that adds costs. Komssi, M., Kauppinen, M., Pyhajarvi, M., Talvio, J., & Mannisto, T. (2010). Persuading Software Development Teams to Document Inspections: Success Factors and Challenges in Practice. 2010 18th IEEE International Requirements Engineering Conference, 283-288. Ieee. doi: 10.1109/RE.2010.40.
...regardless of its importance, some practitioners perceive any review as a disturbance of their valuable time. Freimut B, Briand LC, Vollei F, “Determining Inspection Cost- Effectiveness by Combining Project Data and Expert Opinion," IEEE Transactions on Software Engineering 31, 12, 2005, 1074–1092. Komssi, M., Kauppinen, M., Pyhajarvi, M., Talvio, J., & Mannisto, T. (2010). Persuading Software Development Teams to Document Inspections: Success Factors and Challenges in Practice. 2010 18th IEEE International Requirements Engineering Conference, 283-288. Ieee. doi: 10.1109/RE.2010.40.
Current review processes face these obstacles due to their rigid and time consuming nature. Nazir, S., Fatima, N., & Malik, S. (2008). Effective Hybrid Review Process (EHRP). 2008 International Conference on Computer Science and Software Engineering, 763-771. Ieee. doi:10.1109/CSSE.2008.1417
industry practitioners experience inspections as being ineffective and difficult Ciolkowski, M., Laitenberger, O., & Biffl, S. (2003). Software reviews: The state of the practice. IEEE software, 46–51. IEEE Computer Society. Retrieved June 7, 2011, from https://ieeexplore.ieee.org/abstract/document/1241366/. Komssi, M., Kauppinen, M., Pyhajarvi, M., Talvio, J., & Mannisto, T. (2010). Persuading Software Development Teams to Document Inspections: Success Factors and Challenges in Practice. 2010 18th IEEE International Requirements Engineering Conference, 283-288. Ieee. doi: 10.1109/RE.2010.40.
...inspections have proved to be resource intensive pertaining to tedious tasks by the inspectors… Suma, V., & Nair, T. R. G. (2008). Enhanced Approaches in Defect Detection and Prevention Strategies in Small and Medium Scale Industries. 2008 The Third International Conference on Software Engineering Advances, 389-393. Ieee. doi:10.1109/ICSEA.2008.79
industry practitioners experience inspections as being ineffective and difficult Ciolkowski, M., Laitenberger, O., & Biffl, S. (2003). Software reviews: The state of the practice. IEEE software, 46–51. IEEE Computer Society. Retrieved June 7, 2011, from https://ieeexplore.ieee.org/abstract/document/1241366/. Komssi, M., Kauppinen, M., Pyhajarvi, M., Talvio, J., & Mannisto, T. (2010). Persuading Software Development Teams to Document Inspections: Success Factors and Challenges in Practice. 2010 18th IEEE International Requirements Engineering Conference, 283-288. Ieee. doi: 10.1109/RE.2010.40.
...inspection is considered an effective method but perceived as boring work… Komssi, M., Kauppinen, M., Pyhajarvi, M., Talvio, J., & Mannisto, T. (2010). Persuading Software Development Teams to Document Inspections: Success Factors and Challenges in Practice. 2010 18th IEEE International Requirements Engineering Conference, 283-288. Ieee. doi: 10.1109/RE.2010.40.
...is the belief that inspections can only be done one way Radice, R. (2002). High Quality Low Cost Software Inspections. Andover: Paradoxicon Publishing. Poulin, L. (2003). High Quality , Low Cost Software Inspections. Quality, (January), 2003-2003.
...inspections are not easy to do well, given the psychology that permeates them. Radice, R. (2002). High Quality Low Cost Software Inspections. Andover: Paradoxicon Publishing. Poulin, L. (2003). High Quality , Low Cost Software Inspections. Quality, (January), 2003-2003.
...inspections have proved to be resource intensive pertaining to tedious tasks by the inspectors… Suma, V., & Nair, T. R. G. (2008). Enhanced Approaches in Defect Detection and Prevention Strategies in Small and Medium Scale Industries. 2008 The Third International Conference on Software Engineering Advances, 389-393. Ieee. doi:10.1109/ICSEA.2008.79
Manual inspections are considered too laborious for widespread adoption. Albayrak, Ö., & Davenport, D. (2010). Impact of Maintainability Defects on Code Inspections. Computer Engineering, 9-12.
...the perception that inspections represent an added cost to software development is still widely prevalent. Radice, R. (2002). High Quality Low Cost Software Inspections. Andover: Paradoxicon Publishing. Poulin, L. (2003). High Quality , Low Cost Software Inspections. Quality, (January), 2003-2003.
(When asked about obstacles...) cited time pressure (75 %) Ciolkowski, M., Laitenberger, O., & Biffl, S. (2003). Software reviews: The state of the practice. IEEE software, 46–51. IEEE Computer Society. Retrieved from https://ieeexplore.ieee.org/abstract/document/1241366/
(When asked about obstacles...) cost (56 %) Ciolkowski, M., Laitenberger, O., & Biffl, S. (2003). Software reviews: The state of the practice. IEEE software, 46–51. IEEE Computer Society. Retrieved from https://ieeexplore.ieee.org/abstract/document/1241366/
(When asked about obstacles...) lack of training in introducing reviews (50 %) Ciolkowski, M., Laitenberger, O., & Biffl, S. (2003). Software reviews: The state of the practice. IEEE software, 46–51. IEEE Computer Society. Retrieved from https://ieeexplore.ieee.org/abstract/document/1241366/
...especially when developers see them as disconnected from their normal day-to-day development activities Shull, F., Feldmann, R. L., Seaman, C., Regardie, M., & Godfrey, S. (2010). Fully employing software inspections data. Innovations in Systems and Software Engineering. doi: 10.1007/s11334-010-0132-1.
(Un-clear) schedule in practice Xu, B. (2010). Cost Efficient Software Review in an E-Business Software Development Project. 2010 International Conference on E-Business and E-Government, 2680-2683. Ieee. doi:10.1109/ICEE.2010.677
Mentioned in
Darío Macchi