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:
The focus of the CSU Applications portfolio includes:
The Applications portfolio is managed by the Enterprise Architect (Applications).
|Application Portfolio Catalogue||Catalogue of all applications in the organisational Application Portfolio and their key attributes.||March 2017|
|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
|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.|