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:a:application [2026/09/12 17:42] – removed - external edit (Unknown date) 127.0.0.1 | public:99_annexes:annex-b-terms-and-definitions:a:application [2026/09/12 17:43] (current) – ↷ Links adapted because of a move operation nick_dido | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | ====== Application ====== | ||
| + | [[public: | ||
| + | |||
| + | ===== Discussion ===== | ||
| + | |||
| + | An Application is software that performs functions for users, [[public: | ||
| + | |||
| + | An Application includes one or more software components organised to provide a defined capability or set of capabilities. The concept does not prescribe a particular: | ||
| + | |||
| + | * Architecture | ||
| + | * Programming language | ||
| + | * Interface | ||
| + | * Deployment model | ||
| + | * Execution environment | ||
| + | * Infrastructure provider | ||
| + | * Distribution model | ||
| + | |||
| + | An Application includes software intended for direct human interaction and software that interacts only with other Applications, | ||
| + | |||
| + | An Application differs from [[public: | ||
| + | |||
| + | ===== Definition ===== | ||
| + | |||
| + | //software that performs functions for users, [[public: | ||
| + | |||
| + | ===== Source ===== | ||
| + | |||
| + | Adapted from general systems and software engineering usage. | ||
| + | |||
| + | DIDO Reference Implementation Conceptual Model | ||
| + | |||
| + | DIDO-TE draft Requirements Register | ||
| + | |||
| + | ===== Note ===== | ||
| + | |||
| + | The classification of software as an Application depends on its role within the relevant context. | ||
| + | |||
| + | Software treated as Infrastructure in one context may perform the role of an Application in another context. The applicable architecture, | ||
| + | |||
| + | An Application does not include the Infrastructure solely because the Infrastructure hosts, executes, stores, connects, or manages the Application. | ||
| + | |||
| + | ===== Example ===== | ||
| + | |||
| + | A sanctions-screening Application receives transaction data, applies screening rules, and returns screening results. | ||
| + | |||
| + | The Application performs the screening function. The compute, storage, networking, operating-system, | ||
| + | |||
| + | ---- | ||
| + | |||
| + | <WRAP centeralign> | ||
| + | © 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc. | ||
| + | </ | ||