About This Architecture

Entity-Relationship Diagram for a library management system modeling four core entities: AUTOR, LIVRO, USUARIO, and EMPRESTIMO. AUTOR records author metadata including name, nationality, and birth date; LIVRO links to AUTOR via foreign key and tracks ISBN, genre, publication year, and inventory; USUARIO stores patron information; EMPRESTIMO connects LIVRO and USUARIO to log loan transactions with scheduled and actual return dates. This normalized schema eliminates data redundancy, enforces referential integrity, and supports queries for book availability, patron history, and overdue tracking. Fork and customize this diagram on Diagrams.so to adapt it for your library system, add additional entities like CATEGORIA or MULTA, or export as .drawio for use in database design tools.

People also ask

How do I design a database schema for a library management system that tracks books, authors, patrons, and loans?

This ER diagram models a library system with four entities: AUTOR (author metadata), LIVRO (book records linked to authors), USUARIO (patron information), and EMPRESTIMO (loan transactions). Foreign keys enforce relationships, enabling queries for book availability, patron borrowing history, and overdue tracking.

DER Sistema de Biblioteca

AutointermediateER diagramdatabase designlibrary managementrelational databasedata modelingnormalization
Domain: Data EngineeringAudience: Database designers and library management system developers
1 views0 favoritesPublic

Created by

August 13, 2026

Updated

August 16, 2026 at 3:03 PM

Type

er

Need a custom architecture diagram?

Describe your architecture in plain English and get a production-ready Draw.io diagram in seconds. Works for AWS, Azure, GCP, Kubernetes, and more.

Generate with AI

AI-generated. Verify before production use. Learn more

Report this diagram