Page 302 - 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

)T MAY BE VALUABLE FOR SITES TO SHARE BEST PRACTICES INFORMATION AS
EXPERIENCE IS OBTAINED 4HIS COULD BE HELPFUL TO BRING ON NEW TEAMS
OR FOR TEAMS TO LEARN ABOUT PROCESSES USED BY OTHER TEAMS (OWEVER
THIS SHOULD BE INITIATED CAREFULLY OVER TIME SINCE THE VARIOUS SITES
MAY INITIALLY BE VIEWED AS COMPETITORS OF EACH OTHER UNTIL THE
COMPETENCE CENTERS BUILD UP THEIR UNIQUE EXPERTISE AND TRUST IS
ESTABLISHED !N EXAMPLE PROCESS DESCRIPTION SUMMARY FOR AN
EXTENDED WORKBENCH MODEL IS GIVEN IN &IGURE
$URING THE THIRD AND FOURTH YEARS VERSIONS n OF THE
'LOBAL 3TUDIO 0ROJECT A SYSTEM OF SYSTEMS APPROACH WAS USED FOR
DISTRIBUTED DEVELOPMENT ;!VRITZER ET AL = 7ITH THIS APPROACH
THE SOFTWARE DEVELOPMENT PROCESS IS STILL DEFINED AND MANAGED
CENTRALLY BUT THE ARCHITECTURE AND REQUIREMENTS ENGINEERING TEAMS
ARE EXTENDED WITH KEY DOMAIN EXPERTS RESIDENT AT THE REMOTE SITES
3PECIALIZED DOMAIN KNOWLEDGE DRIVES THE OVERALL REQUIREMENTS AND
SOFTWARE ARCHITECTURE SPECIFICATION EFFORTS AS EARLY PHASE ACTIVITIES
&REQUENT COMMUNICATION BETWEEN THE CENTRAL AND REMOTE TEAMS AND

! # # #! % # "

! # #$!
# ' $" "" # ' #
" " #
#"

$ ! #"
! % # ! # $ # #
" # "#"
# ! "

# ! #
"#"

& $#
# ! # "#"

1, Ê£ä°ÎÊ Ý>“«iÊiÝÌi˜`i`ÊܜÀŽLi˜V ʓœ`iÊ«ÀœViÃÃ