How ogonzalez-2021370/control-cine works
Project Type and Purpose
• This is a standalone, Windows‐desktop full‐stack application (C++/CLI with Windows Forms) for managing all cinema operations: movies, rooms, assignments, clients, tickets, users and HTML report generation.
• Persistence is file‐based (CSV import/export). No external services or databases.
High‐Level Component Breakdown
A. Presentation Layer (UI)
• LoginForm – handles authentication and role selection (Administrator vs. Operator)
• CRUD forms (Form1, FormReportePeliculas, FormReporteSalas, FormReporteAsignaciones, etc.) – each module’s dialog panels for create/read/update/delete operations
• Report Forms – display HTML reports in embedded browser control or launch default browser
B. Business Logic Layer
• Domain Entities – classes: Pelicula, Sala, Asignacion, Cliente, Boleto, Usuario
• Managers/Controllers – “Array…” classes (e.g., ArrayPeliculas, ArrayClientes, …) implement in‐memory arrays, CRUD operations, validations, associations
• Security/Session Manager – user login, role permissions enforcement
C. Data Access Layer
• CSV Importer/Exporter – routines under “Cargar archivos .csv” folder that read/write domain data to files: Peliculas.csv, Salas.csv, AsigPeliculasSalas.csv, Clientes.csv, CompraBoleto.csv, Usuarios.csv
• Persistence Interface – a thin adapter between Array… managers and CSV routines
D. Reporting Module
• HTML Generator – transforms in‐memory data (via Array… managers) into HTML tables and writes “Reportes generados/*.html”
E. External/Support
• File System – CSV files, generated HTML reports
• Manuals (Technical/User) – PDF documents for reference
Relationships and Data Flow
• UI Forms → invoke Business Logic methods on Controllers/Managers
• Controllers operate on Domain Entities stored in Array… classes
• Controllers call Persistence Interface to load or save CSV files
• Reporting Module reads Domain data from Controllers, outputs HTML to disk
• LoginForm calls Security Manager → grants UI access based on role
Architectural Patterns & Principles
• Layered Architecture (Presentation → Business → Data)
• MVC‐like separation: Forms = View+Controller, Array… classes = Model
• Single Responsibility: each Array… class manages one entity type
• Composition & Association: Asignacion links Pelicula+Sala, Boleto references Cliente & Asignacion
• File‐based Repository Pattern: CSV adapter abstracts persistence
Essential Elements
• Clear labels for each component (e.g., “ArrayPeliculas Manager”, “Pelicula Entity”, “Peliculas.csv”)
• Annotations for user roles (Administrator vs. Operator) tied to LoginForm and UI visibility
Putting It All Together
[Tier 1: Presentation]
• LoginForm, Form1 (CRUD UIs), ReportForms
↓
[Tier 2: Business Logic]
• ArrayPeliculas, ArraySalas, ArrayAsignaciones, ArrayClientes, ArrayBoletos, ArrayUsuarios
• Pelicula, Sala, Asignacion, Cliente, Boleto, Usuario classes
• SecurityManager (role enforcement)
↓
[Tier 3: Data Access]
• CSVImporter/Exporter adapters
↓
[Tier 4: Storage]
• Peliculas.csv, Salas.csv, AsigPeliculasSalas.csv, Clientes.csv, CompraBoleto.csv, Usuarios.csv
• Reportes generados/*.html
• On startup: CSVImporter.loadAll() → Array… populate memory
• On CRUD: UIForm.call(ArrayManager.create/update/delete) → CSVExporter.save()
• Generate report: ReportForm.request() → ArrayManager.fetchData() → HTMLGenerator.write()