|
|
 |
Software Quality
|
|
|
|
|
|
Posted by: Jim Johnson
Posted on: Sunday, 4th March 2001, 12:00 AM.
The very first thing that you need to do is define a defect for software quality. Generally speaking I think this would relate to how the software functions according to the situation it is modeling. For example, if software is intended to help you in balancing your checkbook on a regular basis there are a number of defects that are possible: incorrect calculation, incorrect categorization of expenditures, etc. What you want to define first is your "Big Y" if that is "Software Quality" then you need to define all of the inputs (x's) that drive Software quality (Analysis, Design, Coding, Testing and Documentation) then use each one of these as a "Y" and define the x's that drive that Y. For example, in terms of Analysis you might say that thoroughness, Analysts knowledge level, user involvement, etc are x's. You then start with one of these as a Y and define the x's for that Y. This method of radical incrementalism is what will drive you ultimately to your critical few items to impact Software Quality.
The Y=f(x) formula is crucial to 6-Sigma success in defining opportunities for improvement as well as projects (once you reach a certain level of degradation).
I hope that this note helps.
Jim Johnson
Message Thread: 
Return To Discussion ForumPost A New MessageRead the Forum Guide to Good Etiquette
"The Bottom Line" Links
|
|
|
