Integration Plan

Every Wave project is anchored by a living Integration Plan. Think of it as your auto-updating project spec — part business doc, part technical blueprint, and always up-to-date.

What’s in the Integration Plan?

• Business Context
  • Capture goals, stakeholders, requirements, and the “why” behind the integration.
• Data Flow
  • Visualize and describe how data moves from source systems to targets.
  • See which profiles are involved and how they’re connected via mappings.
• Implementation
  • Manage todos, tasks, and checklists for each step.
  • Track progress on mapping, code generation, and testing.
  • All code, mappings, and tests are linked back to the plan.

How Does It Work?

• Conversationally Evolving: As you chat with Wave (or add artifacts), the plan evolves. Business requirements, test cases, and tasks are added and updated automatically.
• Editable: Add or update any section via chat (“add a test case for birthdate edge cases”) or direct UI input.
• Source of Truth: The plan is visible to everyone on your team, so engineers, PMs, and SMEs are always aligned.

Why Use the Integration Plan?

• Never lose track of business goals, mapping decisions, or technical todos.
• Collaboration-first: No more scattered Google Docs, tickets, or chat threads — keep everything in one place, auto-organized.
• Drives automation: Every code artifact, mapping update, or test case is linked to the plan, so you always know why something exists.

Typical Workflow

1. Start a new project and describe your integration goal in chat.
2. Wave creates the initial plan with context, profiles, and tasks.
3. Iterate:
   • Add new requirements or constraints via chat or UI
   • Refine test cases, mapping logic, or business context as needed
4. Execute:
   • Generate code and mappings as you complete steps in the plan
   • Track real progress, not just checkboxes

Pro Tip

Ready to see how the data model works? Learn about data profiles and fields →