Applications often have the following attributes;
- they are used by users to execute business processes
- provide functional supports for specific business capabilities or processes within UCD
- depend upon Technical Component(s) to function - typically a cloud service or a software product
- used natively or tailored (configured or customised) to fit UCD requirements
- described using a unique internal name that is understood across UCD
encompassing...
- on-premise and cloud hosted
- off-the-shelf and bespoke developed
- internally and externally managed
- paid (subscription, a one-time fee) and free of charge solutions
Applications v Technical Components
It is essential to distinguish between the Application and the underpinning Technical Components upon which it relies.
The table below aims help explain the difference
| Application |
Technical Component (Product) |
|
| Does it directly provide support to business capabilities or business processes? |
Yes |
No |
| Does it provide business benefits on its own? |
Yes |
No |
| Does it have a service desk? |
Yes |
Maybe |
| Does it have an internal name or business-related name that is known by the end user? |
Yes |
Maybe |
| Can an end user work with it? |
Yes |
Maybe |
| Can it be used in different applications? |
No |
Yes |
| Is it a standard IT product such as an operating system, infrastructure component, or database? |
No |
Yes |
.png)
Abstract Examples
A simple cloud based application may have a single technology / technical component - the underpinning software-as-a-service itself [Application X]
A more complex application may have a number of technologies / technical components[Application Y]
The same technology / technical component can be used in more than one application [Product 1]
Naming of Applications
For many simple Software-as-a-Service based Applications, the name of the Application and the name of the underpinning Technology (the SaaS product) are often the seen as the same thing.
For many others Applications, the name intentionally differs from the underpinning Technology,
- to enhance clarity to non-technical stakeholders
- to create custom UCD branding
- to distinguish between the local implementationand the generic technology stack
- decouple from name changes in the vendor's product lineup
.png)
Worked Examples
| Application |
Technical Component |
| EA Tool |
Alfabet Accelerator |
| Google Drive |
Google Workspace for Education Plus |
| Google Calendar |
Google Workspace for Education Plus |
UCD IT Services
Computer Centre, University College Dublin, Belfield, Dublin 4, Ireland.Contact us via the UCD IT Support Hub: www.ucd.ie/ithelp