Report for Sept 2018

DTI026 API Gateway and API Management Tool

New Proposed Milestones To Be Confirmed

RAG

AMBER

Report for Sept 2018

Achievements in Last Period

Activities in this current phase are aligned with getting WS02 ready to transition Service Management/Production Services.

• Work has continued with DEV build for WS02, involving activities to ensure network connectivity, configuration of WS02 and load balancing configuration
• Work has commenced on Security Use Cases

Issues

• No new issues
• Currently reviewing delivery timescale and budget across whole programme

Next Steps

• Continuing with the technical tasks associated with making WS02 "production" ready.
• Develop and deliver training
• Arrange discussions/meetings to decide roles and responsibilities
• Gain agreement regarding Security Use Cases
• Agree new milestones for project

DTI028 Maturing the API Infrastructure

New Proposed Milestones To Be Confirmed

RAG

AMBER

Report for Sept 2018

Achievements in Last Period

Technical activities in this period have focused on  delivering a containerised API into the infrastructure.   This work is significant as through this exploration we can better understand the move to production.

•  Delivered a containerised API into the infrastructure via a java microservice.  The outcome brings us closer to a Microservices infrastructure by removing unnecessary dependencies (tomcat, consul) and allows networking and discovery to be handled by the external abstractions of Kubernetes.  This exploration has allowed us to better understand how the Kubernetes architecture can benefit our API programme as a whole.
• Meeting took place with Call Logging Administrative team to provide advice and guidance on how we may be able to consume the services and implement our deliverables in an optimal fashion. Initial scoping of work associated with this has been added to the plan.

Issues

• No new issues

Next Steps

• WP 2 - containerised microservice (completion)
• WP 4.1 - templates for new APIs - Python
• WP 7.1 - utilise centralised logging - writing to logs
• WP 7.2 -  utilise centralised logging - reporting from logs
• Agree new milestones for project

DTI029 Maturing the API Service

New Proposed Milestones To Be Confirmed

RAG

AMBER

Report for August 2018

Achievements in Last Period

• D5 Sustainability Plan -  Some meetings/discussions have taken place to discuss this deliverable against the backdrop of the need to develop a target operating model , for the implementation and management of the APIs. It is likely we will propose removal of this deliverable to be replaces with Target Operating Model and propose for delivery in next Tranche. This needs further consideration and discussion with the programme sponsor.
• Events Uitility Booking - The event booking attendance recording tool is currently in development.  A system has been designed which will allow independent tutors to take attendance via a mobile device focusing on direct interactions with an API without the need for complex logins or authorisation.  The infrastructure has been developed and Adrian is currently focusing on providing the components of the API and then developing the mobile first application.

Issues

• No new issues

Next Steps

• Secure Software Standard Development is scheduled for Nov (Resource Restrictions)
• Further discussion regarding Target Operating Model
• Agree new milestones for project

DTI018 Continuous Service Improvement APIs

Discretionary

Milestones

RAG

AMBER

Report for August  2018

Achievements in Last Period

Progress has continued on managing the API’s approved by the Steering Group.

There are currently have 7 proposed API’s in the project.

3are awaiting UAT (Card API, Pure API and HR) one has been deployed to Live (Org Hierarchy). 2 are being triaged (AD and Learn Gradebook Access) and Eugex Schools Feed has been approved to start capturing the requirements in a more detailed form.

One API approved for Triage has been withdrawn – Computer Lab Occupancy. This is because an API already exists which can be utilised.

We have identified a need to define the training approach for testers so that UAT can progress on 4 API’s which are currently awaiting testing.

The backlog is now being pro-actively managed through JIRA.

Issues

• No new issues
• Currently reviewing delivery timescale and budget across whole programme

Next Steps

Define UAT approach, guidance and training

• Provide training for testers
• Raise PICCL to change delivery timelines 
• Progress API’s through triage
• Agree new milestones for project

22/12/17 - Project withdrawal approved by WIS 22/12/17 - PICCL Change 6

6/12/17 - Recommendation is to withdraw and review requirements again in 18/19 due to PICCL Issue 5, project risk 5

13/10/17 - Project suspension approved by WIS 13/10/17 - PICCL Change 4

Project closure approved by WIS 23/3/18

5/2/18 - Recommendation is to close project early - PICCL Decision 8

6/12/17 - Recommendation is to review conditions for removing project from suspension in 18/19, PICCL Change 7, project risk 10, project risk 11

17/11/17 - Project suspension approved by WIS 17/11/17 - PICCL Change 7