Email:
Password: [?] 
  Register with the DACS
Site Search: Advanced Search
Search: Bibliographic Database(SEBD)     Lifecycle Database(SLED)    DoD Acronyms 
DACS Home DACS Services Publications Training About Us DACS Store Suggest A Link
Rate this page's content:
  poor
excellent


This is a listing of sources for best practices for software inspections.
  • Formal Inspections - The practice of conducting formal Inspections on requirements, architecture, designs at all levels (particularly detailed design), on code prior to unit test, and on test plans, to assess the quality of all baselined artifacts prior to release for project use.

  • Improving Quality Through Software Inspections - This is an article by Karl E. Weigers from the CAI-sponsored IT Metrics and Productivity Institute dated 29 September 2008. This is a description from the CAI web site:

    "Software inspections and their cousins, reviews and walkthroughs, are proven techniques for reducing the number of defects in a program before it goes out the door. If you are in an organization of two or more people, some kind of inspection activity should be a part of your standard software development process."

  • Software Assessments, Benchmarks, and Best Practices - Written by Capers Jones, Addison-Wesley Pub Co; 1st edition (April 28, 2000), this book explores the methodologies used by businesses for software development, while software benchmarking collects quantitative data on such topics as schedules and costs. This guide combines assessments and benchmark studies to improve software analysis, and identifies best and worst practices of software development.

  • Software Inspection: An Industry Best Practice - This book is a collection of papers published by IEEE in 1999 and edited by Bill Brykczyinski.

    A reviewer comments: "This is a handy book with a summary and compendium of papers on inspections. The books traces the industry experience with inspections as mirrored in the technical papers published on the subject. For those interested in an important best practice, this is an invaluable resource that is complementary to the standard books on the subject. I am particularly interested in the inspection of natural language requirements documents and found the papers in this area valuable."

  • SPMN Sixteen Critical Software Practices - The Software Program Managers Network (SPMN) was established in 1992 by the Assistant Secretary of the Navy to identify proven industry and government software best practices and convey these practices to managers of large-scale DoD system acquisition programs. The SPMN 16 Critical Software PracticesTM specifically address underlying cost and schedule drivers that have caused many software intensive systems to be delivered over budget, behind schedule and with significant performance shortfalls.

Suggest Supporting Web Sites
Related pages:
sidebar
sidebar
sidebar

s

s

s

s


SISOS cover
DACS Latest Technical Report


TEMS Logo
Visit the DTIC TEMS Initiative

   DACS Gold Practice Initiative ROI Dashboard
 
Acquisition Process Improvement
Architecture-First Approach
Assess Reuse Risks and Costs
Binary Quality Gates at the Inch-Pebble Level
Capture artifacts in rigorous, model-based notation
Commercial Specifications and Standards/Open Systems
Defect Tracking Against Quality Targets
Develop and Maintain a Life-cycle Business Case
Ensure Interoperability
Formal Inspections
Formal Risk Management
Goal-Question-Metric Approach
Integrated Product and Process Development
Manage Requirements
Metrics-based Scheduling
Model Based Testing
Plan for Technology Insertion
Requirements Trade-Off/Negotiation
Statistical Process Control
Track Earned Value
  Access benefit data from software technical and management improvements including SEI CMMI, PSP/TSP, Cleanroom, Inspections, and Agile Development.

View the ROI Dashboard
Copyright © 2010, ITT Corporation    Privacy Policy
webmaster@thedacs.com
775 Daedalian Drive Rome, NY 13441
(800) 214-7921 Fax: 315-838-7130
This site is best viewed in Firefox 1.0+ or IE 6.0+
XHTML