
π Student Projects (College Reports) Β· Use Case
What students, examiners and the administrator do in an online examination system.
Drawing diagramβ¦
Use case diagram for an online examination system: a student registers, logs in, takes an exam, submits answers and views results; an examiner creates question banks, schedules exams and reviews descriptive answers; the admin manages users and courses. Submitting an exam includes auto-grading objective questions; webcam proctoring extends taking an exam.
flowchart LR
student(["π€ Student"])
examiner(["π§βπ« Examiner"])
admin(["π‘οΈ Administrator"])
subgraph SYS ["π₯οΈ Online Examination System"]
UC1(["Register and log in"])
UC2(["Take exam"])
UC3(["Submit answers"])
UC4(["View results"])
UC5(["Auto-grade objective questions"])
UC6(["Webcam proctoring"])
UC7(["Create question bank"])
UC8(["Schedule exam"])
UC9(["Review descriptive answers"])
UC10(["Manage users and courses"])
end
student --> UC1
student --> UC2
student --> UC3
student --> UC4
examiner --> UC7
examiner --> UC8
examiner --> UC9
admin --> UC10
UC3 -.->|"includes"| UC5
UC6 -.->|"extends"| UC2Who uses a college library system and what each of them can do: members, the librarian and the system administrator.
The database of a library system: books and their copies, authors, members, loans, reservations and fines, with keys and cardinality.
How data moves through a library system: members and the librarian, the main processes, and the data stores they read and write.
The main classes of a library system with attributes, methods and UML relationships.
The steps when a member borrows a book: checks, loan record and the copy status update.
Database design for online exams: courses, exams, questions and options, attempts, answers and results.