Service Modeling Language

Last night Heather Kreger gave an overview of the Service Modeling Language (SML) to members of the OGF's OGSA working group. The high-level view that I took away from this is that SML is a modelling effort based purely on XML (particularly XML Schema), rather than initiatives that map CIM or UML into XML. The advantage of this is that it has a cleaner rendering; for example, it doesn't have to translate the CIM or UML use of inheritance (which XML Schema doesn't directly support).

In practice, models can be rather large. SML also uses Schematron to enable models to be split across multiple documents, while still enabling validation against the models. A related activity, CML, is producing some core models in SML.

SML is backed by BEA, BMC, CA, Cisco, Dell, EMC, HP, IBM, Intel, Microsoft, and Sun, so certainly has industry support. They intend to submit the specification to a standards body in a few months time, although it will be a while after that before it is published as a recommended specification.

My personal opinion is that this may well be useful down the line. Anyone working on models now should not wait for this but should continue with whatever language and system you are currently using. SML won't be ready for production use for quite a while and will need to build a user community and some momentum before it sees widespread use. But with this range of backers, it might just happen.

Comments

Webinar: Powering your business with Cloud Computing

On October 14th, I will be hosting a Grid Computing Now! web seminar on the topic of Cloud Computing. We have lined up two very interesting speakers who are using Cloud now to make businesses work. Ross Cooney had a good technological solution to sell but couldn't make it economic until Cloud Computing allowed him to pay for his computation only when he needed it. He will discuss the instant benefits and long term impact of cloud computing to the development, competitiveness and scalability of your application. Alan Williamson created the BlueDragon Java CFML runtime engine that powers MySpace.com. He advises several businesses and will give an overview of the different types of services available and how to avoid being locked-in to a single supplier. You can register for this event here .

Business Model Canvas

A Business Model Canvas is a tool for mapping the core functions and capabilities of an organisation. Compared to the Core Diagrams that I described in an earlier post , the business model canvas attempts to present more aspects of the business, starting with the value proposition – a statement of what the organisation offers to its users (in the business world, to its customers). It shows the activities and resources, as Core Diagrams do, but also shows user relationships & channels, and also benefits and costs. I’m not aware of any universities that have used this tool but you can find examples from elsewhere on the web. We are considering business model canvases as a tool for mapping the strategic capabilities of units at the University of Edinburgh. Phil Taylor, our EA contractor, sketched an outline of what a business model canvas might begin to look like for HR: This is only intended to be suggestive: the real canvas would need to result from in-depth discussions abo

Changing Principles

In EA, architecture principles set a framework for making architectural decisions. They help to establish a common understanding across different groups of stakeholders, and provide guidance for portfolios and projects. Michael Durso of the LSE gave a good introduction to the idea in a webinar last week for the UCISA EA community. Many organisations take the TOGAF architecture principles as a starting point. These are based on the four architectural domains of TOGAF: business, information/data, applications, technology/infrastructure. These principles tend to describe what should be done, e.g. re-use applications, buy in software rather than build it, keep data secure. See for example the principles adopted at Plymouth University and the University of Birmingham . Recently though, I encountered a different way of looking at principles. The user experience design community tend to focus more on how we should do things. E.g. we should start with user needs, use iterat

Distributed Thinking

Search This Blog