Sydney Student is an administration system that will offer students a simplified, seamless relationship with the University from first enquiry through to alumni engagement, and provide staff with improved support to make clear decisions, reduce risks and spend more time on valuable activities. This system is being built using market leading software, SITS:Vision.

Please find below a glossary designed to assist you in understanding some of the terminology used in relation to the Sydney Student Program.

For definitions of key acronyms, abbreviations and terminology used in the University of Sydney’s official publications, business communications and systems see the University glossary.

See the Editorial Style Guide for information about the University's recommended style in a number of areas, including grammar and preferred spellings. It also includes sections on how to refer to the University and avoid discriminatory language.

A-B-C-D | E-F-G-H | I-J-K-L | M-N-O-P | Q-R-S-T | U-V-W-X-Y-Z


approval, refers to the final acceptance of a formal project deliverable. Approval is normally provided by the business sponsor. Occurs after endorsement.

business requirement, a single, documented business need of the University based on analysis of the business drivers and goals, constraints and business processes.

build, refers to the project phase where the solution is developed/configured in accordance to the business requirements, rules, functions, processes and non functional requirements.

configuration, adapting and modifying an off-the-shelf application, such as SITS:Vision, to meet identified business requirements.

cutover, switching from an old (hardware and/or software) system to a replacement system.

cutover (window plan), schedule of tasks to be carried out from the point of final Board approval for Go/No Go to the point where it is agreed to operate business as usual.

cutover checkpoint, a task in the cutover window plan which represents a scheduled meeting to validate the progress of activities up to that point.

cutover preconditions, a list of tasks, milestones and deliverables required to be completed and assessed prior to the final Board Go/No Go.

data migration, the process of transferring data between storage types, formats, or computer systems, such as from FlexSIS to SITS:Vision.

design, refers to the project phase where business requirements, rules, functions and processes are gathered, defined and documented.

defect, a deviation from the expected testing result. Sometimes referred to as a bug. (see Testing)

diet, a set of units of study in which a student may enrol in order to attain a recognised award. The diet may comprise a combination of compulsory and elective units of study.


endorsement, refers to the acceptance of a formal project deliverable by appropriate business and project stakeholders. Endorsement is usually provided by key stakeholders and is the step before approval.

enhancement, customisation changes that improve the operation of the system.

fallback (cutover), the activity to revert to the original system should the migration to the new system be unsuccessful.

functional requirement, a specific input, behaviour or output determined by the University to be delivered as part of Sydney Student.

Go / No Go, determination to proceed with, abandon or delay the planned Go Live of Sydney Student.

Go Live, the point at which a new system is taken into production.

Go Live validation checks, these checks are executed using selected test cases previously used during UAT that represent the major system functionality.

health “vital” signs, measurable data that monitors the overall “health” of a University Business Unit pre, during and post cutover. An example is a Key Performance Indicator (KPI) that already exists in a business such as % service level.


interface, the regular exchange of information between two computer systems in a pre-defined, normally electronic, format. This does not refer to the undocumented use of data extracts.

issue, refers to the result of an event that delays project progress often as a result of a “risk” materialising.


Non-functional requirement, criteria that will be used to judge the performance of the Sydney Student system.


Quality Centre, the software tool that assists with testing.

reporting, presentation of a subset or summary of a dataset for the purpose of informing. The actual presentation may use a number of different media, for example printed paper, web browser, email or by extract to a software application such as MS-Excel or Business Objects. In some specific instances, for example statutory reporting to a government body such as DEEWR, the process may be described as an interface (cf.) by means of which large volumes of data are presented in electronic format for further analysis.

risk, a risk is an uncertain event or set of events that, should it occur, will have an effect on the achievement of objectives. See issue.

Service Delivery Model (SDM), a framework to describe how administrative services are organised, including people, systems and processes across the University to offer student’s a simplified, seamless relationship with the University from first enquiry through to alumni engagement, and provide staff with improved support to make clear decisions, reduce risks and spend more time on valuable activities.

single source of truth, a single source of truth for a data element is achieved where the data element is stored once only (for example, in a single table within a single database). This data may be drawn from this single source of truth and displayed in multiple areas.

scope, describes the business areas and interactions covered by this project such as:

  • organisational areas (business units / geographical locations)
  • people (staff, customers, society)
  • processes and operations
  • products and services to internal or external customers
  • property
  • systems and interfaces
  • information management.

script, a step-by-step guide to complete a task.

SITS:Vision, the technology solution being implemented by the University as part of the Sydney Student Program. SITS manages student administrative processes from enquiries through to graduation and alumni. The system acts as the central point of information on students and their qualifications and integrates with supporting applications such as finance systems, campus access systems, library systems, estate management, human resource systems and virtual learning environments.

Sydney Student, Sydney Student is a student administration system that will offer students a simplified, seamless relationship with the University from first enquiry through to alumni engagement, and provide staff with improved support to make clear decisions, reduce risks and spend more time on valuable activities. This system is configured from market leading software, SITS:Vision.

systems support, the continued provision of services and material by ICT to their customers necessary for the use and improvement of a system during its lifecycle.


  • acceptance testing – also known as User Acceptance Testing (UAT) is a process to obtain confirmation by a subject matter expert, preferably the owner or client of the object under test, through trial or review, that a system meets mutually agreed-upon requirements.
  • end-to-end testing – the process of testing transactions or business processes as they pass right through the computer systems. To ensure that all aspects of the business are supported by the systems under test.
  • regression testing – to provide a general assurance that no additional errors were introduced in the process of fixing other problems. Regression testing is commonly used to test the system efficiently by systematically selecting the appropriate minimum suite of tests needed to adequately cover the affected change.
  • system testing – an investigatory testing phase, where the focus is to have almost a destructive attitude and tests not only the design, but also the behaviour and even the believed expectations of the customer. It is also intended to test up to and beyond the bounds defined in the software/hardware requirements specification(s).
  • unit testing – a method by which individual units of source code /configuration are tested to determine if they are fit for use. This is usually performed within the build phase.

Tribal, the SITS:Vision solution vendor.

trusted data, data provided as a compilation of one or more (partial or full) authoritative data sources. Trusted data is often maintained within a different location (database or application) to the underlying authoritative data sources. Trusted data sources are established primarily to assist with applications integration and reporting requirements.


use cases, used in testing. The proposed interactions between the actors and the system as described in the business processes.

wave, a grouping of project related workstreams that are delivering business functions and benefits.

workstream, a subset of a wave. A series of related tasks and activities within the student lifecycle.