SMS-S1_1-PD TPSE Requirements Specification v1.0

TPSE Requirements Specification

Product Description


Document Control

Document Information

Information

Document ID

Document Owner

Issue Date

Last Saved Date 17 July 2011

File Name document.doc

Document History

Version Issue Date Changes

0.1 Initial Document. Copied from “PD Product Descriptions Document

Oct09 v02.doc” with RACIE responsibilities added.

Document Approvals

Role Name Signature Date

1 of 31


Contents

1 Document Purpose 3

2 Product Description Composition 4

3 Product Description Quality Criteria 5

2 of 31


1 Document Purpose

The Purpose of this document is to:

Understand the detailed nature, purpose and function of the product

Identify the sources of information or supply of the product

Describe the required appearance of the product

Identify the level of quality required of the product

Enable identification of activities to develop and quality control the product

Define the people or skills required to develop and check the product

3 of 31


2 Product Description Composition

Product Description CompositionIdentifier SMS-S1.1-PD

Title TPSE Requirements Specification

Purpose This product will define ICT Environment and Infrastructure Configuration Requirements for the TPSE. The TPSE must enable the requirements of the SMS Application States to be met.

Phase: Build & Config

Composition This product will be comprised of the following:

1. Interim TPSE infrastructure and environment requirements

2. Full TPSE infrastructure and environment requirements

The product must:

Be based on the Constraints Model from Appendix D of PD (Mobilisation stage) Environment Hosting Strategy

Cover all logical environments defined in the Environment Hosting Strategy PD (Mobilisation stage).

Specify the requirements to meet the needs of all SMS activities to be performed in the TPSE including:

o Capacity, performance and reliability requirements

o Interface requirements

o Integration requirements

o Security requirements

o Disaster Recovery and Continuity Management requirements.

Consider the approach to virtualisation.

Consider the variances between technical environments at different TAFEs.

4 of 31


Product Description CompositionDerivation The product will be developed by referring to:

PD (Mobilisation stage) Environment Hosting Strategy Technical Architecture Documentation for TSM

Environment Establishment Plan

This product has relationships with the following products in this phase:Dependencies:

Peers:

Dependents:

Format and Presentation

Word 97-2003 document based on the standard template specified by the SMS PMO.

Responsibilities Responsible

Accountable Infrastructure Management Team (PV and TAFE ICT)

Consulted

Informed

Endorsed

Signatory

Quality Criteria The product will:

Conform to approved document conventions, standards and formats as specified by the PMO

Be consistent with the sources used to derive the product and

Address all areas identified in the product description.

Quality Method

Quality Tolerance

Entry Criteria:As per the Project Plan (includes dependencies).

Exit Criteria:

# KPI Precision

1. TAFE-ICT acceptance of the product 100%

2. Meets TPSE requirements 100%

5 of 31


Product Description Composition# KPI Precision

3. Number of unmitigated risks resulting from TAFE-ICT peer reviews

Zero

4. Number of issues (defects) resulting from TAFE-ICT peer reviews

Zero

5. Number of unauthorised changes made to the product

Zero

6. Effort required for re-work after the TAFE-ICT peer review process

Less than 5% of original effort

7. Number of items identified requiring remediation as a result of the PMO formal document checklist

Less than 5

8. Traceability to functional and non-functional requirements

100%

9. Coverage of functional and non-functional requirements

100%

10. Accuracy to the business requirements 100%

11. Consistent with standards, methodology and frameworks specified in the design strategy

100%

12. Integration points (inputs and outputs) defined

100%

13. Platform or environment dependencies identified

100%

14. Coverage of IT assets 100%

15. Consistency with the Business Process Design (BPD)

100%

16. Consistency with the Data Conversion Business Requirements Review

100%

17. Consistency with the Non-Functional Requirements Specification

100%

18. Consistency with the Interface Definition 100%

Product Duration: 12 days

6 of 31


Product Description Composition

Exceedance Criteria: 25% or 4 days (whichever is shorter), rounded to the nearest full day.

Quality Check skills and/or people required

Review of the product will require knowledge of technical infrastructure including operating systems, server and client hardware, databases, virtualisation and networking including TSM product requirements.

3 Product Description Quality Criteria

The purpose is clear, unambiguous, and consistent with other products The product is described to a level of detail sufficient to plan and manage its

development The composition of the product describes the contents/elements of the

product, rather than being a requirements specification Responsibility for the development of the product is clearly identified Responsibility for the development of the product is consistent with the roles

and responsibilities described in the project management team organisation and the Project Quality Plan

The quality criteria are consistent with the project quality standards, standard checklists and Acceptance Criteria

The quality criteria can be used to determine when the product is fit for purpose

The types of quality check required are able to verify whether or not the product meets its stated quality criteria

4 Key Performance Indicators

4.1 Foundation

The TAFE ICT SMS project encompasses a broad range of software development and support services. The SMS Strategies propose approaches to planning, solution design, development and implementation activities, and identify a number of deliverables (or ‘products’). To support the management of software and service quality, and also to provide measurable quality and suitability criteria to the contract negotiation, a framework of acceptability criteria and key performance indicators was developed. This document utilises the framework for such criteria for a subset of SMS deliverables and delivery processes, as illustrated below.

7 of 31


Solution• Performance Measures

Strategies

Data

Solution

Infrastructure

Application

Project KPIs

Products• Quality &

Acceptance Criteria

TPSEInterim TPSE TAFE

Services• Service

Level Agreements

PD208 Test Strategy

PD204 Conf iguration Management Strategy

PD203 Release Management Strategy

PD202 Support and Service Strategy

PD209 Design Management Strategy

PD207 Deployment StrategyPD205 Environment

Hosting Strategy

PD206 Data Management Strategy

• Sof ter KPIs• Requires Objectivity

• Service Requests• Defects & Incidents• Operational Hours• Uptime

• Responsive• Reliable• Functional

PD210 Product Description

Development

PD212 Draf t Service Specif ications Development

Figure 1 - Source and Categories for KPIsProduct KPIs are defined to assess the acceptability of this deliverable. To structure KPI definition across the project scope, products are classified by type (the kind of deliverable -- Plan, Framework, Support process, Service Specification, Agreement, Requirement, Design, Script, and Report).

The KPIs in this document are applicable to SMS Phase 1.1 only (see figure, below). KPIs are directly applicable to, and can be used as a basis for, subsequent SMS program phases.

8 of 31


Phase 1.1 Phase 1.2

Phase 2.1

Phase 3.1

Support for Upgrade activities

Support for ALL Sites

Phase 3.2

8 SitesPILOT

(PIR)

TAFE

Other Sites ...

Phase 2.2

Single Configuration State

Scope is:

• 2x QLS Sites and one PIR

• 3 remaining non-QLS sites

• Support

TPSE Infrastructure

Data

Solution

Application

Other SitesSwinburne

Holmesglen

Box Hill Institute

Other Sites ...

• TPSE inf rastructure is constant

• Applicable to TAFEs and Dual Sectors

Figure 2 - SMS Project Phases

The KPIs herein are used as a mechanism to control service provider quality and behaviour in outsourcing arrangements, driving the desired business outcomes and are defined based upon anticipated priority areas.

4.2 Outcomes

Refer to the Quality Tolerance

4.3 Services

Design Management# Service

TA

FE

ICT

TA

FE

Tec

hn

olo

gyO

ne

Plu

s+

Imp

lem

enta

tio

n

Ser

vice

s

Description Notes

1.Design services required for SMS Application State(s) Data, Live Pilot TAFE Data and all other TAFEs Data.

2.Design Management

Interface design and build to cover for interfaces as agreed for the TPSE and then for

9 of 31


ALL TAFE institutes (for all phases)

3.Design Management Planning

C C A+R

Development of the design management plan for each phase of the TPSE and each specific TAFE implementation.

4.Ongoing Design Management

C C A+R

Ongoing project management of design and development activities

5.TechnologyOne Student Management Enhancements

6.Gap Business Research Study

R+E R+E

A+R

Undertake the gap business research study for each implementation of SMS. This study will ascertain approach to fulfilling additional/modified requirements.

Relationship with Stream 1 services TBC.Governance structure defined as per PD 800 to consider this split.

7.Specify non-functional requirements

R+E R+E

A+R

Document the non-functional requirements applicable for a particular SMS implementation.

8.Scope TechnologyOne Student Managememt Product Enhancements

C+E C A+R

Scope required changes to the TechnologyOne Student Management product.

Relationship with Stream 1 services TBC. Governance structure defined as per PD 800 to consider this split.

9.Develop TechnologyOne Student Managememt Product Enhancements

I I A+R

Develop and deliver enhancements to TechnologyOne Student Management.


10.Represent Sector enhancements required

A+R

C C Representing ongoing Sector view of TechnologyOne Student Managememt enhancements required

10 of 31


11.TechnologyOne Student Management Application Configuration

Responsibilities of TAFE ICT & TAFE depend on SMS being implemented (TPSE v TAFE)

Interface design and build to cover for interfaces as agreed for the TPSE and then for ALL TAFE institutes (for all phases)

12.Develop Business Process Descriptions

C R A+R

Develop Business Process Descriptions including defining the target business processes for the particular SMS implementation.


13.Prototype Application Configuration

C C A+R


14.Data Takeup and Configure TechnologyOne Student Managememt

C C A+R


15.Interface design

C C A+R

Design of interfaces including test stubs required..(internal and external)

16.Interface development

C C A+R

Development of interfaces including test stubs required. (internal and external)

17.Report design

C C A+R

18.Report development

C C A+R

19.Systems Integration

Responsibilities of TAFE

11 of 31


ICT & TAFE depend on SMS being implemented (TPSE v TAFE)

20.Solution Architecture Development

C C A+R

Provision of a solution architecture for all environments across all phases (includes all TAFEs and TPSE). Includes security architecture.

21.Architectural Oversight

C C A+R

Architectural QA of Solution Design and Development

22.Configure Custom Software Development Environments and Tools

Configure custom software development environments and tools.

23.Custom Software Design

C+E C A+R

Development of logical and physical design documents.

24.Custom Software Development

I I A+R

Development of custom software components including unit testing and peer review activities.

25.Operational Procedure Design

R R C Accountability with TAFE ICT for TPSE implementations or with TAFE for their own SMS

26.Governance of design

27.Joint Design Authority

A+R

R R Provision of inputs and reports to the Joint Design Authority

28.Design Specific Quality Assurance Services

29.Requirements Traceability

30.Requirements Traceability Matrix creation and maintenance

I C A+R

-

31.Audit of Requirements Traceability Matrix

A+R

- C -

32.Prototype demonstrations

A+R

R I - Demonstrations of prototypes to end users.


33.Source code quality assurance

34.Independent code reviews

I I A R+E

Third Party Endorsement (not the ISP)

35.Code walkthroughs

- - A+ -

12 of 31


R36.

Automated validation of code I I A+

RI Automated validation of

code against coding standards including adherence to mandatory development practices including configuration management and unit test coverage.

37.Application configuration quality assurance

38.Audit of application configuration

I I A+R

Review by Student Management Expert consultant of application configuration developed.

Environment Hosting Management# Service

TA

FE

ICT

TA

FE

Tec

hn

olo

gyO

ne

Plu

s+

Imp

lem

enta

tio

n

Ser

vice

s P

artn

er Description Notes

1. Environment Hosting Agreement

Note: No hosting agreement is required for PROD as it is being hosted at the TAFEs.

2. TPSE Specifications

R C+E

A+R R Provisioning of a document that details the TPSE environment specifications for the purpose of establishing an environment hosting agreement

Selection and Approval of the hosting provider will happen during contract negotiation (assumption 5, Section 2.4 (PD 205)

3. Contract Terms and Conditions

C - A+R R The provisioning of an environment hosting agreement detailing contract terms and conditions

See also Contract Management (2.3)

4. Environment Establishment Plan

5. Vendor Development / Unit Testing / System Testing

I - A+R - Provisioning of a plan for the establishment of an application development / unit test / system test environment where all application development and testing (Custom code development and configuration) will take place.

Hosted at TechnologyOne Headquarters in Queensland.

6. Interim TPSEIncluding the

E - A+R R Provisioning of a plan for the establishment

Hosted at TechnologyOne

13 of 31


following staging environments:

Validate Delivered Software

Data Conversion

Business Process

of an Interim TPSE environment where limited testing can be preformed.

Headquarters in Queensland. No performance issues are expected. Timing for the duration of the Interim TPS is subject to SMS project plans.

7. TPSEIncluding the following staging environments:


Data Conversion

Business Process

System Integration Testing

Acceptance Testing

Training

E - A+R R Provisioning of a plan for the establishment of an outsourced TPSE environment where all software validation, Data Conversion, Business Process, System testing (integrated Application Code (vanilla & custom), Application Configuration, Data Management, Interfaces, Integration testing and Sociability testing) will take place.

Hosted independentlySIT will be on demand.,

8. TAFE Pre Production

E A+R

E C Provisioning of a plan for the establishment of a pre production environment where the TAFE release testing can occur prior to deployment to production systems.

Hosted at TAFE. Applicable to institutes that do not opt for the TPSE Pre- Production. TAFE are to build the infrastructure according to specifications provided by Prime. Prime to also specify the risks around the specification provided.

9. TAFE Production E A+R

C - Provisioning of a plan for the establishment of the production environment (including BAU environments such as training, disaster recovery, etc)

Hosted at TAFE

Training Strategy Product ownership is to be defined.

10. Preliminary Design - Infrastructure


12. Preliminary Design - - A+R - Provisioning of a Preliminary Design that is to be conducted prior to detailed design.

14 of 31


During Preliminary Design it is expected that any TAFE sector specific Infrastructure Designs / constraints will be considered. Designs will be in accordance with DIIRD standards.

13. Preliminary Design Review (Infrastructure / Environments)

- - A+R - Provisioning of a preliminary design review where the results of peer reviews are assessed and preliminary design documents are reviewed.

RACI will be different for each environment depending on where it is hosted

14. Preliminary Design Review Feedback (Infrastructure / Environments)

- - A+R - All feedback from the preliminary design review will be considered for inclusion or update to the existing design in line with baseline configuration and baseline requirements and preliminary design documents will be updated and circulated for acceptance.

15. Interim TPSE

16. Preliminary Design C - A R Provisioning of a Preliminary Design that is to be conducted prior to detailed design.



R - A+R - Provisioning of a preliminary design review where the results of peer reviews are assessed and preliminary design documents are reviewed.


C - A R All feedback from the preliminary design review will be considered for inclusion or update to

15 of 31


the existing design in line with baseline configuration and baseline requirements and preliminary design documents will be updated and circulated for acceptance.

19. Acceptance and signoff

E I A C Signoff of the preliminary design

20. TPSE

21. Preliminary Design of TPSE including the following logical environments:


Data Conversion

Business Process


Acceptance Testing

Training

C - A R Provisioning of a Preliminary Design that is to be conducted prior to detailed design.



R - A+R - Provisioning of a preliminary design review where the results of peer reviews are assessed and preliminary design documents are reviewed.



C - A R All feedback from the preliminary design review will be considered for inclusion or update to the existing design in line with baseline configuration and baseline requirements and preliminary design documents will be updated and circulated for acceptance.



E I A C Signoff of the preliminary design


26. Preliminary Design R R A+R C Provisioning of a Preliminary Design that is to be conducted prior to detailed design.

16 of 31




R R A C Provisioning of a preliminary design review where the results of peer reviews are assessed and preliminary design documents are reviewed.



C C A+R C All feedback from the preliminary design review will be considered for inclusion or update to the existing design in line with baseline configuration and baseline requirements and preliminary design documents will be updated and circulated for acceptance.



E S I - Signoff of the preliminary design

30. TAFE Production

31. Preliminary Design R R A+R C Provisioning of a Preliminary Design that is to be conducted prior to detailed design.



R R A C Provisioning of a preliminary design review where the results of peer reviews are assessed and preliminary design documents are reviewed.


33. Preliminary Design Review Feedback (Infrastructure /

C C A+R C All feedback from the preliminary design review will be

RACI will be different for each environment depending on where it

17 of 31


Environments) considered for inclusion or update to the existing design in line with baseline configuration and baseline requirements and preliminary design documents will be updated and circulated for acceptance.

is hosted


E S I - Signoff of the preliminary design

35. Detailed Design – Infrastructure Test Environments


37. Detailed Design - - A+R - Provisioning of a Detailed Design prior to development of the infrastructure environments.

38. Detailed Design Review (Infrastructure Environments)

- - A+R - Provisioning of a detailed design review where the results of peer reviews are assessed and detailed design documents are reviewed.


39. Detailed Design Review Feedback (Infrastructure Environments)

- - A+R - All feedback from the detailed design review will be considered for inclusion or update to the existing design in line with baseline configuration and baseline requirements and detailed design documents will be updated and circulated for acceptance.


40. Interim TPSE

41. Detailed Design of the Interim TPSE, including the following logical environments:


Data Conversion

Business Process

C - A R Provisioning of a Detailed Design prior to development of the infrastructure environments.

42. Detailed Design R - A+R - Provisioning of a RACI will be different

18 of 31


Review (Infrastructure Environments)

detailed design review where the results of peer reviews are assessed and detailed design documents are reviewed.

for each environment depending on where it is hosted


C - A R All feedback from the detailed design review will be considered for inclusion or update to the existing design in line with baseline configuration and baseline requirements and detailed design documents will be updated and circulated for acceptance.



E I A C Signoff of the detailed design

45. TPSE

46. Detailed Design of the TPSE, including the following logical environments:


Data Conversion

Business Process


Acceptance Testing

Training

C+E

- A R Provisioning of a Detailed Design prior to development of the infrastructure environments.

Independent third party endorsement of the design across all environments to be arranged by TAFE ICT


R - A+R - Provisioning of a detailed design review where the results of peer reviews are assessed and detailed design documents are reviewed.



C - A R All feedback from the detailed design review will be considered for inclusion or update to the existing design in line with baseline configuration and baseline requirements and detailed design documents will be updated and circulated for acceptance.


49. Acceptance and E I A C Signoff of the detailed

19 of 31


signoff design 50. Detailed Design –

Infrastructure Production Environments


R C A+R C Provisioning of a detailed design and specification for the Pre Production Environment.

RACI to be resolved. Verify comments

52. TAFE Production Environment

R R A+R C Provisioning of a detailed design for the Production Environment.

RACI to be resolved. Verify comments


R R A C Provisioning of a detailed design review where the results of peer reviews are assessed and detailed design documents are reviewed.



C C A+R C All feedback from the detailed design review will be considered for inclusion or update to the existing design in line with baseline configuration and baseline requirements and detailed design documents will be updated and circulated for acceptance.



E S I - Signoff of the detailed design

56. Capacity Planning for TPSE

C I A+R R Provision of environments and infrastructure usage reports for capacity planning and sizing

57. Build

58. Infrastructure

59. Vendor Development Environment/s

- - A+R - Build of the Development Environments for the TAFE SMS Solution

Hosted at TechnologyOne Headquarters

60. Interim TPSEIncluding the following staging environments:


Data Conversion

Business Process

C - A R Build of the Interim TPSE environments for SMS.

Hosted at TechnologyOne Headquarters

20 of 31


61. Cut-over of environments

I - A+R C Provision of all services related to the cut-over of the solution from the interim TPSE to the TPSE.

62. TPSEIncluding the following staging environments:


Data Conversion

Business Process

System Integration Test

Acceptance Test

Training

E - A R Build of the TPSE Environments for SMS (as per section 3.5 of the Environment Hosting Strategy-PD 205)

Hosted independently.Independent third party endorsement of the design across all environments to be arranged by TAFE ICT


C A+R

E - Build of the TAFE Pre Production Environments for the TAFE SMS Solution

Hosted at TAFE

64. TAFE Production C A+R

E - Build of the TAFE Production Environments for the TAFE SMS Solution

Hosted at TAFE

65. Vendor Baseline Baseline Applications to be loaded

66. Hardware - - A+R C Setup and testing of all hardware in accordance with the design specifications

67. Supporting Software / Tools

- - A+R - Installation and testing of software / tools in accordance with the design specifications.

This will include: Operating

Systems Security Database

Server Software

Application Server Software

Web Server Software

Virtualisation Technologies

Monitoring Messaging

Operating systems, ICT infrastructure and known tools are defined in the Constraints Model section of the Environment Hosting Strategy (PD205). Some tools are currently under review.

68. Satellite Applications

C - A+R - All satellite applications are to be installed and tested in

"Stubs"will be used for the Library Management System,

21 of 31


accordance with the design specifications.

This will include: Finance Time Tabling Library

Management System

ID Management

Learning Management

ID Management and Learning Management Systems. TechnologyOne Financials and Celcat Timetabling full products will be used for the Finance and Time Tabling Interfaces.

69. TPSE Baseline Baseline Applications to be loaded

70. Hardware for following environments:


Data Conversion

Business Process


Acceptance Testing

Training

E - A R Setup and testing of all hardware in accordance with the design specifications

Independent third party endorsement of the design across all environments to be arranged by TAFE ICT


C - A R Installation and testing of software / tools in accordance with the design specifications.



Server Software


Web Server Software

Virtualisation Monitoring Messaging

Includes the provisioning all suitable upgrades, patches, bug fixes in the environment.


C - A R Installation and testing of satellite applications in accordance with the design specifications

This will include: Finance

Time Tabling Library

Assumption: 5 common satellite

applications will be loaded. As an option

we could possibly use "stubs".

22 of 31


Management System

ID Management

Learning Management

73. TAFE Baseline Baseline Applications to be loaded

74. Capacity Planning for TAFE

C R A+R C Provision of environments and infrastructure usage reports for capacity planning and sizing for individual TAFEs (including PILOT)

75. Hardware C A+R

E - Setup and testing of all hardware in accordance with the design specifications


C A+R

E - Installation and testing of software / tools in accordance with the design specifications.



Server Software


Web Server Software

Virtualisation Monitoring Messaging


C A+R

E - All satellite applications are to be installed and tested in accordance with the design specifications

This will include: Finance Time Tabling Library

Management System

ID Management

Learning Management

Assumption: all applicable satellite applications will be loaded. As an option we could possibly use "stubs".

78. Test (PD208 Test Strategy)

79. TPSE

23 of 31


Infrastructure80. Application

Environment Test (Operation & Connectivity)

C I A R Establish all Development, Testing and Pre Production Environments and ensure that the environments are fully operational at all times.

81. Database Environment (Operation & Connectivity)

C I A R Establish all Database Development, Testing and Pre Production Environments and ensure that the environments are fully operational at all times.

82. Backup, Recovery and Restoration Services Infrastructure

C I A R Provide Specifications for Backup, Recovery and Restoration Services to the SMS Project Team (e.g., UPS, Tape Drives, DRP, etc).

This is for the baseline infrastructure

83. Throttling I - A+R R Includes throttling of various components of the SMS to ensure performance

84. TAFE Infrastructure

85. Application Environment Test (Operation & Connectivity)

C+E

A+R

C+E - Establish all Development, Testing and Pre Production Environments and ensure that the environments are fully operational at all times.

86. Database Environment (Operation & Connectivity)

C+E

A+R

C+E - Establish all Database Development, Testing and Pre Production Environments and ensure that the environments are fully operational at all times.

87. Backup, Recovery and Restoration Services Infrastructure

C+E

A+R

C+E - Provide Specifications for Backup, Recovery and Restoration Services to the SMS Project Team (e.g., UPS, Tape Drives, DRP, etc).

This is for the baseline infrastructure

88. Other Infrastructure Tests

89. Web Services Environment (Operation & Connectivity)

E C A R Establish all Web Services Development, Testing and Pre Production Environments and ensure that the

C-TAFE to be consulted and involved during infrastructure tests at the TAFE sites.

24 of 31


environments are fully operational at all times.

90. Desktop Sociability Environment Establishment

E C A R Establish a Desktop Sociability Testing Environment.

91. Desktop Sociability Environment (Operation & Connectivity)

E C A R Establish a Desktop Sociability Testing Environment.

at TAFEs

92. EAI/Messaging Environment (Operation & Connectivity)

E C A R Establish all EAI/Messaging Development, Testing and Pre Production Environments and ensure that the environments are fully operational at all times.

93. Environment Availability Plan

94. Interim TPSE C I A R Provisioning for a plan which identifies when the environments will be available.

95. TPSE C I A R Provisioning for a plan which identifies when the environments will be available.

96. TAFE C A+R

C - Provisioning for a plan which identifies when the environments will be available.

97. Environment Booking Process

98. Interim TPSE C I A R Provisioning for an environment Booking Process which identifies how to book access to an environment. An availability schedule will be published for the SMS Project team on a weekly basis to ensure visibility of the environment availability. It is anticipated that an electronic booking request will be lodged and a confirmation will be sent to the requestor informing them of the outcome of the request. This notice will occur within 24 hours of the request being raised.

99. TPSE C I A R Provisioning for an environment Booking

25 of 31


Process which identifies how to book access to an environment. An availability schedule will be published for the SMS Project team on a weekly basis to ensure visibility of the environment availability. It is anticipated that an electronic booking request will be lodged and a confirmation will be sent to the requestor informing them of the outcome of the request. This notice will occur within 24 hours of the request being raised.

100.TAFE C A+R

C - Provisioning for an environment Booking Process which identifies how to book access to an environment. An availability schedule will be published for the SMS Project team on a weekly basis to ensure visibility of the environment availability. It is anticipated that an electronic booking request will be lodged and a confirmation will be sent to the requestor informing them of the outcome of the request. This notice will occur within 24 hours of the request being raised.

101.Environment Access Process

102.Interim TPSE C I A R Provision for an environment access and authorisation process which identifies the requirements for secure access (Onsite or remote) to an environment. It is anticipated that environments will be available via remote

26 of 31


access (Web Services, Secure VPN, etc)

103.TPSE C I A R Provision for an environment access and authorisation process which identifies the requirements for secure access (Onsite or remote) to an environment. It is anticipated that environments will be available via remote access (Web Services, Secure VPN, etc)

104.TAFE Pre Production (New & Legacy)

C A+R

C - Provision for an environment access and authorisation process which identifies the requirements for secure access (Onsite or remote) to an environment. It is anticipated that environments will be available via remote access (Web Services, Secure VPN, etc)

105.TAFE Production (New & Legacy)

C A+R

C - Provision for an environment access and authorisation process which identifies the requirements for secure access (Onsite or remote) to an environment. It is anticipated that environments will be available via remote access (Web Services, Secure VPN, etc)

106.Environment Management Processes (ITSM/ITIL)

107.Incident Management

I - A R Provision of an effective incident management process to restore normal SMS operation (within SLAs) in TPSE as quickly as possible and minimize the adverse impacts of business operations, thus ensuring that the best possible levels of

27 of 31


service quality and availability are maintained

108.Problem Management

I - A R Provision of processes to resolve the root-cause of any incidents related to TPSE.

109.Event Management I - A R Provision of processes to proactively monitor to detect events, analyse them and determine the appropriate control action related to TPSE.. Event Management is the basis for monitoring and control of the operational SMS.

110.Capacity and Performance Management

I - A R Provision of services to ensure current and future capacity and performance demands of SMS users are delivered in a cost-effective manner in TPSE.

111.IT Service Continuity Management

CI - A R Provision of Business Continuity Plans of each TPSETAFE by ensuring that relevant IT infrastructure and SMS services can be recovered within required and agreed business timescales.

112.Service Level Management

CI - A R Provision of processes to ensure the agreed level of service is established in TPSE (to be agreed as part of the contract) and provided for each SMS and ensure that the service delivered achieves the targets. In addition, customer satisfaction with the SMS should be monitored and proactively improved.

113.Security Management

CI - A R Provision of services in TPSE to ensure SMS security is aligned with business security requirements and ensure that information security is effectively managed in all SMS

28 of 31


activities. Information Security Management ensures that confidentiality, integrity and availability of SMS related assets, information and data is maintained

114.Knowledge Management

I - A R Provision of services to maintain relevant documentation that enables the service provider to provide a high level of Support and continually improve. The purpose of Knowledge Management is to ensure that the right support person has the right knowledge, at the right time to support the SMS.

115.Infrastructure Management

I - A R Provision of management processes to effectively manage ICT infrastructure.

116.Environment Service Level Agreements

117.Interim TPSE R I A R Provision for an Environment Service Level Agreement to ensure that any planned or unplanned outages are managed and that Environments are made available in a timely manner.

118.TPSE R I A R Provision for an Environment Service Level Agreement to ensure that any planned or unplanned outages are managed and that Environments are made available in a timely manner.

119.TAFE Pre Production (New & Legacy and interfaces)

C A+R

C - Provision for an Environment Service Level Agreement to ensure that any planned or unplanned outages are managed and that Environments are made available in a timely manner.

120.TAFE Production C A+ C - Provision for an

29 of 31


(New & Legacy) R Environment Service Level Agreement to ensure that any planned or unplanned outages are managed and that Environments are made available in a timely manner.

121.Environment Decommissioning

122.Vendor Development / Unit Testing / System Testing

- - A+R - Decommissioning of environment

123.Interim TPSEIncluding the following staging environments:


Data Conversion

Business Process

C I A+R Decommissioning of environment

124.TPSE Including the following staging environments:


Data Conversion

Business Process

System Integration Test

Acceptance Test

Training

C I A R Decommissioning of environment

125.TAFE Legacy C A+R

- C Decommissioning of environment

30 of 31

Documents

SMS-S1_1-PD TPSE Requirements Specification v1.0