Page 300 - Software and Systems Requirements Engineering in Practice
P. 300

ç          ç  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


                         7E WILL ILLUSTRATE TWO EXAMPLE ORGANIZATIONS THAT WERE USED ON
                      THE 'LOBAL 3TUDIO 0ROJECT  '30   $URING THE FIRST TWO YEARS OF THE
                      '30  A PRODUCT STRUCTURE APPROACH WAS USED TO ORGANIZE THE PROJECT
                      AND AN EXTENDED WORKBENCH MODEL DEVELOPMENT PROCESS WAS USED
                      ;3ANGWAN ET AL      =  4HIS RESULTED IN A HUB AND SPOKE ORGANIZATIONAL
                      STRUCTURE  &IGURE       WHERE THE REMOTE COMPONENT DEVELOPMENT
                      TEAMS COMMUNICATED MOSTLY WITH THE CENTRAL TEAM ROLES  E G   CHIEF
                      REQUIREMENTS  ENGINEER   CHIEF  ARCHITECT   PROJECT  MANAGER   AT  THE
                      HEADQUARTERS OR CENTRAL SITE
                         2EQUIREMENTS INFORMATION IS TRANSFERRED FROM THE CENTRAL TEAM TO
                      EACH  REMOTE  COMPONENT  DEVELOPMENT  TEAM  IN  THE  FORM  OF  MODELS
                      AND  SPECIFICATIONS   4HE  DOCUMENTATION  PACKAGE  IS  USED  TO  HELP
                      COMMUNICATE  TO  THE  REMOTE  TEAMS  THE  WORK  THAT  WILL  BE  DONE  IN
                      ACCORDANCE  WITH  THE  DEVELOPMENT  PLAN   4HE  WORK  TO  BE  DONE  IS
                      SCOPED  TO  BE  IMPLEMENTED  BY  A  RELATIVELY  SMALL  COMPONENT
                      DEVELOPMENT  TEAM   MAXIMUM  OF  TEN  ENGINEERS    4HE  ROLES  OF  THE
                      DEVELOPMENT TEAM MEMBERS ARE MULTIFUNCTIONAL  INCLUDING DOMAIN
                      DESIGN  DEVELOPMENT  AND TESTING EXPERTISE  4HUS  WITH THE EXTENDED
                      WORKBENCH MODEL  REQUIREMENTS DEFINITION AND ANALYSIS ARE DONE BY
                      THE  CENTRAL  TEAM  AT  A  SINGLE  SITE   HOWEVER   DOMAIN  EXPERTISE  IS
                      DEVELOPED OVER TIME AT THE REMOTE SITES  /NE WAY TO BUILD UP THIS
                      REMOTE DOMAIN EXPERTISE IS TO HAVE THE REQUIREMENTS ENGINEERS AT THE
                      REMOTE SITES WORK AS TEMPORARY MEMBERS OF THE CENTRAL SITE S 2% TEAM
                      AND THEN SERVE AS THE DOMAIN EXPERTS IN THE REMOTE TEAM
                         4HIS HUB AND SPOKE ORGANIZATION IS TYPICALLY USED WHEN A CENTRAL
                      ORGANIZATION IS UTILIZING REMOTE DEVELOPMENT SITES FOR THE FIRST TIME  )T
                      OFTEN WILL TAKE A YEAR OR MORE TO BE ABLE TO DEVELOP THE DOMAIN EXPERTISE
                      2%  AND DEVELOPMENT SKILLS IN THE STAFF IN THE REMOTE TEAMS  4HUS  THE
                      CENTRAL TEAM TRANSFERS SOME OF THEIR KNOW HOW TO THE REMOTE TEAMS OVER
                      TIME SUCH THAT THEY ARE ABLE TO TAKE ON A BIGGER ROLE IN THE DEVELOPMENT
                      PROJECT   7E  RECOMMEND  TO  ORGANIZATIONS  STARTING  DISTRIBUTED
                      DEVELOPMENT FOR THE FIRST TIME TO TAKE A LONG TERM VIEW  SINCE THERE WILL
                      BE A SUBSTANTIAL LEARNING CURVE TIME NECESSARY FOR THE REMOTE TEAMS TO
                      BECOME PRODUCTIVE CONTRIBUTORS TO THE DEVELOPMENT PROJECT













                         1, Ê£ä°£Ê  Ý>“«iÊiÝÌi˜`i`ÊܜÀŽLi˜V…Ê“œ`iÊ}œL>Ê`iÛiœ«“i˜ÌÊ
                      œÀ}>˜ˆâ>̈œ˜
   295   296   297   298   299   300   301   302   303   304   305