Explore UCD

UCD Home >

What is an Application?

Applications are digital solutions that provides functionality to UCD’s community, typically accessed through a web browser, mobile device, or desktop. 

Applications have a defined purpose, clear boundaries, accountable stakeholders intentionally packaged, branded, and maintained over time (whether custom-built in-house, externally developed, or commercial off-the-shelf).  

Applications include on-premise hosted and cloud services; subscriptions; paid for and free solutions. 

Applications include solutions deployed, managed and implemented for use across multiple schools or units (University-wide Applications) and solutions deployed, managed and implemented for use in one school or unit (Local Applications).

There are a wide range of applications in use in UCD only some of which fall within the scope of UCD Enterprise Architecture.

Key Concepts

In Scope

The applications that fall within the scope of UCD Enterprise Archtecture are any application irrespective of scale deployed by a UCD College, School, Institute/Centres, Unit, Wholly Owned Subsidiary Company, or other organisational entities as designated by the UMT Digital Campus Group, that;

  • enables or supports university business capabilities and processes
  • where UCD is the data controller or processor

In scope applications are classed as either;

  • Enabling Applications - solutions supporting specific functions and activities enabling UCD’s business capabilities and processes
  • Infrastructure Applications - solutions that support technical operations and processes within UCD
  • Learning/Teaching Applications - course/discipline-specific software packages, supporting teaching and learning, or taught research in particular academic domains or modules

Out of Scope

  • Research Solutions - software used by a researcher (or research team),  for the delivery of a research project
  • Personal Use Tools/Apps - software that individuals have personally enabled and use for their own activities, and do not contribute to the UCD’s business capabilities or processes
  • Applications deployed within UCD licensee, separate legal entities to UCD, and incubator companies, for their own use

Applications within the scope of UCD Enterprise Archtecture will;

  • be captured in the EA Repository
  • have Application Business Owner and Application Technical Owner assigned
  • be governed by a future "UCD Digital Application Governance" and "Technical Assessment/Registration Procedures"

Personal Use Tools/Apps are Applications that enable/support personal tasks and activities.

These are typically tools or apps that individuals have personally enabled and use for their own activities - personal productivity / research / content consumption, etc, and would includes the likes of Personal Banking,  Flights / Hotels / Taxis Booking, Social Media, Health & Wellness, AI tools / assistants.

Any application, app, website that requires a UCD subscription or contract, is used for business related content creation (rather than content consumption) or enables/supports university business activities, capabilities and processes must be treated as Enterprise Enabling Application.

Personal Use Applications must not be used to store or process UCD data.  If they are used to store or process UCD data then they should be viewed/categorised as enterprise enabling application.

Research Solutions are software used by a researcher (or research team),  for the delivery of a research project

Research Solutions must comply with all relevant UCD policies, including;

  • All servers/devices must be registered in the Device Registration Portal
  • Data must be align to UCD’s Research Data Management Policy 

Learning/Teaching Applications - Course/discipline-specific software packages used in delivery of particular academic domains or modules in teaching, learning, or taught research.

Includes solutions used by students in academic and taught research programmes within UCD

Examples include specialised learning applications, assessment and quiz, content creation of course materials, stats analysis software, data collection tools, specialised simulation / modeling software, etc...

Enabling Applications are solutions supporting specific functions - enabling, supporting or contributing to Business Capabilities or Processes within UCD.

Includes solutions delivering Core Capabilties Learning & Teaching, and Research Management, as well as Enabling Capabilities such as Financial Management, Library Administration, Engagement and Relationship Management, Legal Services, etc...

See Higher Education Reference Models for a list of all the Business Capabilities within the UCD context.

Infrastructure Applications are solutions that support technical operations and processes within UCD.

Such applications are not available to general users, and typically enable the delivery of other applications across the University.

Examples include Storage Systems, Security Solutions. etc...

Applications are a UCD instance wrapped around technical components - typically a vendor's cloud service or a software product - often customised or configured to fit UCD requirements.

For example our Applications System is built on the Salesforce; Brightspace is built on D2L Brightspace; Course Catalogue is built on InfoHub; Timetabling is built on CMIS.

  Application Technical Component
Definition Delivers functionality directly supporting business processes or user needs Delivers the underpinning hardware, software or service that enables applications to run
Naming Described using a name that is understood across UCD - e.g. EA Repository Proprietary name given by the Vendor - e.g. Alfabet Accelerator 11.x.x
Lifecycle Driven by business demand Driven by vendor release cycles, end-of-life announcements, and support contracts
Dependency Relies on one or more technical products May underpin multiple applications

As part of any application data gathering exercises and/or technical assessments, we’ll request information on these underpinning technical components/products.

The level of customisation/configuration to create a UCD Application out of a vendor's cloud service or a software product, may range from minimal (e.g. setting up accounts and access), through to high customisation (altering the codebase, developing custom scripts)

Applications broadly fall into 3 archetypical deployment styles - 

  • Standalone Application
  • Application with Modules
  • Platforms and Platform-Enabled Applications

Standalone Application

Application with Modules

Platforms and Platform-Enabled Applications

Self-contained application requiring minimal interoperability, localised configuration, and typically delivering one function.

Application with optional or semi-independent modules - often enabled, purchased or licenced separately - that provide additional features or extended functionality.

Platform-enabled applications operate within an integrated platform eco-system. 

Each platform-enabled application has have a distinct independent release schedule, but shares common capabilities / shared services provided by the platform - e.g. APIs, data models, user authentication and management

The application must be registered.

The application must be registered.

Modules must be registered if they are served or offered to users as distinct offerings, or users are likely to view or understand them as distinct or independent - i.e. the modules are heavily customised or packaged to provide distinct functionality or services.

The platform-enabled applications and the platform must be registered.

All are within the scope of UCD Digital Application Governance policy (covered by application data gathering exercises and/or technical assessments).

Enterprise Enabling Applications include;

  • University-wide Applications - solutions deployed, managed and implemented for use across multiple schools or units
  • Local Applications - solutions deployed, managed and implemented for use in one school or unit

All Enterprise Enabling Applications are within the scope of UCD Digital Application Governance policy (covered by application data gathering exercises and/or technical assessments).

All Enterprise Enabling Applications should be captured

All Enterprise Enabling Applications should have an Application Business Owner and an Application Technical Owner

All Enterprise Enabling Applications would be within the scope of future "UCD Digital Application Governance" and "Technical Assessment Process"

Applications should be described using a name that is understood across UCD - determined by the Application Business Owner

The name may match the underpinning technical products proprietary name - i.e. a particular cloud service or a software package;

  • this is more likely where the application is used largely “as delivered by the vendor"

The name may be made intentionally distinct from products proprietary name;

  • this is more likely where application has been significantly adapted / reflecting the unique UCD instance
  • to create user-friendly name or incorporate UCD branding
  • avoid promoting proprietary brands / vendors internally
  • provide flexibility if the underlying product changes
  • obfuscates the underpinning technical product, to enhance clarity to non-technical stakeholders

FAQ - Is this an enterprise enabling application?

Note - All enterprise enabling application should be captured

Use Case

Is this an Enterprise Enabling Solution?

Solutions that do not support business activities, capabilities or processes

I.e. Tools or apps that individuals have personally enabled and use for their own activities. Includes websites used for personal research, content consumption, etc.

E.g. Personal Banking apps, apps and websites for booking flights / hotels / taxis , social media apps, health & wellness apps, AI tools / assistants used for personal productivity

No - However the use of AI within UCD should comply with UCD’s AI Principles

No

Solutions used in the delivery of academic and taught research programmes within UCD

E.g. learning management systems, assessment and quiz tools, course materials content creation, etc…

Yes

Solutions supporting research management within UCD.

E.g. Research management systems, research databases, approved shared research software, specialised simulation or modeling software, data collection tools

Yes

Specialised learning applications (e.g. stats analysis software, specialised simulation / modeling software, data collection tools)

Yes

Solutions supporting specific functions - enabling, supporting or contributing to Business Capabilities / Activities / Processes within UCD

E.g. Library Systems, Finance and HR Platforms, Legal case management systems

Yes

The technical infrastructure - platforms and systems - that enabling the applications that support UCD’s business activities, capabilities and processes.

Yes

Bespoke or experimental systems selected, configured, or developed by individual researchers or research groups to meet niche, discipline-specific, or project-specific requirements/outputs/outcomes

No - however

  • All servers/devices connected to the UCD network must be registered in the Device Registration Portal
  • All Research Data must be align to UCD’s Research Data Management Policy 
  • Any solution that support Research Management or are used for delivery of academic and taught research programmes should be registered

No

Websites that require a UCD subscription, contract or are used for business related research, content creation, etc, 

E.g. Gartner, InfoTech, 

Yes

Cloud Services used that require a UCD subscription or contract

E.g. HEAnet Brokered Services, 

Yes

Consumer software and cloud services used to creating “UCD content”, including  documentation, training and support materials, etc, 

E.g. Canva, Miro, Adobe

Yes

Apps on your phone.

No - unless it support a business activities, capabilities or processes. 

Probably not …

Internally managed server.

No - unless it support a business activities, capabilities or processes. 

Probably not …

UCD website running on a web hosting platform such as Plesk, Wex, Squarespace.

No - unless it support a business activities, capabilities or processes. 

Probably not …

UCD website running on a UCD’s T4 CMS Platform. 

No - the website is viewed as data/content. The Application TerminalFour CMS has already been captured as university-wide application

No

Heavily customised Google/O365 form that supports a business process, or collects data that supports business decision making

Yes

Google/Excel spreadsheet that holds data that supports business decision making.

No this is seen as data/content

No

Application that ETLs (Extracts, Transforms, Loads) or consolidates data from multiple sources to convert into a usable format - supporting a business process or decision making.

Yes

Google/Teams site that is used for file sharing, communication, project management?

No these are seen as data/content. Google and Teams have already been captured as university-wide applications.

No

I’m running the same software or cloud service as another school/college/unit - but it's not listed in the Application Catalogue

Where schools have separate agreements, contracts, licences, etc… each should be captured as a local application

Yes

It’s free (or UCD don’t pay for it)

All applications that support UCD’s business activities, capabilities or processes, regardless of cost, must be registered

Yes

It’s just used by just one person and/or on one machine

All applications that support UCD’s business activities, capabilities or processes, regardless of scale or number of users, must be registered

Yes

It’s required by students as part of their Learning/Teaching or Taught Research module?

All applications used to enable business, teaching or research activities, must be registered.

Yes 

Software developed be a UCD Researcher for the duration of the project, to address a specific ​research ​output/outcome

No - systems developed by a researcher (or research team), for the duration of the project, to address a specific ​research ​output/outcome are out of scope

No

It’s not used for Business, Teaching or Research, isn’t paid for by UCD, and doesn’t store or process any UCD data.

No - Applications that do not support business activities, capabilities or processes are out of scope

No

System software - Operating Systems, Device Drivers, Utility/Configuration Software - software packages that control the hardware of your server, desktop or laptop machine?

No - The system software packages installed that make your laptop/desktop/server usable don’t need to be registered

No

Web browser. 

No - a web browser only allows a user to access/consume other applications, and is not seen as an enterprise application itself.

No

An External Integration Point is a system or service provided by a third party that UCD has built an interface or integration into, that UCD shares data across.

Yes - Where an interface or integration between a UCD application and an external system is in place - the external systems should be recorded to provide UCD with visibility and governance over the ecosystem of core integrations supporting its operations.

E.g. Examples would include a secure API exchanging enrolment data with an accredited partner system, and statutory reporting feed to a regulatory body with a return integration, would both be captured as an external systems with established interfaces/integrations.

No - Where there is no established interface or integration. E.g. returning a completed report to external auditors, via their web portal.

Yes

UCD IT Services

Computer Centre, University College Dublin, Belfield, Dublin 4, Ireland.

Contact us via the UCD IT Support Hub: www.ucd.ie/ithelp