User

Go up to Terms and Definitions

A User is a person, Organization, or system that interacts with or uses a system, service, or resource to achieve a purpose.

A User can interact through:

• A user interface
• An application programming interface
• An Endpoint
• A command-line interface
• An automation interface
• A service request
• A message
• A delegated process
• Another supported interaction mechanism

A User can identify:

• Its identity
• Its name
• Its type
• Its associated Organization
• Its assigned Roles
• Its permissions
• Its credentials
• Its applicable authentication method
• Its applicable authorization
• Its applicable Governance Domains
• Its applicable Policies
• Its applicable Governance Policies
• Its Provenance
• Its Traceability

A User can act in one or more Roles. The assigned Role establishes the responsibilities, permissions, and expected behaviors applicable to a particular interaction.

person, Organization, or system that interacts with or uses a system, service, or Resource to achieve a purpose

Adapted from:

• DIDO Reference Architecture
• DIDO Reference Implementation Conceptual Model
• DIDO-TE draft Requirements Register

A User does not need to be a human. An Organization or automated system can act as a User when it interacts with or uses another system, service, or Resource.

A User differs from a Role:

• A User identifies the person, Organization, or system that interacts with or uses a capability
• A Role identifies the responsibilities, permissions, and expected behaviors assigned to that User

A User can act in multiple Roles. Multiple Users can act in the same Role.

A User differs from an Organization:

• An Organization is an identifiable body structured to pursue defined purposes and exercise assigned responsibilities
• A User is an interacting or using party

An Organization becomes a User in a particular context when the Organization interacts with or uses the applicable system, service, or Resource.

A User differs from a Node:

• A User uses or interacts with a system, service, or Resource
• A Node is an identifiable participant that performs one or more assigned Roles in a distributed system

The same system can act as both a User and a Node when it satisfies both definitions.

A User identity does not by itself establish permission to perform an action. The applicable Role, authorization, and Governance Policy determine the permitted actions.

A person uses DIDO-TE to initiate a Test Run.

The person is the User. The person acts in the Test Operator Role.

The Test Operator Role permits the User to:

• Select an approved Test Definition
• Select an approved Test Environment
• Supply permitted Test Argument Values
• Initiate Test Execution
• Monitor the Test Run
• View the resulting Test Results

The User cannot approve the resulting Validation Decision unless the applicable Governance Policy also assigns the required approval Role.