Page 299 - Software and Systems Requirements Engineering in Practice

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

Q
N
E
I
N
G
N
G
I
E
R
%
E
M
R
U
I
S
ç
T
E
N
A
ç ç # # 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 ç ç
H
õ /RGANIZATIONSõFORõ$ISTRIBUTEDõ0ROJECTS
'OOD COMMUNICATIONS ARE IMPORTANT FOR GOOD REQUIREMENTS
ENGINEERING )N A LARGE SURVEY AMONG PROFESSIONALS ON THEIR
EXPERIENCES WITH DISTRIBUTED DEVELOPMENT COMMUNICATION
PARTICULARLY FACE TO FACE MEETINGS WAS FREQUENTLY MENTIONED AS A
SOLUTION TO DIVERSE 2% PROBLEMS ;)LLES 3EIFERT ET AL = 7E HAVE
OBSERVED THAT PROJECT MANAGERS FOR GLOBALLY DISTRIBUTED PROJECTS WILL
OFTEN CAREFULLY MONITOR THEIR TRAVEL COSTS ;3ANGWAN ET AL = 7HEN
THERE S AN UNEXPECTED INCREASE IN TRAVEL BETWEEN TWO DEVELOPMENT
SITES IT S OFTEN A GOOD INDICATOR THAT THERE IS SOME TYPE OF PROJECT
PROBLEM INVOLVING THE TWO SITES
0ROJECT MANAGERS CAN USE MANY ORGANIZATIONAL STRUCTURES FOR DOING
REQUIREMENTS ENGINEERING ACROSS MULTIPLE DEVELOPMENT SITES 3OME OF
THE PROJECT ORGANIZATIONAL APPROACHES THAT COULD BE CONSIDERED INCLUDE
ORGANIZING BY PRODUCT STRUCTURE PROCESS STEPS RELEASE COMPETENCE
CENTER AND OPEN SOURCE )N A PRODUCT STRUCTURE ORGANIZATIONAL APPROACH
THE REQUIREMENTS ENGINEERS AND ARCHITECTS ALLOCATE FEATURES TO
COMPONENTS AND THE COMPONENTS ARE ALLOCATED AS WORK PACKAGES TO
THE DIFFERENT SITES )N A PROCESS STEPS STRUCTURE WORK IS ALLOCATED ACROSS
THE SITES IN ACCORDANCE WITH THE PHASES OF THE DEVELOPMENT PROCESS
E G REQUIREMENTS ENGINEERING MAY BE DONE AT ONE SITE DEVELOPMENT
AT ANOTHER SITE S AND TESTING AT YET ANOTHER SITE )N A RELEASE BASED
ORGANIZATION APPROACH THE FIRST PRODUCT RELEASE IS DEVELOPED AT ONE
SITE THE SECOND AT ANOTHER SITE ETC /FTEN THE RELEASES WILL BE
OVERLAPPED TO MEET TIME TO MARKET GOALS E G ONE SITE IS TESTING THE
NEXT RELEASE ANOTHER SITE IS DEVELOPING A LATER RELEASE AND YET ANOTHER
SITE IS DEFINING THE REQUIREMENTS FOR AN EVEN LATER RELEASE )N A PLATFORM
STRUCTURE SEE #HAPTER ONE SITE MAY BE DEVELOPING REUSABLE CORE
ASSETS OF THE PRODUCT LINE AND OTHER SITES MAY BE DEVELOPING
APPLICATION LEVEL SOFTWARE THAT USES THE PLATFORM )N A COMPETENCE
CENTER ORGANIZATIONAL APPROACH PROJECT WORK IS ALLOCATED TO SITES
ACCORDING TO THE TECHNICAL OR DOMAIN EXPERTISE LOCATED AT A GIVEN SITE
&OR EXAMPLE PERHAPS ALL USER INTERFACE DESIGN IS DONE AT A SITE WHERE
USABILITY ENGINEERING EXPERTS ARE LOCATED WITH EXPERIENCE DESIGNING
SIMILAR PRODUCTS )N AN OPEN SOURCE STRUCTURE MANY INDEPENDENT
CONTRIBUTORS DEVELOP A SOFTWARE PRODUCT IN ACCORDANCE WITH A TECHNICAL
INTEGRATION STRATEGY #ENTRALIZED CONTROL IS MINIMAL EXCEPT WHEN AN
INDEPENDENT CONTRIBUTOR INTEGRATES HIS CODE INTO THE PRODUCT LINE
4HESE ORGANIZATIONAL APPROACHES MAY CHANGE OVER TIME &OR EXAMPLE
COMPONENTS MAY BE ALLOCATED AT FIRST WITH THE INTENT THAT THE REMOTE
SITE WILL DEVELOP THE SKILLS OVER TIME TO BECOME A COMPETENCE CENTER IN
THE FUNCTIONALITY THAT COMPONENT PROVIDES ;!VRITZER ET AL =