Generic Pattern Overview: Difference between revisions
Jump to navigation
Jump to search
mNo edit summary |
No edit summary |
||
| Line 27: | Line 27: | ||
|'''Generic Pattern''' | |'''Generic Pattern''' | ||
|'''Description''' | |'''Description''' | ||
|'''[[Property: | |'''[[Property:Belongs_to_infrastructure_Service_Category|Service Category]]''' | ||
|'''[[Property:Page_maturity|Maturity]]''' | |'''[[Property:Page_maturity|Maturity]]''' | ||
|- | |- | ||
Revision as of 10:40, 26 November 2019
This page contains the links to all 16 Generic Patterns that this OIAm repository positions in the infrastructure landscape. They are grouped by the infrastructure sector to which they belong.
| Generic Pattern | Description | Sector | Maturity |
| Access Distribution | This function serves to increase the maximum load that a given resource can handle, and/or allowing access to instances of the resource spread over multiple sites. | Business Support
|
3 |
| Managed File Transfer | This Pattern provides a means to transport loosely structured data from a source to one or more targets, either ad hoc or structurally.. | Business Support
|
3 |
| Access Security | An implementation of this Pattern can be used to secure access to back-end resources. | Business Support
|
3 |
| Application Hosting | The Application Hosting function can accommodate (business) application services. | Business Support
|
4 |
| Content Hosting | This pattern hosts relatively static content, and makes it available to authorized users in a suitable form. | Business Support
|
3 |
| Workspace | This Pattern models a gateway between the physical and digital world, such as a user workspace. | Commons
|
4 |
| Message Handling | This Pattern accepts messages from senders, and then handles transport, storage, and delivery to recipients. | Commons
|
4 |
| File Storage | This Pattern offers functionality to manipulate (store, retrieve and modify et cetera) data in loosely structured form (e.g. files). | Core
|
4 |
| Authentication & Authorization | Helps to secure IT facilities and applications by validating digital identities and permissions. | Core
|
3 |
| Data Transport | This Pattern provides the means to transport digital data between automated systems. | Core
|
2 |
| Data Zone Protection | This Pattern realizes a security separation between different Data Transport zones. | Core
|
4 |
| Raw Storage | This Pattern offers functionality for the storage and retrieval of unstructured data at a single, logical location; it may also provide "intelligence" to administrators and/or consumers. | Core
|
4 |
| Data Protection & Archive Management | This Pattern can help to realize a level of data protection for sets of data and/or convert these sets into archives. | Operations
|
2 |
| Facilities Monitoring | This Pattern helps Operations and Security personnel to monitor other facilities for noteworthy events. | Operations
|
3 |
| Facilities Deployment | This Function can deploy the software part of an IT (sub)system, and/or configurations thereof. | Operations
|
3 |
| Identity & Permission Management | Instances of this Generic Pattern are able to maintains the propagation and consistency of digital identities and digital permissions that are recognized within the organization. | Operations
|
3 |
Note: the following Pattern Definition is a proposal:
| Generic Pattern | Description | Service Category | Maturity |
| Relational Data Management | This Pattern provides the function layout to model "strictly structured data" handling, in a relational fashion. |
There are no deprecated Generic Patterns.
| Generic Pattern | Description | Sector | Maturity |