DocumentCode
1077731
Title
Point/Counterpoint
Author
Gilb, T.
Volume
25
Issue
2
fYear
2008
Firstpage
64
Lastpage
67
Abstract
Traditional software engineering jumps too quickly from high-level quality statements to design ideas. To be clear about design, we must add a step to quantify the quality levels required. Words are ambiguous and lead to misunderstandings. Compare ";I want a user-friendly system"; to ";I want a system that reduces the number of accidental errors made by novice users to fewer than five per 1,000 transactions."; You can engineer and prove the latter. The author has defined 10 principles for quantifying quantification and a notation system for them.
Keywords
software metrics; software quality; software engineering; software metrics; software quality; user-friendly system; Computer industry; Delay; Guidelines; History; Manufacturing industries; Programming profession; Software quality; Software systems; System testing; User interfaces; software engineering; software metrics; software quality;
fLanguage
English
Journal_Title
Software, IEEE
Publisher
ieee
ISSN
0740-7459
Type
jour
DOI
10.1109/MS.2008.43
Filename
4455634
Link To Document