Abstract
Software as a Service (SaaS) providers can serve thousands of customers, which have hundreds of thousands of overlapping requirements, using a single application instance to offer service at a lower price. Even with a potentially large number of customers with varying requirements, a multitenant application should make co-tenancy transparent to the tenants, which means that every tenant must appear to be the sole owner of the application, to achieve this, a highly configurable multitenant solution is needed. In this paper, we analyze variation in multiple tenants' requirements, to propose a classification for multitenant application requirements, and implement variability realization techniques depending on requirement levels. Furthermore, we prioritize the tenants' requirements to satisfy as many customer requirements as possible, and provide key guidelines to software architects and developers to implement a configuration layer in a multi-tenancy architecture.
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Disclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.