[LINK] RFC: Cloud Computing Architecture

[Richard Chirgwin]

Roger,

To  your client-side risks I would add another flexibility issue. If a 
requirement emerges that is not supported in the cloud environment, then 
the user may be therefore unable to respond to that requirement.

I'm sure that this could be described better, but it's Saturday and 
there's about a dozen litres of tomato waiting to be bottled ...

RC


Roger Clarke wrote:
> I've flung together a paper that tries to nudge computer scientists 
> out of their cocoons, and adopt a broad enough conception of cloud 
> computing.  The intended venue is a Workshop in Melbourne.
>
> It's phrased in the clipped fashion used in engineering conferences, 
> in the hope that it might survive the likely mauling it will get from 
> reviewers.
>
> Constructively negative feedback gratefully received!
>
>
>             User Requirements for Cloud Computing Architecture
>                http://www.rogerclarke.com/II/CCSA-0911.html
>
> To date, the literature on software architecture for cloud computing 
> is focussed almost entirely on the service-provider. It accordingly 
> fails to reflect the fact that cloud computing is a form of 
> client-server relationship, and hence architectures must encompass 
> the software and devices that users utilise in order to invoke 
> functions in the cloud. Yet worse, analyses to date commonly fail to 
> adequately reflect the risks that users are subject to when they use 
> cloud services. This paper proposes a comprehensive model that 
> reflects user needs, and identifies implications of the model for 
> computer scientists working in the area.
>
>
> The International Workshop of Software Architecture Principles for and
> with Cloud Computing (ArchiteCloud 2010)
> http://www.nicta.com.au/people/tosicv/architecloud2010
>
>
>