Laajan toiminnallisuuskokonaisuuden lisääminen moniasiakassovellukseen
Jaakkola, Joonatan (2026)
2026
Tietotekniikan DI-ohjelma - Master's Programme in Information Technology
Informaatioteknologian ja viestinnän tiedekunta - Faculty of Information Technology and Communication Sciences
Hyväksymispäivämäärä
2026-07-23
Julkaisun pysyvä osoite on
https://urn.fi/URN:NBN:fi:tuni-202607238413
https://urn.fi/URN:NBN:fi:tuni-202607238413
Tiivistelmä
According to the software life-cycle model, the software that is meant to be evolving must be constantly changing, otherwise it will be heading towards phaseout phase. The change in this context means responding to users’ needs. One example of how this can be achieved is by expanding software with a large feature set.
Software development and delivery have both changed over the years. Agile models have gained ground in software development as well as delivery-related DevOps philosophy. Software hosting has moved from on-premises servers into cloud environments. Under SaaS-principles, customers’ responsibility is only using the software and paying a fee. Software providers can offer software as multi-tenant software, meaning that all customers using the software use a single deployment but have their own isolated instances.
The theoretical basis is established in the first chapters of the thesis. This study focuses on specific software developed using Domain-Driven Design principles. It will be examined from the perspective of a small IT enterprise. The software has two installations, and both are multi-tenant. One of them is administered by another enterprise. New features were needed only for one installation. The feature set could have been implemented into a new system, but because of life cycle thinking and future potential, it was decided to be done as an extension.
The feature set contains functionalities related to facilities and other associated properties. The needed feature set is defined in Chapter 4. After that, the content of the feature set is compared to existing functionalities, detailing how the new features were integrated into the current architecture. A significant part of the work was features that extended multi-tenant architecture by allowing content of tenancies to be managed simultaneously by the system dministrator. These needed to be implemented carefully because ensuring data isolation to prevent leakage between tenancies is critical.
The development process for this project was agile. It was adapted to function for the context of a small enterprise and two-person development team. Important parts were consistent customer meetings and demonstrating features via a separate staging environment despite infrequent merges into the master branch. The whole process is described in the final sections of the thesis, concluding with a reflection on both the technical choices and the process itself.
Software development and delivery have both changed over the years. Agile models have gained ground in software development as well as delivery-related DevOps philosophy. Software hosting has moved from on-premises servers into cloud environments. Under SaaS-principles, customers’ responsibility is only using the software and paying a fee. Software providers can offer software as multi-tenant software, meaning that all customers using the software use a single deployment but have their own isolated instances.
The theoretical basis is established in the first chapters of the thesis. This study focuses on specific software developed using Domain-Driven Design principles. It will be examined from the perspective of a small IT enterprise. The software has two installations, and both are multi-tenant. One of them is administered by another enterprise. New features were needed only for one installation. The feature set could have been implemented into a new system, but because of life cycle thinking and future potential, it was decided to be done as an extension.
The feature set contains functionalities related to facilities and other associated properties. The needed feature set is defined in Chapter 4. After that, the content of the feature set is compared to existing functionalities, detailing how the new features were integrated into the current architecture. A significant part of the work was features that extended multi-tenant architecture by allowing content of tenancies to be managed simultaneously by the system dministrator. These needed to be implemented carefully because ensuring data isolation to prevent leakage between tenancies is critical.
The development process for this project was agile. It was adapted to function for the context of a small enterprise and two-person development team. Important parts were consistent customer meetings and demonstrating features via a separate staging environment despite infrequent merges into the master branch. The whole process is described in the final sections of the thesis, concluding with a reflection on both the technical choices and the process itself.