Page 575 - Cloud computing: From paradigm to operation

XaaS 3

Table III.6 – Home application using DaaS

Legend Use case
Derived – Unified management interface
requirements – Diversity of DaaS client
– Optimized adaptation for content type
– Dynamic configuration adaptation
– Support of DaaS client peripherals

Table III.7 – Charging scheme for DaaS

Legend Use case

Use case title Charging scheme for DaaS
Use case This use case depicts the case where charging functionality is required in DaaS. The purpose of
description this use case is to show various environments of CSCs that use common resources provided by
the same CSP.
There are two actors in this diagram: CSC and CSP; they provide software and hardware.
• The CSP needs to manage DaaS user profiles including the types of users. (#1 in figure).
• As, depending on the type of users, the rate for using resource can be offered differently,
the CSP manages the policy for resource usage. (# 2 in figure).
• The CSC uses resources (#3 in figure) and the CSP manages software and hardware usage
statics (#4 in figure).
• The CSP manages accounting (#5 in figure) by monitoring software and hardware usage
statistics (use case 3). The CSC can use storage, CPU and memory as in IaaS, and whenever
an application (software) runs on CSP. DaaS also provides storage, CPU and memory. The
CSP needs to store accounting information of software and hardware usage whenever the
usage occurs.
• Considering user profile, software and hardware usage statistics, and the policy of resource
usage to reflect different types of usage, the CSP produces bills and requests payment to
CSCs (#6 in figure).
High-level figure
describing the use
case

567