
π Student Projects (College Reports) Β· Use Case
Students, teachers, the exam cell and parents in a college result and attendance system.
Drawing diagramβ¦
Use case diagram for a student result management system: a student views marks, attendance and report cards and applies for revaluation; a teacher enters marks and marks attendance; the exam cell publishes results and generates report cards; a parent views the child's results and attendance. Publishing results includes calculating grades and CGPA; applying for revaluation extends viewing results.
flowchart LR
student(["π€ Student"])
teacher(["π§βπ« Teacher"])
cell(["ποΈ Exam Cell"])
parent(["πͺ Parent"])
subgraph SYS ["π Student Result Management System"]
UC1(["View marks and results"])
UC2(["View attendance"])
UC3(["Download report card"])
UC4(["Apply for revaluation"])
UC5(["Enter marks"])
UC6(["Mark attendance"])
UC7(["Publish results"])
UC8(["Calculate grades and CGPA"])
UC9(["Generate report cards"])
end
student --> UC1
student --> UC2
student --> UC3
teacher --> UC5
teacher --> UC6
cell --> UC7
cell --> UC9
parent --> UC1
parent --> UC2
UC7 -.->|"includes"| UC8
UC4 -.->|"extends"| UC1Who 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.
What students, examiners and the administrator do in an online examination system.