Requirements

Non-Functional Requirements

Tun-Ya Yu 2 Comments
ID Description Rational
01 The system should be available and operable for at least 99% of the time. Availability
02 The database of the system should be protected. Security
03 The system should be backed up every 24 hours. System Backup
04 The system should be designed with direct and indirect accessibility consideration. Accessibility
05 The system should support the most common browsers and also be able to be used from a mobile device. Platform compatibility.
06 The system should meet the legislation of this kind of application. Legal and licensing issues
07 The system design should be clear to understand. User Friendliness
08 The system should respond in under 5 seconds for every request. Effectiveness

Functional Requirements

Tun-Ya Yu Leave a comment
Id Description Rational
01 User should be able to view the module description and review without login. User can view the module information without login, in case the user does not have a university account yet.
02 User should be able to login with their university id.
03 A logged in user should be able to have a nickname or to be anonymous. A user shall login with the particular university id, but could have a nickname for rating and posting to preserve privacy.
04 Logged in users should be able to leave feedback and ratings on modules which they have taken. Users can only leave feedback on the modules they have been enrolled in to ensure accurate ratings.
05 Each module page should include four aspects: Module description, rating of lecture, rating of marking, and communication board.
06 Rating criteria of lectures should include a scale of difficulty, engagement, size of class, helpfulness and clarity. Rating criteria of lectures should help users understand how the modules are taught.
06 Rating criteria of marking shall include a scale of scores, difficulty of coursework, and difficulty of exams. Rating criteria of marking should help users understand how to achieve better results and the coursework requirements.
07 Module description shall include the syllabus, type of coursework, and size of coursework group. Module description should help user to have an understanding of the overview of the module.
08 The system should be able to suggest suitable modules for users. The system should be able to suggest modules from users’ enrollment status and their scores in previous modules.
09 The system should provide a platform for student communication in module sections. The platform for communication shall help students to develop greater engagement with the module materials, opportunities for peer support/peer learning.
10 User should be able to give feedback on the system. This function will ensure user satisfaction.