Prioritizing SCM for Managing Inconsistency in Distributed Software Project Development
Dillip Kumar Mahapatra1, Tanmaya Kumar Das2

1Dillip Kumar Mahapatra, Associate Professor & Head of Deptt., Information Technology, Krupajal Engineering College, Bhubaneswar, Odisha, India.
2Tanmaya Kumar Das, Asst. Professor, Dept. of Computer Science & Engineering, C.V. Raman College of Engineering, Bhubaneswar, Odisha, India

Manuscript received on 12 December 2012 | Revised Manuscript received on 21 December 2012 | Manuscript Published on 30 December 2012 | PP: 58-64 | Volume-2 Issue-1, December 2012 | Retrieval Number: A0367112112 /2012©BEIESP
Open Access | Editorial and Publishing Policies | Cite | Mendeley | Indexing and Abstracting
© The Authors. Blue Eyes Intelligence Engineering and Sciences Publication (BEIESP). This is an open access article under the CC-BY-NC-ND license (

Abstract: The evolution of software engineering has been constant over the past four decades. Some major technological discontinuities, however, can be identified in this progress, which caused a more radical rethinking of the previous established approaches. This, in turn, generated research for new methods, techniques and tools to properly deal with the new challenges. Distributed Software Development (DSD) has recently evolved, resulting in an increase in the available literature. Organizations now have a tendency to make greater development efforts in more attractive zones. The main advantage of this lies in a greater availability of human resources in decentralized zones at less cost. There are, however, some disadvantages which are caused by the distance that separates the development teams. Coordination and communication become more difficult as the software components are sourced from different places, thus affecting project organization, project control, and product quality. New processes and tools are consequently necessary. This paper highlights the software engineering process for distributed software development and related topics in coordination of projects and project artifacts. Different configuration management systems (CMS) approaches and techniques are discussed; these include client-server, k-mutual exclusion, and distributed configuration management systems. New trends in CMS technologies and approaches are also outlined here. Some major areas are addressed in this paper like: how does CMS enable collaborative work; information exchange among clients at different geographical areas and the knowledge management across distributed clients.
Keywords: Aggregation, Co-operative, Collaborative, Editors, Knowledge Management, Milestones, SCM, Release, Version, Version-Control.

Scope of the Article: Knowledge Management