|
| 1 | +# Accounting Software - Windows Forms Application |
| 2 | + |
| 3 | +This is a **Windows Forms-based Accounting Software** developed using a **5-layer architecture**. The application communicates with a **SQL Server** database using the **Database First** approach, and follows **Repository** and **Unit of Work** design patterns for efficient data access and transaction management. |
| 4 | + |
| 5 | +## Features |
| 6 | + |
| 7 | +- **User-friendly Windows Forms Interface**: The application provides an intuitive interface for users to manage accounts, record transactions, and generate financial reports. |
| 8 | +- **5-Layer Architecture**: The project is structured to separate concerns across different layers: |
| 9 | + 1. **Presentation Layer (UI)**: Handles user interactions through Windows Forms. |
| 10 | + 2. **Application Layer**: Contains business logic for accounting tasks. |
| 11 | + 3. **Domain Layer**: Defines the core entities like `Account`, `Transaction`, etc. |
| 12 | + 4. **Data Access Layer**: Manages data operations with **Entity Framework (Database First)**. |
| 13 | + 5. **Infrastructure Layer**: Provides support services like logging and configuration. |
| 14 | + |
| 15 | +## Technologies |
| 16 | + |
| 17 | +- **Windows Forms**: To build the desktop application interface. |
| 18 | +- **SQL Server**: For storing all accounting-related data. |
| 19 | +- **Entity Framework (Database First)**: Models and database context are generated from the existing database schema. |
| 20 | +- **Repository Pattern**: Abstracts database operations to promote flexibility. |
| 21 | +- **Unit of Work Pattern**: Manages transactions across multiple repositories to ensure consistency. |
| 22 | + |
| 23 | +## Design Patterns |
| 24 | + |
| 25 | +1. **Repository Pattern**: Provides a clean abstraction layer over data access, ensuring that business logic is not tightly coupled to the database implementation. |
| 26 | +2. **Unit of Work Pattern**: Ensures that multiple changes across different repositories are committed as a single transaction, providing consistency and integrity. |
| 27 | + |
| 28 | +## Benefits |
| 29 | + |
| 30 | +- **Separation of Concerns**: Each layer is dedicated to a specific responsibility, making the application easier to maintain and extend. |
| 31 | +- **Modular and Scalable**: The architecture allows for easy updates or replacement of components without affecting the entire system. |
| 32 | +- **Consistency in Data Operations**: Using Unit of Work ensures that all data changes happen within a single transaction, reducing the risk of data corruption. |
| 33 | + |
| 34 | +## Getting Started |
| 35 | + |
| 36 | +1. **Set Up the Database**: Use SQL Server to create the database and then generate the models using the **Entity Framework Database First** approach. |
| 37 | +2. **Configure the Application**: Update the connection string in the application’s configuration file. |
| 38 | +3. **Run the Application**: Open the solution in Visual Studio and run the project. |
0 commit comments