https://www.infra-repository.org/oiar-2013/index.php?action=history&feed=atom&title=PAT.Data_ManagementPAT.Data Management - Revision history2026-05-06T14:27:35ZRevision history for this page on the wikiMediaWiki 1.40.0https://www.infra-repository.org/oiar-2013/index.php?title=PAT.Data_Management&diff=121&oldid=prevJan Schoonderbeek: start2012-11-11T23:22:21Z<p>start</p>
<p><b>New page</b></p><div>{{Maturity|3}}<br />
{{Pageheaderbox4PatternType<br />
|PATname=Data Management<br />
|summary=Provides preservation, retrieval, manipulation and management of strictly structured data, such as databases<br />
|version=0.22<br />
|owner=J.A.H. Schoonderbeek<br />
|sector=Infrastructure Sector Core<br />
}}<br />
This pattern provides a description of generic data management facilities. The most common realization of this functionality is known as 'database'.<br />
{{PAgraphic<br />
|graphic=PAT.Data_Management.png<br />
|source=Pattern_Types.vsd<br />
|size=500px<br />
|title=Data Management pattern<br />
|kind=Type<br />
}}<br />
{{Pattern Type Composition}}<br />
{{Pattern Type Composition Row<br />
|facility=BT.Structured Data Store<br />
|choice=must<br />
|reason=The structured storage of data is the heart of the Data Management pattern. Data is organized in such a way, that information can easily be retrieved, for example by a query, executed by a Data Engine facility.<br />
}}<br />
{{Pattern Type Composition Row<br />
|facility=BT.Data Engine<br />
|choice=must<br />
|reason=The Data Engine offers various ways to preserve, retrieve, manipulate and manage data that is being stored in a structured data store facility.<br />
}}<br />
{{Pattern Type Composition Row<br />
|facility=BT.Control Interface<br />
|choice=may<br />
|reason=A Data Management system should preferably be managed by a centralized facility. However, it may be desirable to manage the facility directly - and the Control Interface offers this means.<br />
}}<br />
{{Pattern Type Composition Row<br />
|facility=BT.Backup<br />
|choice=may<br />
|reason=This facility provides a means to back-up data for recovery purposes. Since the data stored may have all sorts of internal consistencies, and may undergo multiple operations at any time, the creation of a consistent point-in-time backup is a specialized job that can usually not be handled by generic backup facilities.<br />
}}<br />
{{Pattern Type Composition Row<br />
|facility=BT.Restore<br />
|choice=may<br />
|reason=The facility includes the means to restore a back-up as created by the Back-up functionality.<br />
}}<br />
{{Pattern Type Composition Row<br />
|facility=BT.Archiving<br />
|choice=may<br />
|reason=This facility preserves data in a persistent way. Archiving parts of a structured data storage requires knowledge of the internal structure of the data, and is thus specific to the implementation of the structured data store.<br />
}}<br />
{{Table Ending}}<br />
{{Pattern Type Neighbors}}<br />
{{Pattern_Type_Adjacent_PAT_Row<br />
|pattern=PAT.Application Hosting<br />
|choice=may<br />
|reason=This Pattern is often a consumer of the services of Data Management.<br />
}}<br />
{{Pattern_Type_Adjacent_PAT_Row<br />
|pattern=PAT.Authentication+Authorization<br />
|choice=may<br />
|reason=A suitable source for identity and permission information may be required for<br />
* controlling access to the data stored in the Data Management facility;<br />
* management of the data, or the Data Management facility itself, using the Control Interface.<br />
}}<br />
{{Pattern_Type_Adjacent_PAT_Row<br />
|pattern=PAT.File Storage<br />
|choice=may<br />
|reason=The Structured Data Store usually needs to be stored itself on a facility, usually as loosely structured data (e.g. a set of files holding a database). To this end, File Storage can be used to model this storage.<br />
}}<br />
{{Table Ending}}<br />
{{PATfooter}}</div>Jan Schoonderbeek