-
Notifications
You must be signed in to change notification settings - Fork 8
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #186 from sa-tre/update-computing-pillar
Update computing pillar
- Loading branch information
Showing
4 changed files
with
232 additions
and
200 deletions.
There are no files selected for viewing
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,80 +1,50 @@ | ||
# Commonly used terms | ||
|
||
(def_actor)= | ||
|
||
## Actor | ||
|
||
Definition of an actor | ||
|
||
(def_application_component)= | ||
|
||
## Application component | ||
|
||
Definition of a application component | ||
|
||
(def_application_service)= | ||
|
||
## Application service | ||
|
||
Definition of a application service | ||
|
||
(def_architectural_principle)= | ||
|
||
## Architectural principle | ||
|
||
Fundamental guidelines that inform the design, decision making and implementation of a TRE. | ||
These principles provide a framework to ensure that the design of the underlying components of a TRE are aligned to consistent goals, values and best practices. | ||
|
||
(def_business_data_object)= | ||
|
||
## Business data object | ||
|
||
Definition of decomposition | ||
|
||
(def_capability)= | ||
|
||
## Capability | ||
|
||
An ability that a system possesses. | ||
Capabilities are typically expressed in general and high-level terms and typically require a combination of organisation, people, processes, and technology to achieve. | ||
|
||
(def_capability_decomposition)= | ||
|
||
## Capability decomposition | ||
|
||
A set of components that realise a capability. | ||
These components will vary depending on the nature of the capability. | ||
Business-focused capabilities will be realised by business processes, roles and services. | ||
Technology-focused capabilities will be realised by applications, application services and interfaces. | ||
In addition to the components realising the capability, a catalogue of standards, frameworks and controls linked to the capabilities will provide guidance on how to implement the capabilities safely. | ||
|
||
(def_component)= | ||
|
||
## Component | ||
|
||
Definition of a component | ||
|
||
(def_process)= | ||
|
||
## Process | ||
|
||
Definition of a process | ||
|
||
(def_role)= | ||
|
||
## Role | ||
|
||
Definition of a role | ||
|
||
(def_specification_pillar)= | ||
|
||
## Specification pillar | ||
|
||
A specification pillar is a group of related capabilities. | ||
SATRE has four specification pillars: Information governance, Computing technology, Data management and Supporting Capabilities. | ||
|
||
(def_tre_organisation)= | ||
|
||
## TRE organisation | ||
|
||
A TRE organisation is the set of people, processes and technology that operate and use a particular TRE. | ||
```{glossary} | ||
Actor | ||
A person, organization, or system that has one or more roles that initiates or interacts with activities. | ||
Example: _The SATRE architecture needs actors such as researchers and internal auditors._ | ||
Application component | ||
An encapsulation of application functionality which is modular and replaceable. | ||
Example: _To perform work within a TRE a researcher might need access to a Desktop or command line interface application component._ | ||
Architectural principle | ||
Fundamental guidelines that inform the design, decision making and implementation of a TRE. | ||
These principles provide a framework to ensure that the design of the underlying components of a TRE are aligned to consistent goals, values and best practices. | ||
Business process | ||
A set of actions which produce a specific desired outcome. | ||
Example: _to access the TRE a researcher needs to complete an onboarding business process._ | ||
Capability | ||
An ability that a system possesses. | ||
Capabilities are typically expressed in general and high-level terms. | ||
Achieving a capability typically requires a combination of organisation, people, processes, and technology. | ||
Capability decomposition | ||
A set of {term}`components <component>` that realise a capability. | ||
These components will vary depending on the nature of the capability. | ||
Business-focused capabilities will be realised by {term}`business processes <business process>`, {term}`roles <role>` and services. | ||
Technology-focused capabilities will be realised by {term}`applications <application component>`, services and interfaces. | ||
In addition to the components realising the capability, a catalogue of standards, frameworks and controls linked to the capabilities will provide guidance on how to implement the capabilities safely. | ||
Component | ||
The statements concerning processes, controls, practices and applications that make up a {term}`capability <capability>`, together with an importance label. | ||
Data Object | ||
A store of data or information. | ||
For example: to know what data is stored within the TRE a study database data object is needed. | ||
This contains information on the data assets within the TRE, who owns them and other compliance information. | ||
Role | ||
A role is a set of connected behaviors, rights, obligations and norms within a TRE system. | ||
Roles are occupied by individuals, who are called {term}`actors <actor>`. | ||
Specification pillar | ||
A specification pillar is a group of related capabilities. | ||
SATRE has four specification pillars: Information governance, Computing technology, Data management and Supporting Capabilities. | ||
TRE organisation | ||
A TRE organisation is the set of people, processes and technology that operate and use a particular TRE. | ||
``` |
Oops, something went wrong.