Computing
| Term | Definition |
|---|---|
| Algorithm | A sequence of computational steps for processing data to achieve a particular outcome. Algorithms can range from the simple (add up a set of numbers) to the complex (use complicated mathematics to search for patterns in image data). Algorithms are usually described generally, as mathematics or in words, in contrast to computer programs which are written in specific computer languages. |
| Analysis | Also Data Analysis. Techniques that produce knowledge from organised information. Processes of inspecting, cleaning, transforming, and modelling data with the goal of highlighting useful information, suggesting conclusions and supporting decision making. Data analysis has multiple facets and approaches, encompassing diverse techniques under a variety of names, in different business, science, and social science domains. See also: Data Analysis π. |
| Application Deployment | The process of installing, configuring, and making software applications available for use within a given environment (eg, a Trusted Research Environment (TRE)). |
| Application Programming Interface (API) | A type of software interface that provides a way for two or more computer programs to communicate with each other. In contrast to a user interface, which connects a computer to a person, an application programming interface connects computers or pieces of software to each other. |
| Application Stack | A number of applications, tools and other software that work in concert to form a complete software solution. |
| Artificial Intelligence (AI) | A branch of computer science that aims to create technology and systems that perform tasks and make decisions in ways that resemble human intelligence. AI systems can be built in various ways, with the most common current method being Machine Learning. Examples: A chess-playing computer program is an example of a specialised AI system (it can play chess, but nothing else). The programs inside a modern robot that can climb stairs and walk over uneven ground is an example of a more general AI system. See also: Machine Learning (ML). |
| Automated Disclosure Control | Disclosure control (qv) without the intervention of a human being each time. Automated disclosure control aims to capture the necessary rules for ensuring a given dataset cannot be used to identify any individual in an automated software system. See also: Disclosure Control. |
| Authorisation | Authorisation is a process of verifying that a person or other agent can legitimately take some action, such as gaining access to a dataset, editing a document, entering a building or making a payment. An administrative authority must determine whether there are sufficient grounds for authorising the action. Authorisation is often shortened to "AuthZ" to disntinguish it from authentication. See also: AAI; Access Control; Authentication. See also: Authorisation π. |
| Cloud Computing | A model of computer access or provision where users rent computer power remotely, rather than buying and installing their own hardware locally. Cloud computing may be described as "public cloud", meaning available to anyone from a wide number of cloud computing companies, or as "private cloud" or "on-premises" (or "on-prem") cloud, meaning installed and provided privately by, for example, a firm for its own uses. Examples: Microsoft Azure, Amazon Web Services (AWS) and Google Cloud Platform (GCP) are large, public cloud providers. |
| Cloud Storage | Computer data storage hosted by a cloud computing firm rather than provided locally. Access to cloud storage requires an Internet connection, in contrast to local storage which is either attached to a user's computer or needs only a local network connection. Examples: Apple's iCloud storage, Google's Drive or Microsoft OneDrive are examples of cloud storage. |
| Code Control | The management and oversight of software code (programs) or source files, including versioning, change tracking, access control and collaboration. Contrast with: Code Lists. |
| Command Line Interface (CLI) | A text-based interface or environment that allows users to interact with a computer or software by typing commands or instructions, in contrast to a graphical user interface. See also: Graphical User Interface (GUI). |
| Common Workflow Language (CWL) | An open standard for describing how to run software tools using command line interfaces, and how to chain them together to create workflows. See also: Command Line Interface (CLI); Workflow. |
| Demilitarized Zone (DMZ) | A physical or logical subnetwork that separates an internal TRE network from untrusted external networks, such as the internet. The DMZ provides limited access to internal networks based on trust. see also: zone |
| Desktop | The Graphical User Interface (GUI) and environment presented to users on their computer screens, typically including icons, menus, and windows for interacting with applications and files. |
| Desktop Applications | Software applications designed to be installed and run on individual computers or Desktop systems, often providing specific functionalities or tools. |
| Federated Analytics | A form of analytics where data analysis happens across multiple independent organisations, with each organisation keeping complete control of their own data. Instead of combining all data in one place, the analysis program or Workflow is sent to each organisation's data. For example, multiple hospitals could participate in medical research by running the same analysis on their local patient records, then sharing only the summarized statistical results. The raw patient data would never leave each hospital, but researchers could still draw insights from the combined statistical findings across all participating hospitals. See also: Data Pooling; Federated Data. |
| Federated Data | A model of data access in which different organizations keep full control of their own data but agree on ways to safely share access to it for specific purposes. Each organization maintains its own data security and rules, but allows approved users to work with the data through agreed-upon tools and systems. For example, research institutions might share access to their datasets while keeping the data within their own secure environments, allowing collaborative research without moving sensitive data to a central location. See also: Data Pooling; Federated Analytics. |
| Federated Identity Mapping | See: Federated Identity π. |
| Federated Learning | See: Federated Learning π. |
| Federated Query | See: Federated Analytics. |
| Graphical User Interface (GUI) | A way of interacting with a computer system based on visual presentations of documents, applications and so on as windows on a screen. Users interact with a GUI using pointing devices (e.g. a mouse or a finger) rather than having to type everything. Contrast with: Command Line Interface (CLI). |
| Interoperability | The ability of two or more systems, devices, or applications to exchange and use information seamlessly. Interoperability enables these systems to work together, often through the adoption of open standards, that facilitate consistent communication and data sharing without requiring custom intergration. Good interoperability promotes collaboration, scalability, and the extension of services by allowing different systems to work together in a standarised, vendor-neutral way, thereby reducing techinal and operational barriers. See also: Interoperability π. |
| Issue Management Process | A systematic approach to identifying, tracking, resolving, and managing issues or problems that arise within a TRE organisation, aiming to minimise their impact and ensure timely resolution. Common mechanisms to manage the effective resolution of such issues can include Corrective and Preventive Actions (CAPAs), which enable such instances to be documented and provide an audit trail of activities undertaken to prevent recurrence. |
| IT Service Provider | A company, department, or entity that delivers information technology services or support to internal or external clients, such as network management, software development, or helpdesk support. |
| Minimum Viable Product (MVP) | A version of a product or service that has the minimum set of features and functionality required to meet the needs of early adopters or customers. The goal of an MVP is to quickly validate the product idea and test the market demand, while minimizing development costs and time-to-market. |
| On-premises | Also "on-prem". See Cloud Computing. |
| Orchestration Zone (OZ) | The zone managing the deployment and maintenance of infrastructure and the configuration of the TRE. This zone contains no research data and is not be accessible to any researcher/project role. Infrastructure management roles operate within this zone. See also: zone. |
| Private Cloud | See Cloud Computing. |
| Public Cloud | See Cloud Computing. |
| Query Management Zone (QMZ) | The zone handling queries sent to the TRE from other, remote TREs or external Job Submission services. Typically it sits alongside a Research Analytics Zone (RAZ) and provides different methods of access to approved research-ready datasets stored within the Secure Data Zone (SDZ) . See also: zone. |
| RegistryΒ | A centralised database, repository, or system that stores and manages information, configurations, or records related to specific entities, such as users, systems, or resources. |
| Research Analytics Zone (RAZ) | The zone providing the means for a researcher to gain direct access to the data their project is approved to use, in an environment suitable for the analyses their research requires. This is often realised as a virtual desktop environment, a computational notebook or similar. There is often a strict requirement that project environments be completely isolated from one another. See also: zone. |
| Secure Data Zone (SDZ) | Zone supporting the management, linkage, curation and provision of research-ready sensitive datasets. Governance roles and Data Managers operate in the SDZ. See also: zone. |
| Structured Query Language (SQL) | A computer programming language designed to organise and work with structured data stored in databases. It allows people to find and use data from databases easily. See also: Structured Data. |
| Technology Stack | The set of technologies (such as programming languages) that work together to implement a software solution. |
| Text Analytics | The process of examining and understanding written information, like electronic health records or other text-based content, to find important and useful insights. It involves analysing the text to identify patterns, trends, or valuable information that can be used for various purposes, such as research or decision-making. |
| TRE Infrastructure | The set of computing resources used to implement and support a TRE. This may include desktop computers, databases, networking devices, firewalls etc. These resources may be physical (hardware owned by the TRE) or virtual (e.g. resources operated by a cloud provider). |
| User Documentation | Written materials, guides, manuals, or instructions to assist users. Documentation typically includes information on features, step-by-step procedures and best practices to make it easier for Users to work. An example of this would be user manuals, quick start guides or troubleshooting sections on websites. |
| User Interface (UI) | See Graphical User Interface (GUI); Command Line Interface (CLI). |
| User Onboarding | The process of introducing and integrating users into an organisations systems and processes. It helps people understand features and learn how to use something effectively. For example, when you download a new app, there is often a step-by-step tutorial on how to make the most of the software. |
| Workflow | Specifically a computational workflow is a set of chained operations used to carry out a particular analysis or other computational task. Workflows simplify complex sequences of activities and enable researchers to automate and track the provenance of the work in workflow execution. Workflows can often be visualised as a network or tree of operations. |
| Zone | A distinct area within a TRE that has specific security, access, or functional characteristics. Zones require different levels of governance and approval for the roles accessing them, and in particular, movement of data between them should be subject to appropriate controls to manage the related disclosure risks. see also: Orchestration Zone (OZ). see also: Query Management Zone (QMZ). see also: Research Analytics Zone (RAZ). see also: Secure Data Zone (SDZ). |