Enterprise Architecture & Liaison
- Data Principles [.pdf]
At CSU we interpret enterprise architecture principles in accordance with the TOGAF definition:
“Principles are general rules and guidelines, intended to be enduring and seldom amended, that inform and support the way in which an organisation sets about fulfilling its mission”
The ultimate goal of enterprise architecture is in maximising the capabilities of the organisation as a whole. Architecture principles play a foundational role in achieving this aim.
The purpose of enterprise architecture principles are to:
- “... supply guidance, constraints, best practices, and criteria to be used in making well- structured, focused decisions” 
- “…supply inputs to planning decisions” 
- Provide “…mediators to balance the usage of conflicting requirements” 
- Provide “… drivers for defining the functional requirements of the architecture” 
In other words, principles help guide change initiatives towards solutions that will be of maximum benefit to all, they help narrow the field to focus on those paths that are the best fit within the vast ecosystem that already exists at the University.
Principles vs. Standards
A common misunderstanding is the difference between principles and standards. While they are similar in nature, principles and standards differ significantly in intention and application.
Essentially, principles provide high level guidance on what should happen within an architecture while standards define how they should happen.
For example a standard may state something like:
“All web pages must be WCAG 2.0 compliant.”
Whilst a principle would give higher level guidance such as:
“All data, information, applications and processes must be easy to use and must be accessible to all relevant parties.”
Applying the Principles
Principles can and should be used at multiple points throughout the life cycle of a change initiative.
However, as a general rule principles are most useful in the early stages while the shape and form of potential solutions are being considered but depending on context they can play an important role during later stages as well.
It is the role of the Architects to advise on the application of the enterprise architecture principles to a specific change initiative. The Architects work with the Solution Coordinator and the Business Analyst to ensure the compliance of a given solution.
If you use the CSU architecture principles and standards to guide your thinking you will maximise your ability to draw on already existing capability throughout the change initiative which should result in a shorter delivery time, a solution that can seamlessly access all necessary information from other university systems.
For clarification on the detail of any CSU enterprise architecture principles please contact any member of the EA&L team.