How davilb64/projeto-tp1 works
Project Type and Purpose
• This is a standalone desktop full-stack application built with Java 22, JavaFX, and Maven, following an MVC architecture.
• Its goal is to automate HR processes (user authentication, candidate management, interviews, payroll, contracts, reports) using CSV files for persistence and FXML/CSS for UI.
File Structure
• Top-level modules:
• src/main/java/app/humanize/controller → JavaFX controllers (UI logic)
• src/main/java/app/humanize/model → Domain entities (Usuario, Vaga, Candidatura, etc.)
• src/main/java/app/humanize/repository → Persistence layer (CSV read/write)
• src/main/java/app/humanize/service → Business logic, validation and report-generation strategies
• src/main/java/app/humanize/util → Utilities (screen navigation, session, external API lookup)
• src/main/resources/view → FXML UI definitions
• src/main/resources/css → Application styles
• CSV files under resources → Data store
• Patterns: MVC separation, Strategy for formatters and report generators, factory for reports, custom exceptions, internationalization via resource bundles.
README Insights
• Confirms layers, tech stack, feature set (authentication, candidate/vacancy management, contracts, payroll, PDF/CSV reports).
• No external database: persistence via CSV.
• Entry points: Launcher.java and Main.java.
Components
a. UI Layer
– FXML Views + CSS
– JavaFX Controllers
b. Domain Model
– Entity classes (Usuario, Candidato, Vaga, etc.)
c. Service Layer
– Business services (LoginService, validation under service/validacoes, report-generation under service/relatorios, formatters under service/formatters)
d. Persistence Layer
– Repositories (BaseRepository, UsuarioRepository, etc.) reading/writing CSV files
e. Data Store
– CSV files in src/main/resources
f. Utility & External Integration
– EnderecoViaCep (calls external CEP API)
– ScreenController, UserSession
Relationships & Data Flow
1. User interacts with a View (FXML + CSS)
2. Controller handles UI events → invokes Service methods
3. Service applies business rules, calls Validators or Report Generators (Strategy)
4. Service calls Repository to read/write domain data
5. Repository reads/writes CSV files (local filesystem)
6. Service may return formatted data (PDF/CSV) via Formatters
7. Controller updates the View with results
Architectural Patterns & Principles
• MVC separation: UI, Controller, Model
• Single Responsibility: each package/layer has a clear role
• Strategy Pattern: interchangeable formatters (PdfFormatter, CsvFormatter) and report generators
• Factory Pattern: dynamic report instantiation
• Dependency Injection via constructors or service locators (ScreenController)
• Internationalization: resource bundle lookups in controllers and views