DIVISION OF INFORMATION TECHNOLOGY
ENTERPRISE ARCHITECTURE Application Standards Version 1.1 -­‐ December 2014 Page | 1 v1.1 DIVISION OF INFORMATION TECHNOLOGY
ENTERPRISE ARCHITECTURE 1. Metadata Version 1.1 TRIM file number -­‐ Short description Provides a description of the standards required of applications used by Charles Sturt University Relevant to Officers who have a responsibility in the planning, selection, procurement and development of applications. Authority Responsible officer Enterprise Architect -­‐ Applications Responsible office Enterprise Architecture, Division of Information Technology Date introduced June 2011 Date(s) modified December 2014 Next scheduled review date December 2015 Related University documents CSU Enterprise Architecture Principles CSU Data Standards CSU Integration Standards CSU IT Infrastructure Standards CSU Records Management Policy CSU Web Policy CSU Mobile by Design Related legislation Key words applications, principles, standards, applications architecture 2. User Interface All applications will have a web interface, compliant with CSU Web Policy. An application may use a Windows based application for in-­‐application management by a limited group of staff but any student interface must be through a web browser. However the preference will be for full web functionality. All commonly used web browsers and platforms must be supported. Applications should be able to deliver static content through (and reuse static content already existing in) our Squiz Matrix Content Management System. This content includes CSS, image and other media files, JavaScript and HTML templates. This content may be cached. HTML and CSS must be standards compliant and accessible. Adobe Flash may be used to add functionality which cannot be delivered through mainstream HTML, CSS and Javascript. Accessible techniques must be used. Users expect responsive applications. Page load and response times should be sub second. Page | 2 v1.1 DIVISION OF INFORMATION TECHNOLOGY
ENTERPRISE ARCHITECTURE Mobile Full application functionality should be available using mobile devices. Web content will use responsive design techniques to optimise display across devices. Mobile apps, when available, will be used to leverage native mobile technologies. Email Applications that send email to users must provide options for users to configure how often and how they receive email. 3. Coding Language In house applications will use Java 7 and optionally Groovy/Grails 2.x on Unix and .Net 4 on Windows. Externally supported applications may use other languages but are expected to be able to interoperate with these platforms. Client side (browser) code will use JavaScript. Patterns In house applications will use a Model View Controller pattern. There will be a Facade layer in front of the model to facilitate changes to either model, or view and controller with minimal changes to the other. The Facade will provide an API that can be mapped to Restful or SOA endpoints for consumption by other systems (via WebMethods). This is recommended for all applications. Client side JavaScript in all applications will use Unobtrusive techniques. Identity and Security All applications must conform to CSU Identity and Security Standards defined in the CSU IT Infrastructure Standard. Authentication will use CSU single sign on which is SAML2 using Shibboleth. CSU are developing an ADFS capability to use with Microsoft Azure. Group memberships for authorisation within applications are available from Active Directory and the Identity and Groups Management System. Group requirements must be negotiated with the Director -­‐ Applications for each application. Integration All applications are required to use Enterprise Master Data, as prescribed in the CSU Data Standards. All applications must be capable of sharing information with the CSU Information. Data and functionality from all applications must be available for reuse by other applications. Integration standards are defined in the CSU Integration Standards. Where possible APIs should expose functionality for reuse in web and mobile applications. Testing All Application code will require unit and user acceptance testing. Page | 3 v1.1 DIVISION OF INFORMATION TECHNOLOGY
ENTERPRISE ARCHITECTURE Version Control Source code for internally supported applications will be managed using Subversion Development Tools Eclipse (with Subclipse plugin) – Java Programming Integrated Development Environment Apache Maven 3 – dependency management for Java back end code Oracle SQL Developer – tool for database development Oracle Developer Suite – for developing Oracle specific application technology Libraries Hibernate – database mapping to Java classes – optional – POJO (Plain Old Java Object) approach is often preferred JQuery – general purpose JavaScript library for use on client Quartz – Java job scheduling Spring – used primarily for dependency injection in Sakai Struts 1 – Java MVC framework used in legacy applications 4. Deployment Platform Applications hosted at CSU must run on hardware configurations as defined in the CSU IT Infrastructure Standard. Network All applications should operate efficiently across firewalled networks in conformance with the CSU IT Infrastructure Standard. Application Management All applications should provide logging and management interfaces as defined by the CSU IT Infrastructure Standards. 5. Document Control Version Author Issue Date Revisions 1.0 1.1 June 2011 Dec 2014 Document Created Mobile Accessibility, Auth, IGMS updates Paul Bristow Paul Bristow Page | 4 v1.1