How lrivas01/trabalho_aed works
Project type and purpose
• This is a small C‐based academic project (TRABALHO_AED), focused on algorithms and data structures for managing “usuario” entities.
• There is no frontend/backend separation or external services—this is a single‐process command‐line/library module.
File structure
• Top-level:
• README.md – project description and due date
• / – C header files (erros.h, usuario.h)
• src/ – implementation file (usuario.c)
• No build scripts are present, but we can assume a simple Makefile or gcc command will compile src/usuario.c linking against include/.
README for additional insights
• The README only states this is an algorithms & data‐structures assignment (due 14/06).
• No further architecture guidance, so we infer responsibilities by file names.
a. Main components
• Command‐Line Application (or Test Harness)
• Usuario Module (business logic & data structures)
• Error Handling Module
• (If added) Build System / Compiler Invocation
b. Relationships and interactions
1. CLI/Test Harness calls public functions in usuario.c (via usuario.h).
2. usuario.c implements user‐entity operations and, on failure, invokes definitions in erros.h.
3. erros.h defines error codes or utilities that usuario.c references.
c. Architectural patterns/principles
• Modular layering: separation between interface (headers) and implementation (src).
• Single responsibility: usuario module handles all user‐entity logic; erros module handles error definitions.
d. Key technologies
• C language
• gcc or Makefile (implicit)
• Standard library (stdio.h, stdlib.h inside usuario.c)
Putting it all together
[CLI/Test Harness]
|
| calls
v
[usuario.c / usuario.h]
|
| uses
v
[erros.h]
• Optionally enclose the compile step at the bottom:
(Makefile/gcc) → outputs executable