GP.Data Management: Difference between revisions

Revision as of 06:57, 7 October 2013

	GP	Data Management	Version:	0.3
	Document type:	Generic Pattern	Owner:	J.A.H. Schoonderbeek

Description

This Generic Pattern belongs to "Core". This Pattern provides the functionality required to manage and make use of "strictly structured data", i.e. it controls the organization, querying, and retrieval of sets of organized data. The Pattern offers functionality to support one or more of the following:

a "modeling language";
a "query language";
a "transaction mechanism".

Services realized

This Pattern realizes the following service(s):

Data Management (This service provides its consumers the ability to manage strictly structured data.)

Functional and Integration view

This is the graphic representation of the functional model of this Generic Pattern:

Generic Pattern Composition

This pattern is an aggregation of the following (mandatory and optional) functions, expressed in Generic Functions:

Icon	Function	Inclusion	Rationale
	Data Engine	recommended	The Data Engine offers various ways to manipulate, query and manage data that is being stored by the structured data store function.
	Structured Data Store	recommended	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.
	Controlling	recommended	When allowing consumers (such as users and/or administrators) the ability to change the configuration of the Data Management facility, special care may be required to prevent unauthorized access to data stored by the Pattern.
	Caching	optional	Since the Data Management pattern underlies many other infrastructure facilities and applications, there often are requirements to guarantee a certain performance level, for which this Caching functionality may provide a significant boost. However, caching introduces additional challenges related to data being consistent and up-to-date, security risks for sensitive data residing in cache memory, et cetera.

Services connected with this Generic Pattern

This Generic Pattern has the following mandatory and optional relations with adjacent Generic Services.

Service	Adjacency	Summary	Rationale
File Storage	recommended	This service offers clients the ability to store, retrieve and modify data in loosely structured form.	Every Data Management pattern must store its data at a lower data level, which means it requires the use of a File Storage service. Even in commercial products that request access to Raw Storage this is true, as these products actually provide the File Storage functionality themselves.
Authentication & Authorization	optional	This service can validate an identity claim, and it can validate the permissions required for an action, as part of an Authentication & Authorization process.	A suitable source for identity and permission information may be required for controlling access to the data stored in the Data Management facility; management of the data; managing the behaviour of the Data Management facility itself, using the Controlling functionality.
Archive Management	optional	This service provides the ability to create and use archives.	The Pattern may need to archive (parts of) a structured data set, and/or may require access to an archive containing (parts of) a structured data set, in order to fulfil requests from its clients; furthermore, it may be necessary to migrate (parts of) an active structured data set to an archive. For any of this, the Data Management pattern needs access to an Archive Management service.

Applied Patterns based on this Generic Pattern

The following Applied Patterns are based wholly or in part on this Generic Pattern:

@@ Line 1: / Line 1: @@
-{{Maturity|3}}
+{{Maturity|4}}
 {{Pageheaderbox4GP
 |name=Data Management
@@ Line 5: / Line 5: @@
 |version=0.3
 |owner=Jan Schoonderbeek
-|summary=This Pattern provides the ability to manage and make use of "strictly structured data", i.e. it controls the organization, querying, and retrieval of sets of strictly structured data.
+|summary=This Pattern provides the ability to manage and make use of "strictly structured data", i.e. it controls the organization, querying, and retrieval of sets of organized data.
 }}
-This Pattern provides the ability to manage and make use of [[OIAm data view|"strictly structured data"]], i.e. it controls the organization, querying, and retrieval of sets of strictly structured data. The Pattern offers functionality to support one or more of the following:
+This Pattern provides the functionality required to manage and make use of  [[OIAm data view|"strictly structured data"]], i.e. it controls the organization, querying, and retrieval of sets of organized data. The Pattern offers functionality to support one or more of the following:
 * a "modeling language";
 * a "query language";
 * a "transaction mechanism".
 {{Pattern Realizes
 |service=GS.Data Management
@@ Line 25: / Line 24: @@
 |function=GF.Data Engine
 |choice=Must
-|reason=The Data Engine offers various ways to preserve, retrieve, manipulate and manage data that is being stored by the structured data store function.
+|reason=The Data Engine offers various ways to manipulate, query and manage data that is being stored by the structured data store function.
 }}
 {{Generic Pattern Composition Row
@@ Line 35: / Line 34: @@
 |function=GF.Controlling
 |choice=Must
-|reason=When allowing clients and/or administrators the ability to change the configuration of the Data Management facility, special care may be required to prevent unauthorized access to data stored by the Pattern.
+|reason=When allowing consumers (such as users and/or administrators) the ability to change the configuration of the Data Management facility, special care may be required to prevent unauthorized access to data stored by the Pattern.
 }}
 {{Generic Pattern Composition Row
 |function=GF.Caching
 |choice=May
-|reason=Since the Data Management pattern underlies many other infrastructure facilities and applications, there often are requirements to guarantee a certain performance level, for which this Caching functionality may provide a significant boost. However, caching introduces additional challenges related to data being up-to-date, security risks for sensitive data residing in cache memory, et cetera.
+|reason=Since the Data Management pattern underlies many other infrastructure facilities and applications, there often are requirements to guarantee a certain performance level, for which this Caching functionality may provide a significant boost. However, caching introduces additional challenges related to data being consistent and up-to-date, security risks for sensitive data residing in cache memory, et cetera.
 }}
 {{Table Ending}}