Deployment and Maintenance

When the total application is developed and tested by the offsite team; the application is deployed into a package and is sent to the client’s location for final testing. Field testing is done by the client’s personnel and the feedback is obtained by the service providers personal from the client for processing. After the total application is deployed at the clients premises, the application enters into the maintenance period where any additional requests by the client and defects fixing are done during the warranty period.

Chapter 6

Conclusion

Although Outsourcing is regarded as a company’s way to reduce Costs there are many other factors which are to be considered like, security issues, Cultural mismatch, re-quirements related etc. Utmost care should be taken by the companies when going for outsourcing. This paper on outsourcing software development tries to give a brief picture of how software is developed in an outsourcing environment. Firstly, it states whether it is a good way to think for outsourcing or not. Secondly, what happens when the software is developed offshore with the available[various types]software lifecycle?

Requirements engineering is a task where the total development of the project de-pends. But, when it comes to outsourcing, there are many other issues that came into picture and it was strongly assumed that a process model is needed for the total require-ments engineering in an outsourcing environment. It is always a good approach to think for requirements engineering outsourcing when the company can follow a step-by-step procedure to ensure that no communication gap and cultural differences are encountered during the total requirements gathering process. Since, communication and culture are the important factors that play a major role for interacting with both the client and service provider. The less the gaps between them the more efficient and effective the work progress.

The Design phase is the task where the actual prototype is built depending on the requirements document delivered by the requirements analyst. While the requirements engineering and High-Level Design is done onsite and low level design is done offsite.

The onsite team is responsible for both the requirements gathering as well as the high level design. They are responsible for The integration of the product is usually handled by the client’s team located onsite.

The Coding phase is the most crucial phase in the development where the total requirements document and the design document play a major role in making software development success. There are a number of issues like security and privacy which are to be taken into consideration while outsourcing coding to a third party. It is always important to make several checks at the service provider’s center by the customer before signing the contract.

The Testing phase usually concentrates on the final corrections to the developed application (or software) . It is always a good approach by the company to look for a different service provider when outsourcing testing services. This not only helps the company in taking up the cost advantage but also in ensuring higher quality.

Finally, Outsourcing is a good approach if it is organised in a meaningful manner. A

37

38 Chapter 6. Conclusion

company has to first concentrate on its core competencies and then let the other things done by a third party. Since outsourcing is a risky approach it is always recommended for the company to make through checks at the service provider center.

Chapter 7

Acknowledgements

Our sincere heartfelt thanks to our supervisor “Mr.Jurgen B¨ostler” and our Course Co-ordinator “Mr.Perl Lindstrom” who has given us this opportunity for doing our thesis at Umea University. Special thanks to our supervisor Mr.Jurgen B¨ostler who has guided us in writing this Master Thesis. we are also thankful to all our family members, friends and colleagues who have supported us. We are very much obliged to all the companies who have assisted us in gathering the vital information required for completion of this report.

39

40 Chapter 7. Acknowledgements

References

[1] BPO - Business Process Outsourcing. http://bpo.starmatrimonials.com/

outsourcing.php (visited 2006-03-14).

[2] Delivery Framework: Delivery models. http://www.visualsoft-tech.com/deliveryfm/deliverymodels.aspx (visited 2006-01-14).

[3] Global Delivery Model. http://www.offshore-softwaredevelopment.com/global-delivery-model.asp (visited 2006-01-14).

[4] Glossary. http://www.e-formation.co.nz/glossary.asp (visited 2006-03-15).

[5] High Level Design, Low level Design. http://www.netsity.com/ourprocess.htm (vis-ited 2006-01-14).

[6] IT biggies eyeing global delivery models: Forrester.

http://www.expresscomputeronline.com/20031110/indianews04.shtml (visited 2006-01-14).

[7] Offshore Delivery Model. http://www.offshore-softwaredevelopment.com/offshore-delivery-model.asp (visited 2006-01-14).

[8] Offshore Delivery Model. http://www.offshore-softwaredevelopment.com/offshore-delivery-model.asp (visited 2006-01-14).

[9] Offshore Development. http://www.navosystems.com/navohtml/offshoredevelopment .html (visited 2006-01-14).

[10] Offsite Delivery Model. http://www.offshore-softwaredevelopment.com/offsite-delivery-model.asp (visited 2006-01-14).

[11] Offsite/Offshore Delivery Model. http://www.offshore-softwaredevelopment.com/offsite-offshore-delivery-model.asp (visited 2006-01-14).

[12] Onsite Delivery Model. http://www.offshore-softwaredevelopment.com/onsite-delivery-model.asp (visited 2006-03-14).

[13] Onsite/Offshore Delivery Model. http://www.offshore-softwaredevelopment.com/onsite-offshore-delivery-model.asp (visited 2006-01-14).

[14] Outsourcing of Business Processes. http://www.valuebasedmanagement.net/methods outsourcing.html (visited 2006-03-14).

[15] Relationship Models. http://www4.butler.com/marketng/winprops.nsf/index/

relationshipmodels?OpenDocument (visited 2006-01-14).

41

42 REFERENCES

[16] Risks in Software Development Outsourcing. http://www.e-zest.net/Outsourcing Central/outsourcing risks.htm (visited 2006-03-15).

[17] Software Development Outsourcing Services. http://www.offshoreoutsourcingservices.

com/software-services-outsourcing.asp (visited 2006-03-15).

[18] What is Outsourcing? http://www.bizbrim.com/outsourcing/outsourcing.htm (visited 2006-03-15).

[19] Accelerance and Steve Mezak. Architecting your software for outsourcing. Accel-erance.com, 2005.

[20] WEB SPIDERS [An ISO 9001:2000 Company]. Application Testing Life Cycle.

http://www.webspiders.com/en/testing whatis.asp (visited 2006-03-28).

[21] David A. Vogel Ph.D.and Jill E. Connelly. Best Practices for Dealing with Offshore Software Development. ManagmentFirst.com, USA, 2005.

[22] Katy Dookrill.

[23] Joy Gumz Frank Parth. System engineering in an outsourcing environment. Tech-nical report, Project Management Institute, Rancho Santa Margarita, CA 92688, 2004.

[24] Brian Hanisch, Corbitt. Requirements engineering during global software develop-ment: Some impediments to the requirements engineering process - a case study.

Technical report, Univeristy of south Australia, Deakin University, Australia.

[25] Philip Hunter. Security issues with offshore outsourcing. Technical report, 2003.

[26] David W Johnson. Test deliverables:test plan, test case, defect-fault, and status report. DevBistro.com, January 2006.

[27] Jyoti Srivastava Kapil Bhatia. Towards a ’model for outsourcing acceptance testing:

Issues, challenges and best practices. Technical report, 4th Annual Software Testing Conference, Tata Consultancy Services, India, 2004.

[28] Jorge Audy Leandro Lopes, Rafael Priladnicki. Requirements specification in dis-tributed software development- a process proposal. Technical report, School of Computer Science PUCRS, Brazil.

[29] Scarlet Pruitt. When outsourcing, don’t forget security, experts say Com-panies often forget about cultural differences that may affect security . http://www.computerworld.com/managementtopics/outsourcing/story/

0,10801,96074,00.html (visited 2006-03-28).

[30] Jorge Luis Nicolas Audy Rafael Prikladnicki. Requirements Engineering in Global Software Developmnet:Preliminary Finding From a Case Study in a SW-CMM context. Technical report, Faculty of Informatics, PPGCC- Brazil, Brazil, 2003.

[31] Ed Kazmierczak Fergus O’Brien Rasha Abbas, Philip Dart. Outsourcing software application development: Issues, implications and impact. Technical report, Uni-veristy of Melbourne, Parkville 3052, Australia, 1997.

REFERENCES 43

[32] Marcia Robinson Ravi Kalakota. Offshore outsourcing: Will your job disappear in 2004? InformIT, 2004.

[33] Suzanne Robertson. An early start to testing: How to test requirements. Technical report, Eurostar’96 Conference, Amsterdam, 1996.

[34] Karen Schweitzer. Business Management

Arti-cle on offshore outsourcing and the various models.

http://www.businessmajors.about.com/cs/businessthought/a/ucoffshoreOutso.html (visited 2006-01-12).

[35] Roger S.Pressman. Software Process. McGraw-Hill, USA, 2001.

[36] Basil Tesler. Outsourcing IT development: Advantages and Disadvanteges.

http://www.webspacestation.com/it-outsourcing-news/articles/outsourcing.html (visited 2006-03-15).

[37] Merlin Thayer, Richard; Dorfman. IEEE computer Society press Tutorial, IEEE, 2000.

[38] Julian Millstein Thomas C.Greble. Security issues in outsourcing. HRO Today, February 2003.

[39] Juan Carlos C. Suarez Tomas Fco.Espino-Rodriguez1, V´ıctor Padron Robaina. The management perception of the strategy of outsourcing-an empirical evidence. Tech-nical report, Universidad de Las Palmas de Gran Canaria, Spain.

[40] India Webdevelopors. Outsourcing Software Development Programming and Cod-ing to India. http://www.indiawebdevelopers.com/services/Coding.asp (visited 2006-03-28).

[41] Linda Westfall. Software requirements engineering: What, why, who, when and how. SQP, 7(4), 2005.

[42] K.E Wiegers. Software Requirements. Microsoft Press, USA, 2003.

[43] Frank Mayadas William Aspray and Editors Moshe Y. Vardi. Globalization and offshoring of software - a report of the acm job migration task force. ACM Journal, 2006.

[44] P.A.V Zhu H; Hall and May J.H. -software unit test coverage and adequacy. ACM Computing Surveys, 29(4):366–427, 1997.