Page 245 - Software and Systems Requirements Engineering in Practice

ç
R
P
E
H
A
E
ç
-
E
S
Q
T
2
E
E
M
I
R
T
ç ç # # H A P T E R ç ç ç 2 E Q U I R E M E N T S ç - A N A G E M E N T ç ç
E
N
T
A
M
N
G
U
N
A
-EASURING 3AVINGS WITH 2% 0ROCESSES
7HEN IMPROVING REQUIREMENTS PROCESSES IN AN ORGANIZATION IT MAY
NOT BE POSSIBLE TO QUANTIFY SAVINGS BY LOOKING JUST AT THE 2% WORK
PRODUCTS AND PRODUCTIVITY IMPROVEMENTS 4HE REAL SAVINGS CAN ONLY
BE DETERMINED BY LOOKING AT A PROJECT HOLISTICALLY (OWEVER THAT MAY
REQUIRE CHANGING MINDSETS &OR EXAMPLE ONE ORGANIZATION THAT WE
LOOKED AT DURING A PROCESS IMPROVEMENT EFFORT USED THE CATEGORY
hSOFTWARE DEFECTv FOR NEARLY ALL REPORTED SOFTWARE BUGS !FTER A ROOT
CAUSE ANALYSIS IT WAS FOUND THAT THE MAJORITY OF THE SOFTWARE BUGS
WERE ACTUALLY PROBLEMS WITH REQUIREMENTS !FTER SOME TRAINING OF THE
2% STAFF TO DO A BETTER JOB OF WRITING REQUIREMENTS THE NUMBER OF
DEFECTS FELL MARKEDLY 3OME SAMPLE DEFECT INDICATORS ARE SHOWN IN
4ABLE
>ÕÃiʜvÊ iviVÌ -Õ}}iÃÌi`Ê,i“i`Þ
,iµÕˆÀi“i˜ÌÊÜ>ÃÊ /À>ˆ˜Ê>˜>ÞÃÌÃÊ̜ÊÜÀˆÌiÊ՘>“Lˆ}՜ÕÃÊ
>“Lˆ}՜Õà ÀiµÕˆÀi“i˜Ìð
,iµÕˆÀi“i˜ÌÊÜ>ÃÊ ,iۈiÜÊÌ iÊ>“œÕ˜ÌʜvÊ̈“iÊëi˜Ìʜ˜Ê>˜>ÞÈðÊ
ˆ˜Vœ“«iÌi iÌiÀ“ˆ˜iʈvÊÌ iÊÀiµÕˆÀi“i˜ÌÊÀiۈiÜÃÊ>ÀiÊ`œ˜iÊ
ÜˆÌ ÊÌ iÊÀˆ} ÌÊ«>À̈Vˆ«>˜Ìð
œ˜vˆV̈˜}ÊÀiµÕˆÀi“i˜Ìà œ`ˆvÞÊÌ iÊ, Ê«ÀœViÃÃÊ̜Ê>`iµÕ>ÌiÞÊ>``ÀiÃÃÊ
ÀiµÕˆÀi“i˜ÌÃÊVœ˜vˆVÌÊÀi܏Ṏœ˜°
,iµÕˆÀi“i˜ÌÊÜ>ÃÊ / iÊ«ÀœViÃÃʓ>Þʘii`Ê̜ÊLiʓœ`ˆvˆi`Ê̜Ê
ˆ˜VœÀÀiVÌ ˆ˜VÕ`iÊ>``ˆÌˆœ˜>Êˆ˜ÌiÀ>V̈œ˜Ê>˜`ÊÀiۈiÜÃÊÜˆÌ Ê
ÃÌ>Ži œ`iÀð
*Àœ`ÕVÌÊvi>ÌÕÀiÊ`ˆ`ʘœÌÊ œ““Õ˜ˆV>̈œ˜ÊÜˆÌ ÊVˆi˜Ìʓ>Þʘii`Ê̜ÊLiÊ
“iiÌÊVˆi˜ÌÊiÝ«iVÌ>̈œ˜Ã “œÀiÊvÀiµÕi˜ÌʜÀÊVœ“«Ài i˜ÃˆÛi°
*iÀvœÀ“>˜ViʜÀʵÕ>ˆÌÞÊ œ˜v՘V̈œ˜>ÊÀiµÕˆÀi“i˜ÌÃʓ>Þʘii`Ê̜ÊLiÊ
Ü>ÃÊLiœÜÊiÝ«iVÌ>̈œ˜Ã >``ÀiÃÃi`Êi>ÀÞÊi˜œÕ} ʈ˜ÊÌ iÊiˆVˆÌ>̈œ˜Ê«ÀœViÃÃÊ
>˜`ɜÀʓ>ÞLiÊ>ÀV ˆÌiVÌÃÊ>˜`Ê`iÈ}˜iÀÃʜÕ} ÌÊ
̜ÊLiʈ˜ÛœÛi`Êi>ÀÞÊi˜œÕ} Ê̜Ê`œÊ>˜ÊivviV̈ÛiÊ
>˜>ÞÈÃʜvÊÌ iʘœ˜v՘V̈œ˜>ÊÀiµÕˆÀi“i˜Ìð
>ˆÕÀiÊ̜ʓiiÌÊ /À>Vˆ˜}ÊÌiV ˜ˆµÕiÃʓ>Þʘii`Ê̜ÊLiʈ“«ÀœÛi`Ê
Ài}Տ>̜ÀÞÊÀiµÕˆÀi“i˜Ìà ÃÕV ÊÌ >ÌÊ`iÈ}˜iÀÃÊV>˜Ê՘`iÀÃÌ>˜`Ê>˜ÞÊ
Ài}Տ>̜ÀÞÊVœ˜ÃÌÀ>ˆ˜ÌÃÊvÀœ“ÊÜ ˆV ÊÌ iÊ
ÀiµÕˆÀi“i˜ÌÃÊ`iÀˆÛi°
/ ÊÇ°ÈÊ 1Ș}Ê iviVÌÃÊvœÀÊ*ÀœViÃÃÊ “«ÀœÛi“i˜Ì