Applications
Solutions that provides functionality to UCD’s community, typically accessed through a web browser, mobile device, or desktop, or that provides functionality or capabilities to other applications.
Applications include on-premise hosted and cloud services; bespoke and packaged solutions; internally managed and externally managed by a third party; subscription and perpetual paid licences; as well as free or open source solutions.
Examples of Applications include Banner (student system), Tableau (analytics and business intelligence tools), and Terminal 4 (website content).
Note. Websites built on Terminal 4 are seen as “content” and not seen as an application. However a website spun up on internally or externally managed web servers or hosting platforms is seen as an application in its own right.
Typical features include they;
- are used by users to execute business processes
- provide functional supports for specific business capabilities or processes within UCD
- depend upon an underpinning Technical Products to function - typically a cloud service or a software package installed on on-premise hardware
- are often tailored to fit UCD requirements
- are described using a common name that is understood across UCD
Foundational Platforms
Foundational Platforms are a specific class of application that provides a pre-integrated ecosystem of applications (for example Microsoft 365) , or provide the capability to build new applications (for example Infohub, Salesforce).
The foundational platform itself and each application deployed are seen as distinct applications. This allows for clarity around ownership roles and responsibilities, and effective modelling of the platform.
Technical Products
It is important to distinguish between the an Application (including Foundational Platform) and a Technical Product.
The table below aims help explain the difference
| Application |
Technical 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)
Illustrated 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]
.png)
Naming Conventions
For many simple Software-as-a-Service based Applications, the name of the Application and the Technical Product are often the seen as the same thing.
For many others Applications, the name intentionally differs;
- to enhance clarity to non-technical stakeholders
- to create custom UCD branding
- to distinguish between the UCD implementation or instance of a generic solution
- decouple from name changes in the vendor's product lineup
The Technical Product name is the Proprietary Name given by the Vendor (and as found in a Proprietary Product Catalogues)
Examples include
| Application |
Technical Product |
| EA Tool |
Alfabet Accelerator |
| Google Drive |
Google Workspace for Education Plus |
| Google Mail |
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