SD.Application Database: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| (3 intermediate revisions by the same user not shown) | |||
| Line 8: | Line 8: | ||
}} | }} | ||
It provides a data store for applications with a predefined structure. | It provides a data store for applications with a predefined structure. | ||
{{Service | {{Service Used Services}} | ||
{{Service | {{Service Used Service Row | ||
|service=SD.Database File Handling | |service=SD.Database File Handling | ||
|choice=Must | |choice=Must | ||
|reason=Every Database service must store its data at a lower [[OIAm data view|data level]], which means it requires the use of a File Handling service. Even in commercial products that request access to Mass Storage this is true, as these products actually provide the File Handling functionality themselves. | |reason=Every Database service must store its data at a lower [[OIAm data view|data level]], which means it requires the use of a File Handling service. Even in commercial products that request access to Mass Storage this is true, as these products actually provide the File Handling functionality themselves. | ||
}} | }} | ||
{{Service | {{Service Used Service Row | ||
|service=GS.Authentication+Authorization | |service=GS.Authentication+Authorization | ||
|choice=May | |choice=May | ||
| Line 22: | Line 22: | ||
* managing the behaviour of the Data Management facility itself, using the Controlling functionality. | * managing the behaviour of the Data Management facility itself, using the Controlling functionality. | ||
}} | }} | ||
{{Service | {{Service Used Service Row | ||
|service=GS.Data Protection Management | |service=GS.Data Protection Management | ||
|choice=May | |choice=May | ||
|reason=The data being handled by this Pattern may need to be protected against data corruption and/or loss. Even though this might be delegated to the lower level of the [[GS.File_Storage|File Storage]] service that the Pattern uses, it's usually much better to handle data protection at the logical level of this Pattern, as at this level the interdependencies of parts of the datasets is known and controllable. | |reason=The data being handled by this Pattern may need to be protected against data corruption and/or loss. Even though this might be delegated to the lower level of the [[GS.File_Storage|File Storage]] service that the Pattern uses, it's usually much better to handle data protection at the logical level of this Pattern, as at this level the interdependencies of parts of the datasets is known and controllable. | ||
}} | }} | ||
{{Service | {{Service Used Service Row | ||
|service=GS.Archive Management | |service=GS.Archive Management | ||
|choice=May | |choice=May | ||
| Line 34: | Line 34: | ||
{{Table Ending}} | {{Table Ending}} | ||
{{Text Footer SD}} | {{Text Footer SD}} | ||
{{clear}} | |||
Latest revision as of 18:19, 28 November 2019
 | Page maturity This page has maturity level 0 (proposal) |
|
SD | Application Database | Version: | 0.2 | 
|
|---|---|---|---|---|---|
| Document type: | Service Definition | Owner: |
 | This service provides a data store for applications with a predefined structure |
Description
This Service Definition belongs to the Service Category "Data Management".
It provides a data store for applications with a predefined structure.
Used Services
This kind of Service (often) uses/is depending on the following Service(s). In ArchiMate (relation) terms, the service is "served by" this/those service(s):
| Service | Usage | Summary | Rationale |
| Database File Handling | recommended | This service offers databases the ability to store, retrieve and modify database data | Every Database service must store its data at a lower data level, which means it requires the use of a File Handling service. Even in commercial products that request access to Mass Storage this is true, as these products actually provide the File Handling 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
|
| Data Protection Management | optional | This service provides the ability to protect data against accidental or wilful corruption. | The data being handled by this Pattern may need to be protected against data corruption and/or loss. Even though this might be delegated to the lower level of the File Storage service that the Pattern uses, it's usually much better to handle data protection at the logical level of this Pattern, as at this level the interdependencies of parts of the datasets is known and controllable. |
| 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. |
Services being served by this service
The following service is registered in this repository to be dependent on this service:
There are no services registered in this repository that may be served by this service. No result
Underlying Pattern Definition(s)
The following Pattern Definition is available to model an aggregated function that realizes this kind of service:
| Service | Description |
| Generic Application Hosting | This service enables business application execution and usage. |
| Pattern Definition | Description |
| Relational Data Management | This Pattern provides the function layout to model "strictly structured data" handling, in a relational fashion. |