Modern business applications are getting increasingly distributed as multi-tenant software as a service (SaaS). This leads to new challenges in terms of quality assurance, because all customers are directly affected by software changes. The resulting problem is to proactively determinate evolutionary effects. Because SaaS applications are often realized in the sense of a software product line, this thesis examines ways of using feature models to face the mentioned problem. For this purpose, two approaches are analyzed: extended feature models with quality attributes annotated per feature and the analysis of structural aspects of feature models and corresponding concrete configurations. The presented attributed feature model approach measures the quality of concrete configurations to make configurations comparable according to specific quality goals. Criteria are elicited for when configurations can be compared to draw helpful conclusions. The structural approach focuses economic questions that are quality assurance related, such as identifying features that none of the tenants selected in their application configurations. Furthermore, three algorithms are presented that demonstrate the structural analysis approach to gather information relevant to quality assurance.

Made available in DSpace on 2017-07-21T14:19:26Z (GMT). No. of bitstreams: 1 Giuvane Conti.pdf: 4640595 bytes, checksum: 144683112870e74bdbcd0335c9aac15a (MD5) Previous issue date: 2015-10-29 / Coordenação de Aperfeiçoamento de Pessoal de Nível Superior / The growth of the smartphone market, combined with the technologies used in these devices, motivates the use of this equipment in field applications because of its georeferencing potential and internet access. In cloud computing, a prominent concept is the Internet of Things (IoT) due to the exponential growth of data where are generated in day-to-day. The idea of centralization of this data, acquired from various areas, such as agriculture, urban mobility, urbanization, government, health, business, etc., are current challenges that the IoT find out to solve. It still in contrast, NoSQL databases, which have some differentiating features from relational models and they have the potential to solve some of these challenges, such as horizontal growth, high data availability and easy storage of complex structures. Another promising technology to solve some of these challenges is the RESTful, a web service that provides faster and works with fewer bytes than the communication with Simple Object Access Protocol (SOAP). In this context, this research was developed with the goal of creating a GIS Mobile application, to collect geospatial data (points, lines and polygons) and store them in an application server, in Software as a Service (SaaS) architecture, using RESTful and NoSQL. The structure follows the concept of IoT, with high potential for integration data from different areas, such as in this study. In this research were performed tests in field at the Fazenda Escola Capão-da-onça (FESCON) on 11 and 13 August 2015. A planning missions, has been pre - set to get the best results from Global Positioning System (GPS). On those dates were collected geo data on crop plots, lines and points of interest, such as erosion areas, failures in the soil and low productivity areas. The samples taken were successful and had no problems or failures, that is, the application provided facility of use and synchronization of the data with the application server. The results of the field surveys, have been exported to files in KML format and presented on thematic maps with the help of Google Earth tool. In conclusion, the project has a high potential for registration of agricultural properties and spatial geo data and, your architecture is relevant for the development of geospatial, agricultural projects in GIS Mobile area, where need to handle complex data and provide high data availability, such as Rural environmental registry (CAR, in brazil); Precision agriculture; Georeferenced control of agricultural, natural resources and urbanization data; and Business logistics applications. / O crescimento do mercado de smartphones, combinado com as tecnologias empregadas nestes aparelhos, motiva seu uso em aplicações a campo devido ao seu potencial de georreferenciamento e acesso a internet. Em computação na nuvem, um conceito proeminente é a Internet of Things (IoT) ou Internet das Coisas devido ao crescimento exponencial de dados que são gerados no dia-a-dia. A ideia da centralização destes dados, provenientes de várias áreas, como: agricultura, mobilidade urbana, urbanização, governamentais, saúde, empresariais, etc., são desafios atuais que a Internet das Coisas procura solucionar. Destaca-se ainda, os bancos de dados NoSQL, os quais possuem potencial para solução de alguns destes desafios. Outra tecnologia promissora para solucionar alguns destes desafios é o padrão RESTful, um web service que apresenta rapidez e trabalha com quantidades reduzidas de bytes em sua comunicação. Neste contexto, esta pesquisa foi desenvolvida com o objetivo de criar um Sistema de Informação Geográfica (SIG) Móvel, que realize a coleta de dados geoespaciais (pontos, linhas e polígonos), se comunique com um servidor de aplicação, no modelo Software as a Service (SaaS) que irá armazenar os dados em um banco de dados MongoDB e sua arquitetura segue o conceito de Internet das Coisas. Foram realizados testes a campo na Fazenda Escola Capão-da-onça (FESCON) nos dias 11 e 13 de agosto de 2015. Um planejamento de missões, foi pré - estabelecido, para obter os melhores resultados do Sistema de Posicionamento Global (GPS). Nas referidas datas foram coletados polígonos em talhões de culturas, linhas e pontos de interesse, tais como áreas de erosão, falhas no solo e áreas de baixa produtividade. As coletas realizadas foram bem sucedidas, o aplicativo proporcionou facilidade de uso e de sincronismo dos dados com o servidor de aplicação. Os resultados, dos levantamentos à campo, foram exportados para arquivos no formato KML e apresentados em mapas, com auxílio da ferramenta Google Earth. Conclui-se que, o projeto apresenta alto potencial de uso para cadastro de propriedades agrícolas e dados espacializados e, sua arquitetura é pertinente para o desenvolvimento de projetos geoespaciais, agrícolas em SIG Móvel, que necessitem tratar dados complexos e apresentem alta disponibilidade de dados, tais como: Cadastro Ambiental Rural (CAR); Agricultura de precisão; Controle georreferenciado de dados agrícolas, recursos naturais e urbanização; e Aplicações empresariais de logística.

An increasing amount of companies and organizations are starting to implement the use of cloud computing in their business. This trend results in that software, which was previously sold and distributed to the customers whom then had to install the software on their own computers, now is being replaced with Software as a Service (SaaS). SaaS makes software available through the customers’ browsers, which results in that the service providers only have to administer a single application. The process to migrate a distributed application to a service delivered as a SaaS lacks sufficient investigation; this paper will provide some guidelines for conducting such a pro- cess. During the work on this paper, a prototype of a service delivered as a SaaS has been devel- oped with the intention to test, among other things, how a distributed relational database can be converted to a key/value pair storage. A conversion of this kind enables data to be stored locally in the customers’ browsers, which relieves some pressure on the server as well as enables the application to be used in offline-mode. The paper results in three guidelines which should be considered when planning to migrate software to a service delivered as a SaaS with a local data- base; Think before you act, Don’t expose your soul and Size matters. These guidelines describe how a migration process should be planned, when an application is not deemed appropriate to migrate and when a conversion of the database is not appropriate. / Allt fler företag och organisationer börjar implementera användandet av olika molntjänster i sin verksamhet. Den här trenden medför att programvaror, som tidigare sålts och distribuerats till kunder vilka sedan själva får installera dem på sina egna datorer, nu börjar ersättas med en Soft- ware as a Service (SaaS). Det innebär att programvaran istället finns tillgänglig på Internet via kundernas webbläsare, något som medför att tjänsteleverantören enbart behöver administrera en enda programvara. Processen att migrera en distribuerad programvara till en SaaS-tjänst saknar ordentlig utredning, det här arbetet syftar därför till att ta fram några vägledande riktlinjer för en sådan process. Under arbetets gång har en prototyp av en SaaS-tjänst utvecklats med syfte att testa bland annat hur en tidigare distribuerad relationsdatabas kan konverteras till nyckel/värde- par. En sådan konvertering möjliggör lokal lagring av data i kundernas webbläsare, vilket mins- kar belastningen på servern samt erbjuder möjligheten att arbeta offline. Arbetet resulterar i tre riktlinjer att beakta då en migration till en SaaS-tjänst med lokal databas planeras; Tänk efter, före, Blotta inte din själ och Storleken har betydelse. Riktlinjerna beskriver hur en migrations- process bör planeras, när en applikation inte anses lämplig att migrera samt när en konvertering av databasen inte anses lämplig.

Många företag idag använder molnet som en del i deras systemarkitektur. Det har blivit allt vanligare att verksamheter flyttar sina applikationer till molnet som gör det möjligt att nå både information och applikationer över internet. Det finns flera olika sätt att använda sig utav molntjänster. Verksamheter kan själva ta hand om infrastrukturen och själva införskaffa den hårdvara som krävs för att driva verksamhetens applikationer och göra det möjligt att nå applikationer och informationssystem över internet. Det finns också möjlighet att hyra en plats i stora datacenter från en tredjepartsleverantör, vilket också kallas för det publika molnet. Att hyra en plats i det publika molnet är fördelaktigt av många anledningar, bara genom att få tillgång till flera datacenter världen över till en låg kostnad är en av dem. En annan är att kunna utnyttja den prestanda som finns i det publika molnet utan att själv behöva göra några investeringar i hårdvara eller infrastruktur. Att själv investera i den infrastruktur som krävs för att ha ett moln med datacenter över hela världen skulle vara väldigt kostsamt för en verksamhet. Det är då mycket kostnadseffektivare att hyra in sig i en tredjepartsleverantörs datacenter. Detta innebär dock att verksamheten måste anpassa sig tredjepartsleverantören samt att den information och de applikationer som verksamheten har hamnar i samma datacenter som andra verksamheters. Den här studien ser närmare på de funktioner i molntjänster som tredjepartsleverantörer kan leverera samt vilka fördelar det kan föra med sig vid utveckling av informationssystem. Studien syftar till att följa upp på verksamheter som under en tid använt sig av molntjänster från en tredjepartsleverantör för att sedan låta dem beskriva vilka fördelar de upplevt. För att genomföra studien har intervjuer med personer som under en längre tid arbetat med molntjänster som levererats av en tredepartsleverantör. Även tidigare forskning på ämnet har studerats. Sedan har även en analys sammanställt den insamlade empirin för att skapa sig en bild över hur relationerna mellan teknikens funktioner och fördelar påverkat arbetet med utveckling av informationssystem. Detta leder fram till en slutsats som presenterar de fördelar samt det resultat som verksamheter kan förvänta sig för utveckling av informationssystem genom användning av en publik molnarkitektur från en tredjepartsleverantör. Den här studien visar att funktioner inom publika moln kan på flera sätt förbättra utvecklingsprocessen för informationssystem. Tekniken kan bidra med funktioner som kan korta ner tiden det tar att sätta upp testmiljöer samt att få applikationer i drift. Det kan också leda till sänkta kostnader genom en fördelaktig pay-as-you-go modell men kan även leda till en inlåsningseffekt mot tredjepartsleverantören. / Many companies today are using the cloud as part of their system architecture. It has become increasingly common for businesses to move their applications to the cloud which makes it possible to access both information and applications over the internet. There are several ways to use cloud services. Businesses can acquire the necessary infrastructure and hardware required to run their applications and make it possible to reach the applications over the internet. There is also the option to rent space in data centers from a third-party provider. This is also referred to as the public cloud. Renting space in the public cloud is beneficial for many reasons as you can get access to multiple data centers worldwide at a low cost. It is also possible to take advantage of the performance of the cloud available if needed without making any investment in hardware or infrastructure. If a business would invest in the infrastructure required to run their own cloud in data centers all over the world it would be very expensive. It is a lot cheaper to rent space in a third-party provider's data center. However, this means that the business must accept the third-party provider’s terms. The information and applications that the business have in the third-party provider’s data centers will be stored together with other clients. In this study we look at the functions of cloud services that third-party providers have to offer and what benefits it can bring for development of information systems. This study aims to follow up on businesses that have used cloud services from a third party and then have them describe what benefits they experienced from using the technology. To conduct this study interviews have been done with people with lots of experience working with public cloud services from third-party providers. Previous research on the topic have also been studied. An analysis compiled the collected empirical data to create an overview of the relations between the technology and how it can benefit and affect the process for development of information systems. This leads to a conclusion that present how an organization's processes for developing information systems may be affected by the acquisition of public cloud services from third party suppliers. This study shows that functions in the public clouds can significantly improve the development process of information systems. It can provide functions and benefits that can reduce the time it takes to set up a test-environment and also shorten the time it takes to implement applications. It may also lead to reduced costs due to its beneficial pay-as-you-go model but may create a locked-in-effect to the third-party provider.

This thesis is devoted to the modern management concept of Corporate Performance Management (CPM, enterprise performance management) and its implementation in selected small company. The first part focuses on the description of the concept of CPM and its individual components (processes, methodologies, metrics and applications). The theoretical part also deals with selected implementation procedures and available CPM maturity models. In the second part a particular small company is introduced to the reader, together with its activities, organizational structure and the reasons behind their interest in CPM. It is then followed by an analysis of the company, its CPM maturity and proposed steps for CPM implementation. These steps are based on the framework presented in this work, which was created by combining different approaches to CPM implementation and available CPM maturity model. The third part, devoted to the implementation of CPM, starts with an analysis of the CPM in the cloud market, followed by a review of two selected solutions. To select the appropriate application, a multi-criterion model is created. The description of actual implementation, and evaluation of its results are included in the last chapter.

Modern business applications are getting increasingly distributed as multi-tenant software as a service (SaaS). This leads to new challenges in terms of quality assurance, because all customers are directly affected by software changes. The resulting problem is to proactively determinate evolutionary effects. Because SaaS applications are often realized in the sense of a software product line, this thesis examines ways of using feature models to face the mentioned problem. For this purpose, two approaches are analyzed: extended feature models with quality attributes annotated per feature and the analysis of structural aspects of feature models and corresponding concrete configurations. The presented attributed feature model approach measures the quality of concrete configurations to make configurations comparable according to specific quality goals. Criteria are elicited for when configurations can be compared to draw helpful conclusions. The structural approach focuses economic questions that are quality assurance related, such as identifying features that none of the tenants selected in their application configurations. Furthermore, three algorithms are presented that demonstrate the structural analysis approach to gather information relevant to quality assurance.

One of the most important attribute a cloud service provider (CSP) offers their customers through their cloud services is scalability. Scalability gives customers the ability to vary the amount of capacity when required. A cloud service can be divided in three service layers, Infrastructure-as-a-Service (IaaS), Platform-as-a-Service (PaaS) and Software-as-a-Service (SaaS). Scalability of a certain service depends on software licenses on these layers. When a customer wants to increase the capacity it will be determined by the CSP's licenses bought from its suppliers in advance. If a CSP scales up more than what was agreed on, then there is a risk that the CSP needs to pay a penalty fee to the supplier. If the CSP invests in too many licenses that does not get utilized, then it will be an investment loss. A second challenge with software licensing is when a customer outsources their applications to the CSP’s platform. As each application comes with a set of licenses, there is a certain level of scalability that cannot be exceeded. If a customer wants the CSP scale up more than usual for an application then the customer need to inform the vendors. However, a common misunderstanding is that the customer expects the CSP to notify the vendor. Then there is a risk that the vendor never gets notified and the customer is in danger of paying a penalty fee. This in turn hurts the CSP’s relationship with the customer. The recommendation to the CSP under study is to create a successful customer relationship management (CRM) and a supplier relationship management (SRM). By creating a CRM with the customer will minimize the occurring misunderstandings and highlight the responsibilities when a customer outsources an application to the CSP. By creating a SRM with the supplier will help the CSP to maintain a flexible paying method that they have with a certain supplier. Furthermore, it will set an example to the remaining suppliers to change their inflexible paying method. By achieving a flexible payment method with the suppliers will make it easier for the CSP to find equilibrium between scalability and licenses. / Ett av de viktigaste attributen en molnleverantör (CSP) erbjuder sina kunder genom sina molntjänster är skalbarhet. Skalbarheten ger kunden möjligheten att variera mängden kapacitet efter behov. En molntjänst kan delas in i tre serviceskikter, Infrastruktur-as-a-Service (IaaS), Platform-as-a-Service (PaaS) och Software-as-a-Service (SaaS). Skalbarheten av en viss service beror på mjukvarulicenser på dessa skikt. När en kund vill öka kapaciteten bestäms detta av CSP:s förhandsköpta licenser från sina leverantörer. Om en CSP skalar upp mer än vad som avtalats, finns det en risk att CSP:n måste betala en straffavgift till leverantören. Investerar CSP i alltför många licenser som inte utnyttjas, blir det en investeringsförlust. En annan utmaning med mjukvarulicenser uppstår när en kund lägger ut sina applikationer på CSP:s plattform. Eftersom varje applikation levereras med en uppsättning av licenser, finns det en bestämd nivå av skalbarhet som inte kan överskridas. Om en kund vill att CSP:n ska skala upp mer än vanligt för en applikation, måste kunden informera applikationsförsäljaren själv. Dock sker det en missuppfattning då kunden förväntar sig att CSP:n ska meddela säljaren om detta. Det finns en risk att säljaren aldrig blir informerad och kunden hamnar i stor risk för att betala en straffavgift. Detta i sin tur skadar CSP:s relation med kunden. Rekommendationen till CSP:n är att skapa en framgångsrik kundrelationshantering (CRM) och leverantörrelationshantering (SRM). Genom att skapa en CRM med kunden kan förekommande missförstånd minimeras och belysa ansvarsområden som råder när en kund lägger ut sin applikation hos CSP:n. Genom att skapa en SRM med leverantörerna kommer det att hjälpa CSP:n att upprätthålla en flexibel betalmetod som de har med en viss leverantör. Dessutom kommer det att vara ett föredöme för de övriga leverantörerna att ändra sin icke flexibla betalningsmetod. Genom att uppnå en mer flexibel betalningsmetod med leverantörerna kommer det att bli enklare för en CSP att hitta en balans mellan skalbarhet och licenser.

Cloud Computing is becoming increasingly popular, with large amounts of corporations revenue coming in from various cloud solutions offered to customers. When it comes to choosing a solution, multiple options exist for the same problem from many competitors. This report focuses on the ones offered by Microsoft in their Azure platform, and compares the architectures in terms of performance and scalability.In order to determine the most suitable architecture, three offered by Azure are considered: Cloud Services (CS), Service Fabric Mesh (SFM) and Virtual Machines (VM). By developing and deploying a REST Web API to each service and performing a load test, average response times in milliseconds are measured and compared. To determine scalability, the point at which each service starts timing out requests is identified. The services are tested both by scaling up, by increasing the power of a single instance of a machine, and by scaling out, if possible, by duplicating instances of machines running in parallel.The results show that VMs fall considerably behind both CS and SFM in both performance and scalability, for a regular use case. For low amounts of requests, all services perform about the same, but as soon as the requests increase, it is clear that both SFM and CS outperform VMs. In the end, CS comes ahead both in terms of scalability and performance.Further research may be done into other platforms which offer the same service solutions, such as Amazon Web Services (AWS) and Google Cloud, or other architectures within Azure. / Molntjänster blir alltmer populära i dagens industri, där stora mängder av företagens omsättning består av tjänster erbjudna i form av molnlösningar. När det kommer till att välja en lösning finns många för samma problem, där det är upp till kunden att välja vilken som passar bäst. Denna rapport fokuserar på tjänster erbjudna av Microsofts Azure plattform, i en jämförelse av arkitekturer som belastningstestas för att mäta prestanda och skalbarhet.För att avgöra vilken arkitektur som är optimalast mäts tre olika tjänster erbjudna i Azure: Cloud Services (CS), Service Fabric Mesh (SFM) och Virtual Machines (VM). Detta görs genom att utveckla och deploya ett REST Web API som är simulerat med användare, där prestanda mäts genom att ta medelresponstiden i millisekunder per anrop. För att avgöra skalbarhet identifieras en punkt där tjänsten inte längre klarar av antalet inkommande anrop och börjar returnera felkoder. Maskinerna för varje tjänst testas både genom att skala upp, genom att förstärka en maskin, men även genom att skala ut, där det skapas flera instanser av samma maskin.Resultatet visar att Virtual Machines hamnar betydligt efter både CS och SFM i både prestanda och skalbarhet för ett vanligt användarfall. För låga mängder anrop ligger samtliga tjänster väldigt lika, men så fort anropen börjar öka så märks det tydligt att SFM och CS presterar bättre än Virtual Machines. I slutändan ligger CS i framkant, både i form av prestanda och skalbarhet.Vidare undersökning kan göras för de olika plattformarna erbjudna av konkurrenter, så som Amazon Web Services (AWS) och Google Cloud, samt andra arkitekturer från Azure.

One of the single biggest challenges for start-ups is to find the necessary funding to achieve growth. Software-as-a-service (SaaS) companies are no different and rely on seed stage investments to build and develop a service in order to acquire paying customers. Given the need of external investments, SaaS companies heavily depend on their valuation for each given investor. The purpose of this study was to investigate the main value determinants for seed stage SaaS company valuations. Hence, the research question at issue was “What are the main value determinants for seed stage SaaS company valuations?”. This study was delimited to seed stage SaaS companies with a business to business (B2B) service offering in Sweden. This qualitative research was carried out through semi-structured in-depth interviews with seed stage SaaS B2B founders and investors operating in Sweden. The primary results of the qualitative research show that the main value determinants can be divided into three main factors. Firstly, external factors, such as the region, industry, and market that the company is operating within. Secondly, company factors include team and founder characteristics, firm characteristics, SaaS metrics and financials, and partnership and alliances. Thirdly, investor factors, including investor type as well as reputation and value-add. Following the findings, similarities and differences with literature were discussed. Based on the results, a revised framework including the main value determinants for seed stage SaaS company valuation was developed. The conclusion of this study is that seed stage SaaS company valuations vary among investor types. The valuation tends to not be bound to a specific valuation method, but rather a process where an overall evaluation is made from a set of criteria, which leads up to the valuation process where the final valuation is set. / En av de största utmaningarna för nystartade företag är att genomföra extern kapitalanskaffning för att uppnå tillväxt. Det gäller även för SaaS-företag (Software-as-a-service) vilka är beroende av investeringar i seed stage (fröstadiet) för att bygga upp och utveckla tjänster för att erhålla betalande kunder. Givet behovet av externa investeringar är SaaS-företag starkt beroende av dess värdering från investerare. Syftet med denna studie var att undersöka de viktigaste värdedeterminanterna för värdering av SaaS-bolag i seed stage. Forskningsfrågan var således "Vilka är de viktigaste värdedeterminanterna för värderingar av SaaS-företag i seed stage?". Studien avgränsades till SaaS-företag som erbjuder B2B-tjänster i Sverige. Denna kvalitativa studie genomfördes genom semistrukturerade intervjuer med seed stage SaaS B2B-grundare och investerare som är verksamma i Sverige. De övergripande resultaten visar att de viktigaste värdedeterminanterna kan delas in i tre huvudfaktorer: externa faktorer, företagsfaktorer, och investerarfaktorer. Externa faktorer avser region, bransch, och marknad inom vilka företaget är verksamt. Företagsfaktorer inkluderar teamet och grundarnas egenskaper, företagets egenskaper, SaaS-mått och finansiella data, samt partnerskap och allianser. Investerarfaktorer avser typen av investerare samt investerarens rykte och mervärde. Utfallet från intervjuerna jämfördes med resultat från tidigare litteratur. Baserat på intervjuresultaten utvecklades ett reviderat ramverk med de viktigaste värdedeterminanterna för värdering av SaaS-bolag i seed stage. Slutsatsen av denna studie är att värdering av SaaS-företag i seed stage varierar mellan olika investerartyper. Värderingen tenderar att inte vara bunden till en specifik värderingsmetod, utan en process där en övergripande utvärdering görs baserat på en uppsättning av kriterier, vilket resulterar i en slutgiltig värdering.

近年來雲端運算蓬勃發展，為資訊系統的建置與服務帶來巨大的改變，其中一個重要趨勢為軟體即服務，並透過多租戶共享資源達到降低成本的優勢。因此如何讓服務可以共享資源，又能兼顧各租戶的客製化需求，這將會是軟體即服務關鍵成功因素。 為了讓租戶客製化自己的綱要，在多租戶的相關研究中，發展出各種綱要映射技術，各適用不同的狀況，但在開發應用程式時候往往無法預估租戶適合使用何種綱要映射技術。本研究提出可以讓多租戶軟體框架具有綱要映射技術的可調性，應用程式開發時候毋需考慮使用何種綱要映射技術，等租用時候再依據應用程式及租戶的特性決定。本研究將以小量租戶效能最佳的Private Table Layout與適合用於大量租戶的Universal Table Layout為例，提出的可調性多租戶實體模式來建構具有可調性的多租戶軟體框架。此外本研究提出的軟體框架經過技術的封裝，開發者不需要了解多租戶的相關技術，就能完成多租戶應用程式的開發。 / Software as a service (SaaS) is an emerging service model of cloud computing. It’s central defining characteristic is the ability for clients to use a software application on a pay-as-you-go subscription basis. However, to be economically sustainable, a SaaS application must leverage resource sharing to a large degree by accommodating different clients of the application while making it appear to each that they have the application all to themselves. In other words, a SaaS application must be a multi-tenant application. An important multi-tenant research topic is the various kinds of schema mapping technology have been developed in order for our tenants to customize their schema. However, it is hard to determine tenants’ need for particular schema mapping technology in different circumstances. This thesis proposes an adaptable schema mapping technology for a multi-tenant application (MTA) framework. The application and tenants’ characteristics do not need to be considered while applications developers are developing their schema mapping technology. This approach will take examples from the Private Table Layout mapping and the Universal Table Layout mapping to illustrate the features of this adaptable multi-tenant software framework. Furthermore, this thesis argues that, with the approach packaged as a software framework, developers are able to complete the development of a multi-tenant application without full understanding of the underlying technologies.