The CORA Model

A practical guide on using a COmmon Reference Architecture to design
and deliver integrated IT solutions successfully
  • Home
  • CORA Model
    • CORA Requirements
    • CORA Foundation
    • CORA and Business Logic
    • CORA Layers...
      • Overview
      • Channel Access
      • Presentation
      • Composition
      • Integration
      • Application
      • Data
      • Security & Compliance
      • IT Governance
    • Target Groups
    • Sitemap
  • Connections
    • Enterprise Architecture...
      • CORA and Technovision...
        • Overview
        • You Experience
        • We Collaborate
        • Process on the Fly
        • Thriving on Data
        • Sector-as-a-Service
      • CORA and TOGAF
      • CORA and IAF
    • Sol./Softw. Architecture
    • Vendor Connection...
      • CORA and SAP
      • CORA and Oracle
      • CORA and Microsoft
      • CORA and IBM
    • Cloud Computing...
      • Overview
      • Static and Dynamic view
  • Methodology
  • Experiences
  • The Authors
  • The Book
    • Paper Version
    • eBook

Technovisions "Sector-as-a-Service" mapped

PostAuthorIconWritten by Theo Elzinga | Print | E-mail

Introduction

This is the sixth blog in a series about Capgemini's Technovison and the mapping onto CORA. In the first blog Technovision was explained, being in short the provisioning of a clear picture of the information technologies that are the most relevant to the organizations' business drivers and how these technologies and their evolution will impact business.

With Technovision the business drivers are mapped to innovations as an input to the IT-Strategy. With the CORA model the gap between the IT strategy and actual implementation of software is bridged because the CORA model can be used at different levels (Enterprise level, project implementation level) and has the possibility to design and implement elements with a mixture of ‘architecture styles’ on the best fitted platform available (or planned).

By mapping the 17 identified key information technology trends within Technovision onto the layers and logical elements of the CORA model the impact on the IT landscape is visualized and assessed in more detail. In the second, third, fourth and fifth the key information technology trends within the "You Experience", "We Collaborate", "Process-on-the-Fly"and "Thriving on Data"cluster. In this blog post this is described regarding the "Sector-as-a-Service" cluster.

The "Sector-as-a-Service" describe the technology changes to the foundation of the systems, the part of the systems that should work continuously and with high reliability.

Through explicit simplification and rationalization, organizations can now liberate themselves from having to build and maintain bespoke legacy systems that do not provide differentiating value.

Furthermore, automation of standard and non-differentiating business services is increasingly provided by third parties on an outsourced basis, either through the software-as-a-service model or through prepackaged software. These help change an existing landscape of bespoke, highly customized and heterogeneous solutions into a more simple, utility-style set of (sector-related) business services. 

The following capabilities ("Technology Trends" or "Building blocks") are part of this cluster:

  • Packaged Sector Solutions: standard, package-based software to support core business services within organizations.
  • Software-as-a-Service: a model of software deployment where an application is hosted as a service provided to usersacross the Internet.
  stvsectorasaservice

As shown in the figure the capabilities have a clear focus on the Application and Integration Layer. The other horizontal layers are layers supporting this layer depending on the architectural style used. For the sake of simplicity the capabilities are described separately, but combinations of capabilities are possible.

Packaged Sector Solutions

There a many reasons to replace outdated heterogeneous legacy systems such as high maintenance costs or be able to support new business models/channels. Whatever the reason, the new core services will need to be more standardised and be able to plug and play with other services from within the organisation or from partners. Open standards for these services are a must to facilitate the interoperability that is required. For this reason the relationship with SOA Governance is mapped explicitly onto the model.
The resulting foundational services (generic and sector specific) should enable the organisation to create headroom for innovation and regain control for regulatory compliance. It is also the necessary step to enable outsourcing of these services.

Because many solutions/platforms are built based on the N-tier architecture style or a combination of N-tier and SOA architecture style special care must be taken when assessing them.

Software-as-a-Service

More and more basic services can be delivered in a software-as-a-service model. Software as an on-demand utility is currently mainly aimed at mid-size companies, but this can be extended to include part of the services for larger organisations, much like shared-service centres.Open standards are a crucial enabler of this move to further outsourcing of foundational services. For this reason the relationship with SOA Governance is mapped explicitly onto the model. Only through open standards can these services become sufficiently generic to allow easy interoperability among the different services. This will then provide the basis for further orchestration of theses services and enable organisation to create ‘process(es)-on-the-fly’ and to ‘thrive on data’.

Because many SaaS-solutions are built based on the N-tier architecture style or a combination of N-tier and SOA architecture style special care must be taken when assessing them.

In the next blog post the technology cluster "Infostructure" will be mapped onto CORA.  

 

Last Updated (Tuesday, 23 November 2010 12:34)

 
Follow Us on Twitter

    leon_klein

Latest Articles
  • CORA Methodology, playing with Lego
  • The roadmap for Fusion Applications, CORA is there to help
  • Technovisions "Sector-as-a-Service" mapped
  • Business Logic and the CORA Model, Part II
  • CORA and Cloud Computing: Static versus Dynamic View
  • Technovisions "Thriving on Data" mapped
  • CORA Foundation
  • Business Logic and the CORA Model, Part I
  • CORA and IBM
  • CORA and Microsoft
  • CORA and Cloud Computing: Overview
  • Technovisions "Process-on-the-Fly" mapped onto CORA
  • Risk aware design: using CORA to investigate an IT solution
  • A ROA based iPhone App for SAP: Part II
  • A ROA based iPhone App for SAP: Part I
  • Technovisions "We Collaborate" mapped onto CORA
  • SAP platform decomposition with CORA: SOA/ROA style
  • 'Why' Driven Solution crafting
  • CORA and TOGAF
  • SAP platform decomposition with CORA: N-tier style
  • Requirements for CORA
  • CORA and Oracle
  • Technovisions "You Experience" mapped onto CORA
  • CORA and SAP
  • CORA in action: design guidelines to implement repositories
  • The basis of all, your data
  • CORA and IAF
  • Technovision and CORA - Overview
  • The importance of an Integration layer

Joomla template created with Artisteer.