WSEAS Transactions on Computers


Print ISSN: 1109-2750
E-ISSN: 2224-2872

Volume 16, 2017

Notice: As of 2014 and for the forthcoming years, the publication frequency/periodicity of WSEAS Journals is adapted to the 'continuously updated' model. What this means is that instead of being separated into issues, new papers will be added on a continuous basis, allowing a more regular flow and shorter publication times. The papers will appear in reverse order, therefore the most recent one will be on top.



How to Comprehend, Rationalize and Develop Version Control Systems? Case: Aalto University

AUTHORS: Antti Miettinen, Jani Nousiainen, Jyri Rajamäki

Download as PDF

ABSTRACT: The topic of the study is topical, as the various universities and non-governmental companies are looking for ways to improve their processes to gain budget savings. This study will debate on the development, comprehension and rationalization of version control system (VCS) usage at Finnish Aalto University. The applied research methodology is a multiple case study analysis. The study has been conducted during a VCS project, which aimed to clarify the usage of VCS at Aalto University by providing a centrally managed system instead of multiple systems which are currently used among the departments of Aalto University. Objective of the study is to examine the possibility to substitute current systems to a one, centrally managed system and clarify the steps important to a VCS acquisition project and suggest improvements to the process of the project. The project itself was conducted at the premises of Aalto University from 2015 to 2016. The most important result is that the reduction of overlapping systems will significantly improve the usage of the system and the local support provided for the system. At the same time, reduction will also offer a possibility to focus on the development of systems instead of just focusing on administrating multiple systems.

KEYWORDS: Case study, Version control system, Acquisition, Rationalization

REFERENCES:

[1] Rochkind, M. J. (1975). The source code control system. IEEE Transactions on Software Engineer-ing, (4), 364-370.

[2] Sink, E. (2011). Version control by example. Pyrenean Gold Press.

[3] Lähteenmäki, I. (2015). Preliminary report on version control system. (Internal report). Espoo: Aalto University.

[4] Yin, R. K. (2009). Case study research: Design and methods (4th ed ed.). Thousand Oaks (Calif.): Sage Publications.

[5] Pritchard, C. L., & PMP, P. (2014). Risk management: Concepts and guidance. CRC Press.

[6] Ministry of Defence, Finland (2011). 'KATAKRI, National Security Auditing Criteria. Version II,' 2011.

[7] Ministry of Finance, Finland (online). The first version of the structural VAHTI-website. https://www.vahtiohje.fi/web/guest/home

[8] Ministry of Justice, Finland (2010). “Government Decree on information security in central government.”

[9] Trivedi, P., & Sharma, A. (2013). A comparative study between iterative waterfall and incremental software development life cycle model for optimizing the resources using computer simulation. 2nd International Conference on Information Management in the Knowledge Economy (IMKE), pp. 188-194.

[10] Myers, G. J., Sandler, C., & Badgett, T. (2011). The art of software testing John Wiley & Sons.

[11] Nielsen, J. (1994). Usability inspection methods. Conference Companion on Human Factors in Computing Systems, 413-414.

[12] Nielsen, J. (March, 2000). Why you only need to test with 5 users. Retrieved from https://www.nngroup.com/articles/why-youonly-need-to-test-with-5-users/

[13] Hutcheson, M. L. (2003). Software testing fundamentals: Methods and metrics John Wiley & Sons.

WSEAS Transactions on Computers, ISSN / E-ISSN: 1109-2750 / 2224-2872, Volume 16, 2017, Art. #6, pp. 51-62


Copyright © 2017 Author(s) retain the copyright of this article. This article is published under the terms of the Creative Commons Attribution License 4.0

Bulletin Board

Currently:

The editorial board is accepting papers.


WSEAS Main Site