Collaboration is a process in which several different people can be a constructive perspective to explore the differences and find a solution that allows to exceed the capabilities of each individual [10]. Collaboration is not just working together but it should give results [11]. Model of collaboration in software development that is proposed in this paper is the result of a series of improvements that have been made of the research in 2011 the first model proposed in this study is a collaboration series of models of software development [7]. The model is the result of collaboration and technology mapping method in each phase of software development. The model was tested with the observation of software project, the results of the rule of compliance at the source code generated 87.8% (with measurement sonar version 2.5). Collaborative development of software is illustrated in Fig. 1.

[12] suggested a proposed a framework for classification and evaluation process in the field of Distributed Software Development and Collaborative Software Development, stated in Collaborative Software Development Framework Analysis. In that collaborative framework classified into 6 dimensions, namely organization distribution, temporal distribution, spatial distribution, process direction, intensity process, and process discipline. Collaboration between programmers in software development consists of four dimensions, namely the spatial distribution, temporal distribution intensity, and process direction [13]. While Collaborative model in the virtual world, covering 5 dimensions of technology, people, processes the information, and leadership [14]. [15] proposed a model of collaboration in software development using the principles of axiomatic design (partnership strategy, collaboration strategy, and software development strategy).

Based on research of collaborative model that has been conducted, it can be concluded that the model of collaboration composed of elements of the method / process, technology, and human. Therefore [8] mapped the human behavior in a team of developers to collaborate. They proposed mapping properties of human behavior in a collaborative team of developers, the mastery of technology, communication, interaction, potential, competence, physical and psychological conditions, and the dynamic changes in humans. Then the property is improved based on the behavior of the data some cases, making it the ability to use tools, mastery of symbols, communication skills, ability to interact, potential, competence, physical state, physiological traits / states, and experiences [8]. Then [9] proposed a model of collaboration for the construction phase of software development (coding and testing) associated with software product quality. Dimensions of collaboration processes in the model include the spatial distribution, temporal distribution, process direction, and intensity. The product quality of software included complexity, documentation, duplications, sizes, and rules of compliance.

[16] conducted a study on the relationship of collaboration in software development teams (called the block, with teamwork quality) with team performance (effectiveness and efficiency-quality-schedule and budget). The study stated that there is a positive correlation between teamwork quality and team performance. While research conducted by [17] stated that mature group development (cohesion, conflict minimum, equilibrium between task and socio-emotional needs, good communication, involvement) positive effect on satisfaction (interaction process and solution). However, mature group had no impact on software quality (functional system, Graphical User Interface, maintenance, cost and benefit). The research conducted by [9] states that there is a positive relationship between human behavior in the process of collaboration in the development team and the quality of the product (source code quality).

References :

[1]     Standish Group, “The Chaos Manifesto 2013 :Think Big, Act Small,” Standish Group International, 2013.

[2]     B. W. Boehm, “Software Risk Management : Principles and Practices,” IEEE Software, vol. 8, no. 1, pp. 32-41, 1991.

[3]     D. Tesch, T. J. Kloppenborg and M. N. Frolick, “IT Project Risk Factors : The Project Management Professionals Perspective,” Journal of Computer Information Systems, vol. 47, no. 4, pp. 61-69, 2007.

[4]     V. Lalsing, S. Kishnah and S. Puduruth, “People Factors in Agile Software Develpment and Project Management,” International Journal of Software Engineering & Aplications (IJSEA), vol. 3, no. 1, pp. 117-137, 2012.

[5]     C. Cook and N. Churcher, “Modeling and measuring collaborative software engineering,” Darlinghurst, Australia, 2005.

[6]     S. Sawyer and P. Guinan, “Software Development : Processes and Performance,” IBM Systems Journal, vol. 37, no. 4, pp. 552-568, 1998.

[7]     T. Kusumasari, I. Supriana, H. Sastramiharja and K. Surendro, “Collaboration Model of Software Developemnt,” in Electrical Engineering and Informatics (ICEEI), Bandung, 2011.

[8]     T. Kusumasari, H. Sastramiharja and K. S. I. Surendro, “Human Behavior Factor of Collaborative Software Development (Faktor Perilaku Manusia dalam Kolaborasi Pengembangan Perangkat Lunak),” Mataram, 2013.

[9]     T. F. Kusumasari, I. Supriana, H. Sastramiharja and K. Surendro, “Human Behavior Conceptual Model in Collaborative Software Development Product Quality,” in International Conference on Advanced Computer Science and Information Systems (ICACSIS), Bali, 2013.

[10]  S. Callahan, M. Schenk and N. White, Building a Collaborative Workspace, Anecdot White Paper, 2008.

[11]  M. Hansen, “Collaboration – How Leaders Avoid the Traps, Create Unity, and Reap Big Results,” 2009. [Online]. Available: http://www.summaries.com/Platinum/Collaboration.pdf. [Accessed 9 January 2013].

[12]  T. Hildenbrand, R. Rothlauf, M. Geisser, A. Heinzl and T. Kude, “Approach to Collaborative Software Development,” in International Conference on Complex, Intelligent and Software Intensive Systems, 2008.

[13]  M. Schwind, A. Schenk and M. Schneider, “A Tool for the Analysis of Social Networks in Collaborative Software Development,” Hawaii, 2010.

[14]  I. Boughzala, G.-J. de Vreede and M. Limayem, “eam Collaboration in Virtual Worlds: Editorial to the Special Issue,” Journal of the Association for Information Systems, vol. 13, no. 10, pp. 714-734, 2012.

[15]  Arsenyan and Büyüközkan, “Modelling Collaborative Software Development Using Axiomatic Design Principles,” IAENG International Journal of Computer Science, vol. 36, no. 3, 2009.

[16]  M. Hoegl and H. G. Gemuenden, “Teamwork Quality and the Success of Innovative Projects: A Theoretical Concept and Empirical Evidence,” Organization Science, Vol.12, No.12, pp. 435-449, 2010.

[17]  R. J. Ocker, “The relationship between interaction, group development, and outcome : a study of virtual communication,” in Proc.IEEE HICSS’01, 2001.

[18]  U. Dompke, “Human Behavior Representation : Definition, Presentasi pada RTO SAS Lecture Series on Simulation of and for Military Decision Making, II-1 –II-12,” 2001.