30th November 2015 to 27th March 2016
A visual overview of all the projects undertaken throughout this contract can be seen here - https://goo.gl/ynn0if (opens new window).
Due to statutory changes, there was a need to allow students to record in e-Vision their highest qualification and ethnicity. I was responsible for ensuring that these two new fields were included across a range of stored procedures, views and functions. It was also necessary to amend QA's implementation of Stu-Talk in order to reference these two new fields. I worked closely with another developer to ensure that he was able to include these two new fields in various management-level Excel reports.
Excel driven report to tally a range of activities (i.e. lecture, seminar or both) with a corresponding absence record, and to report on any anomalies found. An anomaly would usually suggest a lecturer had failed to take a register for the event, and the report would list all such anomalies during the reporting period.
The user is able to run the report given a wide range of selection criteria (reporting period, course group, campus, etc.)
Similar to the Attendance Monitoring Report developed previously, but focus was on looking at event records (EVE, EVI and EVA) and trying to match these up with absence records (SAB); the rationale here being to try to identify tutors who have a timetabled event that has not had a register recorded for that event. As with the âAttendance Monitoring Reportâ, the user running the report was able to select one or more criteria:
Whilst based on existing similar reports, this was a new report providing information on student attendance on specific course groups based on a range of criteria selected by the user:
I was responsible for creating a new stored procedure that would take the userâs selection criteria, extract the data from SITS and present the data in a format suitable for inclusion in an Excel spreadsheet. A second developer was responsible for taking the output from my stored procedure and using this to populate said spreadsheet.
Database development was undertaken in Microsoft SQL Server Management Studio 2012, using Microsoft Visual Studio and Team Foundation Server for source control.
During development, it was necessary to create new tables to retrieve semester details (e.g. begin and end date for current semester); and also to modify an existing view in order to retrieve student personal detail (SPD) and fee status information.
The stored procedure created had several complex parts to it:
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.
Assisted both with the creation, documentation and handover process surrounding the creation of staff SITS accounts.
Resolved a problem affecting the availability of timetables in the live instance of SITS e-Vision.
Resolution of many other ad-hoc queries and problems, all within SLA.
Created and documented a process to allow administrative staff the means to bulk import student photographs and store these as related documented using DCU. I then created an SRL to allow export of student photograph data into a spreadsheet, suitable for use in card printing software.
QA maintains a large database of customers and contacts that require regular imports and updates. Part of this import process involves checking for duplicate customers. A user reported a problem with this customer de-duplication report (stored procedure) and I was responsible for investigating the issue.
A new TUP was created to monitor changes to the enrolment status of all SCE records. When the enrolment status changed to either 'WS' or 'NC', a process would trigger to send an email to the IT helpdesk, informing them of the change. A new SRL was created for this notification email.
QA has several SRLs used to prove that a given student is actively enrolled on a course; these SRLs are typically required by councils, banks, etc.
Due to the expansion of QA across multiple locations, it was necessary to tailor these SRLs to reflect a studentâs base campus. Previously, the SRLs were only required for students based at a single campus.
Based around SPR, the SRLs were amended to automatically retrieve a studentâs campus based on the âLocationâ field. Additionally, an existing SLP was amended in order to show a different logo dependent on the studentâs campus.