CBDI Journal Index
The CBDI Journal is now published on an occassional basis and since September 2010 is now freely available to visitors.
You can download the complete journal below, or access the individual reports, together will many other reports from the back-catalog of CBDI Journals.
See also the Research Note Index for further reports and insights
Note: The complete back-catalog of CBDI Journals prior to September 2010 together with a broader range of guidance is only available via the CBDI-SAE Knowledgebase, which is only accessible to paying subscribers. The journal reports listed below are just a small selection of the guidance and reports that we have chosen to make freely available here.
CBDI Journal Editions
Editorial: Raining on the “Cloud Service Model” Parade
Practice Guide: Everything is a Service?
Exploring the path towards a unified service model
The Cloud movement is discussing the term Everything as a Service (EaaS or XaaS). In principle this is a welcome development, encouraging business and IT participants to adopt services and service oriented concepts everywhere. However it appears that the E/XaaS initiative may be more about marketing than reality. In this article we suggest how this very promising idea might be developed to clarify Cloud Service taxonomy and deliver convergence of business and IT perspectives in a Unified Service Model.
By David Sprott
Practice Guide: Developing an Enterprise Mobility Framework
Is your enterprise ready for mobility and BYOD? It is a growing imperative, but not many are. Enterprise Mobility – the use of mobile computing within the enterprise – has gained significant momentum in recent times. This report establishes the requirements for an Enterprise Mobility Framework and outlines some of the key elements.
By Lawrence Wilkes
Individual CBDI Journal Reports
This report looks at various ways in which Capability Planning and Analysis might be applied in specialized scenarios and service portfolio planning.
The Capability concept is widely accepted as a useful technique to bridge the business perspective and the service architecture. But capability identification is frequently as far as it goes. Our experience is that capability can provide a really powerful mechanism to justify, drive and govern service delivery and provide integrated business and IT planning and management. This report outlines a structured approach to the analysis and planning of business and IT capabilities.
Business design is set to undergo a dramatic transformation. The convergence of ecosystem automation and autonomics, architecture for continuously evolving business, together with the merger of consumer and business IT will have a profound impact on conventional business models.
By David Sprott
In previous reports we have advised on approaches for modeling for business improvement and the adaptable enterprise. In this report we return to this topic and show by example how enterprises are innovating in their process design to deliver significant improvements in customer experience. They do this by going beyond basic process modeling with capability models for organizational intelligence. We show by example how this model provides an integrating framework for implementing a broad range of organizational and technological initiatives.
Beware the New Silos. A governance approach to coordinating the disciplines involved in business improvement (pdf)
There are six primary disciplines involved in business improvement – Business Architecture, Enterprise Architecture, Business Process Management, Business Capability Management, Service Oriented Application Modernization and IT Service Management. In many enterprises the level of coordination between the disciplines is inadequate resulting in silos which deliver suboptimal results for the enterprise. In this report we explore the issues and propose a governance based approach to balancing responsibilities, accountabilities and managing conflicts and maturity.
Across the industry Application Modernization is a synonym for legacy renewal and transformation. It's widely viewed as a technology based process. In contrast we recommend that modernization must be business driven. It's a major opportunity to create a modern architecture which reflects the current and future business needs. Getting concrete understanding of the future business needs is of course not a trivial task and in this article we provide guidance on using the increasingly popular BPMN notation in a systematic and efficient approach to business driven modernization.
In this report we examine how the CBDI-SAE SOA process can evolve to support Application Modernization, by introducing new disciplines to cover the planning and architectural aspects of Application Modernization, the discovery of knowledge encapsulated in the applications, and finally to perform the reengineering that may result in new business requirements.
SOA Governance has taken on a renewed importance as organizations seek to scale up their early SOA experiences. Scarcely a week seems to go by without SOA governance popping up in a story on the newswires. Too often however the advice given is too vague with a lack of specific measures that can be taken by organizations that need to achieve much better accountability in challenging economic times, or is focused on the narrow view of governance that is supported by a vendor's products. Our experiences in the field show that despite the challenges there is now an opportunity to get to grips with overall IT governance, of which SOA is one, albeit key, part. This article distills the main lessons learnt in the form of a SOA governance framework with practical guidelines for progression in real world contexts.
At the heart of the service concept is conformance with the principle of the "contract based" capability. Whilst many SOA principles will be optional depending upon context, the use of service contracts is likely to be required, because a well formed service is likely to be the primary enabler of the agile business. At the same time it is important to use a pragmatic level of specification detail that is appropriate to the context of use. Our practice research to date has focused on the Rich Service Specification and the Service Level Agreement. In this report we extend that guidance to cover evolution of specification artifacts across the full service life cycle, in an integrated way, to include all the involved parties.
We continue to develop our thinking on SOA Adoption Roadmap as we work with customers. In this report we map out the framework in a more orderly manner than we have done previously, and also taking the opportunity to introduce practical guidance on customization for various circumstances that we have encountered. We have also updated and structured our guidance on patterns.