|
1.0 Introductory Remarks
The chairman welcomed members to the meeting.
2.0 Administrative issues
2.1 The members present agreed that:
Student’s account module should be functional before registration starts on the 18TH of January 2013.
The Emhare system would be run parallel with the old system as this will allow live testing of the Emhare system.
Measures to enforce that students complete the online registration for first and second semester would be put in place. Such measures include ensuring that chairpersons of various departments will only sign the blue forms after a student has completed the second semester online registration.
Emhare system will not roll forward students who did not complete their first semester online registration. Such students’ results will be suppressed until they have completed online registration for the first semester
Workshops will be arranged for Sars, Deans, Chairpersons And Secretaries to buy in to the project and measures will be put in place to ensure that they use the system.
3.0 Infrastructural Issues
3.1 The Chairman assured the members present that Emhare System will run on a high spec server.
4.0 Security issues
4.1 It was noted that the QA teams were yet to deliver any QA test reports to the development team. The Chairman will meet the QA team leader on 16 January 2013 to discuss challenges being faced by the development team as a result of lack of input from the QA teams.
4.2 The committee recommended that:
(a) the QA teams be expanded or
(b) QA services be outsourced to the Computer Science Department or externals
4.3 Members agreed that the Emhare system could only be launched online(internet) after security measures have been implemented QA team to present their report on security issues before the registration starts such that the Emhare team decides whether to make the system accessible on the internet or not.
4.5 The committee resolved that the Emhare team will do the following to ensure security to the system:
- Ensure the system uses HTTPS for all connections
- Implement OS firewall to allow HTTP traffic only
- Authenticate users
- Implement password policy
- Students to use barcodes and staff to use ec number as default passwords on first login and system should force users to change password on first successful login.
- All generic accounts in the system to be removed
- Implement an audit trail system and the logs to be easily interpreted.
5.0 Emhare registration process
5.1 The second semester courses to be loaded in the system before the registration starts.
5.2 The engineers to indentify roles of Sars, Chairperson’s Deans and Secretaries within the Emhare System and these roles to be approved by the Admin Computer Committee.
5.3 The members agreed to borrow naming conventions of reports from the Academic Registry
5.4 The Emhare system to incorporate a facility which allows users to generate adhoc query reports.
5.5 Members agreed that all major and critical reports should be working properly.
5.6 Engineers to identify all static data to be uploaded within the Emhare system and to come up with work plan.
There being no other business the meeting ended at 1630 hours.
|
