How arcanik78/appenvios-de-cargas works
Main Components
• User Interface (Presentation Layer): Represented by the “appEnvios” project. This includes all the Windows Forms (e.g., Form1, RegEnvioIU) and associated UI logic. It serves as the front-end for end users interacting with the system.
• Business Logic Layer: Encapsulated in the “CmpEnvios” project. This module includes classes for managing core business entities such as Cliente, Carga, and Envio and may include data access code and other utility classes.
• Data Persistence Layer: The SQL Server database whose schema is outlined in “Base de Datos/ScriptBD.sql”. This is where all persistent data (client information, shipment records, etc.) is stored.
• (Optionally) Internal Utilities/Configurations: Files like app.config and project-specific settings, which might be part of the infrastructure that configures components and their interactions.
Relationships and Data Flows
• That the Business Logic Layer processes this data and interacts with the Database for CRUD operations (Create, Read, Update, Delete).
• Optionally, illustrate any feedback from the Database back to the UI via the business logic.
Architectural Patterns and Design Principles
• Layered Architecture: Emphasize the three-tier structure (Presentation, Business Logic, Data Persistence).
• Separation of Concerns: Differentiate the responsibilities of each layer clearly.
• Modular Design: Note that CmpEnvios isolates business rules and models away from UI concerns, facilitating maintainability and potential reuse in other applications or contexts.
• If applicable, mention any design-time generated components (as seen by the Designer, My Project, and configuration files) that support the Windows Forms and data access layers.
Relevant Technologies and Frameworks
• Visual Basic .NET (primary programming language).
• Visual Studio 2019 (development environment).
• SQL Server (database system).
• Windows Forms (for the desktop user interface).