PAT.User Workspace

From OIAr Archive 2013
Jump to navigation Jump to search
Informational
Informational
Page maturity
This page has maturity level 3 (usable)

This is a Pattern document

Document icon PAT User Workspace Version: 0.3 OIAr logo
Document type: Pattern Type Owner:

S.A.D. Jumelet


Informational
Informational
Create commentary

Description

This Pattern Type belongs to "Infrastructure Sector Commons". This Pattern models the generic user workspace. With it, all different variants of user workspaces can easily be modeled, including telephony solutions (that in some cases provides an additional workspace, dedicated to the application of telephony).

Note that the pattern depends on many adjacent patterns, which in turn will also have to be modeled in a fitting variant.

Graphical Overview

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

User Workspace
User Workspace


(The source file of this picture can be downloaded here).

Pattern Type Composition

This pattern has the following mandatory and optional subfunctions, expressed in Building Block Types:

Icon Function WA Inclusion Rationale
BT.Workspace Projection icon Workspace Accommodation CR mandatory This Building Block Type represents the functionality that is delivering the Workspace Presentation to the end-user and the device the end-user is using to 'receive' or access his workspace.
BT.User Input icon User Input CR mandatory This type of facility enables users to feed data into the Workspace. Note that if remote operation of the workspace is needed, then facilities of this type are located with the user at the remote location. This facility type has a broad range of possible applications, from document scanning facilities to bar code or finger print readers.
BT.User Output icon User Output CR mandatory Users most always need to be able to retrieve data from their Workspace in other formats than display on the main screen. Printouts are the main example here. Note that if remote operation of the workspace is needed, then this facility may be located with the user at the remote location, or it may be located elsewhere, depending on the output device and its purpose. For example, the user working from home may wish to print a document on a department printer instead of his/her personal printer.
BT.Presentation Engine icon Presentation Engine SE mandatory This facility covers the methods with which the workspace is exposed to the user. While this is a built-in facility for many workspace solutions (e.g. the ubiquitous PC), it is a design choice for many other solutions (e.g. Server Based Computing solutions), and has impact on the usability and feature-richness of the workspace, and on the technical facilities needed to support the workspace.
BT.Workspace Engine icon Workspace Engine CR mandatory This is the core component offering the workspace itself. It provides the run-time environment for client applications.


Pattern Type Neighbors

This pattern has the following mandatory and optional relations with adjacent (sub)functions, expressed in Pattern Types (PAT). Note: if the table below is empty, then there are no architecturally prescribed relations with adjacent subfunctions:

Function Adjacency Description
Data Transport mandatory This pattern takes care of all data transport between facilities inside this pattern, and also allows for access of the facility by clients. Note that data transport security is not handled within the User Workspace pattern itself.
Facilities Deployment optional If user workspaces should be deployed automatically, then this Pattern Type can take care of that.
optional This Pattern describes the communication solutions that are offered to end users in a centralized way, like Call Handling, Messaging and Mail solutions.
Raw Storage mandatory When users create or consume data, it needs to be stored and retrieved in a suitable manner. This pattern desribes these type of solutions.
Authentication & Authorization mandatory Since the User Workspace offers access to company resources, it's use needs to be checked against repositories with permission rules, presumably based on identities.


Pattern Variants based on this type

Pattern VariantBrief descriptionOwnermaturity
PAV.User Workspace.Corporate CentralUser Workspace.Corporate CentralJ.A.H. Schoonderbeek1
PAV.User Workspace.TabletUser Workspace.TabletJ.A.H. Schoonderbeek2