本文選題：PaaS + SaaS��； 參考：《山東大學(xué)》2014年碩士論文

【摘要】：隨著云計(jì)算的興起,軟件的交付與使用模式正在發(fā)生著變化。作為云計(jì)算的一部分,PaaS平臺(tái)為SaaS應(yīng)用提供完整的開(kāi)發(fā)、部署及運(yùn)行環(huán)境。租戶通過(guò)PaaS平臺(tái)租用自己所需的SaaS應(yīng)用,而且無(wú)需購(gòu)買(mǎi)硬件設(shè)備和進(jìn)行軟硬件的維護(hù)。在一個(gè)開(kāi)放式的電子商務(wù)PaaS平臺(tái)上會(huì)存在大量的SaaS應(yīng)用以供租戶使用。在這止匕SaaS應(yīng)用中,有很多應(yīng)用具有相似或相同的功能,例如,很多在線網(wǎng)店都會(huì)具有搜索商品的功能。根據(jù)軟件工程中基于構(gòu)件的軟件開(kāi)發(fā)的原則,我們可以對(duì)這些“功能”進(jìn)行復(fù)用,因此,本文將致力于研究在開(kāi)放的電子商務(wù)PaaS平臺(tái)上進(jìn)行基于構(gòu)件的SaaS應(yīng)用構(gòu)建的問(wèn)題研究。在PaaS平臺(tái)中進(jìn)行基于構(gòu)件的SaaS應(yīng)用構(gòu)建所涉及到的幾個(gè)主要問(wèn)題。第一,如何將可復(fù)用構(gòu)件機(jī)制有機(jī)整合到PaaS平臺(tái)上?第二,如何在PaaS平臺(tái)上對(duì)構(gòu)件進(jìn)行管理?第三,針對(duì)SaaS應(yīng)用的多租戶特性,如何綁定構(gòu)件才能更好的滿足不同租戶的SLA協(xié)議? 在本文中,為了解決在PaaS平臺(tái)中進(jìn)行基于構(gòu)件的SaaS應(yīng)用構(gòu)建所涉及到的幾個(gè)主要問(wèn)題,我們主要進(jìn)行了一下工作。首先,為了將可復(fù)用構(gòu)件機(jī)制整合到PaaS平臺(tái)中,本文提出了一種加強(qiáng)型的電子商務(wù)PaaS平臺(tái),即在PaaS平臺(tái)上增加了一層構(gòu)件層。構(gòu)件層負(fù)責(zé)構(gòu)件的存儲(chǔ)和調(diào)用。其次,為了更好的管理構(gòu)件開(kāi)發(fā)商所提交的大量構(gòu)件和方便以后SaaS應(yīng)用開(kāi)發(fā)商檢索自己所需的構(gòu)件,本文提出了抽象構(gòu)件的概念。抽象構(gòu)件是對(duì)具有相似功能的構(gòu)件的概括,它只涉及構(gòu)件的抽象描述而沒(méi)有具體實(shí)現(xiàn)。通過(guò)抽象構(gòu)件與實(shí)體構(gòu)件之間的相似度,我們將具有相似功能的構(gòu)件聚類(lèi)到同一個(gè)抽象構(gòu)件之下。最后,不同租戶往往會(huì)與SaaS應(yīng)用提供商簽訂不同的SLA協(xié)議,在SLA協(xié)議租戶指明自己所需要應(yīng)用提供的服務(wù)質(zhì)量。為了能夠滿足多租戶的不同SLA請(qǐng)求,本文提出了構(gòu)件的后期綁定策略,即在租戶與SaaS應(yīng)用提供商簽訂SLA協(xié)議之后根據(jù)其中的租戶請(qǐng)求,選取合適的構(gòu)件進(jìn)行調(diào)用。在所有滿足SaaS應(yīng)用提供商的功能性要求的構(gòu)件中選取一個(gè)滿足租戶SLA請(qǐng)求的構(gòu)件需要綜合考慮構(gòu)件的多個(gè)QoS屬性,即從多個(gè)QoS目標(biāo)中選取一個(gè)最適合的構(gòu)件供租戶使用。SaaS提供商位于構(gòu)件提供商與應(yīng)用租戶之間,不僅需要考慮滿足租戶的請(qǐng)求還要考慮如何使得自己的利益最大化。我們綜合考慮了在構(gòu)件中在存在滿足租戶請(qǐng)求和不存在構(gòu)件滿足租戶請(qǐng)求的兩種情況,如何選取合適的構(gòu)件調(diào)用。 本文最后進(jìn)行了實(shí)驗(yàn)?zāi)M,通過(guò)模擬實(shí)驗(yàn)來(lái)驗(yàn)證了基于抽象構(gòu)件模型的構(gòu)件管理和基于SLA的構(gòu)件后期綁定的可行性。
[Abstract]:With the rise of cloud computing, software delivery and usage patterns are changing. As a part of cloud computing, PaaS platform provides a complete development, deployment and running environment for SaaS applications. Tenants rent their own SaaS applications through PaaS platform, and do not need to purchase hardware equipment and software and hardware maintenance. There will be a large number of SaaS applications for tenants on an open PaaS platform. In this SaaS application, many applications have similar or identical functions, for example, many online stores will have the ability to search for products. According to the principle of component-based software development in software engineering, we can reuse these "functions". Therefore, this paper will focus on the research of building component-based SaaS applications on open e-business PaaS platform. There are several main problems involved in building component-based SaaS applications on PaaS platform. First, how to integrate reusable component mechanism into PaaS platform? Second, how to manage the components on the PaaS platform? Thirdly, in view of the multi-tenant feature of SaaS applications, how to bind the components to better meet the SLA agreement of different tenants? In this paper, in order to solve the main problems involved in building component-based SaaS applications on the PaaS platform, we mainly do some work. Firstly, in order to integrate the reusable component mechanism into the PaaS platform, this paper proposes an enhanced e-business PaaS platform, in which a layer of component layer is added to the PaaS platform. Component layer is responsible for component storage and call. Secondly, in order to better manage a large number of components submitted by component developers and facilitate future SaaS application developers to retrieve their own required components, this paper proposes the concept of abstract components. Abstract component is a summary of component with similar function. It only involves abstract description of component without concrete implementation. Through the similarity between abstract component and entity component, we cluster the components with similar function into the same abstract component. Finally, different tenants often sign different SLA agreements with SaaS application providers. In order to satisfy the different SLA requests of multi-tenant, this paper proposes a post-binding policy of component, that is, after signing SLA agreement between tenant and SaaS application provider, according to the tenant request, select the appropriate component to call. Among all the components that meet the functional requirements of SaaS application providers, selecting a component that meets the SLA request of the tenant needs to take into account the multiple QoS attributes of the component. That is to choose one of the most suitable components for tenants to use. SaaS provider is located between component provider and application tenant. It is necessary to consider not only satisfying the tenant's request but also how to maximize their own interests. In this paper, we consider the two cases of satisfying tenant's request and non-existent component's satisfying tenant's request, and how to select the appropriate component call. At the end of this paper, the simulation is carried out to verify the feasibility of component management based on abstract component model and SLA-based component late binding.
【學(xué)位授予單位】：山東大學(xué)
【學(xué)位級(jí)別】：碩士
【學(xué)位授予年份】：2014
【分類(lèi)號(hào)】：TP393.09;TP311.52

【參考文獻(xiàn)】

中國(guó)期刊全文數(shù)據(jù)庫(kù) 前2條

1 張若英,邱雪松,孟洛明;SLA的表示方法和應(yīng)用[J];北京郵電大學(xué)學(xué)報(bào);2003年S2期

2 趙俊峰,王亞沙,謝冰,楊芙清;一種支持構(gòu)件服務(wù)質(zhì)量的構(gòu)件管理框架[J];電子學(xué)報(bào);2004年S1期

，

本文編號(hào)：2081926