CBDI-SAE Reference Framework for SOA
The CBDI Service Architecture & EngineeringTM (CBDI-SAETM) for SOA is a comprehensive, defined approach for service architecture including taxonomy, classification and policies together with repeatable service engineering processes that guide the delivery of the agile enterprise, implemented in a knowledgebase with integrity between the architecture concepts, processes, tasks, techniques and deliverables.
Why Service Architecture & Engineering?
Many SOA initiatives will fail to deliver on the promise of business agility and reduced cost. Good architectural thinking is often ignored by implementing project and program teams. Many organizations are treating SOA as just another technology to be accommodated into their existing practices. They are delivering and using services but there is no structure to their service activity and there is little or no consensus or consistency across the organization on what SOA is, let alone explicit policies and repeatable processes that permit governance. The result is there is something near service anarchy in many corporations as inconsistent, incomplete and duplicative services are delivered by unchanged solution and integration processes.
SOA requires a differentiated approach that is more analogous to a manufacturing and assembly environment, where different classes of service have different, repeatable processes that reflect varying requirements for funding, provisioning, assembly and management. Enterprises need to adopt more mature architecture and engineering processes and practices for delivering and managing IT assets that more closely parallel other engineering disciplines. This is an essential next step to deliver services that are not only fit for purpose, but also deliver future flexibility, utility and cost.
CBDI-SAE provides a defined, structured approach to architecture and engineering tasks and deliverables that provides visible traceability from business requirements to implemented services. The structured approach provides the necessary level of formality over policy implementation to ensure governance over business requirements and architectural policies.
The CBDI-SAE Reference Framework is delivered via the CBDI-SAE Knowledgebase for SOA.
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.
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.
The terms virtualization, utility computing and Cloud computing are often used interchangeably which can be very confusing. This report aims to provide clarification - to identify the similarities and differences in those characteristics, and provide a framework in which organizations can decide which capabilities they require in specific situations – as it is unlikely that one model alone will suit all requirements.
There is no "one size fits all" methodology, ours or anyone else's, and so best practice in method development calls for incorporation of a framework of artifacts, tools and techniques that can be tailored to the nuances of each organization that wants to implement the methodology. However, most popular methods don't tend to focus on the needs of service lifecycle instead covering a broad but typically less focused method landscape. CBDI's SAE™ Reference Framework is built to remedy that problem by highlighting aspects of methodology such as process, techniques and artifacts needed to embrace SOA concepts in a structured manner. This article provides an introduction to the Architecture component of the Reference Framework and the rationale that went into its creation.