13th November 2017 to 3rd June 2018
University of Kent
KentVision
I was contracted to develop and maintain three key areas:
Within each of these three areas, I was tasked with several smaller projects as well as working with the software testers on the resolution of bugs and the implementation of improvements. My role also involved regularly liaising with project leads and tracking all work done via JIRA.
A visual overview of all the projects undertaken throughout this contract can be seen here - https://xr7sy.app.goo.gl/JGMX (opens new window).
I was the lead developer on a project with a number of deliverables:
The project was split into five components and I was responsible for packaging these components and producing documentation. I worked closely with the project sponsor, software testers and other developers, tracking all work through JIRA. The components identified were:
A number of distinct 'mini-projects' were identified and listed below.
I was the lead developer for a series of improvements and developments focused around both staff and students timetables. Further details are provided below.
Not quite a full-blown project, a mini project is a significant piece of work scoped, tested and implemented using normal software development methodology. A mini project will typically be an improvement to a business process, introducing efficiencies and reducing complexity where possible.
An investigation established that an SLP embedded within a TPE record was failing on account of a list retrieve operation bringing back more records than was permitted (capped at 250). As a result, certain events were not shown on the student's timetable. The problem was resolved as a result of the following:
As a result of the above, an additional ten SLPs were rendered as superfluous. The above RQH also greatly simplified the means by which the student's SPR code was ascertained, as this could be derived from either a system register or a task answer (i.e. whether logged on as student or staff).
RQI (TTADMTTG1_S.sql) in BitBucket
Reference KV-2305
Documentation was prepared detailing all the individual parts of each component as well as any dependencies. SITS projects were then created for each component and moved from the development environment to test. Working closely with the software testers, I then prepared documentation detailing how the actions of the users would impact upon the underlying data.
I was tasked with improving e:Vision search tools that allowed staff to view timetables for ANY module, regardless of whether or not that module occurrence was available for timetabling.
I made the following improvements to all tasks designed to allow staff to view timetables:
Throughout all of the Attendance Monitoring components, navigation buttons were required to return the user to the main Attendance Monitoring homepage, as well as to the previous screen or other significant steps (such as a search page).
I went through all Attendance Monitoring components and created consistent styling (including colour, placement and labelling) to all navigation buttons as well as ensuring that the user could easily navigate from one section to another in an intuitive manner.
References KD-95 and KD-97
The following was delivered as part of this project:
Many improvements and developments were done to the staff and student-facing workshop portals. I was responsible for reducing page-load time from around 30 to 5 seconds; this was achieved by replacing legacy SRLs / SLPs with a single SQL query within an RQH. jQuery was then used to allow the user to alternate between views of past, present and future workshops.
RQI (TTNTSPRSWD1.sql) in BitBucket