PAV.Facilities Deployment.Vendor Market
|
PAV | Facilities Deployment.Vendor Market | Version: | 0.1 | 
|
|---|---|---|---|---|---|
| Document type: | Pattern Variant | Owner: |
Pattern Variant Lineage
This Pattern Variant is based on the following Pattern Type(s):
| Pattern Type | Description |
| Facilities Deployment | Provides a set of facilities to automate the deployment and administration of platforms, applications and/or configurations |
Business purpose
Devices that are used in the organization can be fitted with applications ("apps") that are obtained externally from this external market or store.
Description
This facility can deploy 3rd party apps to a specific class or brand of devices.
Characteristics & indications of usage
This facility or market is not under control of our organization. Furthermore, the apps obtained from this market are created by third parties, are not screened or approved by our organization, and may need to be paid for.
Because our employees have free access to this market by default, it is likely that they will obtain apps from this market.
Graphical Overview
This is the graphical representation of the infrastructure functions in this Pattern Type, plus their main relations:
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 |
Elements
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)