Phase 3: Gap Analysis¶

3.1 Comparison with Existing Modules¶

Map every requirement to existing system capabilities:

gap_analysis:
  client: "Example Ltd."
  analyst: "AI-Analyst"
  date: "2025-01-20"

  # Fully supported – configuration only
  native_fit:
    - requirement_id: "REQ-001"
      module: "Warehouse"
      feature: "Automatic numbering of receipts"
      status: "Fully supported"
      effort: "Configuration – 1 hour"
      notes: "Just set the pattern in entityDefs"

    - requirement_id: "REQ-003"
      module: "AutoCRM"
      feature: "Contact and account management"
      status: "Fully supported"
      effort: "None"

  # Requires configuration/customization
  configuration_required:
    - requirement_id: "REQ-005"
      module: "Workflow"
      feature: "Low stock notification"
      action: "Create workflow trigger on StockItem"
      effort: "4 hours"

    - requirement_id: "REQ-008"
      module: "AutoCRM"
      feature: "Custom field for customer segment"
      action: "Add enum field CustomerSegment on Account"
      effort: "2 hours"

  # Requires new development
  development_gaps:
    - requirement_id: "REQ-002"
      feature: "Mobile receiving via barcodes"
      description: |
        Requires a new mobile interface with camera API
        integration for barcode scanning.
      estimated_effort: "40 hours"
      priority: "High"
      entities_required:
        - "No new entities – extend StockReceipt"
      technical_notes: |
        - PWA app for mobile devices
        - Offline-first architecture
        - Sync when connectivity is restored

    - requirement_id: "REQ-012"
      feature: "Integration with accounting system Pohoda"
      description: |
        Export invoices to XML format compatible
        with Pohoda.
      estimated_effort: "20 hours"
      priority: "Medium"
      entities_required: []
      technical_notes: |
        - Use existing Pohoda extension
        - Field mapping per client

  # Summary
  summary:
    total_requirements: 15
    native_coverage: 6  # 40%
    configuration_coverage: 4  # 27%
    development_required: 5  # 33%
    total_estimated_hours: 120

3.2 Architectural Fit¶

For larger gaps assess architectural impact:

architecture_fit:
  target_stack: "EspoCRM 9.x + AutoERP extensions"
  backend: "PHP 8.2"
  frontend: "Vue 3 (for custom UIs)"
  integrations:
    - "Pohoda XML export"
    - "Barcode scanning (mobile PWA)"
  constraints:
    - "On-prem deployment"
    - "Offline mode required for warehouse"

3.3 Risk Assessment¶

risks:
  - id: RISK-001
    area: "Mobile PWA"
    description: "Offline barcode scanning reliability"
    mitigation: "Offline-first cache, background sync, test in warehouse network conditions"
    owner: "Tech Lead"
    impact: "High"
    likelihood: "Medium"

  - id: RISK-002
    area: "Pohoda integration"
    description: "Field mapping variability"
    mitigation: "Configurable mapping, pilot export with accountant"
    owner: "Integration Engineer"
    impact: "Medium"
    likelihood: "Medium"

Phase 3 Checklist¶

[ ] All requirements mapped to existing capabilities
[ ] Configuration/customization needs identified
[ ] Development gaps estimated and prioritized
[ ] Architectural fit and constraints evaluated
[ ] Risks identified with mitigations

➡️ Continue with Validation for the final analysis phase.