Blunder Dome Sighting  
privacy 
 
 
 

Hangout for experimental confirmation and demonstration of software, computing, and networking. The exercises don't always work out. The professor is a bumbler and the laboratory assistant is a skanky dufus.



Click for Blog Feed
Blog Feed

Recent Items
 
Trustworthy Deployment: What's That?
 
Is Distributed Trustworthiness Soup Yet?
 
MDDi: Integrated Tool Chains for Software Developm...
 
Dynamic Languages Improve Software Quality?
 
Rigorous Software Engineering at the Application-D...
 
Automated Authentication of Programming Standards?...
 
The Important Software Standards: Quality, Perform...
 
Virtual Classrooms Model Social/Collaborative Soft...
 
Microsoft Cracks Open the Word, Excel, and PowerPo...
 
A Litany of Lists: Creatiing Secure Applications

This page is powered by Blogger. Isn't yours?
  

Locations of visitors to this site
visits to Orcmid's Lair pages

The nfoCentrale Blog Conclave
 
Millennia Antica: The Kiln Sitter's Diary
 
nfoWorks: Pursuing Harmony
 
Numbering Peano
 
Orcmid's Lair
 
Orcmid's Live Hideout
 
Prof. von Clueless in the Blunder Dome
 
Spanner Wingnut's Muddleware Lab (experimental)

nfoCentrale Associated Sites
 
DMA: The Document Management Alliance
 
DMware: Document Management Interoperability Exchange
 
Millennia Antica Pottery
 
The Miser Project
 
nfoCentrale: the Anchor Site
 
nfoWare: Information Processing Technology
 
nfoWorks: Tools for Document Interoperability
 
NuovoDoc: Design for Document System Interoperability
 
ODMA Interoperability Exchange
 
Orcmid's Lair
 
TROST: Open-System Trustworthiness

2005-07-16

 

Software Inspection's Lonely Adherents

ACM News Service: Software Under Scrutiny.  I was amazed to see a blurb that features software inspections as something that has not penetrated practice very much. 

Sue Bushell’s 2005-07-07 CIO Australia article confirms that to be the case, with great explanation for how inspections can be tied to demonstrable reduction of software-development costs.  The article clarifies the resistance to inspections and also describes the importance of inspection, the common methodology in almost every software process improvement methodology.  There are some useful principles as well as an assertion by Karl Wiegers that one of the greatest payoff is in inspection of requirements, about as up-front in the software-development stages as you can get.

An intriguing factor with regard to inspections is that the payoff approaches 1:1 (break-even) as the development processes become more successful at not having defects in the first place.  This may lead management to want to abandon them.  It becomes important to have clear understanding of what the phenomenon is.

 
Construction Structure (Hard Hat Area) You are navigating Orcmid's Lair.

template created 2004-06-17-20:01 -0700 (pdt) by orcmid
$$Author: Orcmid $
$$Date: 10-04-30 22:33 $
$$Revision: 21 $