Abstract
Distributed software development has resulted in formation of business partners spread across different economic, temporal, and organizational zones collaborating together for shared authorship of evolving software artifacts. However, the distributed approach is not without risks, and organizations implement specific test strategies to assist in the verification process of work-in-progress software artifacts. This paper discusses the test strategies adopted in the software development lifecycle by a service provider pursuing distributed software development in New Zealand, Australia, and India. Verification and validation processes have been deployed to ascertain the quality, security and traceability of artifacts developed in distributed sites. Findings reveal that strategies are based on protection of sensitive data through management of test database, use of drivers and interfacing stub supports between modules, as well as compliance verification on incremental releases through a customized “Synchronize and Stabilize” lifecycle model. A staging environment, within the case business context, is used for evaluating the robustness of the software product before its official launch in production environment. The actual ongoing work practices within distributed software business environments are presented, which provide value to academia, industry, ICT sector and government institutions.
Sign-in/Register to access full text options 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callDisclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
