rxsaturn/banco-de-dados-1

Purpose and Entry Points

This is a Portuguese-language database course repository, primarily for Banco de Dados I, with supplementary Banco de Dados II material. It is documentation- and assignment-driven, not an executable application. The root README.md provides only the repository identity.

Core starting points are the course PDFs at root (bd1_01_intro_bd.pdf through bd1_06_nomaliza.pdf), written exercises (Exercício1.md, Exercício2.md), and the academic-calendar database project under Projeto/.

BD1 Learning Sequence

The root PDFs define the foundational instructional progression: database introduction, database-project introduction, ER/DER modeling, relational modeling, model transformation, and normalization. Their ordered naming establishes the primary conceptual flow:

bd1_01_intro_bd.pdf, bd1_03_der.pdf, bd1_04_modelo_relacional.pdf.

Equivalent exercise sheets are grouped separately in Exercicios/, aligning practice work to each stage:

Exercicios/bd1_exercicios_03_der.pdf, Exercicios/bd1_exercicios_06_normaliza.pdf.

Academic Calendar Database Project

The principal applied artifact is an SGCA (Sistema de Calendários Acadêmicos) database-design project. Requirements drive the model and implementation sequence:

Projeto/Requisitos Calendário Acadêmico.md,

Projeto/SGCA.pdf.

Project stages are explicitly separated into requirements/modeling, database creation, and a database-connected application:

Projeto/Sistema Calendários Acadêmicos - Parte 1 Corrigida.md,

Projeto/Sistemas de Calendários Acadêmicos - Criação do Banco.md,

Projeto/Sistemas de Calendários Acadêmicos - Aplicação Conectada ao Banco de Dados.md.

The repository does not expose source code, schema files, database vendor configuration, or application runtime artifacts; the project materials are instructional specifications.

Modeling and Data-Design Flow

The intended database lifecycle is: capture academic-calendar requirements → create an ER/DER model → map entities and relationships to a relational schema → normalize relations → create/populate/query the database → connect an application to the database. This is supported by both the BD1 sequence and project documents, especially Projeto/Requisitos Calendário Acadêmico.md and Projeto/Sistemas de Calendários Acadêmicos - Criação do Banco.md.

The key architectural boundary is between conceptual/logical database design and physical implementation/application connectivity. No deployed service, API boundary, or persistence implementation is represented in the tree.

BD2 Advanced Database Systems Material

banco_de_dados_II/ extends the curriculum into storage, access paths, query processing, transactions, recovery, and distributed data partitioning. Main instructional components include:

banco_de_dados_II/Armazenamento de Dados e Hierarquia de Memória.md,

banco_de_dados_II/Índices em Árvore (B-Tree e B+Tree).md,

banco_de_dados_II/Sharding_e_Particionamento_em_Bancos_de_Dados_Distribuidos.md.

Detailed modules under banco_de_dados_II/documents/ cover relational algebra, query evaluation, external sorting, relational operators, transaction management, and failure recovery.

Executable/Generated Assets

There are two Python scripts, apparently educational or presentation-support utilities rather than application entry points:

apresentacao_assets/generate_diagrams.py and

banco_de_dados_II/scripts/consistent_hashing_visualization.py.

No dependency manifests, service definitions, database containers, CI configuration, or external-service integrations are present. Python is the only identifiable runtime from the tree, while the primary deliverable remains static course and project documentation.