Usage Guide

The Requirements Traceability Matrix (RTM) is designed to serve the following purposes:
:To support the capture and management of all categories of requirements and business rules.
:To provide a means of verifying that the project team correctly understands the requirements and business rules.
:To allow for traceability of detailed requirements back to high-level drivers, objectives and benefits and thereby demonstrate to the project sponsor and senior management
that all elements of the project can be justified.
:To allow for traceability of the solution design elements back to the requirements to ensure that they have been fully catered for.
:To provide a means of communicating the requirements to the people who will design, implement and test the solution.
:To provide a baseline document to be referred to when determining whether issues with the solution are to be treated as defects or change requests.

The requirements within this document are meant to be solution independent. They are intended to provide a statement of what the solution is to do and how well it should do
it but not of how it will be implemented.

Approval of this document along with the associated Service Specification Overview (if provided) is taken as confirmation that our understanding of the requirements and
business rules is correct.

A significant amount of explanatory text is provided within this document either below or as information rows within the worksheets.
Questions regarding the content of the document, the requirements for your project, should be directed to the relevant Business Analyst or Project Manager.

Guide to Worksheet Columns

Acceptance criteria (recommended if the requirement is not a easily testable)
Criteria that can be used to assess whether the work products satisfy the requirements. This is the basis for developing review criteria and test cases.
For example, 'At least 50% of students think the new student portal is a significant improvement on the previous portal and that it is in line with their expectations of a modern
web site'.
Accepted (recommended)
States whether the project sponsor has accepted that the solution satisfies this requirement and is ready for deployment into production. Typically used during the User
Acceptance Testing phase.
Conflicting Requirements (optional)
The IDs of other requirements that may conflict with this requirement. This may be necessary when requirements are gathered from different sources.
Date (recommended)
When the requirement was captured or last modified. This is valuable when trying to track the source of a requirement at a later date.
Elicited By (mandatory)
The specific details of who captured the requirement
Description (mandatory)
A description of the requirement that has been gathered from stakeholder(s).
Should be written using an active wording style rather than the MoSCoW style when documenting requirements.
For example; rather than “The solution must provide an online help function”, use “Provide an online help function”. The priority column alone is used to indicate that a
requirement is mandatory.
At a minimum, a high quality requirement must exhibit the following characteristics:
- Cohesive
- Complete
- Consistent
- Correct
- Feasible
- Modifiable
- Unambiguous
- Testable.
As part of being concise and consistent, you should aim to keep requirements descriptions to no more than 2 lines

Frequency of usage (recommended)

An indication of how often the report is used, inclusive of all users. Refer to the Lists worksheet for a list of the possible values and their meaning.
High level capability (mandatory)
A high level, brief description of the process/functionality/capability that the requirement addresses. This can be treated as a short title for the requirement and is useful for
quickly locating requirements of interest.

ID (mandatory)
All requirements statements should be allocated a unique ID. This supports traceability, aids communication and facilitates change impact assessment.
The format of these IDs is usually XXXN although other formats are allowed. The XXX is a unique string that helps to associate the ID with the requirements sections to which it
belongs. It is preferable to use a string that readers will easily associate with the subject name. For example, if the subject is Ordering, you might use ORD as the string. The N
part of the ID is a sequential integer that uniquely identifies the requirement within the subject area. E.g. ORD1, ORD2, ORD3.
Be wary of changing the ID of any existing requirement. This may cause problems for traceability.

Implementation phase
For solutions that will be rolled into production over a series of phases, this attribute indicates the phase in which the requirement is to be satisfied.
NFR Traceability (mandatory)
The ref number of the related item in the Non-Functional Req's Analysis template used to elicit non-functional requirements. Used to support traceability.
Parent requirements (recommended)
The ID(s) of the parent requirement(s) that each requirement can be traced back to. This is a key element in enabling traceability and evaluating the completeness of the set of
requirements needed for the project success.

Priority (mandatory)
An indication of the importance of the requirement. Refer to the Lists worksheet for a list of the available options and their meaning.
Rationale (recommended)
Where appropriate, you should describe why the requirement is important. This may include references to other requirements if it makes sense to do so. This is optional
although generally recommended as a good practice.

Requirements group ID (optional)

Project Services | Requirements Traceability Matrix Page 1 of 63

688167766.xlsx Printed: 08/30/2023 18:41:19
 Requirements can optionally be grouped with other related requirements by using a common Group ID. This also assists in traceability and evaluating the completeness of the
set of requirements needed for the project success.
Use the following format for Group IDs - G001,G002,G003,...
The format of Group IDs is intentionally different from the Requirement ID format to reduce the risk of confusion.

Requirement status (mandatory)

An indication of the current status of the requirement. Refer to the Lists worksheet for a list of the possible values and their meaning.
Note: If a requirement has been stated as 'Out of Scope' then the reason and the new owner of the requirements must be stated in the Comments column
Stakeholder (mandatory)
The name or initials of the stakeholders who have contributed to each requirement should be listed.
If initials are used, those stakeholders should be listed on the Front Page as contributors along with their initials.
Testable requirement (recommended)
All requirements should be written in such a way that it is possible to objectively test whether they have been completely and correctly satisfied. Therefore, the value entered in
this column should normally be Yes. There are occasions when a stakeholder insists that a requirement that is not easily tested be recorded. For example, 'It has to have the
wow factor'. Requirements that cannot be tested/verified should be challenged for validity and broken down into more meaningful requirements where possible.

Frequently Asked Questions

1 Where do I set the Program Component/Sub-Project Name that appears at the top of each worksheet?
Set the name of your program component/sub-project name in cell C5 of the Front Page. It will automatically apply to each of the worksheet titles from there.
2 What is a Functional (a.k.a Utility) Requirement?
A functional (a.k.a Utility) requirement specifies the required capabilities of the product or service , or things the product or service must do for its users. They define the
functionality offered by a product or service to meet a particular need or support a particular outcome. These requirements can be viewed as ‘what the service must do’, and
are used to determine whether the service designed and built delivers the required outcomes, or is ‘fit for purpose’.
is a statement that describes ‘what the service does’, and can be used to determine whether a service is able to meet its required outcomes, or is ‘fit for purpose’.
3 In other
What is awords - what features,
Non Functional functions, capabilities, services or outputs does the business need?
Requirement?
There are a number of categories of non functional requirements that define the quality attributes required of the product or service. Non-functional requirements include:
:Service Level Requirement - These define the required attributes of the product or service in terms of when the service must be available for use, what its capacity and
performance must be, its required reliability in terms of service continuity and security. The specific SLRs should be negotiated and agreed with the customer.
:Service Management and Support Model Requirements
:Technical Operating Requirements
:Accessibility Requirements - are statements that refer to the inclusive practise of making websites usable by people of all abilities and disabilities
:Usability Requirements - are statements that refer to the ease in which the product can be used to achieve specific goals with effectiveness and efficiency

6 Why are some requirements marked with a strikethrough font?

Any requirement that has been given a status of Deprecated will have the font of all cells in the row set with a strikethrough font. This is achieved using conditional format rules.

Project Services | Requirements Traceability Matrix Page 2 of 63

688167766.xlsx Printed: 08/30/2023 18:41:19
 #REF!
i Columns in the yellow sections are for Business Analysts to complete.
Related
Requirements Conflicting
ID High level capability Description Rationale Related IT service Stakeholder Priority Date Elicited By requirements scope Parent requirements Requirement Status
Group ID requirements
ref
High level process, function or
capability that the requirement existing IT customer The reference number of
addresses. facing and/or Who provided Priority of this When was the any related requirements ID of other
Unique A description of each requirement that is: Cohesive, Complete, Consistent, Correct, Feasible, Who captured the ID of the relevant higher ID for a group of related Current status of each
Why is this requirement needed? supporting IT services this requirement requirement scope statements from requirement(s) that are
identifier Modifiable, Unambiguous and Testable. requirement? level requirement(s). requirements. requirement.
that the requirement requirement? (Hi,Me,Lo) captured? Functional Requirement in conflict.
relates to Definition (FRD) doc

<Name of subject area or topic> Mandatory column Mandatory column

Example Cetak FRS Mahasiswa dapat mengunduh formulir rencana studi (FRS) dalam bentuk PDF Mahasiswa dapat melihat FRS dari mana saja Student Portal service MHS Medium 7 Apr 2012 1 SRQ2 G007 WTF1 New
dan kapan saja
New
New
New
<Name of subject area or topic>
New
New
New
<Name of subject area or topic>
New
New
New
<Name of subject area or topic>
New
New
New
Business Process Improvement
i This section is optional. If your project requires some BPI, you may need to capture requirements related to that here. You may need to break this out into multiple more specific sections.
BPI1 New
BPI2 New
BPI3 New
Reporting
i A section for reporting requirements has been included here due to the importance of capturing reporting requirements early in the project life cycle.
i Reporting requirements often lead to data storage and processing requirements which in turn lead to data capture or integration requirements. The late identification of detailed reporting requirements can result in expensive changes to a system and/or impaired reporting abilities.
i Reporting requirements can be a difficult area to specify. Users often want to see examples of the reports before they can tell us what they need. It may be helpful to subdivide this section into operational, technical, dashboard and ad-hoc reports for example.
RPT1 New
RPT2 New
RPT3 New
Integration and interfaces with other systems
Example Support Merlin / library system Ensure that the new system supports the same interfaces to the library systems that are Need to minimise/avoid impacts to other GD Mandatory 7 Apr 2012 HLR3 HLR3 New
interfaces provided by Merlin. systems.
INT1 New
INT2 New
INT3 New
Data migration and conversion
i Data migration requirements typically cover the one-off migration of data from existing systems into the new system(s).
i Data conversion requirements may relate to the migration but can also cover the ongoing conversion of data as it moves through the system interfaces.
Example Migrate current account data Ensure that all current account data in Themis is migrated into the new system. Current account data is needed for operational GD Mandatory 7 Apr 2012 HLR2 HLR2 New
purposes. Inactive accounts will be moved to
the warehouse.

Example Translate subject codes for libr Ensure that subject codes in the new system are translated back into the old subject code Need to minimise/avoid impacts to other GD Desirable 7 Apr 2012 HLR3 HLR3 New
format before they are sent to the library system. systems.
DMC1 New
DMC2 New
DMC3 New

Project Services | Requirements Traceability Matrix Page 3 of 63

688167766.xlsx
 i This template has many rows such as this providing information on how to populate the RTM for your project along wit

i You should delete these rows before presenting the RTM to others for review.

<set your project name on the Front Page> - Non Functional Requirements

ID High level capability Description

High level process, function or A description of each requirement that is: Cohesive,
Unique identifier capability that the requirement Complete, Consistent, Correct, Feasible, Modifiable,
addresses. Unambiguous and Testable.

Service level Requirements (SLRs)

i This section is used to capture the Service Level Requirements for the service
Service availability
SLR-SAM1
SLR-SAM2
SLR-SAM3
SLR-SAM4
SLR-SAM5
SLR-SAM6
IT Service Continuity (Includes DR)
SLR-ITSCM1 MTO
SLR-ITSCM2 RTO
SLR-ITSCM3 RPO
SLR-ITSCM4
SLR-ITSCM3
SLR-ITSCM4
Capacity and performance
SLR-CM1
SLR-CM2
SLR-CM3
Service Desk
SLR-SD1
SLR-SD2
SLR-SD3
General Support Model
SLR-GSM1
SLR-GSM2
Incident Management
SLR-IM1
SLR-IM2
Request Fulfilment
SLR-RF1
SLR-RF2
Service Management and Support Model Requirements
i This section is used to capture the requirements for ITS to effectively manage the service(s) when operational
Supplier Management (SSM)
SupM1

Project Services | Requirements Traceability Matrix

688167766.xlsx
 SupM2
SupM3
Service Desk
SD1
SD2
SD3
Request Fulfilment
RF1 Comply with ITS standard Service requests will comply with ITS standard
request fulfilment process request fulfilment process and ultimately be
reportable from the ITS Service Management
tool
RF2
RF3
Incident Management
INC1 Use ITS standard incident Incidents will be managed according to and
management process will comply with ITS standard Incident
Management process and ultimately be
reportable from the ITS Service Management
tool
INC2
INC3
Problem Management
PM1 Use ITS standard problem Problems will be managed according to and
management process will comply with ITS standard Problem
Management process and ultimately be
reportable from the ITS Service Management
tool
PM2
PM3
Knowledge Management
KM1 Follow KM Standards for Production of documentation and support
KBAs, Known Errors, User materials will follow KM standards
Guides, procedures
KM2
KM3
Change Management
CHM1 Use ITS standard change Problems will be managed according to and
management process will comply with ITS standard Change
Management process and ultimately be
reportable from the ITS Service Management
tool
CHM2
CHM3
Release & Deployment Management
RDM1 Use ITS standard release Problems will be managed according to and
management process will comply with ITS standard release
Management process and ultimately be
reportable from the ITS Service Management
tool
RDM2
RDM3
Asset & Configuration Management
SACM1 Use ITS standard Asset & Problems will be managed according to and
Configuration management will comply with ITS standard Asset &
process Configuration Management process and
ultimately be reportable from the ITS Service
Management tool

Project Services | Requirements Traceability Matrix

688167766.xlsx
 SACM2
SACM3
Service Validation and Test Management
SVT1
SVT2
SVT3
Financial & Resource Management
FRM1
FRM2
FRM3
Governance/Compliance/Conformity
i What laws, regulations, policies, standards, external affairs or other factors must the solution conform to? Failure of the
i Be wary of listing standards that imply a specific solution approach too early in the project. When a solution approach h
CNF1 Comply with University Ensure that the solution is compliant with and
regulations upholds the enforcement of University
regulation 8.3.R2 Computing Network and
Facility Rules.
CNF2 Comply with the Public Ensure that the solution is compliant with and
Records Act upholds the enforcement of the Public Records
Act (Vic) 1973.

CNF3 Comply with privacy acts Ensure that all data that is stored, processed
or transmitted by the solution is done so in
accordance with the Information Privacy Act
(Vic) 2000 and the Privacy Act (Cth) 1988.
CNF4 Comply with the Health Ensure that all data that may be defined as
Records Act health information that is stored, processed or
transmitted by the solution is done so in
accordance with the Health Records Act (Vic)
2001.

CNF5 Comply with copyright acts Ensure that the solution is compliant with and
upholds the enforcement of the Copyright Act
(Cth) 1968 and the Copyright Amendment
(Digital Agenda) Act (Cth) 2000.
CNF6 Support users with Ensure that the solution can be accessed by
disabilities users with disabilities in accordance with the
Disability Discrimination Act (Cth) 1992,
Disability Standards for Education (Cth) 2005
and the Equal Opportunity Act (Vic) 2010.
Compliance to be assessed against WCAG
2.0 AA.

CNF7
CNF8
Technical Operational Requirements
i This section is used to capture the requirements for ITS technical support teams to effectively technically maintain, supp
ITS Technical Operating Standards and Activities
TOR1
TOR2
TOR3
Events & Remediation Management
ERM1
ERM2
ERM3
Build, Deploy, Decommission
BDD1
BDD2

Project Services | Requirements Traceability Matrix

688167766.xlsx
 BDD3
Project Checklists
Information Security Management (ISM)
i The following are standard requirements that apply to most University systems. Your sponsor should be familiarised w
If there is an intent by the business to have any component of the solution hosted externally, e.g. Student Gmail, you sho
i may need to be factored into the requirements.
SEC1 Central user authentication Ensure that the electronic identities of all users
are established through the University’s
Identity and Access Management tool before
allowing access to the solution.
SEC2 External system Ensure that external systems and interfaces
authentication are identified, authenticated, and authorised
before granting access to the solution.
SEC3 Comply with ITS Security Ensure that the solution complies with the
Policy requirements stated in the ITS Security Policy.
At a minimum, ensure that access to
confidential or sensitive information is
protected by a password.
SEC4 Controlled access Ensure that access to information and
functionality is restricted through access levels
that incorporate segregation of incompatible
duties.
SEC5 Protection against malware Ensure that the solution is protected from
viruses and malicious code.
SEC6 Logging of security Ensure that the solution records information
incidents related to potential or actual security incidents.
SEC7 Non-repudiation Ensure that the solution can record details of
system events and the responsible individual
such that they cannot deny that the event took
place.
SEC8 Encryption of stored data Ensure that sensitive information is encrypted
in order to protect the operations and privacy
of the University and its stakeholders.
SEC9 Encryption of transmitted Ensure that all data that is not generally
data available to the public that is to be transmitted
over the Internet is encrypted.
SEC10 Hardware security Ensure that hardware is physically secure and
kept cool and dry.
SEC11 Data accuracy Ensure that all data held or transported by the
solution is kept complete, accurate and valid.
SEC12 Minimise access to ports Ensure that each system component only
exposes the minimum number of required
network ports both internally (internal
University network) and externally (non-
University network/Internet).
SEC13 Appropriate placement of Ensure that each component of the solution
solution components has been placed in the appropriate network
zone.
SEC14 Testing and verification of Ensure that each component of the system
components solution is tested and verified to be compliant
with ITS security build standards.
SEC15 Testing and verification of Ensure that all components of the solution are
components tested for security vulnerabilities, mis-
configurations and control weaknesses and
that all known issues are identified and
corrected.
SEC16 System checklist / risk If the solution is to be externally hosted,
assessment ensure that the ITS Externally Hosted System
Checklist / Risk Assessment is completed and
any outstanding risks are accepted by the CIO
or his/her delegate.

Project Services | Requirements Traceability Matrix

688167766.xlsx
 SEC17 Security controls Ensure that all required ITS security controls
have been implemented and confirmed
through testing that they are operating
effectively.
SEC18 Disaster recovery plans Ensure that disaster recovery plans are
adequately documented and submitted to the
IT Security and Risk Manager.
SEC19 Testing of disaster Ensure that disaster recovery plans for the
recovery plans solution are tested successfully, i.e. testing
has confirmed that Recovery Time Objective
(RTO) and Recovery Point Objective (RPO)
requirements can be met.
SEC20 Provision of security Ensure that results of all security related
related tests and results testing and all security related project artefacts
are provided to the IT Security and Risk
Manager.
SEC21
Accessibility - User Consumed Content
i The following are standard requirements that apply to systems that are to have a web interface. Your sponsor should be
ACC1 Accessibility for all users Ensure that web services can be accessed by
all users, including those with disabilities.

ACC2 Comply with WCAG 2.0 Ensure that web accessible elements of the
Level AA solution comply with the Web Content
Accessibility Guidelines set out in WCAG 2.0
Level AA.

ACC3 Text alternatives Provide text alternatives for any non-text

content such as images.

ACC4 Labels for form fields Add labels to form fields.

ACC5 Alternatives for video and Provide alternatives for time-based media
audio such as video and audio.

Project Services | Requirements Traceability Matrix

688167766.xlsx
 ACC6 Structure markup Use structural markup such as headings (e.g.
<h1> - <h6>) and lists (e.g. <ul> <ol>) to
organise content.

ACC7 Contrast Provide a contrast ratio of 4.5:1 between

foreground text and the background.

ACC8 Data table headings Add column and row headings (e.g. <th>) to
data tables.

ACC9 Increased text size Ensure that all pages are readable and
functional when text size is increased by up to
200%.

AC10 Accessibility via keyboard Make all functionality available via the
keyboard.

ACC11 Sufficient time for reading Provide users with enough time to read and
use content.

ACC12 Avoid seizures Do not design content in a way that is known

to cause seizures.

ACC13 Consistent navigation, Help users navigate, find content and

headings and links determine where they are via consistent
navigation, headings and links.

ACC14 Language identification Identify the human language of the page (e.g.
English).

Project Services | Requirements Traceability Matrix

688167766.xlsx
 ACC15 Consistent content order Present content in a consistent order from
and predictable behaviour page to page and make the behaviour of
interactive components predictable.

ACC16 Labels, cues and Provide sufficient labels, cues and instructions
instructions for users when completing forms.

ACC17 Skipping to content Add skip to content links.

ACC18 Avoid 'click here' Avoid 'click here' links.

ACC19 Page titles Add meaningful page titles.

ACC20 Javascript and adaptive Ensure that changes to the page via Javascript
technologies are reported to adaptive technologies.

Accessibility - Author Generated Content

i The following are standard requirements that apply to systems which allow users to author content that will be viewable
AGC1 Comply with ATAG Ensure that author content generated by the
solution comply with the Authoring Tool
Accessibility Guidelines (ATAG).

AGC2 Accessible automatic Ensure that automatically specified content is

content accessible.

AGC3 Preservation of Ensure that accessibility information is

accessibility information preserved.

AGC4 Accessible content Ensure accessible content production is

production possible.

AGC5 Guide authors Guide authors to produce accessible content.

Project Services | Requirements Traceability Matrix

688167766.xlsx
 AGC6 Alternate content Assist authors with managing alternative
content for non-text content.

AGC7 Accessible templates Assist authors with accessible templates.

AGC8 Accessible pre-authored Assist authors with accessible pre-authored

content content.

AGC9 Automatic accessibility Assist authors in checking for accessibility

checks problems.

AGC10 Automatic accessibility Assist authors in repairing accessibility

corrections problems.

AGC11 Support accessible content Ensure the availability of features that support
production the production of accessible content.

AGC12 Documentation Ensure that documentation promotes the

production of accessible content.

Usability
i The following are standard requirements that apply to systems that are to have a user-facing interface. Your sponsor sho
i Some other usability factors to consider are:
i - keyboard accelerators
i - languages required
i - online help
USA1 University MOEs Ensure that the system can be operated using
the current MOEs in place at the University.

USA2 Browsers If a web-browser based system, ensure that

the system operates using all common web
browsers and versions, namely: Internet
Explorer, Firefox, Chrome and Safari, back to
versions which are supported by the University
MOE.

USA3 Devices If a web-browser based system, ensure that

the system operates successfully using the
most commonly used devices, namely:
- PC
- 7' and 10' tablets
- smartphones

Project Services | Requirements Traceability Matrix

688167766.xlsx
 USA4 Operating Systems If a web-browser based system, ensure that
the system can be operated using the most
commonly used operating systems used on
tablets and smartphones, namely:
- iOS
- Android

USA5 Navigation If a web-based system, ensure that the system

provides a consistent navigation across the
system

USA6 Location Ensure that the system provides the user with
information about where they are in the system
or a task.
USA7 Task completion - success 75% of new users to the system should be
able to complete the 5 most common tasks
successfully on the first attempt.
USA8 Task completion - time Ensure that the system allows users to
complete a task in an acceptable time.
- 75% of users rate the time taken to complete
a task based on its complexity as good, very
good or excellent.
USA9 Page load If web-based, page load is less than 10
seconds for 90%
USA10 Content Ensure that headings, font size, spacing and
colour are consistent across the system.
USA11 Findability - navigation Ensure that the system allows users to find the
most common functions easily through the
system navigation.
- 75% of users rate the system as 'easy to find
content or functionality'.

USA12 Findability - Search Ensure that the system provides a search

mechanism to assist users to find specific
content or function.
- 75% of users rate the system search as
good, very good or excellent.
USA13 User-friendly error Ensure that the system provides user-friendly
messages error messages in all circumstances.
- users can resolve problems from error
messages without additional support 95% of
the time
USA14 Undo feature Provide an 'undo' feature within the tool. Allow
users to undo at least the last 3 edits within the
screen they are working on or back to the most
recent save.
USA15 Ease of learning and use Ensure that the system is easy for new users
to learn and use.

USA16 Power users Ensure that features are provided that allow
power-users to do their work quickly and
effectively. For example, short-cut keys.
USA17 Keyboard Ensure that users are able to use the system
by keyboard only (not mouse) by use of tab,
shift-tab, enter and other keys.

USA18 Provide the display date fields in Australian

Date Display format (DD/MM/YYYY) or similar

Project Services | Requirements Traceability Matrix

688167766.xlsx
 USA19

Australian dictionary Comply with Australian dictionary standards

Web Analytics & Reporting
WAP1 Web analytics UoM Deploy web analytics tracking using UoM
standard tracking Google Analytics central account.

WAP2 Service/project owner UoM Google Analytics training completed by

training key service/project staff.

Branding
BRD01 UoM branding Provide the ability to customise the solution
with UoM logo, branding. Consistent use of
colours and style standards
BRD02 UoM branding Provide the ability to apply consistent colours
and style standards to the solution

BRD03 Usability Allow UoM-specific terminology to be defined

by the system administrator

Supporting Elements & Requirements

i This section is used to capture the requirements for partners and products that are necessary to the service
Organisational Change Management & Communication
OCM1
OCM2
OCM3
ITS Technologies & Tools - Service & Operations Management
SOM1
SOM2
SOM3
Training & Education
TED1
TED2
TED3
Operational Acceptance Package (Operational handover)
i The following are standard requirements that apply to most projects. Your sponsor should be familiarised with them an
OAP1 Service Model Guide Provide Service Model Guide document prior
to implementation of the solution.
OAP2 Specific Support Provide Specific Support
procedures/KBAs/Wis procedures/KBAs/WIs prior to implementation
of the solution.
OAP3 Technical Operating Guide Provide Technical Operating Guide document
prior to implementation of the solution.
OAP4 Specific Technical Provide Specific Technical Operating
Operating procedures/KBAs/WIs prior to implementation
procedures/KBAs/Wis of the solution.
OAP5 Training for support staff Provide comprehensive training for personnel
supporting the maintenance and upgrade of
the IT components of the solution.

Project Services | Requirements Traceability Matrix

688167766.xlsx
 OAP6 Training for SMEs Provide business subject matter experts with
comprehensive training in the business use of
the solution.
OAP7 Ongoing training for users Provide a separate training module or service
for ongoing training in the business use of the
solution.
OAP8 As built' documentation Provide ‘As built’ documentation for the IT
components of the solution.

Project Services | Requirements Traceability Matrix

688167766.xlsx
how to populate the RTM for your project along with many examples.

quirements

Rationale Related IT service Stakeholder Priority

existing IT customer
facing and/or Mandatory
Why is this requirement Who provided this
supporting IT services Desirable
needed? requirement?
that the requirement Optional
relates to

y manage the service(s) when operational

Project Services | Requirements Traceability Matrix

688167766.xlsx
Project Services | Requirements Traceability Matrix
688167766.xlsx
factors must the solution conform to? Failure of the solution to conform to these will have direct implications for the University.
oo early in the project. When a solution approach has been selected, you should revisit this section and add any additional relevant standards that must be adhered to.
Failure to comply may
result in significant
financial and reputational
damage for the University.
Failure to comply may
result in significant
financial and reputational
damage for the University.
Failure to comply may
result in significant
financial and reputational
damage for the University.
Failure to comply may
result in significant
financial and reputational
damage for the University.

Failure to comply may

result in significant
financial and reputational
damage for the University.
Failure to comply may
result in significant
financial and reputational
damage for the University.

pport teams to effectively technically maintain, support and operate the service(s) once implemented into production

Project Services | Requirements Traceability Matrix

688167766.xlsx
ty systems. Your sponsor should be familiarised with them and endorse them. You may remove them if they are not applicable to your project.
ution hosted externally, e.g. Student Gmail, you should refer to the Externally Hosted System Documentation Request for guidance on the sort of considerations that
Simplifies access and IT Security and Risk Mandatory
improves usability. Manager

IT Security and Risk Mandatory

Manager

IT Security and Risk Mandatory

Manager

IT Security and Risk Mandatory

Manager

IT Security and Risk Mandatory

Manager
IT Security and Risk Mandatory
Manager
IT Security and Risk Mandatory
Manager

IT Security and Risk Mandatory

Manager

IT Security and Risk Mandatory

Manager

IT Security and Risk Mandatory

Manager
IT Security and Risk Mandatory
Manager
IT Security and Risk Mandatory
Manager

IT Security and Risk Mandatory

Manager

IT Security and Risk Mandatory

Manager

IT Security and Risk Mandatory

Manager

IT Security and Risk Mandatory

Manager

Project Services | Requirements Traceability Matrix

688167766.xlsx
 IT Security and Risk Optional
Manager

IT Security and Risk Mandatory

Manager

IT Security and Risk Mandatory

Manager

IT Security and Risk Mandatory

Manager

re to have a web interface. Your sponsor should be familiarised with them.

Section 24 of the Disability Web Accessibility Program Mandatory
Discrimination Act makes it Leader
unlawful to discriminate,
when providing goods and
services, against another
person on the basis of the
person's disability.

The University has Web Accessibility Program Mandatory

endorsed WCAG 2.0 Level Leader
AA as its standard in
relation to web content.
More information is
available at
http://www.w3.org/.

Allows non-text content to Web Accessibility Program Mandatory

interpreted by assistive Leader
technologies, such as
Braille readers and speech
synthesizers.
Labels need to be explicitly Web Accessibility Program Mandatory
associated with form input Leader
fields in order for them to
be read by assistive
technologies, such as
Braille readers and screen
readers.

Users with visual Web Accessibility Program Mandatory

impairments and deafness Leader
require audio descriptions,
captions and/or transcripts
to help them access
content contained in video
and audio.

Project Services | Requirements Traceability Matrix

688167766.xlsx
Most screen reader users Web Accessibility Program Mandatory
navigate content using Leader
structural mark-up such as
heading tags and lists
rather than in a linear
fashion. Correct structural
markup also allows content
to be accessed by a wide
variety of platforms,
including mobile and
handheld devices.

All users, particularly those Web Accessibility Program Mandatory

with vision impairments, Leader
have trouble reading text if
the contrast is insufficient.
Screen reader users have Web Accessibility Program Mandatory
difficulty navigating data Leader
tables if columns and rows
are not given headings.
Users with vision Web Accessibility Program Mandatory
impairments often have to Leader
increase the text size in
order to be able to read
content.
40% of people with a motor Web Accessibility Program Mandatory
impairment have difficulty Leader
using their hands. Many
have trouble using mice
because of limited hand-
eye co-ordination, trouble
finding a pointer or hand
tremors.

Many users with disabilities Web Accessibility Program Mandatory

take longer to find things, Leader
read things and physically
respond to events.

Users with photosensitive Web Accessibility Program Mandatory

seizure disorders can have Leader
a seizure triggered by
content that flashes at
certain frequencies for
more than a few flashes.

Consistent navigation Web Accessibility Program Mandatory

makes it easier for all Leader
users to keep track of their
location, particularly those
with memory or reading
problems.

Both assistive technologies Web Accessibility Program Mandatory

and conventional user Leader
agents can render text
more accurately when the
language of the web page
is identified.

Project Services | Requirements Traceability Matrix

688167766.xlsx
 The synthetic speech of Web Accessibility Program Mandatory
screen readers makes it Leader
difficult for users to
understand spatial
relationships and users
with cognitive limitations
become confused if
components appear in
different places on different
pages.

Everyone makes mistakes. Web Accessibility Program Mandatory

However some people Leader
have more difficulty
creating error-free input
and detecting that they
have made an error.

Adding skip links allows Web Accessibility Program Mandatory

users of adaptive Leader
technologies to by pass
repeated areas of content,
that often appear at the top
of the page, and access
content directly.

Both search engines and Web Accessibility Program Mandatory

screen readers commonly Leader
navigate pages by looking
at link text.
Users of voice Web Accessibility Program Mandatory
synthesizers and Braille Leader
readers rely on page titles
to identify pages when they
have multiple pages open.

Changes to page layout Web Accessibility Program Mandatory

caused via Javascript are Leader
often are not reported to
assistive technologies

h allow users to author content that will be viewable via the web. For examples, a CMS, blog or wiki.
The ATAG set out Web Accessibility Program Desirable
guidelines for ensuring that Leader
any web content generated
by users is accessible.
If the system allows users Web Accessibility Program Desirable
to enter information that Leader
will automatically generate
web content, then the
system should ensure that
the content is accessible.

If the system allows users Web Accessibility Program Desirable

to edit content, then the Leader
accessibility of the content
should be preserved.
The system shouldn't Web Accessibility Program Desirable
restrict the ability of users Leader
to create accessible
content.
If the system allows users Web Accessibility Program Desirable
to style content (e.g. text) Leader
then options should prompt
them to produce
accessible content.

Project Services | Requirements Traceability Matrix

688167766.xlsx
 If the system allows users Web Accessibility Program Desirable
to upload images, it should Leader
prompt them to provide alt
text.
If the system allows users Web Accessibility Program Desirable
to create content using Leader
templates, then those
templates themselves
should be accessible.
If the system allows Web Accessibility Program Desirable
authors to generate Leader
content using code
snippets (e.g. a table or
list), then those code
snippets should be
accessible.

If the system should Web Accessibility Program Desirable

provide a mechanism for Leader
authors to allow them to
check if their content is
accessible.
The system should provide Web Accessibility Program Desirable
help content authors to Leader
correct accessibility
problems.
Accessible content Web Accessibility Program Desirable
features should be active Leader
by default.
The system documentation Web Accessibility Program Desirable
should help content Leader
authors to correct
accessibility problems.

re to have a user-facing interface. Your sponsor should be familiarised with them and endorse them. You may remove them if they are not applicable to your project

The system will operate User Experience Design Mandatory

effectively for students and Manager
staff within the University.
A significant and growing User Experience Design Mandatory
percentage of the Manager
proposed users are free to
use browsers of their
choosing. We must make
reasonable efforts to
support the majority of
those users.

A significant and growing User Experience Design Mandatory

percentage of the Manager
proposed users are free to
use devices of their
choosing. The expectation
of users is now that web-
based systems are
supported by a range of
devices available. Many
users use multiple devices
across this range.

Project Services | Requirements Traceability Matrix

688167766.xlsx
These are the 2 main User Experience Design Mandatory
operating systems used by Manager
smartphone and tablets,
and need to be supported.

Consistency of navigation User Experience Design Mandatory

allows users to always Manager
know where they are in the
system, and be able to
move around the system
freely.

Users need to know where User Experience Design Mandatory

they are in a process or in Manager
the web/mobile site.
Users should be able to User Experience Design Mandatory
complete the tasks that the Manager
system is designed for.
Users will have an User Experience Design Mandatory
expectation on time limits Manager
for tasks.

Provides users with an User Experience Design Mandatory

efficient interface to use. Manager
Consistency will provide User Experience Design Mandatory
familiarisation with users, Manager
and allow them to find
The navigation
information andsystem
complete User Experience Design Mandatory
needs to beefficiently.
tasks more logical and Manager
well organised.
Testing of the navigation
system should be tested
during design

Users should be able to User Experience Design Mandatory

use search as an Manager
alternative to navigation to
find content or tasks.

Improves user satisfaction. User Experience Design Mandatory

Reduces calls to support Manager
desk.

Allows users to recover User Experience Design Desirable

quickly from minor Manager
mistakes.

Reduces training and User Experience Design Mandatory

documentation needs. Manager
Reduces errors. Improves
user satisfaction.
Improves efficiency and User Experience Design Mandatory
user satisfaction. Manager

This allows users to move User Experience Design Mandatory

quickly around the system, Manager
particularly useful when
they are using the system
for long periods of time.

Allows users to view dates User Experience Design Mandatory

in expected format. Manager

Project Services | Requirements Traceability Matrix

688167766.xlsx
 User Experience Design Mandatory
Spelling and grammar
Manager
comply with Australian
standards, and are correct
for the UoM location.

Enable visibility of end- Web Analytics & Reporting Mandatory

user interaction with online Manager
assets. This capability
supports data-driven
decision making and
troubleshooting.

Completion of base-level Web Analytics & Reporting Desirable

Google Analytics training Manager
enables service/project
staff to utilise web analytics
data for production of
reporting on web asset
usage.

The system will be

exposed to external users
and to students
The system will be
exposed to external users
and to students
Terminology must be
understandable by
University staff and
external users

ducts that are necessary to the service

Your sponsor should be familiarised with them and endorse them. You may remove them if they are not applicable to your project.

Project Services | Requirements Traceability Matrix

688167766.xlsx
Project Services | Requirements Traceability Matrix
688167766.xlsx
Date Elicited By NFR Traceability Parent requirements

The ref number of the related

item in the Non-Functional
When was the requirement Who captured the ID of the relevant higher level
Req's Analysis template used
captured? requirement? requirement(s).
to elicit this requirement. Used
to support traceability.

Mandatory column Mandatory column

Project Services | Requirements Traceability Matrix

688167766.xlsx
Project Services | Requirements Traceability Matrix
688167766.xlsx
itional relevant standards that must be adhered to.

Project Services | Requirements Traceability Matrix

688167766.xlsx
ot applicable to your project.
est for guidance on the sort of considerations that

Project Services | Requirements Traceability Matrix

688167766.xlsx
Project Services | Requirements Traceability Matrix
688167766.xlsx
Project Services | Requirements Traceability Matrix
688167766.xlsx
Project Services | Requirements Traceability Matrix
688167766.xlsx
ove them if they are not applicable to your project.

Project Services | Requirements Traceability Matrix

688167766.xlsx
Project Services | Requirements Traceability Matrix
688167766.xlsx
e to your project.

Project Services | Requirements Traceability Matrix

688167766.xlsx
Project Services | Requirements Traceability Matrix
688167766.xlsx
Requirements Group ID Conflicting requirements Requirement Status Comments / Questions / Issues

Record any comments, questions or issues

within this column and place your initials at
the end of your comment. Example: More
ID for a group of related ID of other requirement(s) that Current status of each
chocolate please. [DH]
requirements. are in conflict. requirement.
Note: If a requirement has been stated as
'Out of Scope' then the reason and the new
owner of the requirements must be stated

New
New
New
New
New
New

New
New
New
New
New
New

New
New
New

New
New
New

New
New

New
New

New
New

New

Project Services | Requirements Traceability Matrix

688167766.xlsx
 New
New

New
New
New

New

New
New

New

New
New

New

New
New

New

New
New

New

New
New

New

New
New

New

Project Services | Requirements Traceability Matrix

688167766.xlsx
 New
New

New
New
New

New
New
New

New Failure to comply may result in

significant financial and reputational
damage for the University.

New Failure to comply may result in

significant financial and reputational
damage for the University.

New Failure to comply may result in

significant financial and reputational
damage for the University.

New Failure to comply may result in

significant financial and reputational
damage for the University.

New Failure to comply may result in

significant financial and reputational
damage for the University.

New Failure to comply may result in

significant financial and reputational
damage for the University.

New
New

New
New
New

New
New
New

New
New

Project Services | Requirements Traceability Matrix

688167766.xlsx
 New

New

New

New

New

New

New

New

New

New

New

New

New

New

New

New

New

Project Services | Requirements Traceability Matrix

688167766.xlsx
 New

New

New

New

New

New

New

New

New

Project Services | Requirements Traceability Matrix

688167766.xlsx
 New

New

New

New

New

New

New

New

New

Project Services | Requirements Traceability Matrix

688167766.xlsx
 New

New

New

New

New

New

New

New

New

New

New

Project Services | Requirements Traceability Matrix

688167766.xlsx
 New

New

New

New

New

New

New

New

New

New

Project Services | Requirements Traceability Matrix

688167766.xlsx
 New

New

New

New

New

New

New

New

New

New

New

New

New

New

New

Project Services | Requirements Traceability Matrix

688167766.xlsx
 New

New

New

New

New

New

New
New
New

New
New
New

New
New
New

New

New

New

New

New

Project Services | Requirements Traceability Matrix

688167766.xlsx
 New

New

New

Project Services | Requirements Traceability Matrix

688167766.xlsx
Testable requirement?
Acceptance criteria Accepted?

If the requirement is not

testable, how can we know Has sponsor accepted the
Is this requirement testable?
this requirement has been solution for each requirement?
fulfilled?

Project Services | Requirements Traceability Matrix

688167766.xlsx
Project Services | Requirements Traceability Matrix
688167766.xlsx
Project Services | Requirements Traceability Matrix
688167766.xlsx
Project Services | Requirements Traceability Matrix
688167766.xlsx
Project Services | Requirements Traceability Matrix
688167766.xlsx
Project Services | Requirements Traceability Matrix
688167766.xlsx
Yes

Yes

Yes

Yes

Yes

Project Services | Requirements Traceability Matrix

688167766.xlsx
Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Project Services | Requirements Traceability Matrix

688167766.xlsx
Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Project Services | Requirements Traceability Matrix

688167766.xlsx
Yes

Yes

Yes

Project Services | Requirements Traceability Matrix

688167766.xlsx
Project Services | Requirements Traceability Matrix
688167766.xlsx
 #REF!
Requirements Conflicting
ID High level capability Description Rationale Stakeholder Priority Date Parent requirements Requirement Status
Group ID requirements
High level process, function or Who provided Mandatory When was the ID of other
Unique A description of each requirement that is: Cohesive, Complete, Consistent, Correct, Feasible, ID of the relevant higher ID for a group of related Current status of each
capability that the requirement Why is this requirement needed? this Desirable requirement requirement(s) that are
identifier Modifiable, Unambiguous and Testable. level requirement(s). requirements. requirement.
addresses. requirement? Optional captured? in conflict.

Service level
i This section is used to capture the needs of the business in regards to the support they'll need in the event of requests or problems of any type.
Example Service Desk support Level 1 support from the ITS Service Desk must be available for users between 8am and 5pm GD Mandatory 7 Apr 2012 HLR2 New
on University business days.
Example Response levels Provide responses for level 1 support requests within 2 hours. GD Mandatory 7 Apr 2012 HLR2 New
SLE1 New
SLE2 New
SLE3 New
System availability
Example Availability Ensure that the system will be consistently available to users between the hours of 8 am to 8 GD Mandatory 7 Apr 2012 HLR2 New
pm on University business days. There should be no more than 12 hours of accumulated
outages during these business hours within any calendar year.

SAV1 New
SAV2 New
SAV3 New
System performance
Example Online response time All screens should complete processing and return a response to the user within 5 seconds. Improves operational efficiency and user GD Mandatory 7 Apr 2012 HLR2 New
satisfaction.
SPE1 New
SPE2 New
SPE3 New
System capacity
i This section is used to capture the information about expected numbers of users and transactions along with anticipated growth patterns.
Example Availability Ensure that the solution is available to, and equally effective for, all users. Users will be in GD Mandatory 7 Apr 2012 HLR2
the following locations:
- Main Parkville campus
- Southbank campus
- Burnley campus
- Shepparton campus
- Dookie campus
- Creswick campus
- Werribee veterinary campus

Example Number of users The expected maximum number of users of the solution per year is <n>. Ensure that the GD Mandatory 7 Apr 2012 HLR2
solution can support the data volumes expected to be generated by this many users.

Example Concurrent users The expected number of concurrent users can vary from <n> to <n>. Ensure that the solution GD Mandatory 7 Apr 2012 HLR2
can still meet the performance requirements with this many concurrent users.

Example Annual transaction volumes It is expected that up to 250,000 books will be borrowed via the new system per year and that GD Mandatory 7 Apr 2012 HLR2
this will grow by 20% per year. Ensure that the solution can support this number of
transactions for at least the next 20 years.
Example Peak transaction volumes It is expected that up to 80% of the anticipated subject enrolments will occur within a one GD Mandatory 7 Apr 2012 HLR2
week period. Ensure that the solution can support this level of activity.

SCA1 New
SCA2 New
SCA3 New
System configuration
Example Ease of configuration changes Allow authorised business users to alter financial delegation limits in the production Reduces overheads and increases ability of GD Mandatory 7 Apr 2012 HLR2 New
environment without technical knowledge or support. business to self-serve.
SCO1 New
SCO2 New
SCO3 New
Continuity
Example Disaster recovery In the event of a major system failure, ensure that the system can be available to users again GD Mandatory 7 Apr 2012 HLR2 New
within 4 hours.
Example Disaster recovery In the event of a major system failure, ensure that no more than 24 hours of data is ever lost. GD Mandatory 7 Apr 2012 HLR2 New

CON1 New
CON2 New
CON3 New

Printed: 08/30/2023 18:41:20 Page 59 of 63

 #REF!
Requirements Conflicting
ID High level capability Description Rationale Stakeholder Priority Date Parent requirements Requirement Status
Group ID requirements
Security
i The following are standard requirements that apply to most University systems. Your sponsor should be familiarised with them and endorse them. You may remove them if they are not applicable to your project.
If there is an intent by the business to have any component of the solution hosted externally, e.g. Student Gmail, you should refer to the ITS Externally Hosted System Checklist for guidance on the sort of considerations that
i may need to be factored into the requirements.
SEC1 Central user authentication Ensure that the electronic identities of all users are established through the Simplifies access and improves usability. Mandatory New
University’s Identity and Access Management tool before allowing access to the
solution.
SEC2 External system Ensure that external systems and interfaces are identified, authenticated, and Mandatory New
authentication authorised before granting access to the solution.
SEC3 Comply with ITS Security Ensure that the solution complies with the requirements stated in the ITS Security Mandatory New
Policy Policy. At a minimum, ensure that access to confidential or sensitive information is
protected by a password.
SEC4 Controlled access Ensure that access to information and functionality is restricted through access levels Mandatory New
that incorporate segregation of incompatible duties.
SEC5 Protection against malware Ensure that the solution is protected from viruses and malicious code. Mandatory New
SEC6 Logging of security incidents Ensure that the solution records information related to potential or actual security Mandatory New
incidents.
SEC7 Non-repudiation Ensure that the solution can record details of system events and the responsible Mandatory New
individual such that they cannot deny that the event took place.
SEC8 Encryption of stored data Ensure that sensitive information is encrypted in order to protect the operations and Mandatory New
privacy of the University and its stakeholders.
SEC9 Encryption of transmitted Ensure that all data that is not generally available to the public that is to be Mandatory New
data transmitted over the Internet is encrypted.
SEC10 Hardware security Ensure that hardware is physically secure and kept cool and dry. Mandatory New
SEC11 Data accuracy Ensure that all data held or transported by the solution is kept complete, accurate Mandatory New
and valid.
SEC12 Minimise access to ports Ensure that each system component only exposes the minimum number of required Mandatory New
network ports both internally (internal University network) and externally (non-
University network/Internet).
SEC13 Appropriate placement of Ensure that each component of the solution has been placed in the appropriate Mandatory New
solution components network zone.
SEC14 Testing and verification of Ensure that each component of the system solution is tested and verified to be Mandatory New
components compliant with ITS security build standards.
SEC15 Testing and verification of Ensure that all components of the solution are tested for security vulnerabilities, mis- Mandatory New
components configurations and control weaknesses and that all known issues are identified and
corrected.
SEC16 System checklist / risk If the solution is to be externally hosted, ensure that the ITS Externally Hosted Mandatory New
assessment System Checklist / Risk Assessment is completed and any outstanding risks are
accepted by the CIO or his/her delegate.
SEC17 Security controls Ensure that all required ITS security controls have been implemented and confirmed Optional New
through testing that they are operating effectively.
SEC18 Disaster recovery plans Ensure that disaster recovery plans are adequately documented and submitted to the Mandatory New
IT Security and Risk Manager.
SEC19 Testing of disaster recovery Ensure that disaster recovery plans for the solution are tested successfully, i.e. Mandatory New
plans testing has confirmed that Recovery Time Objective (RTO) and Recovery Point
Objective (RPO) requirements can be met.
SEC20 Provision of security related Ensure that results of all security related testing and all security related project Mandatory New
tests and results artefacts are provided to the IT Security and Risk Manager.
Accessibility
i The following are standard requirements that apply to systems that are to have a web interface. Your sponsor should be familiarised with them.
ACC1 Accessibility for all users Ensure that web services can be accessed by all users, including those with Section 24 of the Disability Discrimination Mandatory New
disabilities. Act makes it unlawful to discriminate,
when providing goods and services,
against another person on the basis of the
person's disability.
ACC2 Comply with WCAG 2.0 Ensure that web accessible elements of the solution comply with the Web Content The University has endorsed WCAG 2.0 Mandatory New
Level AA Accessibility Guidelines set out in WCAG 2.0 Level AA. Level AA as its standard in relation to web
content. More information is available at
http://www.w3.org/.
ACC3 Text alternatives Provide text alternatives for any non-text content such as images. Allows non-text content to interpreted by Mandatory New
assistive technologies, such as Braille
readers and speech synthesizers.
ACC4 Labels for form fields Add labels to form fields. Labels need to be explicitly associated Mandatory New
with form input fields in order for them to
be read by assistive technologies, such as
Braille readers and screen readers.

Printed: 08/30/2023 18:41:20 Page 60 of 63

 #REF!
Requirements Conflicting
ID High level capability Description Rationale Stakeholder Priority Date Parent requirements Requirement Status
Group ID requirements
ACC5 Alternatives for video and Provide alternatives for time-based media such as video and audio. Users with visual impairments and Mandatory New
audio deafness require audio descriptions,
captions and/or transcripts to help them
access content contained in video and
audio.
ACC6 Structure markup Use structural markup such as headings (e.g. <h1> - <h6>) and lists (e.g. <ul> <ol>) Most screen reader users navigate Mandatory New
to organise content. content using structural mark-up such as
heading tags and lists rather than in a
linear fashion. Correct stuctural markup
also allows content to be accessed by a
wide variety of platforms, including mobile
and handheld devices.

ACC7 Contrast Provide a contrast ratio of 4.5:1 between foreground text and the background. All users, particularly those with vision Mandatory New
impairments, have trouble reading text if
the contrast is insufficient.
ACC8 Data table headings Add column and row headings (e.g. <th>) to data tables. Screen reader users have difficulty Mandatory New
navigating data tables if columns and rows
are not given headings.
ACC9 Increased text size Ensure that all pages are readable and functional when text size is increased by up Users with vision impairments often have Mandatory New
to 200%. to increase the text size in order to be able
to read content.
AC10 Accessibility via keyboard Make all functionality available via the keyboard. 40% of people with a motor impairment Mandatory New
have difficulty using their hands. Many
have trouble using mice because of limited
hand-eye co-ordination, trouble finding a
pointer or hand tremors.
ACC11 Sufficient time for reading Provide users with enough time to read and use content. Many users with disabilities take longer to Mandatory New
find things, read things and physically
respond to events.
ACC12 Avoid seizures Do not design content in a way that is known to cause seizures. Users with photosensitive seizure Mandatory New
disorders can have a seizure triggered by
content that flashes at certain frequencies
for more than a few flashes.
ACC13 Consistent navigation, Help users navigate, find content and determine where they are via consistent Consistent navigation makes it easier for Mandatory New
headings and links navigation, headings and links. all users to keep track of their location,
particularly those with memory or reading
problems.
ACC14 Language identification Identify the human language of the page (e.g. English). Both assistive technologies and Mandatory New
conventional user agents can render text
more accurately when the language of the
web page is identified.
ACC15 Consistent content order Present content in a consistent order from page to page and make the behaviour of The synthetic speech of screen readers Mandatory New
and predictable behaviour interactive components predictable. makes it difficult for users to understand
spatial relationships and users with
cognitive limitations become confused if
components appear in different places on
different pages.

ACC16 Labels, cues and Provide sufficient labels, cues and instructions for users when completing forms. Everyone makes mistakes. However some Mandatory New
instructions people have more difficulty creating error-
free input and detecting that they have
made an error.
ACC17 Skipping to content Add skip to content links. Adding skip links allows users of adaptive Mandatory New
technologies to by pass repeated areas of
content, that often appear at the top of the
page, and access content directly.
ACC18 Avoid 'click here' Avoid 'click here' links. Both search engines and screen readers Mandatory New
commonly navigate pages by looking at
link text.
ACC19 Page titles Add meaningful page titles. Users of voice synthesizers and Braille Mandatory New
readers rely on page titles to identify
pages when they have multiple pages
open.
ACC20 Javascript and adaptive Ensure that changes to the page via Javascript are reported to adaptive Changes to page layout caused via Mandatory New
technologies technologies. Javascript are often are not reported to
assistive technologies
Author Generated Content
i This section is optional. It is intended to be used in circumstances in which the application allows users to author content that will be viewable via the web. For examples, a CMS, blog or wiki.
AGC1 Comply with ATAG Ensure that author content generated by the solution comply with the Authoring Tool The ATAG set out guidelines for ensuring New
Accessibility Guidelines (ATAG). that any web content generated by users
is accessibile.

Printed: 08/30/2023 18:41:20 Page 61 of 63

 #REF!
Requirements Conflicting
ID High level capability Description Rationale Stakeholder Priority Date Parent requirements Requirement Status
Group ID requirements
AGC2 Accessible automatic Ensure that automatically specified content is accessible. If the system allows users to enter New
content information that will automatically generate
web content, then the system should
ensure that the content is accessibile.
AGC3 Preservation of accessibility Ensure that accessibility information is preserved. If the system allows users to edit content, New
information then the accessibility of the content
should be preserved.
AGC4 Accessible content Ensure accessible content production is possible. The system shouldn't restrict the ability of New
production users to create accessibile content.
AGC5 Guide authors Guide authors to produce accessible content. If the system allows users to style content New
(e.g. text) then options should prompt
them to produce accessibile content.
AGC6 Alternate content Assist authors with managing alternative content for non-text content. If the system allows users to upload New
images, it should prompt them to provide
alt text.
AGC7 Accessible templates Assist authors with accessible templates. If the system allows users to create New
content using templates, then those
templates themselves should be
accessible.
AGC8 Accessible pre-authored Assist authors with accessible pre-authored content. If the system allows authors to generate New
content content using code snippets (e.g. a table
or list), then those code snippets should
be accessible.
AGC9 Automatic accessibility Assist authors in checking for accessibility problems. If the system should provide a mechanism New
checks for authors to allow them to check if their
content is accessible.
AGC10 Automatic accessibility Assist authors in repairing accessibility problems. The system should provide help content New
corrections authors to correct accessibility problems.
AGC11 Support accessible content Ensure the availability of features that support the production of accessible content. Accessibile content features should be New
production active by default.
AGC12 Documentation Ensure that documentation promotes the production of accessible content. The system documentation should help New
content authors to correct accessibility
problems.
Usability
i The following are standard requirements that apply to systems that are to have a user-facing interface. Your sponsor should be familiarised with them and endorse them. You may remove them if they are not applicable to your project.
i Some other usability factors to consider are:
i - keyboard accelerators
i - languages required
i - online help
USA1 Usability within Windows Ensure that the solution supports Windows operating systems. The majority of the proposed users use New
Windows based systems. Either Windows
XP or higher.
USA2 Usability on Macintosh Ensure that the solution supports Macintosh operating systems. Twenty five percent (25%) of University New
users use Macintosh workstations.
USA3 Common browsers and If the solution is going to be web-based, ensure that it fully supports the devices, A significant percentage of the proposed New
devices browser types and browser versions that are commonly used by the general users are free to use browsers of their
University audience as determined by the top 95% of hits on the University's Home choosing. We must make reasonable
page over the last 3 months. efforts to support the majority of those
users.
USA4 Graceful degradation If the solution is going to be web-based, ensure that the solution gracefully degrades A significant percentage of the proposed New
but remains functional for the other 5% of users. users are free to use browsers of their
choosing. We must make reasonable
efforts to support the majority of those
users.
USA5 Web standards If the solution is going to be web-based, ensure that all significant current and Adherence to standards is important in New
impending standards for web-based development are reflected in the solution design. ensuring the usability, portability,
maintainability and longevity of the
solution.
USA6 User-friendly error Ensure that the system provides user-friendly error messages in all circumstances. Improves user satisfaction. Reduces calls New
messages to support desk.
USA7 Undo feature Provide an 'undo' feature within the tool. Allow users to undo at least the last ?? Allows users to recover quickly from minor New
edits within the screen they are working on or back to the most recent save. mistakes.

Printed: 08/30/2023 18:41:20 Page 62 of 63

<project name> - Business Rules
i Columns in the yellow sections are for Business Analysts to complete.
Related
ID Description Rationale Source Date Parent rules
requirements
Who or where ID(s) of related
Unique A description of each business rule that is relevant to the proposed solution. Each rule should be reflected in one or more requirements that are designed When was the ID of the relevant higher
Why is this requirement needed? did this rule requirements or
identifier to support or enforce the business rule. rule captured? level rule(s).
come from? requirement groups

Business Rules
i Business rules can be distinguished as being invariant and independent requirements that either constrain structure or behaviour or require something to be done as the result of a defined trigger condition.
i These rules must be respected and supported by all persons, processes and systems.
i
i Business rules generally fall into two groups: Structural rules and Operating rules.
i Structural rules can be used to:
i - define terminology
i - define the nature or operating structure of an organisation
i - define the nature or structure of entities that the organisation works with
i - define the allowable relationships between the entities that the organisation works with.
i Operating rules can be used to:
i - define what actions must be performed based on some trigger condition
i - define what actions cannot be performed under certain conditions
i - define how information should be derived or transformed.
i
i Most importantly, you should remember that business rules exist and govern the structure and operations of the business regardless of what systems may or may not be in place.
i The requirements captured in this document should be in alignment with these business rules. You can use the Related requirements column to associate business rules with the related requirements.
i The solution that is delivered should support the implementation and enforcement of the business rules.
i
i Business rules should be:
i - stated in appropriate terminology to enable domain SMEs to validate the rules
i - documented independently of how they will be enforced
i - stated at the atomic level and in declarative format
i - separated from processes that the rule supports or constrains
i - maintained in a manner that enables the organisation to monitor & adapt the rules as the business policies change.
i
Example No more than 20% of program participants can be foreign nationals. Commonwealth law requires us to ensure that DIISR
no more than 20% of program participants are
foreign nationals.

Example Students must provide proof of their citizenship status before their admittance to a mobility program is approved. GD BR1 G007
BR1
BR2
BR3
BR4
BR5
BR6
BR7
BR8
BR9
BR10
BR11
BR12
BR13

Project Services | Requirements Traceability Matrix Page 63 of 63

688167766.xlsx