How amruthaamara1/inventorymanagementsystem works
Project type and purpose
• This is a WPF desktop application written in C#/.NET using the MVVM pattern.
• It’s an Inventory Management System: manages products, sales/purchase transactions, and generates/export reports (CSV).
File structure
• Top-level App.xaml/App.xaml.cs and MainWindow.xaml/MainWindow.xaml.cs: bootstrap and host the UI.
• Commands: reusable ICommand implementations (RelayCommand).
• Converters: WPF IValueConverters (BoolToVisibilityConverter).
• Views & ViewModels: one-to-one mapping of XAML View files under Views/ to ViewModel classes under ViewModels/.
• Models: domain entities (Product, Transaction, Report).
• Services: business-logic layer (ProductService, TransactionService, ReportService, IReportGenerator implementations like SalesReportGenerator).
• Data: EF Core’s DbContext and Migrations for SQLite schema.
• Helpers: FileExporter for CSV export (uses CsvHelper & SaveFileDialog).
README for additional insights
• Confirms MVVM, EF Core with SQLite, CsvHelper for exports, async/await and ObservableCollection for live UI updates.
a. Main components
• UI Layer (WPF Views & Converters)
• Presentation Layer (ViewModels & Commands)
• Service / Business Logic Layer (Services + IReportGenerator implementations)
• Data Access Layer (EF Core’s DatabaseContext + Migrations)
• External/Infrastructure (SQLite database file; CsvHelper + SaveFileDialog for export)
b. Relationships & interactions
• Views bind to Properties/Commands in ViewModels (INotifyPropertyChanged, ObservableCollection).
• ViewModels invoke Services (e.g. ProductService.AddProductAsync, TransactionService.RecordSaleAsync, ReportService.GenerateReportAsync).
• Services use DatabaseContext (CRUD via EF Core’s DbSet<T>) and Linq queries.
• ReportService composes with one or more IReportGenerator implementations to produce Report models.
• Helpers/FileExporter uses CsvHelper library and WPF’s SaveFileDialog to persist CSV to disk.
c. Architectural patterns & design principles
• MVVM enforces separation of concerns: Views ↔ ViewModels ↔ Models.
• Dependency Inversion: ViewModels depend on service interfaces.
• Asynchronous programming (async/await) for all I/O.
• Observable pattern for UI refreshes.
d. Relevant technologies
• WPF (Views, App.xaml)
• MVVM (ViewModels, Commands, Converters)
• Entity Framework Core (DatabaseContext, Migrations, Data Annotations)
• SQLite (local file database)
• CsvHelper & SaveFileDialog (export)
• LINQ, async/await