Architecture guidelines for SaaS development process

© 2017 Association for Computing Machinery. Software-As-A-service (SaaS) has received significant attention from software providers and users as software delivery model. Most of the existing companies are transferring their business into SaaS model. This intensely competitive environment has imposed many challenges for SaaS developers for the development process. SaaS development is a very complex process and SaaS success depends on its architecture design and development. This paper identifies important key factors from literature and provides guidelines for SaaS developers to support these factors in SaaS architecture development process. Ultimately, it will be beneficial for SaaS developers to improve the development process of SaaS application.

Guidelines for Cloud Computing architecture: development process

Cloud computing (CC) has received significant attention from different types of businesses and Industries and emerged as a new utility for businesses activities. The philosophy behind CC shows a great potential to transform a major part of the IT industry, making computing environment and resources even more attractive as a cost-effective service and changing the way IT hardware is designed and purchased. Resulting day by day more small and medium and large enterprise are adopting different types of CC services. However, strong market competitive environment for converting existing IT services to CC environment imposed different types of challenges for the CC architect. Development of CC architect environment in any organisation is a very complex process and success depends on its proper architecture design and development according to business requirements. The aim of this paper identifies the major type of key factors from literature and provides different guidelines for organisations to support the CC architecture development process. Finally, the different types of CC services generally referred to as CC architect are explained how they all work. This paper will be helpful and provides certain guidance on situations where specific types of CC services are particularly not the best option for any organization

Desenvolvimento de vertente SaaS para produto de submissão de dados em plataformas de business intelligence

Relatório de desenvolvimento do trabalho para obtenção do Grau de Mestre em Engenharia Informática e de ComputadoresO Tableau é uma ferramenta de Business Intelligence que contém uma extensão denominada Write-Back, criada pela empresa Xpand IT, que permite a escrita dinâmica de conjuntos de dados no Tableau. Com esta dissertação, pretende-se efetuar a migração da aplicação Write-Back, que é uma aplicação on-premise, para um Software as a Service. Esta migração foi feita na plataforma da Microsoft Azure com um Azure App Service, um Azure SQL Database, um Azure Front Door e um Azure Application Insights. Efetuou-se um estudo da aplicaçãoWrite-Back on-premise atual e sobre Software as a Service (SaaS), verificando-se que são precisos assegurar 3 requisitos principais para construir uma aplicação SaaS, nomeadamente a segurança e multi-tenant, a escalabilidade e a robustez. Seguidamente, foram efetuadas algumas mudanças para assegurar uma arquitetura multi-tenant, como foi o caso da gestão dos tenants de forma dinâmica, a otimização das queries da base de dados do Write-Back e a garantia da segregação total entre os utilizadores. Por último, foram efetuados testes de desempenho na aplicação SaaS, tendo-se chegado à conclusão de que com a capacidade e da versão do servidor adquirido, a aplicação conseguirá suportar entre aproximadamente 400 e 600 interações, com um período de crescimento de 0.1 segundos.Tableau is a Business Intelligence tool that contains an extension calledWrite-Back, created by the company Xpand IT, which allows dynamic writing of datasets in Tableau. With this dissertation, we intend to migrate the Write-Back application, which is an on-premise application, to a Software as a Service. This migration was performed on the Microsoft Azure platform with an Azure App Service, an Azure SQL Database, an Azure Front Door and an Azure Application Insights. A study was carried out on the current on-premiseWrite-Back application and on Software as a Service (SaaS), verifying that it is necessary to ensure 3 main requirements to build a SaaS application, namely security and multi-tenant, scalability and robustness. Then, some changes were made to ensure a multi-tenant architecture, such as the dynamic management of tenants, the optimization of the Write-Back database queries and the guarantee of total segregation between users. Finally, performance tests were carried out on the SaaS application, reaching the conclusion that with the capacity and version of the server purchased, the application will be able to support between approximately 400 and 600 interactions, with a ramp-up period of 0.1 seconds.N/