Test driven architecture enabled process for open collaboration in global

Abstract

A method for developing a software project includes identifying business cases and goals for the software project, defining a common interface architecture through which components of the software project are to be integrated, identifying software project components to be integrated over the common interface, defining high level requirements of the project components, elaborating the component interfaces and defining detailed component requirements, implementing the project components, testing the project components individually, defining integration tests for testing integrated components, and executing the integration tests on a set of integrated components.

Description

CROSS REFERENCE TO RELATED UNITED STATES APPLICATIONS[0001]This application claims priority from “A Test Driven Architecture Enabled Process for Open Collaboration in Global Software Development Environments”, U.S. Provisional Application No. 60 / 868,109 of Avritzer, et al., filed Dec. 1, 2006, the contents of which are herein incorporated by reference.TECHNICAL FIELD[0002]This disclosure is directed to a process to enable collaboration of global software development teams by defining a common architecture for collaboration and testing process to drive the pace of software development.DISCUSSION OF THE RELATED ART[0003]The overhead for managing global software development teams, for developing work packages and defining the detailed requirements for each work package severely constrains the scalability, productivity and quality of work performed in global software development environments. The development of detailed requirements typically consumes most of project resources. In addit...

AI Technical Summary

Benefits of technology

This approach increases team productivity, reduces central team overhead, and enables objective performance evaluation, allowing remote teams to work autonomously while ensuring high-quality code production with fewer defects, thus improving overall project efficiency and scalability.

Problems solved by technology

The overhead for managing global software development teams, for developing work packages and defining the detailed requirements for each work package severely constrains the scalability, productivity and quality of work performed in global software development environments.

The development of detailed requirements typically consumes most of project resources.

In addition, requirements churn has been reported as a major source of project delays.

The current mode of operation of using a central team to perform project management, requirements, architecture, and integration and testing incurs very large overhead for the central team and limits the number of teams that could productively participate.

Specifically, MDRAD focuses on central team definition of requirements, and lacks guidelines and methods for enabling open collaboration, quantitatively rating teams' performance, and for allocating work packages efficiently.

However, neither UP nor RUP address quantitative performance ratings to do team comparisons, and efficient work allocation based on team performance.

When domain experts are from different locations, there's a travel burden for some of them to achieve the all in one room design approach.

However, when distributed teams need to perform tasks within a physical room, team members may resent leaving their home offices for frequent and extended travel to a “foreign work room”.

Images