2.1. Functional Requirements with Priority Weights - Satyum97/Course-Management-System GitHub Wiki
FUNCTIONAL REQUIREMENTS WITH PRIORITY WEIGHTS
The Functional requirements along with its priority weights for CMS are as follows :
Label | Name | Statement | Priority |
---|---|---|---|
R1 | Authentication | System must authenticate each user before using the software | 5 |
R2 | Course Enrollment | System must enable students to enroll/drop from courses | 5 |
R3 | Sign Up | System must allow users to sign up on the portal | 5 |
R4 | Password reset | System must allow user to reset their password in case they forgot their previous one | 5 |
R5 | Course history | System must provide the students to view history of their attended courses | 3 |
R6 | Add/Update/Delete courses | System must allow admins to update/add/delete courses | 5 |
R7 | Dashboard | System must provide a dashboard to manage all the courses and program in one place | 4 |
R8 | Notifications | System must provide notification to the students for any update related to the course that student has enrolled | 3 |
R9 | Search | System must allow students to search courses and view their content | 4 |
R10 | Search Filter | System must allow students to search courses based on requirements(eg. Class Prefix, Class Term, etc.) | 4 |
R11 | Assign Instructor | System must allow admin to assign an instructor to the course | 5 |
R12 | Admin User Identification | System must identify the admin user by its admin and password | 5 |
R13 | Database | System must provide a storage to store course information and user information into database | 5 |
R14 | Login | System must provide Login to its user based on the authentication details entered during SignUp | 5 |
R15 | Logout | System must be able to Logout it users | 4 |