Skip to content

Detailed Use Case Estimates

Granular effort estimates with UI/API functional splits and complexity drivers.


Technical Defense Summary

Estimates in manufacturing costing are often underestimated due to "Hidden Complexity." We defend our numbers through four pillars: 1. Strict Explainability: Every UI field must map to a traceable data source (High UI logic). 2. Cascading Validation: A change in Step 1 (Material) must validly propagate through 20+ operations (High API logic). 3. Excel Parity: Replicating messy Excel logic in a structured database is an R&D effort, not just CRUD. 4. Audit Integrity: Immutable versioning requires complex snapshot triggers, not simple "Save" buttons.


📊 Use Case Baseline (Effort Split)

ID Use Case Name UI/Frontend API/Backend Total Days Strategic Complexity Driver
UC-001 Complete RFQ Flow 3.0 5.0 8 E2E State Synchronization
UC-101 Import Template 1.0 4.0 5 Visual Schema Mapping (pandas)
UC-103 Legacy Format 2.0 4.0 6 Structural Pattern Recognition
UC-202 Multi-Op Cost 1.0 3.0 4 Recursive Batch Logic
UC-203 Cascading Scrap 0.5 2.5 3 Compounding Mathematical Drift
UC-301 Drill Down UI 3.0 1.0 4 Explanatory Data Lineage
UC-302 Version Compare 3.0 2.0 5 Side-by-Side Diff Algorithm
UC-303 Benchmark UI 3.0 2.0 5 Real-time Variance Needle Gauge
UC-304 Approval Hub 2.0 3.0 5 Cross-Organization Approval State
UC-402 Material Update 1.0 3.0 4 Global Snapshot Propagation
UC-501 Standard Quote 4.0 1.0 5 PDF Layout Fidelity
UC-701 Tally Sync 1.0 7.0 8 External API Fault Tolerance
UC-801 Incremental Sync 1.0 4.0 5 CRC/Hash Change Detection
UC-902 Forensic Search 2.0 1.0 3 Timeline Audit Replay

🛠️ Granular Task Breakdown

UC-001: Complete RFQ-to-Quote Flow

  • UI/Frontend (3.0d): Multi-step wizard UI, real-time cost summary sidebar, validation toasts.
  • API/Backend (5.0d): Orchestration service for all sub-engines, RFQ status machine, DB transactions.

UC-101: Import Standard Template

  • UI/Frontend (1.0d): File drop-zone, coordinate-based error highlighting.
  • API/Backend (4.0d): pandas/openpyxl extraction logic, cell-reference mapping engine.

UC-301: Drill Down on Cost Line

  • UI/Frontend (3.0d): Interactive dependency graph, "Explain Me" flyout panels.
  • API/Backend (1.0d): Metric lineage retrieval service.

UC-303: Benchmark against History

  • UI/Frontend (3.0d): Real-time variance HUD, needle-gauge component for visual drift detection.
  • API/Backend (2.0d): Logical fingerprinting to find "similar parts," historical price retrieval service.

UC-701: Sync with Tally ERP

  • UI/Frontend (1.0d): Connection settings, sync status dashboard.
  • API/Backend (7.0d): Tally XML/JSON adapter, rate limiting logic, retry/dead-letter queues.

📈 Effort by Category (%)

Category Typical Split Why?
UI Development 35% High focus on 'Explainability' requires complex interactive components.
API & Business Logic 50% Manufacturing math (Scrap, MHR, Amortization) is logic-heavy.
Data & Infrastructure 15% Versioning snapshots and async data pipelines.

← Work Breakdown | Use Cases →