# 电子工程代写|软件项目作业代写Software Project代考|CS4530

## 电子工程代写|软件项目作业代写Software Project代考|Measuring the Interaction Between Cloud Customers

Schmietendorf et al. adapted the COSMIC method for cloud system size measurement [16]. In particular, they focused on the interaction between a cloud customer and the system provided by a cloud vendor.

For the authors, the COSMIC measurement strategy is defined considering the size of a chosen part of the developed cloud system for the purpose of measurement. They provided a rich list of possible size aspects such as the size of the involved services, the interaction between them, the customers, the resources, etc.

The scope of measurement is identified as the application of a service in the cloud system based on chosen characteristics (e.g., scalability, low cost), whereas the decomposition and granularity are established at five different levels, described below. The data movement-based interactions in the different cloud system levels correspond to the functional processes.

The FURs in the scope of measurement are based on the following characteristics:

• The on-demand services that are instantiated on the cloud system are controlled by triggering events and special object of interest like costs and resources.
• The network is the channel with which services communicate as separate layers, measured by means of COSMIC Entry and Exit data movements.
• Instead, Reads and Writes measure data movements from/to persistent storage with which the resource pooling is performed.
• The elasticity factor involves functional processes of service scaling on data groups like ‘storage size’ and ‘location’ requirements.
• The measured service itself supports the functional processes based on the object of interest like billing and service level agreement (SLAs) terms.

Thus, they investigated the cloud systems defining the following five levels of functionality (see also Fig. 3.3) and their interactions [16]:

1. The base level of virtualisation, representing the different virtual instances producing a service
2. The level of instances clustering on machine level
3. The level of multi-data centres, representing the aspects of multiple redundan cies of machines on differently located data centres
4. The service level of the SOA, where the distributed application is run and the measurement is performed in terms of service interactions
5. The service chain levels if the application is distributed through different cloud vendors

## 电子工程代写|软件项目作业代写Software Project代考|Measuring the Interaction Between SOA Services

Distributed applications in cloud environments can be considered as a particular form of SOA software in which cloud-specific services can occur. Thus, the official guideline for sizing SOA with COSMIC can be applied [18].

An SOA-based software is designed following a specific pattern in which application components provide services to other components, exchanging data through a communication protocol (e.g., messaging queue), typically over a network. Even though sizing service-oriented software with Function Point Analysis fails when reconstructing or mapping the Functional User Requirements, the COSMIC method defines the concept of ‘layers’ that perfectly matches the SOA-based software sizing, without needing to adapt the method in any particular way.

The organisalion for the Adyancement of Strustured Information Standards (OASIS) defines SOA as ‘a paradigm for organising and utilising distributed capabilities that may be under the control of different ownership domains. It provides a uniform means to offer, discover, interact with and use capabilities to produce desired effects consistent with measurable preconditions and expectations’ [19].

Services are accessible to each other by means of a public interface, in the form of application program interfaces (APIs) often through simple Create/Read/Update/ Delete (CRUD) operations. Not only do the APIs allow the services to communicate with each other but also they make the service independent in terms of development and execution. Indeed, the calling software does not have or need to know anything about how a service actually performs its tasks. This eases the independent work of parallel development teams and the inclusions of third-party components in SOAs. APIs are also useful for COSMIC sizing since they are independent of both involved technologies and implementations. Usually, APIs strictly follow the definition of FURs of the distributed application, being available from the early stages of the project.

Table $3.1$ shows the classification given by the COSMIC guideline for SOA software [19].

The ‘application services’ provide specific business operations. They implement the features that characterise the distributed application; thus the most of the FURs are related to them. Each functionality can be invoked using an API in the form of network messages.

## 电子工程代写|软件项目作业代写Software Project代考|Measuring the Interaction Between Cloud Customers

• 在云系统上实例化的按需服务通过触发事件和特殊感兴趣对象（如成本和资源）来控制。
• 网络是服务作为独立层进行通信的通道，通过 COSMIC 进入和退出数据移动来衡量。
• 相反，读取和写入测量来自/到执行资源池的持久存储的数据移动。
• 弹性因素涉及对“存储大小”和“位置”要求等数据组进行服务扩展的功能过程。
• 测量的服务本身支持基于感兴趣对象的功能流程，例如计费和服务水平协议 (SLA) 条款。

1. 虚拟化的基础级别，代表产生服务的不同虚拟实例
2. 机器级别的实例集群级别
3. 多数据中心的级别，代表不同位置数据中心上机器的多个冗余方面
4. SOA 的服务级别，其中运行分布式应用程序并根据服务交互执行测量
5. 如果应用程序通过不同的云供应商分发，则服务链级别

## 电子工程代写|软件项目作业代写Software Project代考|Measuring the Interaction Between SOA Services

“应用服务”提供特定的业务操作。它们实现了分布式应用程序的特征；因此大多数 FUR 都与它们有关。每个功能都可以使用网络消息形式的 API 调用。

myassignments-help数学代考价格说明

1、客户需提供物理代考的网址，相关账户，以及课程名称，Textbook等相关资料~客服会根据作业数量和持续时间给您定价~使收费透明，让您清楚的知道您的钱花在什么地方。

2、数学代写一般每篇报价约为600—1000rmb，费用根据持续时间、周作业量、成绩要求有所浮动(持续时间越长约便宜、周作业量越多约贵、成绩要求越高越贵)，报价后价格觉得合适，可以先付一周的款，我们帮你试做，满意后再继续，遇到Fail全额退款。

3、myassignments-help公司所有MATH作业代写服务支持付半款，全款，周付款，周付款一方面方便大家查阅自己的分数，一方面也方便大家资金周转，注意:每周固定周一时先预付下周的定金，不付定金不予继续做。物理代写一次性付清打9.5折。

Math作业代写、数学代写常见问题

myassignments-help擅长领域包含但不是全部: