T MU AM 06004 ST

Standard

Requirements Schema

Version 3.0
Issue date: 13 August 2021
Effective date: 13 August 2021

© State of NSW through Transport for NSW 2021

 T MU AM 06004 ST
Requirements Schema
Version 3.0
Effective date: 13 August 2021

Disclaimer
This document has been prepared by Transport for NSW (TfNSW) specifically for its own use
and is also available for use by NSW public transport agencies for transport assets.

Any third parties considering use of this document should obtain their own independent
professional advice about the appropriateness of using this document and the accuracy of its
contents. TfNSW disclaims all responsibility and liability arising whether directly or indirectly out
of or in connection with the contents or use of this document.

TfNSW makes no warranty or representation in relation to the accuracy, currency or adequacy

of this document or that the document is fit for purpose.

The inclusion of any third party material in this document, does not represent an endorsement
by TfNSW of any third party product or service.

For queries regarding this document, please email Transport for NSW Asset Management Branch at
standards@transport.nsw.gov.au or visit www.transport.nsw.gov.au

© State of NSW through Transport for NSW 2021

 T MU AM 06004 ST
Requirements Schema
Version 3.0
Effective date: 13 August 2021

Standard governance
Owner: Senior Manager Systems Engineering, Asset Management Branch
Authoriser: Director Asset Management Partnering and Services, Asset Management Branch
Approver: Executive Director, Asset Management Branch on behalf of the AMB Configuration Control
Board

Document history
Version Summary of changes
1.0 First issue, 04 December 2014.
2.0 Second issue, 14 April 2016.
Added clarification that all of the schema fields are mandatory. Added requirements for satisfies
links, verifies links and validates links.
3.0 Third issue
Incorporated the agreed contents of appended technical note TN 027:2018
Incorporated additional metadata fields to reflect Digital Engineering outputs on projects
Incorporated changes/additions to other metadata fields due to stakeholder feedback

© State of NSW through Transport for NSW 2021 Page 3 of 36

 T MU AM 06004 ST
Requirements Schema
Version 3.0
Effective date: 13 August 2021

Preface
The Asset Management Branch (AMB), formerly known as Asset Standards Authority (ASA) is a
key strategic branch of Transport for NSW (TfNSW). As the network design and standards
authority for NSW Transport Assets, as specified in the ASA Charter, the ASA identifies,
selects, develops, publishes, maintains and controls a suite of requirements documents on
behalf of TfNSW, the asset owner.

The ASA deploys TfNSW requirements for asset and safety assurance by creating and
managing TfNSW's governance models, documents and processes. To achieve this, the ASA
focuses on four primary tasks:

• publishing and managing TfNSW's process and requirements documents including TfNSW
plans, standards, manuals and guides

• deploying TfNSW's Authorised Engineering Organisation (AEO) framework

• continuously improving TfNSW’s Asset Management Framework

• collaborating with the Transport cluster and industry through open engagement

The AEO framework authorises engineering organisations to supply and provide asset related
products and services to TfNSW. It works to assure the safety, quality and fitness for purpose of
those products and services over the asset's whole-of-life. AEOs are expected to demonstrate
how they have applied the requirements of ASA documents, including TfNSW plans, standards
and guides, when delivering assets and related services for TfNSW.

Compliance with ASA requirements by itself is not sufficient to ensure satisfactory outcomes for
NSW Transport Assets. The ASA expects that professional judgement be used by competent
personnel when using ASA requirements to produce those outcomes.

About this document

This document aims to provide a standard schema for requirements, to help the exchange of
consistent information across TfNSW divisions and suppliers that are involved in the planning
and acquisition of TfNSW new or altered assets.

This document has been developed in consultation with key stakeholders within TfNSW.

This document is the third issue.

© State of NSW through Transport for NSW 2021 Page 4 of 36

 T MU AM 06004 ST
Requirements Schema
Version 3.0
Effective date: 13 August 2021

Table of contents
1. Introduction .............................................................................................................................................. 6
2. Purpose .................................................................................................................................................... 6
2.1. Scope ..................................................................................................................................................... 6
2.2. Application ............................................................................................................................................. 6
3. Reference documents ............................................................................................................................. 7
4. Terms and definitions ............................................................................................................................. 7
5. TfNSW requirements schema................................................................................................................. 9
6. Structuring requirements information................................................................................................. 10
6.1. Requirement element-level information ............................................................................................... 10
6.2. Requirement management information ............................................................................................... 11
7. Structuring verification information .................................................................................................... 17
7.1. Verification element-level information .................................................................................................. 17
7.2. Verification activity information ............................................................................................................ 18
8. Structuring validation information....................................................................................................... 19
8.1. Validation element–level information ................................................................................................... 19
8.2. Validation activity information .............................................................................................................. 20
9. Linking and traceability ........................................................................................................................ 21
Appendix A Example schema implementation (non-DE enabled projects) ...................................... 25
A.1. Example business requirements (non-DE) .......................................................................................... 26
A.2. Example system requirements (non-DE)............................................................................................. 27
A.3. Example subsystem requirements (non-DE) ....................................................................................... 28
A.4. Example verification activities (non-DE) .............................................................................................. 29
A.5. Example validation activities (non-DE) ................................................................................................ 30
Appendix B Example schema implementation (DE-enabled project) ............................................... 31
B.1. Example business requirements (DE-enabled project) ....................................................................... 32
B.2. Example system requirements (DE-enabled project) .......................................................................... 33
B.3. Example subsystem requirements (DE-enabled project) .................................................................... 34
B.4. Example verification activities (DE-enabled project) ........................................................................... 35
B.5. Example validation activities (DE-enabled project) ............................................................................. 36

© State of NSW through Transport for NSW 2021 Page 5 of 36

 T MU AM 06004 ST
Requirements Schema
Version 3.0
Effective date: 13 August 2021

1. Introduction
Different divisions of Transport for New South Wales (TfNSW), transport agencies, and the
TfNSW supply chain have previously used ad hoc bespoke requirement structures or schemas
on projects. Using different schemas has created difficulties in exchanging common and
consistent requirements information between entities.

A common requirements schema avoids the need to transcribe and restructure requirements
information (metadata) passed between different organisations.

2. Purpose
This document provides a standard schema for requirements data definition and management
for exchange of requirements between organisations on TfNSW projects. It elaborates on the
guidance provided in T MU AM 06007 GU Guide to Requirements Definition and Analysis.

2.1. Scope
The document defines a common minimum requirements schema for use on major transport
capital projects with medium to high levels of novelty, complexity or risk, with additional optional
requirements included for projects utilising Digital Engineering (DE) methodologies (shaded in
grey in the tables).

This document is not for use on maintenance projects except where they are major refresh or
upgrade projects that occur as part of the maintenance program, where new or altered
requirements and assets are realised.

This document does not specify or cover the use of requirements management tools.

This document does not cover the specialised requirements schema for software testing. Refer
to T MU TE 81003 ST Test Processes and Documentation for Programmable Electronic
Systems and Software for this specialised requirement.

This document does not cover the broader topic of requirements definition and analysis. Refer
to T MU AM 06007 GU for guidance.

This document does not cover commercial contractual arrangements.

2.2. Application
This standard is to be used by TfNSW divisions, agencies and the suppliers that define and
manage requirements for planning and acquiring TfNSW new or altered assets.

© State of NSW through Transport for NSW 2021 Page 6 of 36

 T MU AM 06004 ST
Requirements Schema
Version 3.0
Effective date: 13 August 2021

3. Reference documents
The following documents are cited in the text. For dated references, only the cited edition
applies. For undated references, the latest edition of the referenced document applies.

International standards

ISO 9000 Quality management systems — Fundamentals and vocabulary

ISO 15288 Systems and software engineering — System life cycle processes

ISO 24765 Systems and software engineering — Vocabulary

ISO 29148 Systems and software engineering — Life cycle processes — Requirements
Engineering

INCOSE Systems Engineering Handbook

Transport for NSW standards

DMS-ST-207 Digital Engineering Standard – Part 2 – Requirements

T MU AM 06007 GU Guide to Requirements Definition and Analysis

T MU TE 81003 ST Test Processes and Documentation for Programmable Electronic Systems

and Software

T MU AM 06006 ST Systems Engineering

T MU AM 06006 GU Systems Engineering

T MU AM 06010 GU Business Requirements Specification

T MU AM 06016 GU Guide to Verification and Validation

4. Terms and definitions

The following terms and definitions apply in this document:

Acceptance test (as defined in ISO 24765)

1. Testing conducted to determine whether a system satisfies its acceptance criteria and to
enable the customer to determine whether to accept the system.

2. Formal testing conducted to enable a user, customer, or other authorized entity to determine
whether to accept a system or component.

AEO Authorised Engineering Organisation

Analysis (as defined in ISO 24765) the process of studying a system by partitioning the system
into parts (functions, components, or objects) and determining how the parts relate to each
other

ASA Asset Standards Authority

© State of NSW through Transport for NSW 2021 Page 7 of 36

 T MU AM 06004 ST
Requirements Schema
Version 3.0
Effective date: 13 August 2021

BR business requirement

BRS a type of specification document that contains business requirements

DE digital engineering

Demonstration (as defined in ISO 24765) a dynamic analysis technique that relies on
observation of system or component behaviour during execution, without need for post-
execution analysis, to detect errors, violations of development standards, and other problems

Factory acceptance test acceptance test carried out at the vendor premises

FAT factory acceptance test

IFAT integrated factory acceptance test

INCOSE International Council on Systems Engineering

Inspection (as defined in ISO 24765) a static analysis technique that relies on visual
examination of development products to detect errors, violations of development standards, and
other problems

Modelling (as defined in ISO 24765) representing a real world process, device, or concept

NA not available, not applicable

Owner (of a requirement) is the entity responsible for meeting the requirement

Requirement (as defined in ISO 29148) statement which translates or expresses a need and its
associated constraints and conditions

Review a method to provide assurance by a competent person that an engineering output

complies with relevant standards and specific requirements is safe and fit for purpose

SAT site acceptance test

Simulation (as defined in ISO 24765) a model that behaves or operates like a given system
when provided a set of controlled inputs

SIT system integration testing

Site acceptance test acceptance test carried out at the destination site

SR system requirement

SRS a type of specification document that contains system requirements

SSR subsystem requirement

SSRS a type of specification document that contains subsystem requirements

Technical requirement a requirement associated with a physical asset, not a process or

general contract requirement

© State of NSW through Transport for NSW 2021 Page 8 of 36

 T MU AM 06004 ST
Requirements Schema
Version 3.0
Effective date: 13 August 2021

Test (as defined in ISO 24765) an activity in which a system or component is executed under
specified conditions, the results are observed or recorded, and an evaluation is made of some
aspect of the system or component

TfNSW Transport for New South Wales

UAT user acceptance test

Uniclass 2015 a unified classification system for all sectors of the UK construction industry

Validation (as defined in ISO 9000) confirmation, through the provision of objective evidence,
that the requirements for a specific intended use or application have been fulfilled

Verification (as defined in ISO 9000) confirmation, through the provision of objective evidence,
that specified requirements have been fulfilled

5. TfNSW requirements schema

The TfNSW requirements schema comprises a standard structure for requirements to enable
the free exchange of requirements information between multiple parties using different
requirements management tools.

The schema identifies the information types (metadata) needed for each requirement, and
provides a standard configuration for requirements management.

The schema identifies the information that is needed for each requirement and standard field
names that can be used by diverse requirements management tools.

The schema describes a data model for the organisation of requirements, and provides a
framework for requirements management.

ISO 15288 Systems and software engineering — System life cycle processes specifies the life
cycle model management process and the International Council on Systems Engineering
(INCOSE) Systems Engineering Handbook specifies the 'V' model. Figure 2 in Section 9 shows
how the schema integrates with the engineering life cycle 'V' model.

ISO 15288 and ISO 29148 Systems and software engineering — Life cycle processes —
Requirements Engineering specify the technical processes of stakeholder requirements
definition, requirements analysis and architectural design. The schema allows for the
management of requirements throughout these technical processes during requirements
decomposition, allocation and solution development.

ISO 15288 and ISO 29148 specify the technical processes of verification and validation and
ISO 15288 specifies the technical processes of integration and transition. The schema provides
a mechanism for tracing integration and composition of a solution throughout these technical
processes.

The requirements schema provides a standard framework for the following activities:

• structuring of requirements

© State of NSW through Transport for NSW 2021 Page 9 of 36

 T MU AM 06004 ST
Requirements Schema
Version 3.0
Effective date: 13 August 2021

• structuring of verification and validation activity evidence

• linking requirements to provide traceability through tracking the requirement decomposition

from system level to subsystem level, and finally to the detailed solution design

• providing traceability through linking verification and validation items to requirements to

ensure that the solution is verified and validated

Appendix A contains a worked example of the requirements schema.

Organisations may include additional information fields to meet their specific requirements,
verification and validation management needs.

6. Structuring requirements information

The requirements schema consists of a number of elements.

The requirements element of the schema is used to store and manage requirements. It can be
used for business requirements, system requirements or subsystem requirements. The
requirements element format is the same for each type of requirement.

6.1. Requirement element-level information

Requirement element-level information provides identifying and management metadata
regarding a particular requirement element containing a collection of requirements.

Each requirement element shall be recorded with its own identifying and administrative
information. Table 1 shows the mandatory information fields (with the exception of the optional
additional DE information in grey shade) for each requirement element.

Table 1 - Requirement element-level information

Field name Description Type Occurs DE field name

Project (DE) Title of the project String One Project name
Type Type of the requirement element. String One Type
Element type is used to differentiate
between business requirements,
system requirements and subsystem
requirements
Name Name of the requirement element String One Document title
Document Project allocated document number of String One Document
number the element number
(DE)
Sources Source(s) of the requirement element String One or Source
more document
number
Owner Owner of the requirement element. String One Contracted
The entity responsible for meeting the organisation
requirement name

© State of NSW through Transport for NSW 2021 Page 10 of 36

 T MU AM 06004 ST
Requirements Schema
Version 3.0
Effective date: 13 August 2021

Field name Description Type Occurs DE field name

Owner code Owner / service provider code of the String One Contracted
(DE) requirement element. organisation
code
Release The date that the version was Date One Date released
date released
Version The version number of the Number One Document
requirement element version
number
Element The status of the requirement element String One State code
status – draft or approved

6.2. Requirement management information

Table 2 shows the mandatory set of information fields (with the exception of optional additional
DE information in grey) that shall be recorded for each requirement. However, for fields where
“Occurs” has a possible value of zero, it is permissible for the field to be empty.

Table 2 - Requirement management information

Field name Description Values Type Occurs DE field

name
Identifier Requirement identifier text (preferably automatic String One Identifier
unique for the project. tool-generated string)
Recommend that the
requirement identifier is
automatically
generated by a tool.
Object type Describes the object • Requirement: a need String One Object type
type in the schema within the scope of work
that needs to be delivered
• Heading: a descriptive
title or subject division
used to structure a set of
requirements or other
objects
• Context: a pretext or
setting, to be read with
the subsequent
requirement(s) for full
understanding
• Information: an
articulation of facts
outside of the scope of
work (in the domain or
delivered by another
scope of work)
• Scope: a physical or
functional limitation of
applicability or extent of
relevance or boundary of
scope of work
• Term: a phrase, definition
or acronym used to
describe something within
the scope of work

© State of NSW through Transport for NSW 2021 Page 11 of 36

 T MU AM 06004 ST
Requirements Schema
Version 3.0
Effective date: 13 August 2021

Field name Description Values Type Occurs DE field

name
Requirement Type of requirement • Technical requirement: String Zero or Requirement
type a property of the one type
operational product (that
exists within the finished
product)
• Process requirement: an
action or step taken to
deliver the product (that
does not exist within the
finished product)
Requirement Level of requirement • Business requirement String One Requirement
level (within the requirement level
hierarchy) • System requirement
• Subsystem requirement
Description Requirement item Text String One Description
description text.
Source Source of the String String One or Document
requirement. more number
Allocation Anticipated Text String Zero 1 or Allocation
apportionment of more
requirement at
decomposition (to be
substantiated with
traceability).
Business requirements
are allocated to system
requirements. System
requirements are
allocated to
subsystems
requirements.
Uniclass Required to the level of Refer to DE Project Data String One or Uniclass 2015
2015 asset information specified in Schema more asset location
location DE Standard code
code (DE) (DMS-ST-207).
Code identifying the
location type. Typically
NA to BRs and most
SRs
Uniclass Required to the level of Refer to DE Project Data String One or Uniclass 2015
2015 asset information specified in Schema more asset location
location DE Standard title
title (DE) (DMS-ST-207).
Title identifying the
location type. Typically
NA to BRs and most
SRs
Asset Code identifying the Refer to DE Project Data String One or Asset location
location location instance. Schema more code
code (DE) Typically NA to BRs
and most SRs

1 The “occurs” value is zero for Subsystem Requirements, as they cannot be further allocated.
© State of NSW through Transport for NSW 2021 Page 12 of 36
 T MU AM 06004 ST
Requirements Schema
Version 3.0
Effective date: 13 August 2021

Field name Description Values Type Occurs DE field

name
Discipline Engineering or other Refer to DE Project Data String One or Discipline
code (DE) related discipline Schema more code
responsible for
requirement
satisfaction, e.g. Civil.
Typically NA to BRs
and most SRs
Sub- Required where an Refer to DE Project Data String One or Sub-discipline
discipline appropriate sub- Schema more code
code (DE) discipline is available
e.g. Drainage. The sub-
discipline responsible
for requirement
satisfaction. Typically
NA to BRs and most
SRs
Uniclass Required for technical Refer to DE Project Data String One or Uniclass 2015
2015 asset requirements. Schema more asset code
code (DE) Required to level of
information specified in
DE Standard
(DMS-ST-207).
Code identifying the
asset type. Typically
NA to BRs and most
SRs
Uniclass Required for technical Refer to DE Project Data String One or Uniclass 2015
2015 asset requirements. Schema more asset title
title (DE) Required to level of
information specified in
DE Standard
(DMS-ST-207).
Title identifying the
asset type. Typically
NA to BRs and most
SRs
Compliance Whether the designed • Compliant String One Compliance
status solution meets the status
requirements. The • Compliant with concession
status may change as • Non-compliant
the solution is
• Partially compliant (or
developed.
Compliant at Interface)
A partially compliant
status indicates that • Not applicable
only some of the • Pending (or ‘to be
necessary compliance determined’ or ‘no
activities have been information’)
completed. The
Remarks field is used
to indicate the reason
for the partially
compliant status.

© State of NSW through Transport for NSW 2021 Page 13 of 36

 T MU AM 06004 ST
Requirements Schema
Version 3.0
Effective date: 13 August 2021

Field name Description Values Type Occurs DE field

name
Criticality Requirement criticality • Essential String One Criticality
for the solution, or vital
to safety/mission. • Desirable
Essential means it is • Optional
mandatory (shall),
desirable means it is
highly recommended
(should), and optional
means the deliverer
can choose to
implement the
requirement or not. A
child requirement
cannot be at a higher
criticality than the
parent requirement
Limit of The limit of the scope • Text String One or Limit of scope
scope covered by the more
requirement. This can
be geographical extent
of locations or the
scope of works. Certain
requirements such as
for control &
communications
systems, may have
multiple limits of scope
due to the distributed
nature of their
functions.
Owner Requirement owner, or • Text String One Project
the sponsor of the contract code
requirement. There
may be projects with
some co-owned
requirements, but a
single accountable
owner should be
identified and agreed
where practicable
Work Required for system • Text String One or DE Project
package requirements (SR) and more Work package
(DE) subsystem code
requirements (SSR).
Refers to the Work
Package that includes
the activity where a
requirement will be
satisfied. NA to BRs.
There may be multiple
Work packages
associated with a
requirement

© State of NSW through Transport for NSW 2021 Page 14 of 36

 T MU AM 06004 ST
Requirements Schema
Version 3.0
Effective date: 13 August 2021

Field name Description Values Type Occurs DE field

name
Proposed Verification method • Review String One or Proposed
verification used to verify that the more verification
method solution will meet the • Analysis method
requirements. • Modelling
The proposed • Simulation
verification method is
not applicable (NA) for • Certification
business requirements. • Inspection
Verification takes place
during the requirements
• Demonstration
delivery phase as the • Test
system solution is • NA (BRs only)
designed and delivered
Proposed Validation method used • Review String One Proposed
validation to validate that the built validation
method solution will meet the • Analysis method
requirements. • Modelling
The proposed • Simulation
validation method is NA
for system • Certification
requirements and • Demonstration
subsystem
requirements.
• Test
• Inspection
• NA (SR and SSR only)
Validation If the validation method • SIT String One or Validation test
test type is a test, it indicates more type
which kind of test is • UAT
expected. • NA
Rationale Provide the reason for • Text String Zero or Rationale
the requirement. This one
field needs to be
completed only if the
source field does not
provide the source of
the requirement.
Remarks Any remark, comment, • Text String Zero or Remarks
notes or explanations more
for the requirement.
Remarks could indicate
the requirement type,
such as a safety
requirement or
interface requirement.
Remarks should not
change the requirement
meaning. If so, new
requirements should be
considered.

© State of NSW through Transport for NSW 2021 Page 15 of 36

 T MU AM 06004 ST
Requirements Schema
Version 3.0
Effective date: 13 August 2021

Field name Description Values Type Occurs DE field

name
Requirement The project phase or • Concept String One or Project
delivery milestone for more milestone
phase requirement delivery. • Specify description
• Procure
• Design
• Manufacture
• Build
• Integrate
• Accept
• Operate
• Maintain
• Evolve
• Dispose/renew/recycle
Requirement Status to assess the • Draft: Author has created, String One Requirement
approval requirement maturity or elicited from Owner or approval
status and to support the stakeholder input, a new status
requirement draft requirement for
development life cycle. potential inclusion in the
specification
• Candidate: Owner has
been identified for the
requirement, which is now
a candidate for inclusion in
the specification
• Agreed: Owner has
agreed to sponsor the
requirement to
Governance for inclusion
in the specification
• Approved: Governance
has approved the
requirement for inclusion
in the specification. All
requirements need to be
approved prior to award
• Cancelled: The
requirement has been
cancelled by:
• Author if Draft
• Owner if Candidate
• Governance if Agreed
• CAP if Approved

© State of NSW through Transport for NSW 2021 Page 16 of 36

 T MU AM 06004 ST
Requirements Schema
Version 3.0
Effective date: 13 August 2021

Field name Description Values Type Occurs DE field

name
Satisfies Also referred to as • Text String One or Satisfies links
links “Parent Identifier”. A more
requirement can satisfy
higher level Parent
requirements.
Identifier(s) of the
parent requirement for
traceability; Business
Requirement(s) or
System
Requirement(s).
Field not applicable if
requirement is from the
highest level BRS
(initial top level BRS
such as a program
level BRS). Project
level BRS requirements
developed from a
program level BRS will
require a parent
identifier for traceability.

7. Structuring verification information

The verification element of the schema is used to manage verification activities associated with
the requirements, including tracing to requirements and recording evidence.

7.1. Verification element-level information

Table 3 contains the mandatory information fields (with the exception of the optional additional
DE information in grey shade) needed for each verification element containing a collection of
verification activities.

Table 3 - Verification element-level information

Field name Description Type Occurs DE field name

Project (DE) Title of the project. String One Project name
Type Type of verification element. Element String One Type
type used to differentiate verification
element from other elements.
Name Name of the verification element. String One Document title
Document Project allocated document number String One Document
number (DE) of the verification element. number
Owner Owner of the verification element. String One Contracted
organisation
name
Owner Owner service provider code of the String One Contracted
code (DE) verification element. organisation
code
Release date The date that the version was Date One Date released
released.

© State of NSW through Transport for NSW 2021 Page 17 of 36

 T MU AM 06004 ST
Requirements Schema
Version 3.0
Effective date: 13 August 2021

Field name Description Type Occurs DE field name

Version The version number of the Numb One Document
verification element. er version number
Element The status of the verification element String One State code
status – draft or approved.

7.2. Verification activity information

Table 4 contains the mandatory information fields (with the exception of the optional additional
DE information in grey shade) needed for each verification activity. However, for fields where
“Occurs” has a possible value of zero, it is permissible for the field to be empty.

Table 4 - Verification activity information

Field name Description Values Type Occurs DE field name

Identifier Verification activity • Text String One Identifier
identifier unique for the
project
Description Verification activity item • Text String One Description
text
Method Verification method. It is • Review String One or Method
used to ensure more
requirements are covered • Analysis
by the proper type of • Modelling
verification items.
• Simulation
• Certification
• Type approval
• Demonstration
• Inspection
• Test
Remarks (or Explanation of the • Text String Zero or Remarks
Rationale) verification method or more
rationale as to how and
why this verification
activity is needed.
Status Status to assess • Draft String One Status
verification activity item
maturity and support its • Candidate
life cycle • Agreed
• Approved
• Cancelled
Success Verification activity item • Text String One Success
criteria success criteria. criteria
Verification Verification item outcome • Text String One or Verification
outcome details. more 2 outcome

2 Value of “occurs” is zero until verification method is executed

© State of NSW through Transport for NSW 2021 Page 18 of 36
 T MU AM 06004 ST
Requirements Schema
Version 3.0
Effective date: 13 August 2021

Field name Description Values Type Occurs DE field name

Test type If the verification method • FAT String One or Test type
is a test, then this more
specifies the test type. If • IFAT
verification method is not • SAT
a test, then Test Type is
NA • SIT
• NA
Result Verification activity item • Passed String One 3 Result
actual result.
• Failed
• Blocked
• Pending
Evidence Document number of the • Text One 4 Document
file containing the Number
evidence. This could be a
document, model,
survey, test results,
meeting/review notes,
and so on.
Executed by Person names and roles • Text String One or Contracted
executing the verification more 5 Organisation
item Code
Executed on The verification item • Text Date One 6 Executed on
execution date
Execution The verification item • Text String Zero or Execution
comments execution comments more comments
Verifies links The verification link • Text String One or Verifies links
identifier to the more
requirement that is under
verification

8. Structuring validation information

The validation element of the schema is used to manage validation activities associated with the
requirements, including tracing to requirements and recording evidence.

8.1. Validation element–level information

Table 5 contains the mandatory information fields (with the exception of the optional additional
DE information in grey shade) needed for each validation element containing a collection of
validation activities.

Table 5 - Validation element-level information

Field name Description Type Occurs DE field name

Project (DE) Title of the project String One Project Name

3 Value of “occurs” is zero until verification method is executed

4 Value of “occurs” is zero until verification method is executed and evidence is available
5 Value of “occurs” is zero until verification method is executed
6 Value of “occurs” is zero until verification method is executed

© State of NSW through Transport for NSW 2021 Page 19 of 36

 T MU AM 06004 ST
Requirements Schema
Version 3.0
Effective date: 13 August 2021

Field name Description Type Occurs DE field name

Type Type of validation element, and is String One Type
used to differentiate the validation
element from other elements.
Name Name of the validation element. String One Document Title
Document Project allocated document String One Document
Number (DE) number of the validation element. Number
Owner Owner of the validation element. String One Contracted
Organisation
Name
Owner Owner service provider code of String One Contracted
code (DE) the validation element. Organisation
Code
Release date The date that the version was Date One Date Released
released.
Version The version number of the Number One Document
validation element. Version
Number
Element The status of the validation String One State Code
status element – draft or approved.

8.2. Validation activity information

Table 6 contains the minimum mandatory element information fields (with the exception of the
optional additional DE information in grey shade) needed for each validation activity. However
for fields where “Occurs” has a possible value of zero, it is permissible for the field to be empty.

Table 6 - Validation activity information

Field name Description Values Type Occurs DE field name

Identifier Validation activity identifier • Text String One Identifier
unique for the project.
Description Validation activity item text. • Text String One Description
Method Validation method, used to • Review String One or Method
ensure requirements are more
covered by the proper type • Analysis
of validation items • Modelling
• Simulation
• Certification
• Demonstration
• Inspection
• Test
Remarks Additional explanation of • Text String Zero or Remarks
the validation method more
Status Status to assess validation • Draft String One Status
item maturity and support
its life cycle • Candidate
• Agreed
• Approved
• Cancelled

© State of NSW through Transport for NSW 2021 Page 20 of 36

 T MU AM 06004 ST
Requirements Schema
Version 3.0
Effective date: 13 August 2021

Field name Description Values Type Occurs DE field name

Success Validation activity item • Text String One or Success
criteria success criteria more criteria
Validation Validation activity item • Text String One or Validation
outcome outcome more 7 outcome
Test type If validation method is a • SIT String One Test type
test, then specifies the test
type. If validation method • UAT
is not a test, then Test • NA
Type is NA.
Result Validation activity item • Passed String One Result
actual result
• Failed
• Blocked
• Pending
Evidence Document number of the • Text String One 8 Document
file / record containing the Number
evidence. This could be a
document, model, survey,
test results, meeting/
review notes etc.
Executed by Person names and roles • Text String One 9 or Contracted
executing the validation more Organisation
activity item Code
Executed on The validation activity item • Text Date One Executed on
execution date.
Execution The validation activity item • Text String Zero or Execution
comments execution comments. more comments
Validates The validation activity link • Text String One or Validates links
links identifier to a requirement more

9. Linking and traceability

The links element of the schema is used to manage traceability between other elements of the
schema. The linkages are 'satisfies', 'verifies' or 'validates'.

The one way links list the relationships between specific requirements (business, system, and
subsystem) and their respective verification and validation activities.

Figure 1 illustrates these linking and traceability requirements.

7 Value of “occurs” is zero until validation method is executed

8 Value of “occurs” is zero if until validation method is executed
9 Value of “occurs” is zero if until validation method is executed

© State of NSW through Transport for NSW 2021 Page 21 of 36

 T MU AM 06004 ST
Requirements Schema
Version 3.0
Effective date: 13 August 2021

Project Information

Business Satisfies System Satisfies Subsystem

Requirement (m:m) requirements (m:m) requirements

Validates Verifies
(m:m) (m:m) Verifies
(m:m)

Validation Verification
activities activities

Figure 1 – Requirement Schema link information

Each business requirement shall have one or more satisfies links from system requirements.

For example, business requirement ABC_BR_001, the passenger waiting time shall be
maximum 10 minutes at stations in peak periods is satisfied by the system requirement
ABC_SR_001; the system shall operate with service intervals of 8 ± 2 minutes.

Each system requirement shall have one or more satisfies links from subsystem requirements, if
there are subsystems.

For example ABC_SR_001, the system shall operate with service intervals of 8 ± 2 minutes in
peak periods is satisfied by multiple subsystem requirements related to train acceleration and
top speed, electrical traction supply capacity, track rating, and the signalling system capacity.

The “many-to-many (m:m)” relationship means that one or more parent requirements are
satisfied by one or more child requirements. Generally one parent requirement is satisfied by
one or more child requirements (that is, a trunk, branch and leaf structure), but in some cases a
child requirement can satisfy more than one parent.

Each system requirement shall have one or more verifies links from verification activities.

Each subsystem requirement, if there are subsystems, shall have one or more verifies links
from verification activities.

Each business requirement shall have one or more validates links from validation activities.

For example, business requirement ABC_BR_001, the passenger waiting time shall be
maximum 10 minutes at stations in peak periods can be validated early in the system life cycle

© State of NSW through Transport for NSW 2021 Page 22 of 36

 T MU AM 06004 ST
Requirements Schema
Version 3.0
Effective date: 13 August 2021

by means of traffic modelling and analysis before design commences, and again validated at
the system acceptance and handover by means of live demonstration and “stopwatch” tests.

Table 7 shows the permitted terms and descriptions for links.

Table 7 - Link information

Link Description Source element Target element

name
Satisfies Requirement decomposition. Source Specific identified Specific
element needs to be the lower level and requirement identified
target element the upper level (for (lower-level) requirement
example: from system requirements to (higher-level)
business requirements)
Verifies Requirement verification Verification Requirement
Validates Requirement validation Validation Requirement

Linking verification and validation items to requirements ensures that the solution can be fully
demonstrated to fulfil the requirements.

Using the requirements schema for all stages of a project allows for progressive verification
through the stages and validation at system acceptance. Figure 2 illustrates how the verification
and validation of requirements link across the engineering life cycle through decomposition and
solution definition to solution integration, composition, and final system acceptance.

© State of NSW through Transport for NSW 2021 Page 23 of 36

 T MU AM 06004 ST
Requirements Schema
Version 3.0
Effective date: 13 August 2021

Requirements
Repository

Business System
Concept Validation
Requirements validates Acceptance
Feasibility
Validation

satisfies
System System
System Design Verification Integration and
D Requirements verifies
ec
om Verification tion

s
si

ie
po satis

rif
fies
po

ve
si
tio
n
Subsystem om
C
an Requirements d
d an
so Subsystem n
lu Subsystem tio
tio Integration and ra
n
de
Design
Verification teg
fin
Procurement, In
n
iti Fabrication, io
on l ut
Construction, So
Installation

Time

Figure 2 - Relationship between requirements and verification and validation

© State of NSW through Transport for NSW 2021 Page 24 of 36

 T MU AM 06004 ST
Requirements Schema
Version 3.0
Effective date: 13 August 2021

Appendix A Example schema implementation (non-DE enabled projects)

Section A.1 to Section A.5 provide an example implementation of the requirements schema for a fictitious project 'ABC'.

The example contains requirement elements of:

• business requirements

• system requirements

• subsystem requirements

The verification and validation elements provide criteria for progressively assuring that the requirements are achieved.

The links for connecting these schema elements are marked as 'satisfies', 'verifies' or 'validates'.

'Satisfies links' show the system requirements that satisfy the “parent” business requirements, and the subsystem requirements that satisfy the “parent” system requirements.

'Verifies links' show verification activities that verify system requirements and subsystem requirements.

'Validates links' include validation activities that validate the business requirements.

© State of NSW through Transport for NSW 2021 Page 25 of 36

 T MU AM 06004 ST
Requirements Schema
Version 3.0
Effective date: 13 August 2021

A.1. Example business requirements (non-DE)

Type Business requirements (BR)
Name ABC project business requirements
Owner Rail network planning
Sources Customer survey ABC
Business case ABC
Release date 01/04/2014
Version 1.0
Element status approved

Identifier Object Reqt Reqt Description Source Allocation Compliance Criticality Proposed Limit of Owner Proposed Validation Rationale Remarks Requirement Requirement
type type Level status verification scope validation test type delivery approval
method method phase status
ABC_BR_001 Reqt Technical BR The passenger waiting TfNSW/Transport System Compliant Essential Simulation A station Planning Test UAT Based on This is for the Accept Agreed
time shall be maximum Planning B station Manager customer initial operation
10 minutes at stations survey of the system.
in peak periods. C station ABC.
D station
ABC_BR_002 Reqt Technical BR The passenger waiting TfNSW/Transport System Compliant Essential Simulation A station Planning Test UAT Based on This is for the Accept Agreed
time shall be maximum Planning B station Manager customer initial operation
15 minutes at stations survey of the system.
in off peak periods. C station ABC.
D station
ABC_BR_003 Reqt Technical BR The passenger journey TfNSW/Transport System Compliant Essential Simulation A station Planning Test UAT Based on This is for the Accept Agreed
time shall be maximum Planning B station Manager business initial operation
2 minutes between case ABC. of the system.
adjacent stations. C station
D station

© State of NSW through Transport for NSW 2021 Page 26 of 36

 T MU AM 06004 ST
Requirements Schema
Version 3.0
Effective date: 13 August 2021

A.2. Example system requirements (non-DE)

Type System requirements (SR)
Name ABC project system requirements
Owner Systems engineering
Sources Business requirements
Release date 01/05/2014
Version 1.0
Element status approved

Identifier Object Reqt Reqt Description Source Allocation Compliance Criticality Proposed Limit of Owner Proposed Validation Rationale Remarks Requirement Requirement Satisfies
type type level status verification scope validation test type delivery approval Links
method method phase status
ABC_SR_001 Reqt Technical SR The system shall Service Train Compliant Essential Test A station Systems NA NA This is for Accept Agreed ABC_BR_001
operate with service planning subsystem B station Manager the initial
intervals of meeting operation
8 ± 2 minutes in peak minutes C station of the
periods. D station system.
ABC_SR_002 Reqt Technical SR The system shall Service Train Compliant Essential Test A station Systems NA NA This is for Accept Agreed ABC_BR_002
operate with service planning subsystem B station Manager the initial
intervals of meeting operation
13 ± 2 minutes in off minutes C station of the
peak periods. D station system.
ABC_SR_003 Reqt Technical SR The system shall Service Train Compliant Essential Test A station Systems NA NA Accept Agreed ABC_BR_003
operate with travel planning subsystem B station Manager
times of meeting
90 ± 30 seconds minutes C station
between adjacent D station
stations.

© State of NSW through Transport for NSW 2021 Page 27 of 36

 T MU AM 06004 ST
Requirements Schema
Version 3.0
Effective date: 13 August 2021

A.3. Example subsystem requirements (non-DE)

Type Subsystem requirements (SSR)
Name ABC project train subsystem requirements
Owner Rolling stock
Release date 10/05/2014
Sources System requirements
Version 1.0
Element status approved

Identifier Object Reqt Reqt Description Source Allocation Compliance Criticality Proposed Limit Owner Proposed Validation Rationale Remarks Requirement Requirement Satisfies
type type level status verification of validation test type delivery approval Links
method scope method phase status
ABC_SSR Reqt Technical SSR The train shall Train Propulsion Compliant Essential Review Train Rolling NA NA Needed to Analysis Accept Agreed ABC_SR_001
_001 travel at speeds perform subsystem Stock meet the XYZ shows ABC_SR_002
from 0 km/h to model & Manager service that this
100 km/h. analysis journey speed is ABC_SR_003
time & T/T required
ABC_SSR Reqt Technical SSR The train shall Train Propulsion Compliant Essential Review Train Rolling NA NA Needed to Analysis Accept Agreed ABC_SR_001
_002 accelerate from perform subsystem Stock meet the XYZ shows ABC_SR_002
0 km/h to model & Manager service that this
100 km/h within analysis journey acceleration ABC_SR_003
30 seconds. time & T/T is required.
ABC_SSR Reqt Technical SSR The train shall Train Braking Compliant Essential Review Train Rolling NA NA Needed to Analysis Accept Agreed ABC_SR_001
_003 decelerate from perform subsystem Stock meet the XYZ shows ABC_SR_002
100 km/h to model & Manager service that this
0 km/h within analysis journey deceleration ABC_SR_003
30 seconds. time & T/T is required.

© State of NSW through Transport for NSW 2021 Page 28 of 36

 T MU AM 06004 ST
Requirements Schema
Version 3.0
Effective date: 13 August 2021

A.4. Example verification activities (non-DE)

Type Verification
Name ABC project verification
Owner Systems assurance
Release date 20/05/2014
Version 1.0
Element status approved

Identifier Description Method Remarks Status Success criteria Verification outcome Test Result Evidence Executed Executed on Execution Verifies links
Type by comments
ABC_VER_001 For 3 hours run trains at intervals of Test Test carried Agreed Trains at intervals of Train intervals: SIT Passed Data D Person 01/06/2014 The train interval was ABC_SR_001
8 minutes from A station to D out without 8 ± 2 minutes at A A station: 8 minutes Logger not always 8 minutes
station, stopping at B station and C passengers. station, B station, C files for trains.
station for 2 minutes. At each station, and D station B station: 8 minutes
station measure the arrival time of C station: 9 minutes
each train. D station: 9 minutes
ABC_VER_002 For 3 hours run trains at intervals of Test Test carried Agreed Trains at intervals of Train intervals: SIT Passed Data D Person 01/06/2014 The train interval was ABC_SR_002
13 minutes from A station to D out without 13 ± 2 minutes at A A station: 14 minutes Logger not always 13
station, stopping at B station and C passengers. station, B station, C files minutes for trains.
station for 2 minutes. At each station, and D station B station: 13 minutes
station measure the arrival time of C station: 13 minutes
each train. D station: 14 minutes
ABC_VER_003 For 3 hours run trains at intervals of Test Test carried Agreed Travel times of 90 ± 30 Travel intervals: SIT Pending ABC_SR_003
8 minutes from A station to D out without seconds between A to B station : 80
station, stopping at B station and C passengers. adjacent stations. seconds
station for 1 minute. At each station
measure the arrival time and B to C station: 100
departure time of each train. seconds
C to D station: 120
seconds
ABC_VER_004 Verify the materials used for the Test Test carried Agreed Trains can travel at Speeds up to 120 km/h SIT Passed Data D Person 01/06/2014 Design document ABC_SSR_001
rails support a train travelling at out on test speeds from 0 km/h to Logger XXX chapter Y.Z:
100 km/h. track. 100 km/h. files Usage of ballast less
track supporting
speeds up to
SSS km/h.
ABC_VER_005 Accelerate the train from 0 km/h to Test Test carried Agreed The train travels at Speeds up to 100 km/h SIT Passed Data D Person 01/06/2014 ABC_SSR_001
100 km/h. Allow the train to travel at out on test speeds from 0 km/h to Logger
100 km/h for 5 minutes. track. 100 km/h files
ABC_VER_006 Accelerate the train from 0 km/h to Test Test carried Agreed The train accelerates Accelerates from SIT Passed Data D Person 01/06/2014 ABC_SSR_002
100 km/h as rapidly as possible. out on test from 0 km/h to 0 km/h to 100 km/h in Logger
track. 100 km/h within 20 seconds files
30 seconds.

ABC_VER_007 Decelerate the train from 100 km/h Test Test carried Agreed The train decelerates Decelerate from SIT Passed Data D Person 01/06/2014 ABC_SSR_003
to 0 km/h as rapidly as possible. out on test from 100 km/h to 100 km/h to 0 km/h in Logger
track. 0 km/h within 25 seconds. files
30 seconds.

© State of NSW through Transport for NSW 2021 Page 29 of 36

 T MU AM 06004 ST
Requirements Schema
Version 3.0
Effective date: 13 August 2021

A.5. Example validation activities (non-DE)

Type Validation
Name ABC project validation
Owner Systems assurance
Release date 01/06/2014
Version 1.0
Element status approved

Identifier Description Method Remarks Status Success Validation outcome Test Result Evidence Executed Executed Execution Validates
criteria type by on comments links
ABC_VAL_001 For 3 hours run trains at Test Test carried agreed Maximum Maximum waiting times: UAT Passed Data logs, E. Person 10/06/2014 D station had ABC_BR_001
intervals of 8 minutes from A out with passenger A station: 8 minutes Stopwatch the longest ABC_BR_002
station D station, stopping at passengers waiting time records, waiting time.
B station: 8 minutes
B station, C station and D . is 10 customer
station. Unload and load 200 minutes. C station: 9 minutes satisfaction
passengers at each station. D station: 10 minutes surveys
At each station measure the
waiting time for passengers.
ABC_VAL_002 For 3 hours run trains at Test Test carried agreed The Maximum journey times: UAT Passed Data logs, E. Person 10/06/2014 ABC_BR_003
intervals of 8 minutes from A out with passenger A station to B station: 2 minutes Stopwatch
station D station, stopping at passengers journey time records,
B station to C station: 2 minutes
B station, C station and D . is maximum customer
station. Unload and load 200 2 minutes C station to D station: 2 minutes satisfaction
passengers at each station. between surveys
At each station measure the adjacent
arrival time and departure stations.
time of each train.

© State of NSW through Transport for NSW 2021 Page 30 of 36

 T MU AM 06004 ST
Requirements Schema
Version 3.0
Effective date: 13 August 2021

Appendix B Example schema implementation (DE-enabled project)

Section B.1 to Section B.5 provide an example implementation of the requirements schema for a fictitious rail project 'DEF'.

The example contains requirement elements (including additional optional fields for DE projects, shaded grey) of:

• business requirements

• system requirements

• subsystem requirements

The verification and validation elements provide criteria for assuring that the requirements are achieved (including additional optional fields for DE projects, shaded grey).

The links for connecting these elements are marked as 'satisfies', 'verifies' or 'validates'.

'Satisfies links' show the system requirements that satisfy the “parent” business requirements, and subsystem requirements that satisfy the “parent” system requirements.

'Verifies links' show verification activities that verify system requirements and subsystem requirements.

'Validates links' include validation activities that validate the business requirements.

© State of NSW through Transport for NSW 2021 Page 31 of 36

 T MU AM 06004 ST
Requirements Schema
Version 3.0
Effective date: 13 August 2021

B.1. Example business requirements (DE-enabled project)

Project DEF Project (DE)
Type Business requirements
Name DEF project business requirements
Document number DEF-SPC-BRS-00001 (DE)
Owner Transport Access Program
Owner code AEO123 (DE)
Sources Customer survey DEF
Business case DEF
Release date 01/04/2014
Version 1.0
Element status approved

Identifier Object Reqt Reqt Description Source Allocation Uniclass Uniclass Asset Discipline Sub- Uniclass Uniclass 2015 Compliance Criticality Proposed Limit
type type level 2015 asset 2015 asset location code (DE) discipline 2015 asset title (DE) status verification of
location location code code (DE) asset method scope
code (DE) title (DE) (DE) code (DE)
DEF_BR_001 Reqt Technical BR Passenger access to GWHEK2M- System Co_80 Transport NWW AR AT EF_35 Stairs and ramps Compliant Essential NA
public transport shall JAJV-NWW- complexes
comply with current AR-ANA-
access legislation. 00001
DEF_BR_002 Reqt Technical BR Transport interchanges GWHEK2M- System Co_80 Transport NWW AR AT EF_40 Signage, fittings, Compliant Essential NA
shall provide accessible JAJV-NWW- complexes furnishings and
amenities. AR-ANA- equipment
00001

Table columns continued below.

Owner Work Proposed Validation Rationale Remarks Requirement Requirement

package validation test type delivery approval
(DE) method phase status
Transport Service WG01 Test UAT Based on customer Accept Agreed
Planning Manager WG02 survey DEF.

Transport Service WG01 Test UAT Based on customer Accept Agreed

Planning Manager WG02 survey DEF.

© State of NSW through Transport for NSW 2021 Page 32 of 36

 T MU AM 06004 ST
Requirements Schema
Version 3.0
Effective date: 13 August 2021

B.2. Example system requirements (DE-enabled project)

Project DEF Project (DE)
Type System requirements
Name DEF project system requirements
Document number DEF-SPC-SRS-0001 (DE)
Owner Systems engineering
Owner code AEO123 (DE)
Sources Business requirements
Release date 01/05/2014
Version 1.0
Element status approved

Identifier Object Reqt Reqt Description Source Allocation Uniclass 2015 Uniclass 2015 Asset Discipline Sub- Uniclass 2015 Uniclass Compliance Criticality
type type level asset location asset location location code (DE) discipline asset code 2015 asset status
code (DE) title (DE) code (DE) code (DE) (DE) title (DE)
DEF_SR_001 Reqt Technical SR Step-free access shall be GWHEK2M-JAJV- Access En_80_50_74 Railway stations HRS AR AT Ss_35 Stair and Compliant Essential
provided at all heavy rail stations. NWW-AR-ANA-00002 subsystem ramp
systems
DEF_SR_002 Reqt Technical SR Passenger lifts shall be provided GWHEK2M-JAJV- Access En_80_50_74 Railway stations HRS ME VT Ss_80_50_60 Passenger Compliant Essential
at HRS where gradients exceed NWW-AR-ANA-00002 subsystem and goods
maximum. lift systems
DEF_SR_003 Reqt Technical SR Step-free access shall be GWHEK2M-JAJV- Access En_32_50_98 Wharfs MAS AR AT Ss_35 Stair and Compliant Essential
provided at all ferry wharves. NWW-AR-ANA-00002 subsystem ramp
systems
DEF_SR_004 Reqt Technical SR Passenger lifts shall be provided GWHEK2M-JAJV- Access En_32_50_98 Wharfs MAS ME VT Ss_80_50_60 Passenger Compliant Essential
at MAS where gradients exceed NWW-AR-ANA-00002 subsystem and goods
maximum. lift systems
DEF_SR_005 Reqt Technical SR Existing toilet facilities at stations GWHEK2M-JAJV- Toilet SL_35_80_68 Public toilets HRS AR AT Ss_40_15_75 Sanitary Compliant Essential
shall be accessible and family NWW-AR-ANA-00002 subsystem appliance
friendly. systems
DEF_SR_005 Reqt Technical SR Existing toilet facilities at wharves GWHEK2M-JAJV- Toilet SL_35_80_68 Public toilets MAS AR AT Ss_40_15_75 Sanitary Compliant Essential
shall be accessible and family NWW-AR-ANA-00002 subsystem appliance
friendly. systems

Table columns continued below.

Proposed Limit Owner Work Proposed Validation Rationale Remarks Requirement Requirement Satisfies links
verification of package validation test type delivery approval
method scope (DE) method phase status
Test HRS AEO123 WG01 NA NA Compliance with DSAPT Accept Agreed DEF_BR_001
Test HRS AEO123 WG01 NA NA Compliance with DSAPT Accept Agreed DEF_BR_001
Test HRS AEO123 WG02 NA NA Compliance with DSAPT Accept Agreed DEF_BR_001
Test NWW AEO123 WG02 NA NA Compliance with DSAPT Accept Agreed DEF_BR_001
Test NWW AEO123 WG01 NA NA Compliance with DSAPT Accept Agreed DEF_BR_002
Test NWW AEO123 WG02 NA NA Compliance with DSAPT Accept Agreed DEF_BR_002

© State of NSW through Transport for NSW 2021 Page 33 of 36

 T MU AM 06004 ST
Requirements Schema
Version 3.0
Effective date: 13 August 2021

B.3. Example subsystem requirements (DE-enabled project)

Project DEF Wollstonecraft TAP Project (DE)
Type Subsystem requirements
Name DEF project Wollstonecraft subsystem requirements
Document number DEF-SPC-SSRS-00001 (DE)
Owner Access
Owner code AEO123 (DE)
Release date 10/05/2014
Sources System requirements
Version 1.0
Element status approved

Identifier Object Reqt Reqt Description Source Allocation Uniclass Uniclass 2015 Asset Discipline Sub- Uniclass 2015 Uniclass 2015 Compliance Criticality
type type level 2015 asset asset location location code (DE) discipline asset code (DE) asset title (DE) status
location title (DE) code code (DE)
code (DE) (DE)
DEF_SSR_001 Reqt Technical SSR Accessible routes shall be GWHEK2M-JAJV- Stations & SL_90_10_96 Wheelchair WLS AR AT Ss_40_10 Signage systems Compliant Essential
created and identified. NWW-AR-ANA-00003 Buildings circulation
spaces
DEF_SSR_002 Reqt Technical SSR Step-free access shall be GWHEK2M-JAJV- Stations & En_90_10_02 Access WLS AR AT Ss_35 Stair and ramp Compliant Essential
compliant with current NWW-AR-ANA-00003 Buildings stairways and systems
legislation. walkways
DEF_SSR_003 Reqt Technical SSR Lifts shall be provided GWHEK2M-JAJV- Stations & SL_90_10_47 Lifts WLS ME VT Ss_80_50_60 Passenger and Compliant Essential
where gradient and station NWW-AR-ANA-00003 Buildings goods lift systems
layout restricts accessibility.
DEF_SSR_004 Reqt Technical SSR Toilet facilities shall be GWHEK2M-JAJV- Stations & SL_35_80_68 Public toilets WLS AR AT Ss_40_15_75_02 Accessible WC Compliant Essential
upgraded to comply with NWW-AR-ANA-00004 Buildings package systems
current access legislation.
DEF_SSR_005 Reqt Technical SSR Toilet facilities shall be GWHEK2M-JAJV- Stations & SL_35_80_68 Public toilets WLS AR AT Pr_40_20_76_06 Baby changing Compliant Essential
upgraded to provide baby- NWW-AR-ANA-00004 Buildings units
change facilities.

Table columns continued below.

Proposed Limit of Owner Work Proposed Validation Rationale Remarks Requirement Requirement Satisfies
verification scope package validation test type delivery approval Links
method (DE) method phase status
review WLS AEO123 WG01.01 Inspection SAT Comply with DSAPT Accept Agreed DEF_SR_001
review WLS AEO123 WG01.01 Inspection SAT Comply with DSAPT Accept Agreed DEF_SR_001
review WLS AEO123 WG01.02 Inspection SAT Comply with DSAPT Accept Agreed DEF_SR_002
review WLS AEO123 WG01.03 Inspection SAT Comply with DSAPT Accept Agreed DEF_SR_005
review WLS AEO123 WG01.03 Inspection SAT Comply with DSAPT Accept Agreed DEF_SR_005

© State of NSW through Transport for NSW 2021 Page 34 of 36

 T MU AM 06004 ST
Requirements Schema
Version 3.0
Effective date: 13 August 2021

B.4. Example verification activities (DE-enabled project)

Project DEF Wollstonecraft Project (DE)
Type Verification
Name DEF Wollstonecraft TAP project verification
Document number DEF-RPT-VV-0001 (DE)
Owner Systems assurance
Owner code AEO123 (DE)
Release date 20/05/2014
Version 1.0
Element status approved

Identifier Description Method Remarks Status Success criteria Verification Test Result Evidence Executed Executed Execution comments Verifies links
outcome Type (DE) by on
DEF_VER_001 BIM/DE model Inspection Agreed Continuous step-free access All objects NA Passed GWHEK2M- D Person 01/04/2013 Model walkthrough DEF_SSR_001
validation for route, clearly signposted. identified in the JAJV-NWW- and gradient measures DEF_SSR_002
compliance. Gradients do not exceed ##. BIM model. AR-M3D- extracted from BIM
DEF_SSR_003
00005 model.
DEF_VER_002 BIM/DE model Inspection Agreed Objects identified in All objects NA Passed GWHEK2M- D Person 01/04/2013 Model walkthrough. DEF_SSR_004
validation for appropriate locations, as per identified in the JAJV-NWW- DEF_SSR_005
compliance. TfNSW requirements. BIM model. AR-M3D-
00005
DEF_VER_003 On-site Inspection Agreed Continuous step-free access Continuous NA Passed GWHEK2M- D Person 01/06/2014 DEF_SSR_001
inspection and route, clearly signposted. access JAJV-NWW- DEF_SSR_002
walk-through. Gradients do not exceed ##. confirmed. AR-ITC-
DEF_SSR_003
Gradients 00006
compliant.
DEF_VER_004 On-site Inspection Agreed Facilities and fixtures found Facilities and NA Passed GWHEK2M- D Person 01/06/2014 DEF_SSR_004
inspection of in-situ. fixtures available JAJV-NWW- DEF_SSR_005
facilities. on site. AR-ITC-
00006

© State of NSW through Transport for NSW 2021 Page 35 of 36

 T MU AM 06004 ST
Requirements Schema
Version 3.0
Effective date: 13 August 2021

B.5. Example validation activities (DE-enabled project)

Project DEF Project (DE)
Type Validation
Name DEF project validation
Document number DEF-RPT-VV-00001 (DE)
Owner Systems assurance
Owner code AEO123 (DE)
Release date 01/06/2014
Version 1.0
Element status approved

Identifier Description Method Remarks Status Success criteria Validation outcome Test Result Evidence Executed Executed on Execution Validates
type (DE) by comments links
DEF_VAL_001 Wollstonecraft: Inspection Agreed Continuous step-free access Continuous access NA passed GWHEK2M- D Person 01/06/2014 WLS only DEF_BR_001
On-site inspection route, clearly signposted. confirmed. JAJV-NWW-
and walk-through. Gradients do not exceed ##. Gradients compliant. AR-ITC-00006

DEF_VAL_002 Wollstonecraft: Inspection Agreed Facilities and fixtures found Facilities and fixtures NA passed GWHEK2M- D Person 01/06/2014 WLS only DEF_BR_002
On-site inspection in-situ. available on site. JAJV-NWW-
of facilities. AR-ITC-00006

© State of NSW through Transport for NSW 2021 Page 36 of 36