Charles Sturt University
Charles Sturt University


The Enterprise Architecture Applications portfolio is responsible for understanding the form and condition of the organisation's applications.

In this context, an "application" can be defined as:

  • 'a software asset that contains an embedded business process or is configured to support a business process within which information assets are used or created' (Queensland Government ICT Planning Methodology 2007), or
  • 'a deployed and operational IT system that supports business functions and services; for example, payroll. Applications use data and are supported by multiple technology components but are distinct from the technology components that support the application.' (TOGAF)

The focus of the CSU Applications portfolio includes:

  • What applications we currently have
  • What applications are needed now and in the future
  • Application 'health'
  • How individual applications are architected
  • Together with the other Enterprise Architecture portfolios - how applications fit together within the broader environment

The Applications portfolio is managed by the Enterprise Architect (Applications).

Key Concepts

  • Governance – the ISIP Governance Committee provides governance over resourcing application activities at CSU. The Data Governance Committee also has a keen interest in the application portfolio.
  • Custodianship – Enterprise Architecture has custodianship of the application portfolio listing in conjunction with the Applications team within DIT. Additionally, custodianship of individual applications is shared between the Applications team and business owners across CSU. A document defining Technology Product Role Definitions is currently being developed and will be available on this site shortly.
  • Health – In the past, the age of internal applications and the version currency of purchased applications have been used as application health measures. A new health assessment framework has recently been developed and undertaken by the Enterprise Architect (Applications) to include:
  1. Measurement across business value
  2. Business impact
  3. Information condition
  4. Application technical condition

Key Artefacts

Title Description Date
Application Portfolio Catalogue Catalogue of all applications in the organisational Application Portfolio and their key attributes. Feb 2019
Application Lifecycle Map Map of each application against its current lifecycle status. Mar 2015*
Application Framework Map of applications against key business functions to show coverage. Nov 2014*
Application Standards Standards about how CSU applications should be structured and constructed. Dec 2014*

* - Document currently under review / redevelopment

Common Queries

How many applications do we have at CSU?The Applications Portfolio Catalogue [.pdf] contains a full list of applications and a summary sheet with relevant statistics.
How many applications does my Division look after?The Applications Portfolio Catalogue [.pdf] includes the Custodian of each application.
How many applications are hosted externally?The Applications Portfolio Catalogue [.pdf] includes which applications are hosted externally in use at CSU.
My application is not meeting my needs. What should I do?Depending on the situation, this may be a simple fix or require a more in-depth solution (e.g. initiating a project) to address. In the first instance you should contact Paul Bristow (Enterprise Architect, Applications). Depending on the circumstances, other CSU Enterprise Architects may need to be involved.
Do we have an application to do X?The Applications Portfolio Catalogue [.pdf] lists our applications with a short description of what they do. For further investigation, please consult Paul Bristow (Enterprise Architect, Applications).
What is the best way to build my new application?The Application Standards contain information on how CSU applications should be structured and constructed. Please contact Paul Bristow (Enterprise Architect, Applications) to discuss your application.