Raportointisovelluksen Laajentaminen - case: Kulku www-sovellus

Opinnäytetyön tavoitteena on tutkia www-sovelluksen laajentamista sovellukselle, jonka nimi on ”Kulku”. Kehitysprosessin aikana ilmeni erilaisia ongelmia, joita me hyödynsimme tutkiessamme uusia ratkaisuja järjestelmän rakennemallin parantamista varten. Työssä kyseenalaistettiin laajennuksen pääongelmaa. Projektin toimeksiantajana oli Suomen It-ratkaisut Oy, suomalainen moniosaaja yritys, joka keskittyy tietotekniikkaan ja tietoteknisiin palveluihin. Työn aikana kuvattiin yrityksen toimintatapoja ja, sitä miten yrityksen vaikutus näkyi työprosessissa. Tuloksena saimme selville, miten suunnitelma toteutui käytännössä, mitä ongelmia siinä oli ja mitä opimme informaation kulun ongelmista monen ohjelmiston välillä. Laajennuksen pääongelmaksi osoittautui standardin puute. Emme keksineet ratkaisua standardin puutteeseen, mutta pystyimme olettamaan, että mitä hyviä ja huonoja puolia standardin luomisesta syntyisi.The purpose of this thesis is to investigate the creation process of the extension for a www application made by Suomen It-ratkaisut Ltd: a Finnish multi-talented company which focuses on IT and IT services. The thesis goes through the development process of a www application extension dubbed “Kulku”. The process was described step by step from planning to completion while also describing the work environment within the development team and the company. The problems were mostly project-specific thus they were iterated upon during the development. The project was developed with a team of two people. I was the main developer and the second developer was the project owner itself. The program was left on the backburner by the project owner and I was instructed to develop a better solution for the reporting extension’s system. During this development period I designed a system that was practically an untangled version of the old system thanks to the reduced amount of repetition. During this design process I started noticing how the underlying cause for the reporting system’s existence might have been due to the lack of standardization of data handling within different companies. Even though the main cause for the reporting extension’s existence was revealed, the research for it proved inconclusive. The development was unorthodox thanks to the development team setup, but it did not hinder the project due to it being akin to a collaboration project in practice. During the system design we noticed that separation of concerns and reduction of repetition caused increased efficiency every time it was applied to the processes of the system. Separation of concerns made it easier for the developers to work with the project and reduction of repetition made the system more stable and modular. Even though we learned that the reason for the extension’s existence was more complicated than anticipated, we currently have no real answer for it, but we believe there is something that could be changed in the future