Cms recommendation Report



Download 0.85 Mb.
Page6/8
Date31.05.2016
Size0.85 Mb.
TypeReport
1   2   3   4   5   6   7   8

University Risk Matrix





LIKELIHOOD

CONSEQUENCES

Insignificant

1


Minor

2


Moderate

6


Major

8


Catastrophic

10


Rare 0.05

0.05

0.10

0.3

0.4

0.5

Unlikely 0.3

0.3

0.6

1.8

2.4

3.0

Possible 0.5

0.5

1.0

3.0

4.0

5.0

Likely 0.7

0.7

1.4

4.2

5.6

7.0

Almost Certain 0.9

0.9

1.8

5.4

7.2

9.0


Outcomes

0.0 - 0.7 LOW - Manage by routine procedure.


0.8 - 2.6 MINOR - Clear published guidelines to be available. Monitor.
2.7 - 4.0 MODERATE - Active management & mitigation. Regular monitoring.
4.1 - 6.9 MAJOR - Senior management attention required. Consider elimination and devise action plan to reduce risk. Execute plan. Monitor.
> 7 EXTREME - Immediate action required. Consider elimination. Active management required. Continuous review & monitoring.

Appendix Three : Risk Treatment Plan



http://teams.admin.uwa.edu.au/sites/projectserver_114/Identification/Architecture/CMS%20Evaluation%20Risk%20Treatment%20Plan.doc

* Risk rating after treatment = Likelihood X Consequence




Risk reference number (in Priority Order) + Description (Prefix risk number with 3 letter identifier)

Treatment Actions

Risk rating after treatment*

Person/s responsible for implementation

Timetable to implement (or “In place”)

How will this risk and treatment option be monitored?

1

Governance

Inability of system to effectively control governance standards set by UWA to ensure compliance with UWA rules.



Monitor existing controls for effectiveness.

2.4 Minor

Fiona Reilly

Grant Malcolm



Prior to system implementation / migration / staff training.

Monitored by Project Reference Group.

2

Scalability

System may not be capable of expansion to sufficient size to meet UWA requirements.



Monitor existing controls for effectiveness.

2.4 Minor

ITS

Upon system implementation.

Monitored by University Website Coordinator during implementation of system.

3

Security

System security inadequate for UWA needs & expectations.



  • Setup SSL encryption of CMS server.

  • Implement more granular permissions for University sub sites.

0.4 Low

ITS

Web Office



Upon system implementation / configuration.

Monitored by University Website Coordinator during implementation of system.

4

Custom functionality
The system may not be able to incorporate custom functionality already developed by the university.

Monitor existing controls for effectiveness.

2.4 Minor

Grant Malcolm

Upon system implementation.

Monitored by University Website Coordinator during implementation of system.

5

Extensibility
The selected system may not allow UWA to develop or extend the functionality as required.

Monitor existing controls for effectiveness.

1.8 Minor

Grant Malcolm

As required.

Monitored by University Website Coordinator as required.

6

Integration with other systems
The system may not be able to integrate with other university systems and data sources.

Monitor existing controls for effectiveness.

1.8 Minor

Grant Malcolm

Upon system implementation.

Monitored by University Website Coordinator during implementation of system.

7

Complexity

Requirements specified may be too complex for selected system to manage.



Monitor existing controls for effectiveness.

1.8 Minor

Sarah Delfante


Fri 25/05/2007

Review by Project Reference Group.

8

Infrastructure

Inadequate infrastructure at UWA to run selected system at optimal performance or insufficient resources to provide adequate service levels.



Monitor existing controls for effectiveness.

1.8 Minor

Grant Malcolm

ITS


Prior to completion or project.

Monitored by Project Reference Group.

9

Short time-frame of project
Limited consultation with stakeholders could result in certain requirements being missed.

  • Develop communication plan to conduct University-wide communication to encourage adoption of new system – note stakeholder input into previous related review work that has been undertaken:

0.6 Low

Grant Malcolm

Prior to system implementation / migration / staff training.

Monitored by the Project Reference Group.

10

Product support & development

Vendors not providing adequate support for selected product.



  • Purchase Squiz support pack.

  • Maintain MySource Matrix expertise in-house.

  • Develop plans and begin preparation to upgrade to MySource Version 4 at the optimum time and before MySource Matrix support is discontinued.

0.3 Low

Web Office

Upon completion of project.

Monitored by University Website Coordinator.

11

Usability
The new system will be more difficult or complex for content authors to use than the existing system.

Monitor existing controls for effectiveness.

0.4 Low

Grant Malcolm

Web Office



Prior to system implementation / migration.

Monitored by University Website Coordinator.



Share with your friends:
1   2   3   4   5   6   7   8




The database is protected by copyright ©essaydocs.org 2020
send message

    Main page