Report for February 2020

Report Date
February 2020

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.

 

We are in early stages of planning a workshop to clarify the longer term vision for API's at the University.

 

Section Two: Projects Not Started

There are no projects not started.

Section Three: Projects in Progress

Project Info                                                                                   Project Manager's Commentary

DTI018

 

Milestones

Delivery of EDW Person Resolver ID API 20-Mar-2020
Delivery of PURE Id Resolver API 20-Mar-2020
Delivery of UniDesk API 03-Apr-2020
Deployment review 17-Apr-2020
Close 24-Apr-2020

 

RAG: AMBER

 

 

Report for February 2020

Achievements in Last Period

  • PURE API 

    • Resolution of initial issue identified inconsistencies in the way non standard individuals are stored. 

    • Regression testing is underway.

  • Unidesk API
    • Liaise with Service Team regarding progression through internal Test and prep prior to external testing.

    • Internal testers still experiencing 403 Forbidden error.  Back with Dev team for resolution.

  • 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.

 

DTI026 API Gateway and API Management Tool

 

Milestones

Milestone Due Date
Acceptance Review 19-Aug-2019
Delivery 20-Aug-2019
Closure 11-Sep-2019

 

RAG: AMBER

Report for February 2020

Achievements in Last Period

  • Documentation with regards delivery of training reviewed.

  • Update Closure report in prep for closure.

Issues

  • At this point in time it is not clear roles and responsibilities regarding ongoing support.  Until agreed formal handover can't take place.

Next Steps

  • Review handover of WSO2 and associated training to Production and address outstanding actions.

  • Update of documentation to address WSO2 now being in the cloud.

  • Raise PICCL to extend end date to the end of March 2020.

  • Close project.

 

DTI028 Maturing the API Infrastructure

Milestones

Milestone Due Date
WP 4.1 - Python templates  Done
WP 7.1 and 7.2 Centralised Logging (writing/reporting to logs)  Done
WP 8 API Standards  Done
WP 6.2 Security Scanning – Dependency Check  Done
WP 6.1 – Security Scanning – ZAP  Done
Approval of API standards and security scanning  Done
D6 Secure Software Development  Done
Closure 25/10/2019

 

RAG: AMBER

 

Report for February 2020

Achievements in Last Period

  • Liaise with project sponsor to confirm project closure and outstanding tasks.
  • Initial draft closure report out or review.

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 make this not achievable within the confines of this project. 

Next Steps

  • Raise PICCL for project closure extended until the end of March 2020
  • Project closure.

 

DTI029 Maturing the API Service

Revised Milestones To Be Confirmed Post Workshop.

RAG: AMBER

 

Report for February 2020

Achievements in Last Period

  • Scheduled API Service Planning Workshop was changed to discussion with senior Apps leadership.
  • Service management and Development working together on model for initial service delivery.
  • Decision made with Apps leadership that we would extend this project to cover initial service delivery tasks.

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 will become clear.

Next Steps

  • Service Management and Development Services to complete development of initial service delivery model.
  • Clarify tasks required to deliver initial service model and re-scope 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.

 

Programme Status
RAG Status
Overall
AMBER
Has formal escalation taken place?
Yes
Escalated to
Alex Carter, Stephan Kaempf, Dave Berry
RAG Commentary
Taking longer than expected to complete development and testing tasks. Service management and development have limited resources to complete initial service delivery model.