راهنمای توسعه نرم‌افزار جهانی (سری آوریباخ در مهندسی نرم‌افزار کاربردی)

economics And Technology Have Dramatically Re-shaped The Landscape Of Software Development. It Is No Longer Uncommon To Find A Software Development Team Dispersed Across Countries Or Continents. Geographically Distributed Development Challenges The Ability To Clearly Communicate, Enforce Standards, Ensure Quality Levels, And Coordinate Tasks. Global Software Development Handbook Explores Techniques That Can Bridge Distances, Create Cohesion, Promote Quality, And Strengthen Lines Of Communication. the Book Introduces Techniques Proven Successful At International Electronics And Software Giant Siemens Ag. It Shows How This Multinational Uses A High-level Process Framework That Balances Agility And Discipline For Globally Distributed Software Development. The Authors Delineate An Organizational Structure That Not Only Fosters Team Building, But Also Achieves Effective Collaboration Among The Central And Satellite Teams. The Handbook Explores The Issues Surrounding Quality And The Processes Required To Realize Quality In A Distributed Environment. Communication Is A Tremendous Challenge, Especially For Teams Separated By Several Time Zones, And The Authors Elucidate How To Uncover Patterns Of Communication Among These Teams To Determine Effective Strategies For Managing Communication. the Authors Analyze Successful And Failed Projects And Apply This Information To How A Project Can Be Successful With Distributed Teams. They Also Provide Lightweight Processes That Can Be Dynamically Adapted To The Demands Of Any Project. Contents 6 Foreword by Manfred Broy 14 Foreword by James D. Herbsleb 18 Preface 20 Acknowledgments 24 About the Authors 26 Glossary 28 Abbreviation List 30 INTRODUCTION 34 Motivation 36 1.1 What is Global Software Development (GSD)? 36 1.2 Challenges to Global Software Development 37 1.3 Managing Global Software Development 39 1.6 Summary and Conclusions 40 1.7 Discussion Questions 40 References 40 Critical Success Factors for Global Software Development 42 2.1 Issues 43 2.2 Critical Success Factors 43 2.2.1 Reduce Ambiguity 43 2.2.2 Maximize Stability 44 2.2.3 Understand Dependencies 45 2.2.4 Facilitate Coordination 46 2.2.5 Balance Flexibility and Rigidity 46 2.3 A Process Framework 47 2.4 Development Phases and Decision Points 49 2.5 Summary and Conclusions 52 2.6 Discussion Questions 52 References 53 PLANNING 54 Requirements Engineering 56 3.1 Background 57 3.1.1 Change Management 57 3.1.2 Quality Assurance (QA) 58 3.1.3 Impact on Related Processes 58 3.2 Requirements Engineering Process 58 3.2.1 Elicitation 59 3.2.2 Modeling 60 3.2.3 Requirements Review 65 3.3 Tooling 66 3.4 Phasing 67 3.5 Summary and Conclusions 68 3.6 Discussion Questions 68 References 69 Requirements for the Architecture 70 4.1 Background 71 4.1.1 How Does an Architecture Relate to the Business Goals? 71 4.1.2 What Influences anArchitecture? 73 4.1.3 What Information Does an Architect Need? 73 4.1.4 What is the Infuence of GSD on the Architecture? 74 4.2 Architecturally Significant Requiements 75 4.2.1 Elicitation 75 4.2.2 Follow-on Activities 81 4.2.3 Documentation 82 4.3 Summary and Conclusions 83 4.4 Discussion Questions 83 References 83 Architecture 84 5.1 Background 85 5.1.1 Accounting for Quality Attribute Requirements 85 5.1.2 Accounting for the Organizational Structure 86 5.1.3 Making Architectural Trade-offs 86 5.2 Designing the System 87 5.2.1 Define ork Units 88 5.2.2 Identify Module Responsibilities 89 5.2.3 Analyze Dependencies 91 5.2.4 Identify Critical Paths 93 5.2.5 Document the Architecture 94 5.2.6 Review the Architecture 96 5.3 Summary and Conclusions 97 5.4 Discussion Questions 97 References 98 Risk Analysis 100 6.1 Background 101 6.1.1 What is a Risk? 101 6.1.2 The Risk Life Cycle 102 6.1.3 Risks in a GSD Context 102 6.2 Managing Risk in GSD Projects 106 6.2.1 Risk Identifcation 106 6.2.2 Mitigating Risks 108 6.2.3 Monitoring Risks 109 6.4 Summary 110 6.5 Discussion Questions 110 References 111 Project Planning Process 112 7.1 Project Planning: An Overview 112 7.2 Feature Release Planning 114 7.2.1 Participants 115 7.3 Development Planning 116 7.3.1 Participants 118 7.4 Cost Estimation 119 7.5 Phasing of the Planning Effort 119 7.5.1 Planning during the Inception Phase 119 7.5.2 Planning during the Elaboration Phase 122 7.5.3 Planning during the Construction Phase 122 7.6 Summary and Conclusions 123 7.7 Discussion Questions 123 References 124 Project Estimation 126 8.1 Top-Down Estimation Approach 127 8.1.1 Who is Involved in This Activity? 128 8.1.2 What are the Inputs and Outputs? 128 8.1.3 Global Development Assertion 129 8.1.4 Size 131 8.1.5 Effort 132 8.1.6 Schedule 133 8.1.7 Top-Down Estimation Steps 133 8.2 Bottom-Up Estimate 136 8.3 Estimation Tools 139 8.4 Summary and Conclusions 139 8.5 Discussion Questions 140 References 140 ORGANIZATION STRUCTURE 142 Software Development Teams 144 9.1 Structure of a GSD Project 145 9.1.1 Roles and Responsibilities 150 9.2 Size 153 9.3 Summary and Conclusions 153 9.4 Discussion Questions 154 References 154 Supplier Manager 156 10.1 Roles and Responsibilities 157 10.2 Desired Skills 159 10.3 Organizational Models 162 10.4 Intercultural Issues 164 10.5 Summary and Conclusions 165 10.6 Discussion Questions 166 References 166 MONITORING AND CONTROL 168 Quality Assurance 170 11.1 Background 170 11.1.1 QA in a Global Context 171 11.2 Measuring Process Quality 173 11.2.1 Defining Pocesses 173 11.2.2 Defining Measues 173 11.2.3 Improving Processes 175 11.3 Measuring Product Quality 175 11.3.1 Defect Types 175 11.3.2 Issues with Product Quality in a GSD Context 176 11.3.3 Strategies for Maintaining Quality in a GSD Context 176 11.4 Product Maintenance 177 11.4.1 Product Maintenance in a Global Context 178 11.5 Summary and Conclusions 181 11.6 Discussion Questions 181 References 182 Infrastructure Support for Global Software Development 184 12.1 Criteria for Selecting the Infrastructure 185 12.1.1 Accessibility 185 12.1.2 Collaboration and Concurrency 185 12.1.3 Processes 186 12.1.4 Awareness and Integration 186 12.2 Communication and Coordination 187 12.2.1 Communication and Collaboration Strategy 187 12.2.2 Communication and Collaboration Infrastructure 188 12.3 Knowledge Management: Software Design, Models, and Documentation 190 12.3.1 Selecting the Knowledge Management Infrastructure 192 12.3.2 Knowledge Management Infrastructure (Gersmann, 2005) 193 12.4 Software Configuation Management 195 12.4.1 Selecting the Software Configuation Management Infrastructure 196 12.4.2 The Software Configuation Management Infrastructure 196 12.4.3 SCM Processes to Facilitate Global Software Development 197 12.5 Summary and Conclusions 200 12.6 Discussion Questions 201 References 201 Communication 202 13.1 Communication Drivers 203 13.2 Communication Barriers 204 13.3 Communication and Coordination 206 13.4 Communication and Control 208 13.4.1 Social Network Analysis 209 13.5 Summary and Conclusions 212 13.6 Discussion Questions 212 References 213 CASE STUDIES 214 GSP 2005 216 14.1 The MSLite Project 217 14.2 Challenges Faced during First Year of MSLite’s Development 218 14.3 Approach for the Second Year of MSLite’s Development 220 14.3.1 Process 220 14.3.2 Collaboration, Communication, and Knowledge Management 223 14.3.3 Requirements 225 14.3.4 Architecture and Design 227 14.3.5 Technical 227 14.3.6 Strategic Issues: Planning and Control 228 14.3.7 Quality Assurance 232 14.3.8 Training 233 14.4 Current Status of the MSLite Development Effort 234 14.5 Next Steps for MSLite 234 References 235 DPS2000 236 15.1 Background 236 15.2 Global Analysis 237 15.3 Design Strategies 238 15.4 DPS2000 Architecture 238 15.5 Project Planning 238 15.6 Project Management 239 15.7 Lessons Learned 240 15.8 Summary 242 References 243 FS2000 244 16.1 Requirements for the New Enterprise 244 16.2 Scaling the Development Process 245 16.3 The Architecture 247 16.4 Restructuring the Organization 247 16.5 Achieving Integration 248 16.6 Lessons Learned 249 16.7 Summary 250 BAS 252 17.1 Background 252 17.2 Global Analysis 253 17.3 BAS Architecture 254 17.4 Project Planning 255 17.5 Project Management 255 17.6 Lessons Learned 256 17.7 Summary 259 References 259 CONCLUDING REMARKS 260 Conclusions 262 18.1 Issues in Globally Distributed Development 262 18.2 Recipe for Success 264 18.3 Sharing Best Practices 266 18.4 Summary and Conclusions 267 References 268 Index 272 Contents......Page 6 Foreword by Manfred Broy......Page 14 Foreword by James D. Herbsleb......Page 18 Preface......Page 20 Acknowledgments......Page 24 About the Authors......Page 26 Glossary......Page 28 Abbreviation List......Page 30 INTRODUCTION......Page 34 1.1 What is Global Software Development (GSD)?......Page 36 1.2 Challenges to Global Software Development......Page 37 1.3 Managing Global Software Development......Page 39 References......Page 40 Critical Success Factors for Global Software Development......Page 42 2.2.1 Reduce Ambiguity......Page 43 2.2.2 Maximize Stability......Page 44 2.2.3 Understand Dependencies......Page 45 2.2.5 Balance Flexibility and Rigidity......Page 46 2.3 A Process Framework......Page 47 2.4 Development Phases and Decision Points......Page 49 2.6 Discussion Questions......Page 52 References......Page 53 PLANNING......Page 54 Requirements Engineering......Page 56 3.1.1 Change Management......Page 57 3.2 Requirements Engineering Process......Page 58 3.2.1 Elicitation......Page 59 3.2.2 Modeling......Page 60 3.2.3 Requirements Review......Page 65 3.3 Tooling......Page 66 3.4 Phasing......Page 67 3.6 Discussion Questions......Page 68 References......Page 69 Requirements for the Architecture......Page 70 4.1.1 How Does an Architecture Relate to the Business Goals?......Page 71 4.1.3 What Information Does an Architect Need?......Page 73 4.1.4 What is the Infuence of GSD on the Architecture?......Page 74 4.2.1 Elicitation......Page 75 4.2.2 Follow-on Activities......Page 81 4.2.3 Documentation......Page 82 References......Page 83 Architecture......Page 84 5.1.1 Accounting for Quality Attribute Requirements......Page 85 5.1.3 Making Architectural Trade-offs......Page 86 5.2 Designing the System......Page 87 5.2.1 Define ork Units......Page 88 5.2.2 Identify Module Responsibilities......Page 89 5.2.3 Analyze Dependencies......Page 91 5.2.4 Identify Critical Paths......Page 93 5.2.5 Document the Architecture......Page 94 5.2.6 Review the Architecture......Page 96 5.4 Discussion Questions......Page 97 References......Page 98 Risk Analysis......Page 100 6.1.1 What is a Risk?......Page 101 6.1.3 Risks in a GSD Context......Page 102 6.2.1 Risk Identifcation......Page 106 6.2.2 Mitigating Risks......Page 108 6.2.3 Monitoring Risks......Page 109 6.5 Discussion Questions......Page 110 References......Page 111 7.1 Project Planning: An Overview......Page 112 7.2 Feature Release Planning......Page 114 7.2.1 Participants......Page 115 7.3 Development Planning......Page 116 7.3.1 Participants......Page 118 7.5.1 Planning during the Inception Phase......Page 119 7.5.3 Planning during the Construction Phase......Page 122 7.7 Discussion Questions......Page 123 References......Page 124 Project Estimation......Page 126 8.1 Top-Down Estimation Approach......Page 127 8.1.2 What are the Inputs and Outputs?......Page 128 8.1.3 Global Development Assertion......Page 129 8.1.4 Size......Page 131 8.1.5 Effort......Page 132 8.1.7 Top-Down Estimation Steps......Page 133 8.2 Bottom-Up Estimate......Page 136 8.4 Summary and Conclusions......Page 139 References......Page 140 ORGANIZATION STRUCTURE......Page 142 Software Development Teams......Page 144 9.1 Structure of a GSD Project......Page 145 9.1.1 Roles and Responsibilities......Page 150 9.3 Summary and Conclusions......Page 153 References......Page 154 Supplier Manager......Page 156 10.1 Roles and Responsibilities......Page 157 10.2 Desired Skills......Page 159 10.3 Organizational Models......Page 162 10.4 Intercultural Issues......Page 164 10.5 Summary and Conclusions......Page 165 References......Page 166 MONITORING AND CONTROL......Page 168 11.1 Background......Page 170 11.1.1 QA in a Global Context......Page 171 11.2.2 Defining Measues......Page 173 11.3.1 Defect Types......Page 175 11.3.3 Strategies for Maintaining Quality in a GSD Context......Page 176 11.4 Product Maintenance......Page 177 11.4.1 Product Maintenance in a Global Context......Page 178 11.6 Discussion Questions......Page 181 References......Page 182 Infrastructure Support for Global Software Development......Page 184 12.1.2 Collaboration and Concurrency......Page 185 12.1.4 Awareness and Integration......Page 186 12.2.1 Communication and Collaboration Strategy......Page 187 12.2.2 Communication and Collaboration Infrastructure......Page 188 12.3 Knowledge Management: Software Design, Models, and Documentation......Page 190 12.3.1 Selecting the Knowledge Management Infrastructure......Page 192 12.3.2 Knowledge Management Infrastructure (Gersmann, 2005)......Page 193 12.4 Software Configuation Management......Page 195 12.4.2 The Software Configuation Management Infrastructure......Page 196 12.4.3 SCM Processes to Facilitate Global Software Development......Page 197 12.5 Summary and Conclusions......Page 200 References......Page 201 Communication......Page 202 13.1 Communication Drivers......Page 203 13.2 Communication Barriers......Page 204 13.3 Communication and Coordination......Page 206 13.4 Communication and Control......Page 208 13.4.1 Social Network Analysis......Page 209 13.6 Discussion Questions......Page 212 References......Page 213 CASE STUDIES......Page 214 GSP 2005......Page 216 14.1 The MSLite Project......Page 217 14.2 Challenges Faced during First Year of MSLite’s Development......Page 218 14.3.1 Process......Page 220 14.3.2 Collaboration, Communication, and Knowledge Management......Page 223 14.3.3 Requirements......Page 225 14.3.5 Technical......Page 227 14.3.6 Strategic Issues: Planning and Control......Page 228 14.3.7 Quality Assurance......Page 232 14.3.8 Training......Page 233 14.5 Next Steps for MSLite......Page 234 References......Page 235 15.1 Background......Page 236 15.2 Global Analysis......Page 237 15.5 Project Planning......Page 238 15.6 Project Management......Page 239 15.7 Lessons Learned......Page 240 15.8 Summary......Page 242 References......Page 243 16.1 Requirements for the New Enterprise......Page 244 16.2 Scaling the Development Process......Page 245 16.4 Restructuring the Organization......Page 247 16.5 Achieving Integration......Page 248 16.6 Lessons Learned......Page 249 16.7 Summary......Page 250 17.1 Background......Page 252 17.2 Global Analysis......Page 253 17.3 BAS Architecture......Page 254 17.5 Project Management......Page 255 17.6 Lessons Learned......Page 256 References......Page 259 CONCLUDING REMARKS......Page 260 18.1 Issues in Globally Distributed Development......Page 262 18.2 Recipe for Success......Page 264 18.3 Sharing Best Practices......Page 266 18.4 Summary and Conclusions......Page 267 References......Page 268 Index......Page 272 Offering a unique perspective on global agility, this handbook describes the convergence of two movements - globally distributed and agile software development. The book explores techniques that can bridge distances, create cohesion, promote quality, and strengthen lines of communication. The authors delineate an organizational structure that not only fosters team building, but also achieves effective collaboration among the central and satellite teams. They explore the issues surrounding quality and the processes required to realize quality in a distributed environment. The book elucidates ho This book introduces a high-level process framework that balances agility and discipline for globally distributed software development. The authors elucidate an organizational structure that not only fosters team building, but also achieves effective collaboration among the central and the geographically distributed teams.--[book cover] Describes the convergence of two movements - globally distributed and agile software development. This book explores techniques that can bridge distances, create cohesion, promote quality, and strengthen lines of communication. It elucidates how to effectively manage communication among geographically distributed teams.