Enterprise Mobility Framework

It won't be long before Enterprise Mobility is considered 'business as usual'. But right now, it is analogous to the early days of PC adoption, where end users are largely creating the ‘pull’ for enterprise mobility, rather than the IT department driving this out from the center. The mobile market is driven by consumers. The consumer (led by consumer-oriented vendors) is setting the trends and establishing the de jure standards, not the enterprise. Inconveniently for organizations, their employees are consumers too – hence the demand for BYOD.

NIST Cloud Computing Reference Architecture

I see NIST have now published their Cloud Computing Reference Architecture as a recommendation. Little has changed conceptually since earlier drafts, but the document is now more detailed and complete.

In earlier commentary on Cloud Computing Reference Architectures, Models and Frameworks I described how there is little concensus on what form a reference "thing" should take or what its content should be, and that most are a mish mash of concepts that have their own structure, but not a consistent structure that enables them to be easily combined or compared for example.   The NIST Cloud Computing Reference Architecture is no different in that respect.

However, it is still a worthy document, and as with earlier NIST output that laid out definitions for core cloud computing concepts such as SaaS/IaaS/PaaS, the reference architecture is bound to be widely referenced as a "standard".

Service Boundaries

Richard Veryard asks in his blog on Service Boundaries  "where did all the boundaries go?"

CBDI Forum was one of the organizations back in those early days that Richard refers to that promoted the concept of service boundaries, but unfortunately not much of our work on that principle is freely available. So, I thought I would rectify that.

The Service Oriented Cloud

Cloud Computing is intrinsically service-based. But this is not just in the highly generalized sense of the term ‘service’, but also in the more specific Service Oriented Architecture (SOA) use of the term, where capabilities are provided via published service interfaces. When Amazon CTO Werner Vogels describes the Cloud as "a collection of services", in AWS terms the capabilities provided are SOA-style software services, complete with published Web Service interfaces.

As well as the PaaS and IaaS capabilities provided by AWS or Microsoft's Azure for example, there are also SaaS capabilities provided by the likes of salesforce.com that can be consumed as software services.

Hence the concept of the Service Oriented Cloud (SOC)  illustrated below.

Cloud Computing Reference Architectures, Models and Frameworks

There are a plethora of different reference architectures, models and frameworks for Cloud Computing (CC). As well as several vendors such as IBM or CISCO, it seems every standards or industry body has to have their own reference "thing" too. Hence there are architectures from DMTF, CSA, SNIA and the Open Group (which has been submitted by IBM) as well as several seemingly competing federal initiatives.  NIST, who have established the de facto definitions of CC and the service and deployment models also have a draft CC Reference Architecture.

So which one should an organization adopt? Of course there’s no straightforward answer to that question and so I have published a research note on Everware-CBDI to provide guidance on how to organize some of the best ideas that are emerging in a practical structure that should stand the test of time.

UML Profiles in Visual Studio 2010

UML Profiles are supported in Visual Studio 2010 (VS2010). Here I examine how they work and whether our CBDI-SAE UML Profile for SOA (SAE Profile) can be used in VS2010

Trialing Microsoft Office 365 Beta

Currently trialing the Microsoft Office 365 Beta. It seems tailored made for small businesses like us. Like many small businesses, we already rely on several disparate hosted services such as email, a SharePoint for collaboration, Skype, Webex, plus some use of Google Docs, and so on, all of which are supplied by different providers, resulting in incompatibilities, lack of integration, multiple signons, etc.
Bringing together all these capabilities under one roof seems attractive. It will also help to ensure everyone is using Office 2010 (no more need to save as 2003!).
Will update as we use it more.