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µÕˆÀi“i˜ÌÃÊ >˜>}i“i˜ÌÊ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
   246   247   248   249   250   251   252   253   254   255   256