A Model for People-Centric Software Configuration Management

Syahrul Fahmy, Aziz Deraman, Jamaiah H. Yahaya, Amir Ngah, Fouad Abdulameer Salman


Software Configuration Management (SCM) is the adaptation of Configuration Management in software engineering to control changes to software products. Its implementation is guided by international standards and procedures, in addition to an array of supporting tools. However, the issues of project delays and products that do not fit its purpose still prevail in software development, questioning the practice of SCM by software organizations. Current research efforts in are mainly focused on technical issues, with little interest (if any) in the role of human in SCM implementation. This paper proposes an alternative view of SCM, which emphasizes the role of human in its implementation. The People-Centric Software Configuration Management (P-SCM) model comprises of four components namely People, Process, Tools and Documentation. It reveals the competency of the software project team, extensiveness of activities carried out by the organization, availability of supporting tools, and comprehensiveness of documentation. PSCM supports software organizations in decision-making activities, provide insights to project discrepancies, identify best practices and pitfalls, support the identification of training needs and the selection of tools. Initial results reveal that P-SCM provides additional input to software organizations in project planning and outsourcing activities.


People-Centric Approach; Software Configuration Management; Software Engineering; Software Quality;

Full Text:



IEEE 828 Standard for Configuration Management in Systems and Software Engineering, the Institute of Electrical and Electronics Engineers, 2012.

IEEE 15939 Standard Adoption of ISO/IEC 15939:2007 - Systems and Software Engineering - Measurement Process, the Institute of Electrical and Electronics Engineers, 2009.

ISO 10007 Quality Management - Guidelines for Configuration Management, International Organization for Standardization, 2009.

ISO/IEC 12207 Standard for Systems and Software Engineering - Software Life Cycle Processes, International Organization for Standardization, 2008.

ISO/IEC 15288 - Systems and Software Engineering - System Life Cycle Processes, International Organization for Standardization, 2008.

ISO/IEC 15939 Systems and Software Engineering - Measurement Process, International Organization for Standardization, 2007.

ISO/IEC/IEEE 24765 Systems and Software Engineering - Vocabulary, International Organization for Standardization, 2010.

S. I. Feldman, “Make - A program for maintaining computer programs,” Software, Practice and Experience, vol. 9, no. 3, pp. 255– 265, 1979.

W. F. Tichy, “RCS - A system for version control,” Software - Practice and Experience, vol. 15, no. 7, pp. 637-654, July 1985.

A. Wright, Requirements for a Modern CM System. CaseWare, Inc., 1990.

Sun Teamware Product Documentation. Sun MicroSystems Inc., 2000.

S. P. De Rosso, and D. Jackson, “What's wrong with git? A conceptual design analysis,” in Proc. 2013 ACM International Symposium on New Ideas, New Paradigms, and Reflections on Programming & Software, New York, 2013, pp. 37-52.

L. McVoy, “Preliminary product line support in bitkeeper,” in Proc. 19th International Conference on Software Product Line, New York, 2015, pp. 245-252.

T. Buchmann, A. Dotor, and B. Westfechtel, “MOD2-SCM: A modeldriven product line for software configuration management systems,” Information and Software Technology, vol. 55, no. 3, pp. 630-650, March 2013.

P. Kaur, and H. Singh, “A layered structure for uniform version management in component based systems,” SIGSOFT Software Engineering Notes, vol. 34, no. 6, pp. 1-7, Dec. 2009.

Y. Ki, and M. Song, “An open source-based approach to software development infrastructures,” in Proc. IEEE/ACM International Conference on Automated Software Engineering, Washington, 2009, pp. 525-529.

T. Mikkonen, and A. Nieminen, “Elements for a cloud-based development environment: online collaboration, revision control, and continuous integration,” in Proc. WICSA/ECSA 2012 Companion Volume, New York, 2012, pp. 14-20.

E. H. Bersoff, V. D. Henderson, and S. G. Siegel, Software Configuration Management: An Investment in Product Integrity. Prentice-Hall, Inc., 1980.

F. J. Buckley, Implementing Configuration Management: Hardware, Software, and Firmware. IEEE Computer Society Press, 1993.

R. Conradi, and B. Westfechtel, “Version models for software configuration management”, ACM Computing Surveys, vol. 30, no. 2, pp. 232-282, 1998.

M. C. Chu-Carroll, J. Wright, and D. Shields, “Supporting aggregation in fine grained software configuration management”, in Proc. 10th ACM SIGSOFT Symposium on Foundations of Software Engineering, New York, 2002, pp. 99-108.

R. Premraj, A. Tang, N. Linssen, H. Geraats, and H. van Vliet, “To branch or not to branch?”, in Proc. 2011 International Conference on Software and Systems Process, New York, 2011, pp. 81-90.

A. Deraman, J. Yahya, S. Fahmy, and Z. Mohamad, “Technical Report 59297-2. Survey on software configuration management approaches in Malaysia,” unpublished.

S. Fahmy, A. Deraman, and J. Yahaya, “Software Configuration Management Practice In Malaysia,” Journal of Theoretical and Applied Information Technology, vol. 94, no. 1, pp. 1-17, 2016.

A. Deraman, J. Yahya, Z. Mohamad, and S. Fahmy, “Technical Report 59297-3. Software configuration management in public higher education institutions: an observation”, unpublished.


  • There are currently no refbacks.

Creative Commons License
This work is licensed under a Creative Commons Attribution 3.0 License.

ISSN: 2180-1843

eISSN: 2289-8131