Page 297 - Software and Systems Requirements Engineering in Practice

I
B
R
S
T
U
ç
2
D
T
E
I
T
E
P
H
A
R

$

ç

I
N
G
%
N
E
N
G
I
E
R
ç
I
R
U
E
Q
E
T
S
N
M
E
#
ç ç # H A P T E R ç ç ç $ I S T R I B U T E D ç 2 E Q U I R E M E N T S ç % N G I N E E R I N G ç ç
AND COMMUNICATION OVERHEAD COSTS ;3ANGWAN ET AL = 4HUS WE
ENCOURAGE SUCH COMPANIES TO PLAN THEIR PROJECTS FOR THE LONG TERM TO
BE ABLE TO REALIZE ANY COST SAVINGS AFTER DOMAIN COMPETENCE IS
DEVELOPED AT THE LOW COST SITES
!S COMPUTING SPEED HAS BEEN ENHANCED AND MEMORY COSTS HAVE
DECREASED THE TREND HAS BEEN TO ADD MORE FEATURES TO A PRODUCT
THROUGH SOFTWARE 4HEREFORE DEVELOPMENT TEAM SIZES ARE GROWING TO BE
ABLE TO DEVELOP LARGE SYSTEMS WITH INCREASING FEATURE CONTENT WITHIN
A REASONABLE TIME TO MARKET ,ARGE TEAMS MAY NOT BE AVAILABLE AT A
SINGLE DEVELOPMENT SITE AND THE NECESSARY DOMAIN EXPERTISE MAY
LIKELY RESIDE AT MANY SITES AROUND THE WORLD 4HUS MOST NEW PROJECTS
TODAY TO DEVELOP LARGE SYSTEMS ARE STAFFED WITH ENGINEERS FROM
AROUND THE WORLD
$EVELOPMENT WORK THAT IS BEING DONE BY DISTRIBUTED TEAMS
CREATES NEW CHALLENGES FOR PROJECT MANAGERS !N EXAMPLE OF A
SOFTWARE AND SYSTEMS ENGINEERING TASK THAT IS BEST DONE BY A SMALL
COLLOCATED TEAM IS ARCHITECTURE DESIGN 3YSTEM ARCHITECTS DO MUCH OF
THEIR CREATIVE WORK WHILE DISCUSSING POSSIBLE DESIGN TRADEOFFS BY
DRAWING PROPOSED DESIGN DIAGRAMS ON A WHITE BOARD AND THEN
DISCUSSING AND MODIFYING THE DESIGN UNTIL IT IS STABLE ENOUGH TO BE
DOCUMENTED WITHIN AN ARCHITECTURE DESIGN DOCUMENT !$$
;#LEMENTS ET AL = &OR EXAMPLE USING AN EXTENDED WORKBENCH MODEL
FOR DISTRIBUTED DEVELOPMENT A SMALL ARCHITECTURE TEAM IS PART OF A
CENTRAL ORGANIZATION WITH MEMBERS ASSIGNED FULL TIME FROM BOTH LOCAL
AND REMOTE SITES ;3ANGWAN ET AL = 4HE TEAM OPERATES AS A
PROJECT WITH A CHIEF ARCHITECT AS ITS LEADER AND A PROJECT MANAGER
RESPONSIBLE FOR THE ENTIRE PRODUCT LIFE CYCLE &URTHERMORE THESE CENTRAL
TEAM ARCHITECTURE DESIGN TASKS ARE STAFFED WITH SOME MEMBERS OF THE
FUTURE REMOTE DEVELOPMENT TEAMS WHO HAVE TEMPORARILY RELOCATED
TO WORK AT THE CENTRAL SITE )DEALLY THE TIME SPENT AT THE CENTRAL SITE
E G SIX MONTHS IS USED TO hTRAINv THE FUTURE REMOTE TEAM MEMBER
ON THE APPLICATION DOMAIN ARCHITECTURE TOOLS AND PROCESSES THAT WILL
BE USED DURING THE DEVELOPMENT 4HESE TEAM MEMBERS WILL HOPEFULLY
BECOME LEADERS OF THE REMOTE DEVELOPMENT TEAMS UPON RETURNING TO
THEIR HOME SITES 4HE DESIGN ARTIFACTS CREATED BY THE CENTRAL ARCHITECTURE
TEAM WILL BE GIVEN TO THE REMOTE TEAMS FOR THEM TO UNDERSTAND THE
ARCHITECTURE OF THE SYSTEM THAT THEY WILL BE DEVELOPING
)DEALLY REQUIREMENTS ENGINEERING LIKE ARCHITECTURE DESIGN IS BEST
DONE BY A SMALL COLLOCATED TEAM (OWEVER REQUIREMENTS ENGINEERS
MUST EITHER HAVE PERSONAL APPLICATION DOMAIN EXPERTISE OR HAVE
ACCESS TO SUCH SUBJECT MATTER EXPERTS &OR LARGE COMPLEX SYSTEMS IT IS
NOT VERY LIKELY THAT ALL THE DOMAIN EXPERTS NECESSARY TO DEFINE A
PRODUCT OR PRODUCT LINE WILL BE LIVING IN THE SAME CITY 4HUS
REQUIREMENTS ENGINEERING PROCESSES FOR DISTRIBUTED PROJECTS MUST
RECREATE THE HIGHLY INTERACTIVE AND EFFICIENT COMMUNICATIONS OF SAY
THE ARCHITECTURE DESIGN TEAM GATHERED AROUND THE WHITE BOARD