HT
← All projects

Academic project — Backend & Database

University Library Management System

Library loan and return management system with user management and penalty tracking.

Period2025
My roleDesign, backend development, and database modeling
TechnologiesPython · SQL · PostgreSQL · UML
01

The starting point

Structure users, books and loans in a consistent relational model, then implement return and penalty rules.

Design and development of a complete loan and return management system for a university library, including user management, borrowing tracking, overdue tracking, and penalty calculation.

University Library Management System
Project visual · open to view full size
02

How it works

Simplified functional workflow
  1. 1Users & books
  2. 2Loans & returns
  3. 3Penalty rules
  4. 4SQL queries & reports
Architecture & implementation
  • User modules: registration, authentication, profile management.
  • Loan management: creation, consultation, return, and history.
  • Automatic overdue and penalty calculation based on business rules.
  • Normalized relational schema and advanced SQL queries for reporting.
  • Application of object-oriented design principles.
Technical decisions
  • PostgreSQL for relational robustness and advanced query management.
  • Schema normalization to avoid redundancy and ensure data integrity.
  • Object-oriented design for a clear and maintainable architecture.
Lessons learned
  • Upfront relational schema design is crucial for data consistency.
  • Advanced SQL queries (joins, aggregates) are essential for meaningful reports.
  • Technical documentation facilitates system maintenance and evolution.
Possible next steps
  • Add a graphical interface for librarians.
  • Integrate advanced search by author, genre, or availability.
  • Generate statistical reports on borrowings.
03

Results & practical value

  • Applied relational modeling, business rules and aggregation queries for loan tracking.

Delivered so far

  • Functional application with user, loan, and penalty modules.
  • Normalized relational schema and advanced SQL queries.
  • Feature testing and validation completed.
  • Technical documentation produced.
04

Scope & limitations

  • Presented as a technical project. No institutional deployment or user count is established.

Source: portfolio documentation. Explanatory visual, not a screenshot from a user institution.