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...
        • CORA and Application Lifecycles
        • Technology Trends...
          • Overview
          • You Experience
          • We Collaborate
          • Process on the Fly
          • Thriving on Data
          • Sector-as-a-Service
      • CORA and TOGAF
      • CORA and Archimate
      • 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
      • ERP and PaaS
  • Methodology
  • Experiences
  • The Authors
  • The Book
    • Paper Version
    • eBook

The Data Layer

This layer provides data-specific software clustered in ‘Data Access’ and ‘Data Storage’ elements. The distinction between these two clusters is based around the separation of responsibilities and of functionality (i.e. access is provided, but only for the storage of Master data). The notice of different data types for storage is essential on enterprise level. Different data types may also need different technology for data access.

sdata_layer

The basis of all, your data

PostAuthorIconWritten by Léon Smiers | Print | E-mail

Introduction

We are thriving on data. We come from a time where data only belonged to one application, but now data-combinations of any sort within and outside the enterprise are possible. Without data and accompanying good data management enterprises would be lost. The data layer has been separated in the CORA model because of its importance for the enterprise. The data layer within the CORA model contains two main clusters, Data Access and Data storage. The distinction between these two clusters is based around the separation of responsibilities and of functionality.

Read more...

 
Follow Us on Twitter

theo_elzinga1_klein     leon_klein

Latest Articles
  • Assessing IT solutions with CORA
  • CORA and Archimate
  • Architecture Styles and CORA
  • ERP and PaaS
  • CORA and Application Lifecycles
  • CORA Methodology (Project level)
  • 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.