Back

Use Case Discovery

Deep-dive into specific customer use cases and requirements

Use Case Overview

  • What is the name/title for this use case?
  • Describe the business process this supports.
  • What business value does this integration provide?
  • Who are the business owners of this process?

Data Flow

  • Describe the data flow end-to-end:
    • • Where does the data originate?
    • • What transformations occur?
    • • Where does the data need to go?
    • • Who consumes the data?
  • Is this a one-way or bidirectional flow?
  • Is this batch, real-time, or event-driven?

Source Details

  • What is the source system?
  • How is data extracted? (file drop, API, database query, event)
  • What triggers the extraction?
  • What is the data format and structure?
  • Sample data available? (sanitized/anonymized)

Transformation Details

  • What transformations are required?
  • Are there conditional routing requirements?
  • Are there data validation rules?
  • What happens when validation fails?
  • Do you need to split or merge files?

Target Details

  • What is the target system?
  • How is data loaded? (file drop, API, database insert)
  • What format does the target require?
  • Are there naming conventions for delivered files?
  • What acknowledgment is expected from the target?

Volume & Performance

  • How many records per transfer?
  • What is the file size range?
  • How frequently does this run?
  • What is the acceptable processing window?
  • Are there SLAs for this integration?

Error Handling

  • What should happen if the source is unavailable?
  • What should happen if the target is unavailable?
  • How should partial failures be handled?
  • Is automatic retry required? What retry logic?
  • Who should be notified on failure?

Dependencies

  • What must complete before this can run?
  • What depends on this completing?
  • Are there any calendar-based dependencies? (business days, holidays)

Current State & Success Criteria

  • How is this use case handled today?
  • What works well with the current approach?
  • What are the pain points?
  • How will you measure success for this use case?
  • What does "done" look like?