From OIAr Archive 2013
Jump to navigation Jump to search
Page maturity
This page has maturity level 1 (stub)

This is a Pattern document

Document icon PAV Authentication&Authorization.Local Version: 0.1 OIAr logo
Document type: Pattern Variant Owner:

J.A.H. Schoonderbeek

Pattern Variant Lineage

This Pattern Variant is based on the following Pattern Type(s):

Pattern Type Description
Authentication & Authorization Secures usage of facilities and applications by validating identities and permissions

Business purpose

This Pattern supports facilities and devices, so it indirectly supports their business purposes.


An instance of this Pattern Variant supports local security to a facility or device. It offers a means for entities to identify or authenticate themselves, and offers authorization services for actions on local resources.

Characteristics & indications of usage

This service is offered locally either because centralized A&A is not available (e.g. because the facility is mobile) or because local A&A has not been disabled in favour of centralized A&A.

Graphical Overview

This is the graphical representation of the infrastructure functions in this Pattern Variant, plus their main relations:

No graphic yet.png
No graphic yet.png

Pattern Variant Composition

This pattern has the following subfunctions, expressed in Building Block Variants:

Environment WA Function check Rationale

Pattern Variant Neighbors

This pattern has the following relations with adjacent (sub)facilities, expressed in Building Block Variants (BBV) and Pattern Variants (PAV). Note: if the table below is empty, then there are no architecturally prescribed relations with adjacent facilities:

Facility Type Environment Description


When designing a facility to implement this Pattern, inclusion of all the following Elements is prescribed; either mandatory, optional or explicitly forbidden. This comes in addition to the Elements prescriptions inside the individual Building Block Variants included in this Pattern:

Element Type Prescribed Rationale

Quality Requirements

When a facility is designed according to this architectural recipe, it must/will satisfy the following Quality Requirements. This is the responsibility of the infrastructure designer. Note that because of the Building Block Variants specified for this Pattern Variant, some of these Requirements might automatically be satisfied.

QA Group Quality Attribute Value
Flexibility Adaptability NS
Scalability NS
Maintainability Manageability NS
Accountability NS
Reliability Availability NS
Integrity NS

More Pattern Variant Neighbours

The following adjacent (sub)facilities, expressed in Pattern Variants (PAV), have a relation with this Pattern Variant. Note: if the table below is empty, then there currently aren't any infrastructure facilities using this Pattern Variant:

Facility Relation Description
User Workspace.Tablet uses this Pattern Variant -

Design Outlines realized with this Variant

No Design Outlines are realized with this Variant (yet)