How omda777/sales-order-application works
Project type and purpose
• This is a console-based C# Sales Order Management System.
• Its purpose is to simulate a retail sales workflow for OOP demonstration: managing customers, products, orders, and payments.
• It’s not a web or microservice app—its architecture is a single executable with logical modules.
File structure
• Top-level solution file: Sales Order Application.sln.
• Four main class-library folders (each with its own .csproj):
• Customers (CustomerSystem namespace)
• Products (Products namespace)
• Order (OrderSystem namespace)
• Payment (PaymentSystem namespace)
• Console entry project: Sales Order Application folder with Program.cs.
• Supporting folder Photo (holds UML.png).
• No external DB: each module holds in-memory lists and CRUD methods.
README for additional insights
• Confirms namespaces and key classes (Person, Customer, Product, Stock, Order, OrderItem, Payment, Transaction).
• Features: data entry (CRUD), sales process, print operations.
Details without over-segmenting
• Four modules plus the Program entry point.
• Data flows (e.g., “CreateOrder → OrderManager.Add()” or “ProcessPayment → TransactionManager.Add()”).
• Avoid showing every class file; instead group them by module (e.g., list Person & Customer under CustomerSystem).