The CORA Model

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.

The Data Storage cluster handles the types of data available for the enterprise. When crafting a solution it is important to know what types of data will be used within the solution. A Transactional data store for instance will be treated differently in a database then a Datawarehouse type of data store. The CORA model data layer shows a list of data types mostly used in applications but other types can be used in your solution. Besides this in the data storage cluster Data Life cycle management also comes into play. Among others the following questions should be raised. How long is the data valid? Do regulations have impact on the amount data need to be stored. Is storage of history data needed?

The Data Access cluster is responsible for access to operations on data resources. Here the difference between a Package Based Application (PBS) and a Custom Software Developed (CSD) becomes clear. In a CSD type of application data can be touched and changed directly. Data access technologies are often used to abstract data from the access for security or performance reasons. Within a PBS type of application direct access of data is most of the times strictly forbidden. Data access is often managed within the PBS application where only certain types of functionality are exposed to the outside world (via the Integration layer).