Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
| public:99_annexes:annex-b-terms-and-definitions:u:user [2026/09/12 17:42] – removed - external edit (Unknown date) 127.0.0.1 | public:99_annexes:annex-b-terms-and-definitions:u:user [2026/09/12 17:43] (current) – ↷ Links adapted because of a move operation nick_dido | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | ====== User ====== | ||
| + | [[public: | ||
| + | |||
| + | ===== Discussion ===== | ||
| + | |||
| + | A User is a person, [[public: | ||
| + | |||
| + | A User can interact through: | ||
| + | |||
| + | * A user interface | ||
| + | * An application programming interface | ||
| + | * An [[public: | ||
| + | * 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 [[public: | ||
| + | * Its permissions | ||
| + | * Its credentials | ||
| + | * Its applicable authentication method | ||
| + | * Its applicable authorization | ||
| + | * Its applicable [[public: | ||
| + | * Its applicable [[public: | ||
| + | * Its applicable [[public: | ||
| + | * Its [[public: | ||
| + | * Its [[public: | ||
| + | |||
| + | A User can act in one or more Roles. The assigned Role establishes the responsibilities, | ||
| + | |||
| + | ===== Definition ===== | ||
| + | |||
| + | //person, [[public: | ||
| + | |||
| + | ===== Source ===== | ||
| + | |||
| + | Adapted from: | ||
| + | |||
| + | * DIDO Reference Architecture | ||
| + | * DIDO Reference Implementation Conceptual Model | ||
| + | * DIDO-TE draft Requirements Register | ||
| + | |||
| + | ===== Note ===== | ||
| + | |||
| + | 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 [[public: | ||
| + | |||
| + | * A User identifies the person, Organization, | ||
| + | * A Role identifies the responsibilities, | ||
| + | |||
| + | A User can act in multiple Roles. Multiple Users can act in the same Role. | ||
| + | |||
| + | A User differs from an [[public: | ||
| + | |||
| + | * 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 [[public: | ||
| + | |||
| + | * 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, | ||
| + | |||
| + | ===== Example ===== | ||
| + | |||
| + | A person uses DIDO-TE to initiate a [[public: | ||
| + | |||
| + | The person is the User. The person acts in the Test Operator Role. | ||
| + | |||
| + | The Test Operator Role permits the User to: | ||
| + | |||
| + | * Select an approved [[public: | ||
| + | * Select an approved [[public: | ||
| + | * Supply permitted [[public: | ||
| + | * Initiate Test Execution | ||
| + | * Monitor the Test Run | ||
| + | * View the resulting [[public: | ||
| + | |||
| + | The User cannot approve the resulting Validation Decision unless the applicable Governance Policy also assigns the required approval Role. | ||
| + | |||
| + | ---- | ||
| + | |||
| + | <WRAP centeralign> | ||
| + | © 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc. | ||
| + | </ | ||