web analytics
Contact me 
Orange D inside a circle

Research details

Solutions suggested for the low Software Inspection adoption

"Solutions suggested for the low software inspection adoption"

Knowledge - Products - Facts
Quoted textReference (inside the source document)Source document
...new simplified inspection process which is easy to implement, requires fewer resource and almost no documentation. 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.
Participants ranked their system understanding and ability to modify the code as higher than if they had not performed the inspection. 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.
An important factor in obtaining better results is the use of information gained from an inspection to better understand the outcomes of the inspection 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.
Inspections can thus help the identification of “test smells”, which are symptoms that something might be wrong in test code [11] and refactoring can be needed [23] Meszaros, G.: XUnit Test Patterns: Refactoring Test Code. Addison Wesley, New York, NY, USA (to appear in 2007). Also available online at http://xunitpatterns.com/ Lanubile, F., Mallardo, T., & Informatica, D. (2007). Inspecting Automated Test Code : A Preliminary Study. Society, 115-122.
Inspections can thus help the identification of “test smells”, which are symptoms that something might be wrong in test code [11] and refactoring can be needed [23] van Deursen, A., Moonen, L., van den Bergh, A., Kok, G.: Refactoring Test Code. In: Pro- ceedings of the 2nd International Conference on eXtreme Programming and Agile Proc- esses in Software Engineering (XP’01) (2001) Lanubile, F., Mallardo, T., & Informatica, D. (2007). Inspecting Automated Test Code : A Preliminary Study. Society, 115-122.
...the widespread use of inspection is more a leadership issue than a technical one. 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.
management support for innovation Shull F, Seaman C, “Inspecting the History of Inspections: An Example of Evidence-Based Technology Diffusion,”. IEEE Software 25, 1, 2008, 88–90. 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.
a dedicated champion Shull F, Seaman C, “Inspecting the History of Inspections: An Example of Evidence-Based Technology Diffusion,”. IEEE Software 25, 1, 2008, 88–90. 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.
support material for engineers Shull F, Seaman C, “Inspecting the History of Inspections: An Example of Evidence-Based Technology Diffusion,”. IEEE Software 25, 1, 2008, 88–90. 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.
data showing success from a similar context Shull F, Seaman C, “Inspecting the History of Inspections: An Example of Evidence-Based Technology Diffusion,”. IEEE Software 25, 1, 2008, 88–90. 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.
tailoring the practice to the target context without eliminating its important parts Shull F, Seaman C, “Inspecting the History of Inspections: An Example of Evidence-Based Technology Diffusion,”. IEEE Software 25, 1, 2008, 88–90. 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.
TAQtIC Denger, C., & Shull, F. (2007). A Practical Approach for Quality-Driven Inspections. IEEE Software, 24(2), 79-86. doi:10.1109/MS.2007.31
source of support for the inspection regimen came from process champions who believed strongly in the practice’s benefits and in making time on projects to apply it. Shull, F., & Seaman, C. (2008). Inspecting the History of Inspections: An Example of Evidence-Based Technology Diffusion. Software, IEEE.
Companies must integrate the review process into the development process and execute it regularly. This requires a defined, nonoptional review process. Ciolkowski, M., Laitenberger, O., & Biffl, S. (2003). Software reviews: The state of the practice. IEEE software, 46–51. IEEE Computer Society. Retrieved from http://www.computer.org/portal/web/csdl/doi/10.1109/MS.2003.1241366
Sistematic reading techniques Ciolkowski, M., Laitenberger, O., & Biffl, S. (2003). Software reviews: The state of the practice. IEEE software, 46–51. IEEE Computer Society. Retrieved from http://www.computer.org/portal/web/csdl/doi/10.1109/MS.2003.1241366
Optimization (tailoring) Ciolkowski, M., Laitenberger, O., & Biffl, S. (2003). Software reviews: The state of the practice. IEEE software, 46–51. IEEE Computer Society. Retrieved from http://www.computer.org/portal/web/csdl/doi/10.1109/MS.2003.1241366