Internal dependencies
This section refers to the dependencies between the high level scope (HLS) areas (i.e. in-scope or internal dependencies) and developing . Developing an understanding of these should help us know where to begin, or at least what to watch out for as we begin. The aim is to capture the nature, direction and significance of the dependency.
Note that I have parked the HLS area "Other" as all areas have a dependency on this work and this work will draw on insights from all other areas. However, we will try to allow this work to proceed as independently as possible from the other scope areas (that all refer to web site content areas).
| Below is dependent on left because: | Student Information | Course, Subject and Degree/Programme Information (CSP) | Postgraduate Information | Research Centres, Institutes and Chairs | Faculty and School Information |
|---|---|---|---|---|---|
| Student Information | n/a | No substantive dependencies | For information relevant to PG students only, but this is more likely to be encountered when looking at F&S | No substantive dependencies | No substantive dependencies |
| Course, Subject and Degree/Programme Information (CSP) | No substantive dependencies | n/a | Likely to be many links between PG programmes and a PG hub/area, if indeed there is to be one. - Need IA work to help determine this. - Need to decide on the primary channel/funnel to PG programme pages. | No substantive dependencies | Decision on purpose of F&S sites |
| Postgraduate Information | Small proportion of SI content likely for PG only, so unsure exactly where it is best located | Probably no substantive dependencies, assuming all course, subject and programme goes in CSP. Seems logical for PG courses and subjects but what about PG programmes? | n/a | Some interaction, given that many research entities supervise PG research. | Some F&S specific PG information likely to remain on the new F&S sites. |
| Research Centres, Institutes and Chairs | No substantive dependencies | No substantive dependencies | No substantive dependencies | n/a | No substantive dependencies |
Faculty and School Information | Reasonable amount of content likely to move from F&S to SI | Substantive course information likely to move from F&S to CSP | Substantive amount of content likely to move from F&S to PG | Reasonable amount of content likely to move from F&S to Research | n/a |
External dependencies
This section refers to the dependencies between WIP II and other initiatives/work drivers that are out of scope for WIP II. Developing an understanding of these should inform our expectations for the rate of progress, help with prioritisation of all team work and be shared back to PMO and up to manage expectations. The aim is more general than for internal, but will give a handle on why dependencies are known
Note that business as usual work might well impact on WIP II in many different way and it is not possible to document them all here.
Applying to all HLS areas
- Squiz Matrix upgrade, including Edit+: More information captured in the comments on the Other HLS
- Upgrades of other components (GSA, F5, Varnish, etc)
Student Information
- Learning success (LS) activity is a part of the wider Student information (SI) scope but not all of it. As such, order to deliver on SI we will have to deliver LS but the exact timing of each is not yet decided.
- In updating the information across all 12 sites in scope for SI some content will be moved to the web sites in LS, some to the staff intranet and some to the "About Us" parts of other pages.
Course, Subject and Degree/Programme Information (CSP)
- CIP and the associated COO will provide components of the course information in scope for CSP.
- Degree Works API potentially
Postgraduate Information
- none
Research Centres, Institutes and Chairs
- Progressing the alternative hosting arrangement would allow a better solution for some of these entities that will otherwise probably be parked/left as is.
Other
- Project Xenon has a significant overlap with the HLS "Other"