We are working towards the conclusion of this phase of the API programme, aiming to launch the initial API service.
There are some development and testing tasks that are nearing completion that have had issues to resolve in order to complete.
Service management and development are collaborating on completion of the initial service delivery model for APIs. This has taken longer than anticipated because of resource pressures within Service Management but is making steady progress.
We are in early stages of a re-planning exercise to clarify the longer term vision for API's at the University.
Regression testing has been progressing. No new issues have been reported.
Unidesk API
Software Dev corrected outstanding issues with API and rereleased for test.
Identified testers have been informed but in present climate is impacting upon their priority to test this API
Liaise with Service Team regarding progression through internal Test and prep prior to external testing. St Andrews contacted and confirmed they remained available for initial external testing.
Person ID resolver API for EDW
Testing raised issue with incomplete responses. Investigation ongoing.
Issues
With UniDesk upgrade on the horizon should we continue to develop the present API. It was confirmed that the API being developed at present would remain in use during the staggered upgrade and was therefore worth continuing with.
Next Steps
PURE API
Completion of regression testing within WSO2 and signed off.
Unidesk API
Liaise with Service Team regarding progression through internal Test and prep prior to external testing.
Sign off of internal testing of API via WSO2.
Initiation of external testing. St Andrews lined up as test external institution.
Promotion of API from Test to Live.
Person ID resolver API for EDW
Correction of error and re-release for test.
Completion of testing within WSO2 and signed off.
Handover process for API's to be agreed. Liaise with Service and Production Management regarding support and handover process.
Agree closure steps with project sponsor and Development Services.
PICCL raised for revised end date.
Issues
At this point in time it is not clear roles and responsibilities regarding ongoing support. It has been agreed this should be picked up by DTI029 Maturing the API Service allowing this project to progress to closure.
Next Steps
Update project report in step with agreed closure process.
Liaise with project sponsor to confirm project closure and outstanding tasks.
Draft closure report out or review and approved.
Project closed.
Issues
Final deliverables for WP 6.1 & 6.2 require review workshops followed by proposals raised at OGG. Initial deliverables suggested that project would include implementation of both elements but costs and timescales have made this not achievable within the confines of this project.
Next Steps
DTI029 Maturing the API Service
Revised Milestones To Be Confirmed Post re-scoping exercise.
RAG:AMBER
Report for March 2020
Achievements in Last Period
Service Management and Development Services to complete development of initial service delivery model.
Weekly review meetings instigated to progress re-scoping exercise.
Issues
Present plan is for Service Management and Development Services to develop the initial service delivery model. Service management and development have little spare capacity to devote to this exercise and it is therefore taking longer than expected to complete. Once this is completed the scope of remaining tasks and responsibility for them will become clear.
Next Steps
Service Management and Development Services to complete development of initial service delivery model.
Clarify tasks and those responsible to complete tasks to deliver initial service model and re-plan project accordingly.
Raise revised milestone PICCL to extend project closure to the end of April which is hoped to provide a suitable period for initial service delivery model to be developed, implemented and the project closed.
