Please enable JavaScript.
Coggle requires JavaScript to display documents.
SLC Book Borrowing System - Coggle Diagram
SLC Book Borrowing System
Constraints
Time
Limited time to work on automatic book scanning system
Economic
Lack of budget available
Limited knowledge on code
Limited knowledge on design
Technical
Accessibility guidelines
Target audience
Design
Utility: Align features with user needs
Accessibility: Use high contrast and familiar font for readability
Effectiveness: Regularly collect user feedback and implement them
Safety: protect user data with strong security and offer easy undo options
Learnability: design intuitive navigation and maintain consistency
User Interfaces
Login
Management Page
View/Edit loan data
Notify overdue borrowers
Users
Users are librarians who will be managing book loans
Students also play a part in the system by scanning the books they borrow
Data
Data Storage: Relational Database
tblBooks
title
author
status
tblLoans
loandate
returndate
tblStudents
Name/Surname
Email/Password
tblStaff
Name/Surname
Email/Password
User data
High amount of data needed to create account as users are librarians (Name, Email, Job Credentials, Blue Card)
Task
Microsoft Teams Submission
Submit PowerPoint, Code, Video
Date Due: 15/11/2024
Algorithms
Security
Local Server
Pseudocode to illustrate the basis of code
Data flow diagrams to display the basis of the system's dataflow
Programmed Components
Process loan or return after gathering student and book ID by updating the tblLoans table in the database
Admins (Librarians) will view/edit loans and book inventory by updating tblLoans and tblBooks