Concern Based SaaS Application Architectural Design
With SaaS application, tenant can focus on application utilization while Independent Software Vendor (ISV) is responsible for application dep- loyment, installation, operation and maintenance. Using Aspect Oriented Soft- ware Development (AOSD), we propos
- PDF / 292,260 Bytes
- 10 Pages / 439.363 x 666.131 pts Page_size
- 18 Downloads / 205 Views
Abstract. With SaaS application, tenant can focus on application utilization while Independent Software Vendor (ISV) is responsible for application deployment, installation, operation and maintenance. Using Aspect Oriented Software Development (AOSD), we propose eight concerns, i.e. configurability, discriminator, measurement, monitoring, tenant management, billing management, performance management, and application management. Those concerns are integrated into a SaaS system architectural design, to enhance SaaS operational flexibility and maintainability. As a proof of concept, we developed a SaaS operational environment using Spring and AOP. Two Java applications have been integrated to this environment after tailoring. We have tested the modules, classes and services and then the applications, to demonstrate that the platform is able to run a set of web applications as a SaaS. Using this system, ISV can modify an existing Java application easily to be a part of SaaS and measure resource usage and monitor SaaS operation by a dashboard. Keywords: SaaS, Software as a Service, Concern, Aspect Oriented Software Development.
1
Introduction
Traditional software users are typically overburdened with operational work such as maintenance and software deployment. SaaS model is raised to overcome these problems. Many software companies start adopting this model. Instead of buying, more and more individual users and companies rent software. Software maintenance and deployment that were previously handled by users now is handled by ISV. Based on [1], [2], [3], [4], [5], [6], SaaS is a hosted software and delivered over a network on a subscription basis. SaaS operational systems could be categorized into platform centric or service provider centric [7]. ISV and tenant are two main factors of SaaS operational systems. The maturity of SaaS application is determined by tenancy, configurability, and scalability [8]. Seven pricing models for SaaS application has been studied by Kalisa [9]. Billing should be built as part of SaaS application [14]. However, this functionality must be flexible because each tenant may have a preference of its his own billing scheme. Enhancement of SaaS application design is required. Aspect oriented software development is one of the application development model to improve the structuring, reusability, and reduce the complexity of the model compared with object oriented model [10]. Linawati et al. (Eds.): ICT-EurAsia 2014, LNCS 8407, pp. 228–237, 2014. © IFIP International Federation for Information Processing 2014
Concern Based SaaS Application Architectural Design
229
Our research has studied “concerns” that should be considered to develop SaaS application based on AOSD. Separation of concern is a fundamental principle to facilitate software deployment [11]. Concern is interest which pertains to the system’s development, its operation or any other aspects that are critical or otherwise important to one or more stakeholders [12]. Core concern represents functional requirement. Cross-cutting c
Data Loading...
