Cloud Computing Use Case White Paper V2 - Draft Table of Contents posted

[drus...@ca.ibm.com]

Today, a draft of the table of the contents was posted. Is there
anything missing that should be included? Please post your responses
on the Cloud Computing Use Cases discussion group at -
http://groups.google.com/group/cloud-computing-use-cases?hl=en .

Proposed Table of Contents

1 Introduction
2 Definitions and Taxonomy
2.1 Definitions of Cloud Computing Concepts
2.2 Taxonomy
2.3 Relationships Between Standards and Taxonomies
2.4 Application Programming Interfaces (APIs)
2.4.1 Developer Roles
2.4.2 Levels of APIs
2.4.3 A Taxonomy of APIs
2.4.4 APIs and Portability
3 Use Case Scenarios
3.1 End User to Cloud
3.2 Enterprise to Cloud to End User
3.3 Enterprise to Cloud
3.4 Enterprise to Cloud to Enterprise
3.5 Private Cloud
3.6 Changing Cloud Vendors
3.7 Hybrid Cloud
4 Customer Scenarios
4.1 Customer Scenario: Payroll Processing in the Cloud
4.2 Customer Scenario: Logistics and Project Management in the Cloud
4.3 Customer Scenario: Central Government Services in the Cloud
4.4 Customer Scenario: Local Government Services in a Hybrid Cloud
4.5 Customer Scenario: Astronomic Data Processing
5 Conclusions and Recommendations

Major changes:

2.1 Definitions and Taxonomy:
- Add definitions of APIs, etc.

2.4 Application Programming Interfaces (APIs) [new section]
2.4.1 Developer Roles:
- The different kinds of developers and their concerns: Somebody
using cloud storage has different concerns than someone wrangling VMs.
Wil Sinclair's post of August 19th is a good starting point:
http://groups.google.com/group/cloud-computing-use-cases/browse_threa....
2.4.2 Levels of APIs:
- The four levels from the September 14th post:
http://groups.google.com/group/cloud-computing-use-cases/browse_threa...
2.4.3 A Taxonomy of APIs:
- The seven categories from the September 3rd post:
http://groups.google.com/group/cloud-computing-use-cases/browse_threa...
2.4.4 APIs and Portability:
- A discussion of portability, including the value of common APIs
and the use of adapters to hide the differences between APIs and
subclasses to expose the differences by extending the common APIs.

3 Use Case Scenarios:
- Add cross-referencing here that links each scenario to the
appropriate categories of APIs. At the end of this section, add new
tables to show the relationships between requirements and APIs,
between the seven use cases and the seven categories of APIs, between
developer roles and use cases, etc. (Basically anything to make this
information easier to understand.)

4 Customer Scenarios:
- Add more scenarios to fill in the gaps of our discussion. Also add
cross-referencing to link each scenario to the appropriate API
information.

Look forward to your comments.