Skip to content
Tamjid Islam edited this page Nov 15, 2024 · 12 revisions

Welcome to the Ju-Exam-Office-Management-System wiki!

  1. User Login Flow • Event: A user (student, department, or exam controller office) logs into the system. • Steps:

  2. The user is presented with a login screen.

  3. User enters credentials (ID, password).

  4. System validates the credentials.

  5. If valid, the user is redirected to their respective dashboard (student dashboard, department dashboard, or exam controller office dashboard).

  6. If invalid, an error message is displayed (e.g., "Invalid attempts. Please try again."). • Required Elements: o Rules:  Password must meet security criteria (e.g., 8 characters, special characters, etc.).  After 5 failed login attempts, account is temporarily locked. o Images: Login page background, user icons, error icons. o Sounds: Optional sound upon successful login or error.

  7. Exam Registration Flow (for Students) • Event: A student registers for an upcoming exam. • Steps:

  8. Student navigates to the "Exam Registration" section.

  9. Available exams are displayed based on the student's enrolled courses.

  10. Student selects the exams they wish to register for.

  11. The system validates that the student is eligible for the selected exams (e.g., prerequisites completed, fees paid).

  12. A confirmation page is shown.

  13. Student receives an email and a registration slip for download. • Required Elements: o Rules:  Only students who have met prerequisites and cleared dues can register.  Registration closes after a set deadline. o Images: Exam list, confirmation page, registration slip design. o Sounds: Notification upon successful registration.

  14. Exam Scheduling and Invigilation Flow (for Faculty/Staff) • Event: Faculty or staff schedule exams and assign invigilators. • Steps:

  15. Faculty logs into their dashboard and accesses the "Exam Scheduling" section.

  16. They select the course and set the exam date, time, and location.

  17. They assign invigilators from the list of available faculty.

  18. A confirmation email is sent to invigilators and students registered for the exam.

  19. System automatically updates the calendar with the exam schedule. • Required Elements: o Rules:  The exam cannot be scheduled on holidays.  Faculty can only be assigned to invigilate exams they are not teaching. o Images: Calendar, exam room maps. o Sounds: Notification sounds for schedule creation and updates.

  20. Exam Grading and Result Submission Flow (for Faculty) • Event: Faculty enters exam results for their students. • Steps:

  21. Faculty navigates to the "Submit Results" section after the exam is completed.

  22. Faculty inputs grades for each student or uploads a CSV file containing grades.

  23. The system validates the grades (e.g., within valid ranges, appropriate format).

  24. Faculty confirms the results.

  25. An automated email with the grades is sent to students.

  26. The exam office is notified of the submission for record-keeping. • Required Elements: o Rules:  Grades must be submitted within a defined period after the exam.  Faculty cannot change grades after final submission without authorization. o Images: Grade input forms, result confirmation screens. o Sounds: Notification upon successful result submission.

  27. Result Viewing Flow (for Students) • Event: Students view their exam results. • Steps:

  28. Student logs in and navigates to the "View Results" section.

  29. The system displays all past exam results, sorted by semester or course.

  30. The student can download a PDF version of their results. • Required Elements: o Rules:  Students can only view results after they are published. o Images: Result sheet templates, download buttons. o Sounds: Optional notification when new results are published.

  31. Notifications and Alerts • Event: The system sends notifications for important events. • Steps:

  32. Notifications are triggered for events like exam registrations, schedule updates, grade submissions, etc.

  33. Alerts are displayed on the dashboard, and emails are sent if applicable. • Required Elements: o Rules:  Critical alerts must be acknowledged by the user. o Images: Notification icons, pop-up alerts. o Sounds: Different tones for critical and non-critical alerts. This system needs strong role-based access controls, automated validations for each workflow, and robust data management to ensure that exam operations run smoothly

  34. Team and Title Details:

Our team name is JU_Six_Wizards. Our team members are: 1. Suraiya Mahmuda(SM) - 364 2. Mahfuz Anam(MA) - 374 3. Mohammed Tamjid Islam(TI) - 382 4. Md. Abdullah Al Mamun(AM) - 390 5. Farhan Ahmed Onu(FO) - 405 6. Kamrul Hasan Nahid(KN) - 407

Our Project Name is JU Exam Office Management System. In this project, we'll work on a system where the tasks of the exam office will no longer analog, all the tasks will be done digitally(online).

  1. Overview of the Project: Our project is on Ju exam office management system it has three type users .They are Exam office, student , department Exam office can give registration form for the exam. Studnet can see their result through internet, can collect marksheet and certificate Department can give exam schedule to the exam office

  2. User Interface 4.1 Login 4.2 Registration 4.3 Dashboard Screen 4.4 Manage Students Screen 4.5 Manage Exams Screen 4.6 Notification System