EA - IT Architecture V2 > Architecture Specification > Modeling application architectures > Managing Data
Managing Data
 
Using Data Stores
Introduction to the data store concept
Usage contexts
Creating a local data store
Creating a external data store
Describing access to a data store
Access Data Stores supports
Accessing to data areas with HOPEX IT Architecture
Accessing the list of file structures with HOPEX IT Architecture
Accessing to NoSQL data domains with HOPEX IT Architecture
Accessing the list of relational schemes with HOPEX IT Architecture
Data stores are used in architecture diagrams to represent data that must be stored to be share between components.
*A data store provides a mechanism to update or consult data that will persist beyond the scope of the current process. It enables storage of input message flows, and their retransmission via one or several output message flows.
A Data store can be supported by different object types:
• A data domain
*A data area represents a restricted data structure dedicated to the description of a software Data Store. It is made of classes and/or data views and can be described in a Data Area Diagram.
• a file structure
*A file structure represents a file folder or a single file used in the technical architecture of an application.
• A NOSQL data domain
*NoSQL data domain represents a set of data stored in a NOSQL database management system and used in the technical architecture of an application.
• A Relational Schema
*Relational schema represents a set schema stored in a database management system and used in the technical architecture of an application.