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

Download as PDF

ABSTRACT: IT environments are a continuously changing entirety. Software and systems in these environments go through their lifecycles and then they are replaced with more advanced and economical solutions. This is a normal phenomenon in education and corporate life. The study examines if and how the different systems could be replaced with a single version control system (VCS) and how to prepare and execute an acquisition project of a new IT system. The research method is a multiple case study composed of three case studies. The findings show that users are ready to change their VCS tools to new ones, as long as they get to manage their own repositories. The departments are ready to renounce their own systems as long as the new system has all the same functions as the old systems. The reduction of the overlapping systems will also save money and the resources of the departments.

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.