How furkannnyzg/librarymanagementsystem works
Main Components
• User Interface (UI) Layer: This includes multiple Windows Forms such as Form1, home, Books, Loan, Members, and kullaniciKayitEkrani. These forms serve as the primary interaction point for users.
• Application/Business Logic Layer: Although not clearly separated by distinct directories (aside from the Models folder), this layer contains the logic behind operations (for example, in the code-behind files and the Models for login and registration) that manages user operations, book management, and loan processing.
• Data Access Layer: The project is connected to a SQL database as highlighted in the README. The App.config file likely contains connection string settings, and the application issues SQL queries to store/retrieve data. This layer represents the communication between the business logic and the SQL database.
• Configuration Component: The App.config file in the project houses important configuration details like database connection strings, which are essential for setting up the data access mechanism.
Relationships and Interactions
• The UI layer (forms) triggers events which send user inputs to associated event handlers.
• Business logic within the code-behind files and Models (login.cs, register.cs) processes the inputs, performs validations, and issues SQL queries.
• The Data Access Layer handles interaction with the SQL database, where data about books, loans, and members is stored or updated.
Architectural Patterns and Design Principles
• Separation of Concerns: Although the division is not strictly layered through multiple projects, there is a natural separation between the presentation (Windows Forms), business (event handlers, Models), and data access (SQL queries via App.config setup) components.
• Event-driven Programming: The Windows Forms are event-driven, communicating user actions that trigger underlying logic.
• Coupling via Configuration: The use of App.config for database connection emphasizes the principle of separating configuration from code logic.
Relevant Technologies
• C# as the core programming language.
• Windows Forms for the UI.
• SQL (likely accessed via ADO.NET or similar data access libraries) for data operations.
• Visual Studio (indicated by the .sln file) which serves as the IDE and project management tool.