Page 251 - Software and Systems Requirements Engineering in Practice
P. 251
A
H
P
2 E Q U I R E M E N T S ç - A N A G E M E N T ç
#
E
T
R
ç
ç ç # 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 ç
/«V *À`ÕVÌ *À`ÕVÌÊ i
-Ì>i
`iÀÊ -«i >ÞÊLiÊV«V>Ìi`ÊLÞÊÌ
iÊ`ÀÛ}Ê
V>Ìi}Àià vÀViÊLi
`ÊÌ
iÊ«À`ÕVÌÊiÆÊi°}°]Ê
Ài}>ÊÃÌ>i
`iÀð
/À>V} -}iÊÌ
Ài>`Ê >ÞÊLiÊV«V>Ìi`ÊLÞÊ
vÀÊvi>ÌÕÀiÊÌÊ Ài}>â>ÌÊÀÊÌ
iÀÊv>VÌÀÃ°Ê ÀÊ
ÌiÃÌ} iÝ>«i]ÊÌÀ>V}Ê«>Ì
ÃÊ>ÞÊ`ÛiÀ}iÊ
vÀÊ«À`ÕVÌÃÊVÀi>Ìi`ÊvÀÊ`vviÀiÌÊ
Ài}Ã]ÊÜ
iÀiÊv>ÊÌiÃÌ}ÊÃÊ`iÊ
LÞÊ>ÊÀi}>ÊÀ}>â>̰
/ ÊÇ°Ê «>ÀÃÊvÊ,iµÕÀiiÌÃÊ >>}iiÌÊvÀÊ*À`ÕVÌÃÊÛðÊ*À`ÕVÌÊ iÃ
4IPS FOR 2EQUIREMENTS -ANAGEMENT
4ABLE SUMMARIZES SOME IMPORTANT TIPS FOR AN EFFECTIVE
REQUIREMENTS MANAGEMENT PROCESS
"EST 0RACTICES
! REAL PROBLEM WITH MANY REQUIREMENTS ENGINEERING PROCESSES IS THAT
THEY DO NOT SCALE WELL ! PROCESS THAT WORKS WITH REQUIREMENTS
MAY EXPLODE WITH 4HE FOLLOWING PRACTICES CAN HELP WITH
MEDIUM TO LARGE SCALE PROJECTS
v 2EQUIREMENTS HIERARCHIES SHOULD BE WELL DEFINED E G PARENT
CHILD RELATIONSHIPS DEPENDING ON THE LEVEL OF ABSTRACTION OF
THE FEATURE OR REQUIREMENT &AILURE TO CREATE A HIERARCHY SUCH
AS A TREE STRUCTURE IN TURN LEADS TO A TWO DIMENSIONAL TRACE
TABLE OF SIZE . ¾ . WHERE . IS THE NUMBER OF REQUIREMENTS
ASSOCIATED WITH TRACES AND AFTER SEVERAL THOUSAND REQUIREMENTS
THE TRACES ARE NO LONGER MAINTAINABLE OR USABLE -ITIGATION
TECHNIQUES INCLUDE THE CREATION OF REQUIREMENT HIERARCHIES IN
THE DATABASE SCHEMA THAT PERMIT DATABASE TRACE QUERIES TO
RETURN A MORE MEANINGFUL SUBSET OF TRACES
v #REATE A GLOSSARY OF TERMS AND USE THE TERMS CONSISTENTLY
THROUGHOUT THE PROJECT &AILURE TO DEFINE A STANDARD GLOSSARY
OF TERMS MAY RESULT IN DIFFERENT TERMS BEING USED TO MEAN THE
SAME THING CAUSING AMBIGUITY AND MAKING IT DIFFICULT TO MINE
FOR TRACE RELATIONSHIPS AT A LATER DATE
v #REATE A PROJECT METAMODEL OR ARTIFACT MODEL AT PROJECT
INITIATION #REATION OF SUCH A MODEL WILL REVEAL ALL THE POSSIBLE
TYPES OF TRACES THAT MAY BE POSSIBLE AND ENABLE THE CREATION OF
AN AUTOMATED IF NECESSARY MANUAL TRACE STRATEGY