How b3-nj0/proyecto_final_ing_soft_ii works
Project type and purpose
• This is a full-stack restaurant order management system.
• The backend is a FastAPI-based REST API that handles menu management, order processing, kitchen workflows, and sales reporting.
• The frontend consists of two static web apps:
• An administrative dashboard (SB-Admin-2 template, charts, tables)
• A customer/kitchen portal (plain HTML/JS/CSS for order placement, ticket printing, kitchen view)
File structure
• Top-level:
• Backend/ – the API server
• Frontend/ – two separate UIs under Front_Dashboard and Front_Personal-Cliente
• Backend layering:
• app/config – environment & DB connection settings
• app/models – ORM models representing tables (users, products, orders, tickets)
• app/schemas – Pydantic schemas for validation & serialization
• app/routes – router modules for each domain (users, productos, pedidos, tickets)
• app/service – business logic services (CRUD, auth, reporting)
• app/main.py – FastAPI instantiation, middleware, router registration
• Frontend: static HTML/JS/CSS org’d by feature (charts, tables, login/register) using vendor assets.
Confirm architecture from README
• Modular router pattern for each business domain
• FastAPI entrypoint orchestrates middleware and router registration for scalability
• RESTful API oriented toward three user workflows (client, kitchen, admin)