Call for Paper - September 2020 Edition
IJCA solicits original research papers for the September 2020 Edition. Last date of manuscript submission is August 20, 2020. Read More

Advance Version Control (AVC): A Paradigm Shift from Version Control to Conflict Management

International Journal of Computer Applications
Foundation of Computer Science (FCS), NY, USA
Year of Publication: 2017
Inderdeep Kaur, Hardeep Singh

Inderdeep Kaur and Hardeep Singh. Advance Version Control (AVC): A Paradigm Shift from Version Control to Conflict Management. International Journal of Computer Applications 167(10):7-15, June 2017. BibTeX

	author = {Inderdeep Kaur and Hardeep Singh},
	title = {Advance Version Control (AVC): A Paradigm Shift from Version Control to Conflict Management},
	journal = {International Journal of Computer Applications},
	issue_date = {June 2017},
	volume = {167},
	number = {10},
	month = {Jun},
	year = {2017},
	issn = {0975-8887},
	pages = {7-15},
	numpages = {9},
	url = {},
	doi = {10.5120/ijca2017914384},
	publisher = {Foundation of Computer Science (FCS), NY, USA},
	address = {New York, USA}


Distance is the major barrier in Global software development. It negatively impacts communication and coordination. Many tools are used to help developers to coordinate their work. One such tool is Software Configuration Management (SCM). But studies have shown that SCM lacks in conflict detection. This weakness has been removed by workspace awareness tool.

This paper describes Advance Version Control tool (AVC), a tool that does versioning of artifacts and actively monitor commit activities of the developer. It is an integration of Configuration Management and Conflict Management. AVC determines conflicts at right time and also provides resolution methods like code sharing. The developed tool allows the developers to focus on their main task i.e. programming without presenting trivial notifications and warnings. AVC also has integrated communication medium to further enhance the coordination.


  1. Carmel, E. 1999. Global software teams: Collaborating across borders and time zones. Prentice Hall upper saddle river, NJ,USA.
  2. Lanubile, F. 2009. Collaboration in distributed software development. Software Engineering, Springer, 174-193.
  3. Ågerfalk, P. J., Fitzgerald, B., Holmström, H., Lings, B., Lundell, B., Conchúir, E. O. 2005. A Framework for considering opportunities and threats in distributed software development. In Proceedings of the International Workshop on Distributed Software Development, Austrian Computer Society.
  4. Gumm, D. C. 2005. Distribution Dimensions in Software Development Projects: A Taxonomy. IEEE Software 23(5), 45–51.
  5. Ågerfalk, P. J., Fitzgerald, B., Holmström, H. andConchúir, E. O. 2008. Benefits of Global Software Development: The Known and Unknown.In Proceedings of ICSP’08the Software process, international conference on Making globally distributed software development a success story. 1-9, Springer-Verlag.
  6. Herbsleb,J.D.,Moitra, D. 2001. Global Software Development. IEEE Software, volume 18, Issue 2, 16–20.
  7. Software configuration management: A practical guide. scmguide.pdf.
  8. Bendix, L., Magnusson, J.,Pendleton, C. 2012. Configuration management stories from distributed software development trenches. IEEE Seventh International Conference on Global Software Engineering (ICGSE).
  9. Grinter,Rebecca.E.1996. Supporting Articulation Work Using Software Configuration Management Systems. Computer Supported Cooperative Work,Volume 5, Issue 4,447- 465.
  10. Clatworthy, I. 2007. Distributed version control: Why and how. In Proceedings of Open Source Development Conference (OSDC).
  11. Raymond, E. Understanding version-control systems. Retrieved from
  12. De Souza,Cleidson, R.B., Redmiles, D. and Dourish, P.2003.” Breaking the code”, moving between private and public work in collaborative software development. In Proceedings of ACM SIGGROUPInternational conference on supporting group work GROUP’03, Florida, USA, 105-114.
  13. Conradi,R. and Westfechtel,B. 1998.Version Models for Software Configuration Management. ACM Computing Surveys, vol.30,232-282.
  14. Bird, C. and Zimmermann, T. 2012. Assessing the value of branches with what-if analysis. In proceedings of the ACM SIGSOFT International Symposium on Foundations of Software Engineering, North Carolina.
  15. Levin,S. and Yehudai, A. 2015.Alleviating Merge Conflicts with Fine-grained Visual Awareness.arXiv preprint arXiv:1508.01872.
  16. Fauzi,S.S.M., Bannerman, P.L. and Staples, M. 2010. Software Configuration Management in Global Software Development: A Systematic Map. In Proceedings of 17th Asia Pacific Software Engineering Conference.
  17. Chen, C. Zang, K. 2013. Team Radar: A Radar Metaphor for workspace Awareness. Evaluation of Novel Approaches to Software Engineering. ENASE 2011. Communications in Computer and Information Science,vol 275. Springer, Berlin, Heidelberg.
  18. Sarma, A., Noroozi, Z. and Hoek Andre, V, D. 2003. Palantír: raising awareness among configuration management workspaces. In Proceedings of the 25th International Conference on Software Engineering, May 03-10, Portland, Oregon.
  19. Dourish, P. and Bellotti, V. 1992. Awareness and Coordination in shared Workspaces. In Proceedings of ACM Conference on Computer-Supported Cooperative Work,Tronto,Ontario,Canada.
  20. “GIT, a free, open source, distributed version control system,”, [Online; accessed 11-April-2011].
  21. “Mercurial is a free, distributed source control management tool.”, [Online; accessed 02-April-2011].
  22. Sarma, A. and Hoek, A. vander. 2002. Palantir: coordinating distributedworkspaces. In Proceedings of 26th International Computer Software and Applications(CMPSAC.2002), pp. 1093 – 1097.
  23. Jacob, T.Biehl., Mary, C.,Greg, S. and George, G. R. 2007. FASTDash: A visual dashboard for fostering awareness in software teams. In proceedings of SIGCHI conference on Human factors in Computing systems ACM, pp 1313-1322, San Jose, USA.
  24. Lucia, A.D., Fasano, F., Oliveto, R. and Tortora, G. 2007. Recovering traceability links in software artifact management systems using information retrieval methods. ACM Transactions on Software Engineering and Methodology, volume 16, issue 4.
  25. Bang, J.Y., Popescu, D., Edwards, G., Medvidovic, N., Kulkarni, N., Rama, G.M., and Padmanabhuni,S. 2010. CoDesign: a highlyextensible collaborative software modeling framework. In Proceedings of ACM/IEEE 32nd International Conference on Software Engineering, vol. 2, pp. 243 –246
  26. Hattori, L. and Lanza, M. 2010. Syde: a tool for collaborative software development. ACM/IEEE 32nd International Conference on Software Engineering,vol. 2, pp. 235 –238.
  27. Lucia, A.D., Fasano, F., Oliveto, R., and Tortora, G. 2010. Fine-grained management of software artefacts: the ADAMS system. Software:Practice and Experience, vol. 40, no. 11, pp. 1007–1034.
  28. Dam, H. K and Ghose, A. 2011. An agent-based framework for distributed collaborative model evolution. In Proceedings of the 12th International Workshop on Principles of Software Evolution and the 7th annual ERCIM Workshop on Software Evolution, NY, USA, pp. 121–130.
  29. Huyen, P.T.T. and Ochimizu, K. 2012. A Change Support Model for Distributed Collaborative Work. CoRR,
  30. Costa, C., Mutra, L. 2013. Version Control in Distributed Software Development: A Systematic Mapping Study. In Proceedingsof ICGSE IEEE 8th International Conference on Global Software Engineering, page 90-99. 
  31. Guimaraes, M.L. and Silva, A.R. 2012. Improving early detection of software merge conflicts. In Proceedings of International Conference on Software Engineering ICSE’12, pages 342–352. IEEE Press.
  32. Brun, Y., Holmes, R., Ernst, M. D. and Notkin, D. 2011. Proactive detection of collaboration conflicts. In Proceedings of the 8th Joint Meeting ofthe European Software Engineering Conference and ACM SIGSOFT Symposium on the Foundations of Software Engineering (ESEC/FSE11), pp.168–178.
  33. Sarma, A. and Hoek, A. vander 2002. Palantir: coordinating distributedworkspaces. In Proceedings of 26th International Computer Software and applications (CMPSAC)pp. 1093 – 1097.
  34. Dewan, P. and Hegde, R. 2007. Semi-Synchronous Conflict Detection and Resolution in Asynchronous Software Development. In Proceedings of the 10th European Conference onComputer Supported Cooperative Work (ECSCW ’07), pages 159–178. Springer, London.
  35. Guimaraes, M.L. and Silva, A.R. 2012. Improving early detection of software merge conflicts. In Proceedings of International Conference on Software Engineering ICSE’12, pages 342–352. IEEE Press.
  36. Y, Brun., R, Holmes., Ernst, M. D., and Notkin, D. 2011. Crystal: Precise and Unobtrusive Conflict Warnings. In Proceedings of the 19th ACM SIGSOFT Symposium and the 13th European Conference Foundations of Software Engineering (ESEC/FSE’11), pp.444-447, NY, USA.
  37. Lanza, M., Hattori, L., and Guzzi, A. 2010. Supporting collaboration awareness with real-time visualization of development activity. In Proceedings of 14th European Conference on Software Maintenance and Reengineering (CSMR), 202 –211.
  38. Nordio, M., Estler, H.-C., Furia, C. A. and Meyer, B. 2011. Collaborative software development on the web. arXiv:1105.0768v3.
  39. Hattori, L., Lanza1,M., D’Ambros, M. 2012. A qualitative user study on preemptive conflict detection. In Proceedings of ICGSE,IEEE Seventh international conference on Global Software Engineering.
  40. Dewan, P. 2008. Dimensions of tools for detecting software conflicts. In Proceedings of ACM international workshop on Recommendation systems for software engineering (RSSE’08). Pp 21-25, NY, USA.
  41. Kaur, I., Kaur, P. and Singh, H. 2017. A Comparative Study of Distributed Version Control Tools. In Proceedings of 5th International conference on Advancements in Engineering and Technology (ICAET-2017), ISBN No. 978-81-924893-2-2.
  42. Damian, D., Izquierdo, L. et al. 2007. Awareness in the Wild: Why Communication Breakdowns Occur. In ICGSE ’07: Inter.Conf. on Global Softw. Eng. IEEE Computer Society,81–90.
  43. Kim, M. 2011. An Exploratory Study of Awareness Interests about Software Modifications. In CHASE ’11: Workshop on Cooperative and Human Aspects of Softw. Eng. ACM, 80–83.


Version control tools, conflict detection, workspace awareness.