Generic Pattern: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
m (Jan Schoonderbeek moved page Pattern Type to Generic Pattern: rename) |
||
| (One intermediate revision by the same user not shown) | |||
| Line 1: | Line 1: | ||
__NOFACTBOX__{{#vardefine: | __NOFACTBOX__{{#vardefine:GP|{{#ask: [[Category:Pattern Type]][[Page maturity::>0]][[Page maturity::<9]]|format=count}}}}{{#vardefine:proposedGP|{{#ask: [[Category:Pattern Type]][[Page maturity::0]]|format=count}}}}{{#vardefine:obsoleteGP|{{#ask: [[Category:Pattern Type]][[Page maturity::9]]|format=count}}}} | ||
[[Image:Icon | [[Image:Icon GP.png|100px|left|Pattern]]A Generic Pattern is a set of Generic Functions that define the possible behaviour of (part of) an infrastructure Product/Solution. A Generic Pattern describes an archetypical architecture of a solution, being technology and implementation and organization agnostic. One ore more Generic Patterns serve as archetypes for the modelling of a [[:Category:Applied Pattern|Applied Pattern]], that outlines a solution at the Functional Design level. It houses the general description of the intended functionality of the Applied Patterns based upon it. The full set of Generic Patterns form the universal and basic structure of all Infrastructure Landscapes. A clickable map of the Generic Patterns that together form the archetype of the Infrastructure Landscape is depicted below: | ||
<imagemap> | <imagemap> | ||
| Line 31: | Line 31: | ||
</imagemap><br><br><br> | </imagemap><br><br><br> | ||
{{#var: | {{#var:GP}} Generic Patterns are defined in this wiki, excluding {{#var:proposedGP}} GPs under consideration, and {{#var:obsoleteGP}} obsoleted GPs. Click on the Generic Pattern names in the table below to access their descriptions/definitions and the [[Generic Functions Overview|Generic Functions]] they are composed of: | ||
<br style="clear:both"/> | <br style="clear:both"/> | ||
{| {{prettytable}} | {| {{prettytable}} | ||
|-align="center" style="color:#{{FGColour03}}; background-color:#{{BGColour03}};" | |-align="center" style="color:#{{FGColour03}}; background-color:#{{BGColour03}};" | ||
|Pattern | |Generic Pattern||Function||Mandatory GFs||Optional GFs||Sector||Maturity | ||
{{#ask:[[Category:Pattern Type]][[Page maturity::>0]][[Page maturity::<9]] | {{#ask:[[Category:Pattern Type]][[Page maturity::>0]][[Page maturity::<9]] | ||
|format=template|template=TableOfPatterns|userparam=Type|link=none | |format=template|template=TableOfPatterns|userparam=Type|link=none | ||
| Line 42: | Line 42: | ||
|} | |} | ||
Note: the following {{#var: | Note: the following {{#var:proposedGP}} Generic Patterns have been proposed. | ||
{| {{prettytable}} | {| {{prettytable}} | ||
|-align="center" style="color:#{{FGColour03}}; background-color:#{{BGColour03}};" | |-align="center" style="color:#{{FGColour03}}; background-color:#{{BGColour03}};" | ||
|Pattern | |Generic Pattern||Function||Mandatory GFs||Optional GFs||Sector||Maturity | ||
{{#ask:[[Category:Pattern Type]][[Page maturity::0]] | {{#ask:[[Category:Pattern Type]][[Page maturity::0]] | ||
|format=template|template=TableOfPatterns|userparam=Type|link=none | |format=template|template=TableOfPatterns|userparam=Type|link=none | ||
| Line 52: | Line 52: | ||
|} | |} | ||
Note: the following {{#var: | Note: the following {{#var:obsoleteGP}} Generic Patterns have been obsoleted. | ||
{| {{prettytable}} | {| {{prettytable}} | ||
|-align="center" style="color:#{{FGColour03}}; background-color:#{{BGColour03}};" | |-align="center" style="color:#{{FGColour03}}; background-color:#{{BGColour03}};" | ||
|Pattern | |Generic Pattern||Function||Mandatory GFs||Optional GFs||Sector||Maturity | ||
{{#ask:[[Category:Pattern Type]][[Page maturity::9]] | {{#ask:[[Category:Pattern Type]][[Page maturity::9]] | ||
|format=template|template=TableOfPatterns|userparam=Type|link=none | |format=template|template=TableOfPatterns|userparam=Type|link=none | ||
Latest revision as of 13:57, 14 March 2013
A Generic Pattern is a set of Generic Functions that define the possible behaviour of (part of) an infrastructure Product/Solution. A Generic Pattern describes an archetypical architecture of a solution, being technology and implementation and organization agnostic. One ore more Generic Patterns serve as archetypes for the modelling of a Applied Pattern, that outlines a solution at the Functional Design level. It houses the general description of the intended functionality of the Applied Patterns based upon it. The full set of Generic Patterns form the universal and basic structure of all Infrastructure Landscapes. A clickable map of the Generic Patterns that together form the archetype of the Infrastructure Landscape is depicted below:
17 Generic Patterns are defined in this wiki, excluding 0 GPs under consideration, and 0 obsoleted GPs. Click on the Generic Pattern names in the table below to access their descriptions/definitions and the Generic Functions they are composed of:
| Generic Pattern | Function | Mandatory GFs | Optional GFs | Sector | Maturity |
| Access Distribution | Provides smart access to back-end facilities, providing services such as caching, health/capacity based load balancing etc. | J.A.H. Schoonderbeek | 3 | ||
| Access Security | Controls and secures (external) user connections with back-end facilities and applications | J.A.H. Schoonderbeek | 3 | ||
| Application Hosting | Accommodates (business) applications and services | ?S.A.D. Jumelet? | 3 | ||
| Content Hosting | Hosts content and makes it available in a suitable form(s) to users | J.A.H. Schoonderbeek | 3 | ||
| Streams Management | A generic pattern to send out and/or receive data in time-dependent streams, such as audio, video or gaming information | J.A.H. Schoonderbeek | 3 | ||
| Message Handling | Provides transport, storage and delivery of messages | S.A.D. Jumelet | 3 | ||
| Orchestration | Provides facilities to create, execute and control automated (business/application) workflows | S.A.D. Jumelet | 2 | ||
| User Workspace | Comprises a set of facilities that offer a digital workspace to end-users, that enables them to use and access applications and/or communicate with other end-users | S.A.D. Jumelet | 3 | ||
| Authentication & Authorization | Secures usage of facilities and applications by validating identities and permissions | J.A.H. Schoonderbeek | 3 | ||
| Data Management | Provides preservation, retrieval, manipulation and management of strictly structured data, such as databases | ?J.A.H. Schoonderbeek? | 3 | ||
| Data Transport | Comprises a set of facilities to transport data between automated systems | J.A.H. Schoonderbeek | 2 | ||
| Data Zone Protection | Controls and secures data exchange between two data transport zones | J.A.H. Schoonderbeek | 3 | ||
| File Storage | Carries out the storage and retrieval of loosely structured data at a single, logical location; can provide advanced functionality ("intelligence") to administrators and/or users. | J.A.H. Schoonderbeek | 4 | ||
| Raw Storage | Carries out the storage and retrieval of "raw bits" data at a single, logical location; optionally provides advanced functionality ("intelligence") to administrators and/or users. | J.A.H. Schoonderbeek | 4 | ||
| Facilities Deployment | Provides a set of facilities to automate the deployment and administration of platforms, applications and/or configurations | S.A.D. Jumelet | 3 | ||
| Facilities Monitoring | Comprises a set of facilities to enable centralized and intelligent monitoring of automated systems, either or both for system health care and security purposes | S.A.D. Jumelet | 3 | ||
| Identity & Permission Management | Provides consistent deployment and management of identity stores and/or permission registers | J.A.H. Schoonderbeek | 3 |
Note: the following 0 Generic Patterns have been proposed.
| Generic Pattern | Function | Mandatory GFs | Optional GFs | Sector | Maturity |
Note: the following 0 Generic Patterns have been obsoleted.
| Generic Pattern | Function | Mandatory GFs | Optional GFs | Sector | Maturity |