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
In this report, we discuss an agile project structure and organization and provide a detailed breakdown of the Application Modernization process in terms of Project Phases and Work Packages.
This approach to application modernization will allow an escalation from a sponsored modernization effort to an enterprise SOA effort over time. It can be viewed as the pragmatic middle ground between a difficult to motivate enterprise level SOA and successive SOA projects that will inevitably lead to service anarchy.
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.
Application Modernization is a commonly used term covering a wide range of practices and technologies. As the world emerges from recession there is growing interest in applying modernization techniques and technologies to reduce complexity and cost and respond to rapidly changing, post recession business models. In this report we explore how the CBDI SAE framework can be evolved to provide a repeatable, business driven backplane for effective application modernization practice.
In this report, we narrate an actual modernization project undertaken by Everware-CBDI North America. The case study illustrates how the Agile Application Modernization approach is used in practice to deliver demonstrably modernized solutions that reflect future business needs. In this scenario we describe how we addressed specific application modernization project needs, while demonstrating how a limited portfolio assessment can significantly improve the outcome.