An Approach to Sharing Business Process Models in Agile-Style Global Software Engineering
The globalization of information technology and the improvement of telecommunication facilities have facilitated software development business processes worldwide. Despite this increasingly popular trend, the initial expectations of the cost reductions of offshore outsourcing have not been realized. Many software development companies are facing difficulties caused by many hidden costs, including translation efforts in language gap, transition risks, learning needs, communication overheads, setup times, ramping up durations, scope creeps, etc. In this paper, we propose an approach to improving knowledge sharing in global software development. In addition, the trend of software development methodology has been changing to iterative and agile style from the classic waterfall model. In iterative and agile software developments, requirement specification, coding, testing, are mainly interested in a relatively short term. The rationale of this change came from the higher software quality and higher customer satisfaction. Iterative process can involve customers and developers into its software development mode carefully and deeply. One of the challenges is to apply an iterative or agile development model into global software developments. The main problem is such iterative and agile process might need the tremendous number of communications and documents for collaboration because of iteration. Thus, software collaboration tools will be valuable for such situations in global software developments.
KeywordsBusiness Process Software Development Global Software Development Business Process Modeling Notation Global Software
Unable to display preview. Download preview PDF.
- 1.Aron, R., Sigh, J.V.: Getting offshoring right. Harvard Business Review, 135–142 (2005)Google Scholar
- 3.Cusumano, M.A., MacCormack, A., Kemerer, C.F., Crandall, W.: Software development worldwide: The state of the practice. IEEE Software, 2–8 (2003)Google Scholar
- 5.Herman, I., Marshall, M.: Graphxml - an xml based graph interchange format (2000), http://ftp.cwi.nl/CWIreports/INS/INS-R0009.pdf
- 6.Business Process Management Initiative, Bpmi.org (2008), http://www.bpmi.org/
- 7.The RuleML Initiative, Ruleml tutorial (2005), http://www.ruleml.org/papers/tutorial-ruleml-20050513.html
- 8.Klein, M.: Capturing design rationale in concurrent engineering teams. IEEE Computer. Special Issue on Computer Support for Concurrent Engineering 26(1), 39–47 (1993)Google Scholar
- 9.van Lamsweerde, A.: Goal-oriented requirements engineering: A guided tour. In: RE, pp. 249–262 (2001)Google Scholar
- 10.Malone, T.W.: The Future of Work: How the New Order of Business Will Shape Your Organization, Your Management Stype, and Your Life. Harvard Business School Press (2004)Google Scholar
- 12.Tanabe, D., Uno, K., Akemine, K., Yoshikawa, T., Kaiya, H., Saeki, M.: Supporting requirements change management in goal oriented analysis. In: Proceedings of the 2008 16th IEEE International Requirements Engineering Conference RE 2008, pp. 3–12. IEEE Computer Society Press, Los Alamitos (2008)CrossRefGoogle Scholar
- 13.W3C: Owl web ontology language guide (2004), http://www.w3.org/TR/owl-guide/