Page 233 - Software and Systems Requirements Engineering in Practice

E
ç
R
A
P
H
2 E Q U I R E M E N T S ç - A N A G E M E N T ç
#
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 ç
%STABLISHING 0OLICIES FOR 2EQUIREMENTS 0ROCESSES AND
3UPPORTING 4HEM WITH 7ORKFLOW 4OOLS 'UIDELINES 4EMPLATES
AND %XAMPLES
! COMMON MISTAKE ON LARGE PROJECTS IS TO START EXECUTING THE PROJECT
WITHOUT HAVING WELL DEFINED PROCESSES GUIDELINES TEMPLATES EXAMPLES
OR INTEGRATED TOOLSETS !S WAS MENTIONED IN EARLIER CHAPTERS NOT
PLANNING OMISSION CAN CAUSE PROBLEMS AS A PROJECT MATURES &OR
EXAMPLE NOT HAVING HIGH QUALITY EXAMPLES OF REQUIREMENTS AND
SPECIFICATIONS MAY RESULT IN LOWER QUALITY REQUIREMENTS AND A LARGE
INITIAL NUMBER OF DEFECTS &URTHERMORE NOT PLANNING FOR TOOL INTEGRATION
CAN RESULT IN A RAPID INCREASE IN WORKLOAD AS THE NUMBER OF REQUIREMENTS
EXPLODES DURING ANALYSIS 4OOL INTEGRATION WILL NOT BE DISCUSSED IN MORE
DETAIL HERE AS A WEALTH OF INFORMATION IS AVAILABLE IN TEXTS AND ON THE
WEB AND THE ACTUAL IMPLEMENTATION OF TOOL CHAINS CAN BE ORGANIZATION
OR PROJECT SPECIFIC 7E SUGGEST FOR EXAMPLE THAT THE READER EXPLORE THE
MANY WHITE PAPERS PUBLISHED BY THE 2$-3 VENDORS
0RIORITIZING 2EQUIREMENTS
0RIORITIZATION AND RANKING OF REQUIREMENTS HAS BEEN DISCUSSED BRIEFLY IN
PRIOR CHAPTERS )T IS A NONTRIVIAL ACTIVITY THAT REQUIRES DECISIONS SUCH AS
WHAT ALGORITHMS WILL BE USED HOW PRIORITIZATION WILL BE CALCULATED AND
STORED THE IMPACT OF DEPENDENCIES ON PRIORITY AND PROPAGATION ISSUES
UP AND DOWN &URTHERMORE ANY WORK IN THIS AREA WILL MOST LIKELY BE
DOMAIN AND ORGANIZATION SPECIFIC )F THE READER IS INTERESTED IN THIS TOPIC
THERE ARE MANY FINE TEXTS AVAILABLE FOR EXAMPLE ;7IEGERS =

%STABLISHING AND 5PDATING THE 2EQUIREMENTS "ASELINE
!S WAS DISCUSSED IN THE PRECEDING SECTION ONCE THE REQUIREMENTS
STABILIZE A BASELINE IS ESTABLISHED SO THAT CHANGES CAN BE TRACKED
-OST 2$-3 TOOLS HAVE FACILITIES FOR ESTABLISHING BASELINES HOWEVER
THAT MAY NOT BE THE END OF THE STORY %XTERNAL DOCUMENTS BLUEPRINTS
GOVERNMENT STANDARDS AND SO ON MAY ALSO NEED TO BE BASELINED &OR
EXAMPLE A CHANGE IN A GOVERNMENT STANDARD MAY RESULT IN A
REEVALUATION OF HAZARDS FOLLOWED BY MODIFIED OR ADDITIONAL MITIGATION
REQUIREMENTS SEE #HAPTER
$OCUMENTING $ECISIONS
4HE DOCUMENTATION OF DECISIONS IS REQUIRED FOR BOTH PROJECT AND
REQUIREMENTS MANAGEMENT !S THERE IS OVERLAP IT MAY BE NECESSARY
TO HAVE A COORDINATED STRATEGY &OR AN EXAMPLE OF WHAT CAN HAPPEN
WHEN DECISIONS ARE NOT DOCUMENTED SEE THE SIDEBAR

0LANNING 2ELEASES AND !LLOCATING 2EQUIREMENTS TO 2ELEASES
0LANNING RELEASES CAN BE A PRODUCT OR PROJECT MANAGEMENT ACTIVITY
DEPENDING ON THE TYPE OF PROJECT $URING THE PLANNING REQUIREMENTS
ARE ALLOCATED TO RELEASES SO THAT PRODUCT VERSIONS WILL BE RELEASED IN A
COST EFFECTIVE MANNER DEPENDING ON THE BUSINESS GOALS E G POSITIVE