data architecture models and views

Business data models

A business data model is a data structure. It is an entity-attribute-relationship model. It defines business terms and concepts in the form of entities, attributes and relationships.

Logical data models

A logical data model has many possible uses:

  • It presents a unified view of the data required by one or more applications in the IS architecture.
  • It defines the data is that required to inform and enable the processes (use cases and business services) of applications.
  • It provides a good place to record many business rules.
  • It may develop into a database schema.
  • It may develop into a canonical data model that defines the data items used in the interfaces of messages, regardless of underlying database schemas.
  • It may help you divide the back-end of an application into loosely-coupled information provide applications, or business components.

Data dissemination view

Data lifecycle view

Data security (and other quality) view

Data qualities are meta data. Data that defines the characteristics of data. The three classic data qualities are CIA: confidentiality, integrity and availability.

Data model view

Define up front the purpose of the data model and how it will be kept in step with other data models. So define the tupe of data model described. Examples:

  • Enterprise/business data model – business terms and facts
  • Canonical data model – data in motion
  • Logical data model – data required by an application
  • Physical data model – database design
  • Does the model define structural business rules?
  • Is the model to be embedded in software designers’ class diagram?
  • Is it used for database schema definition?

Data entities mapped to Business functions

Data flow view

Data storage view

Data archiving view

Questions to be described in this section are e.g.:
How should you index files?
Does data have to be maintained for long periods of time?
How quickly must you be able to access data?
Must data be readily accessible, even with future software?
Do you need to keep data in its original format an d never alter it?

Data Architecture Views