Charles Sturt University
Charles Sturt University


The Open Group Architecture Framework (TOGAF) defines principles as:

"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 CSU Enterprise Architecture principles are designed for use in accordance with this definition and are listed below. They are used as a set of rules and guidelines to inform decisions and ensure the optimal implementation of change.

Maximise Benefits to the Organisation

  1. Enterprise benefit - information assets, systems and processes must be designed, planned, prioritised and managed to maximise value to the enterprise as a whole.
  2. Non-duplicative solutions – reuse of existing solutions is preferred over introduction of new solutions.
  3. Governance - governance mechanisms must be used to ensure well-considered prioritisation, design, and implementation of solutions.

Information Management is Everybody's Business

  1. Information assets - information is an enterprise asset that requires purposeful management.
  2. Authoritative information - processes (manual and technological) must use authoritative information wherever possible.
  3. Consistency - shared information must be synchronised with its authoritative source of truth so as to maintain consistency.

Common Use Functionality

  1. Service orientation - information and applications should be architected to be modular and reusable.
  2. Interoperability – solutions must implement integrations according to standards.
  3. Shared information - authoritative information must be shared and not recreated or duplicated.

Good Corporate Citizenship

  1. Security – security of data, information, applications and processes must be maintained at a level appropriate to its sensitivity.
  2. Privacy - privacy of an individual's data and information must be protected within policy and legislative bounds.
  3. Intellectual property – the intellectual property of the university must be maintained within policy and legislative bounds.
  4. Compliance – solutions must meet all legislative and policy compliance obligations.
  5. Accessibility - data, information, applications and processes must be easy to use and must be accessible to all relevant parties.

Technical Sustainability

  1. Buy vs. build - the purchase of solutions is preferred over building. Collaborative building is preferred over independent building.
  2. Standards compliance – solution architecture must comply with enterprise architecture standards.
  3. Diversity – proliferation of technological diversity must be limited to that which can be sustainably supported.
  4. Environmental – applications and processes must support environmental sustainability objectives.