Page 243 - Software and Systems Requirements Engineering in Practice

E
T
P
R

ç
H

A
2 E Q U I R E M E N T S ç - A N A G E M E N 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 ç
3CALABILITY
0ROCESSES PUT IN PLACE AT THE BEGINNING OF A PROJECT MAY NOT TAKE INTO
CONSIDERATION THE NUMBER OF REQUIREMENTS THAT MAY NEED TO BE
MANAGED AS REQUIREMENTS DEFINITION NEARS COMPLETION &OR EXAMPLE
A PROJECT WITH FEATURES TO START MAY NOT APPEAR TO BE A LARGE PROJECT
"UT IF WE CONSIDER THE NOT UNREASONABLE EXPLOSION OF EACH FEATURE TO
OR MORE hHIGH LEVELh REQUIREMENTS WE NOW WILL HAVE OVER
HIGH LEVEL REQUIREMENTS !DDING AN ADDITIONAL EXPLOSION LAYER OF
DETAIL NEEDED TO IMPLEMENT THE PRODUCT AND CREATE TEST CASES ASSUME
AN EXPLOSION OF WE LL WIND UP WITH A TOTAL OF REQUIREMENTS
AND AT LEAST THE SAME NUMBER OF TRACES 3UCH A NUMBER OF REQUIREMENTS
TO MANAGE AND TRACE IS NOT UNREASONABLE FOR TODAY S LARGE PROJECTS )T
IS THEREFORE IMPERATIVE THAT TRACE MECHANISMS BE TO THE EXTENT
POSSIBLE INTRINSIC TO ROUTINE PROCESSES WITHOUT A BURDENSOME MANUAL
EFFORT 3OME TECHNIQUES FOR MITIGATING ISSUES OF SCALE ARE DESCRIBED IN
THE SECTION h"EST 0RACTICESv LATER IN THIS CHAPTER

#REATION OF A 2EQUIREMENTS -ANAGEMENT 0ROCESS
)T IS EASY TO UNDERESTIMATE THE EFFORT NECESSARY TO PROPERLY MANAGE
REQUIREMENTS ON A PROJECT 5NFORTUNATELY PROCESS PROBLEMS TEND NOT
TO SHOW UP UNTIL IT IS LATE IN THE PROJECT AND IT CAN BE VERY DIFFICULT AND
LABOR INTENSIVE TO MAKE CHANGES TO IN PLACE PROCESSES #ONSEQUENTLY
IT IS IMPORTANT TO PLAN EARLY FOR HANDLING LARGE QUANTITIES OF DATA
REQUESTS FOR CHANGE AND HIGH PRODUCTIVITY THROUGH AUTOMATION
&OR EXAMPLE REQUIREMENTS ESPECIALLY NONFUNCTIONAL REQUIREMENTS
MAY IMPACT OTHER REQUIREMENTS AND SO SEARCH AND MODIFICATION
MECHANISMS ARE BEST AUTOMATED )N THIS SECTION WE WILL WALK THROUGH
THE PROCESS OF CREATING A REQUIREMENTS MANAGEMENT ENVIRONMENT )N
FOLLOWING SECTIONS WE WILL PROVIDE ADDITIONAL DETAILS ABOUT SPECIFIC
ASPECTS OF REQUIREMENTS MANAGEMENT
4HE DEFINITION OF PROCESSES OR PROCESS IMPROVEMENT BEGINS
WITH THE DEFINITION OF WORK PRODUCTS THAT ARE NEEDED FOR THE
ORGANIZATION 4HEY CAN BE DEFINED IN A TAXONOMY OR AN ARTIFACT
MODEL SEE #HAPTER BUT THE IMPORTANT THING IS NOT TO LEAVE
OUT ANYTHING THAT MAY BE NEEDED
4HE NEXT STEP IS TO SCOPE THE ARTIFACTS BASED ON BUSINESS NEED
E G WHAT IS IN AND WHAT IS OUT
!UTOMATION AND TRACING STRATEGIES ARE DEFINED BY EVALUATING
THE RELATIONSHIPS BETWEEN THE ARTIFACTS AND DETERMINING IF
TRACES ARE NECESSARY AND IF THEY ARE WHETHER THEY WILL BE
CREATED AND MAINTAINED MANUALLY OR AUTOMATICALLY
&OR EACH ARTIFACT THAT NEEDS TO BE CREATED E G SPECIFICATIONS
SUCH AS A CUSTOMER REQUIREMENTS DOCUMENT TEMPLATES NEED
TO BE CREATED AND REVIEWED