Page 244 - Software and Systems Requirements Engineering in Practice

ç ç 3 O F T W A R E ç ç 3 Y S T E M S ç 2 E Q U I R E M E N T S ç % N G I N E E R I N G ç ) N ç 0 R A C T I C E

)F ACTIVITIES TO CREATE THE ARTIFACTS ARE NOT IN PLACE THEY NEED TO
BE DEFINED ALONG WITH ROLES STANDARDS AND QUALITY ASSURANCE
PROCEDURES #REATING IDEALIZED SAMPLE DOCUMENTS OR REPORTS
IS A GREAT WAY TO ENSURE GOOD QUALITY
"E SURE TO DEFINE INTERFACE PROCESSES FOR INTERACTING WITH
PRODUCT MANAGEMENT MANUFACTURING AND TESTING
$ON T FORGET MAINTENANCE AND VERSION CONTROL !FTER A PROJECT
IS COMPLETED IT MAY BE NECESSARY TO MANAGE CHANGE FOR FUTURE
PRODUCT RELEASES OR REPAIRS

! REQUIREMENTS ENGINEERING MANAGEMENT PROCESS IS OFTEN
DESCRIBED IN A DOCUMENT CALLED A REQUIREMENTS ENGINEERING
MANAGEMENT PLAN 2%-0 ! TABLE OF CONTENTS FOR AN EXAMPLE 2%-0
IS GIVEN IN &IGURE

' $# % "$ !(
#! $ #
/,*)-
)*
# - !), +/$, ' (.- ("$( ,$("
! , ( -
! " ! " " # "
! $ ! #" ! % !% &
+/$, ' (.- ("$( ,$(" 2, '$
+/$, ' (.- ("$( ,$(" ,) --
+/$, ' (.- ("$( ,$(" ))&-
! $ ! #" % #
. % #)& , (.$!$ .$)(
+/$, ' (.- &$ $. .$)(
+/$, ' (.- ( &2-$-
+/$, ' (.- * $!$ .$)(
+/$, ' (.- &$ .$)(
! $ ! #" #
+/$, ' (.- - &$(
)(!$"/, .$)( ( " ' (.
# (" )(.,)& ) ,
)& - ( -*)(-$ $&$.$ -
# (" )(.,)& )&$ 2
# (" )(.,)& ,) -- - ,$*.$)(
$-$)(-
)''/($ .$(" . ./-
( ").$ .$(" )''$.' (.-
# (" )(.,)& ))&-
-/,$(" # (" .$0$.2
'* . ( &2-$-
"$! # (" "
+/$, ' (.- ( " ' (.
/ &$.2
,)", --
+/$, ' (.- 0 &)*' (.
/ &$.2
,)", --
"$ ! ! # #
0 ,0$ 1
-*)(-$ $&$.$ -
,,$ ,-
#!
, $($(" 0 $& $&$.2
, $($(" .#) -
, $($(" ,$. ,$
'*&)2 , (-$.$)(
' ! ! "" # '# # "
' " " # "# ! (" " # #
' ! $ ! #" ! % & "#
' "!" # #
' ! "" # (" "
' " # "# ! $" " $ #"
1, ÊÇ°ÓÊ Ý>“«iÊ,iµÕˆÀi“i˜ÌÃÊ ˜}ˆ˜iiÀˆ˜}Ê >˜>}i“i˜ÌÊ*>˜Ê­, *®Ê
/>LiʜvÊ œ˜Ìi˜ÌÃ