# Context Mapping: Connecting Bounded Contexts > [!Note] > **Context Mapping** establishes an explicit **integration contract** between [[Bounded Context]], defining how they **communicate**, document **dependencies**, and preserve each team’s **autonomy**. Context Mapping draws a clear line between two [[Bounded Context]], capturing their relationship as a formal **technical integration contract**. It specifies how contexts **exchange information**, sets out **clear responsibilities**, and records any **dependencies** to ensure teams understand their collaboration points. By documenting the integration strategy, Context Mapping enables **controlled integration** while safeguarding each context’s **independence**, allowing teams to evolve their models without unintended coupling. --- ## References - Vernon, V. (2016). _Domain-driven design distilled_. Addison-Wesley Professional. - Vernon, V. (2013). _Implementing domain-driven design_. Addison-Wesley Professional. - Khononov, V. (2021). _Learning domain-driven design: Aligning software architecture and business strategy_. O’Reilly Media. - Alammar, J., & Grootendorst, M. (2024). _Hands-on large language models: Language understanding and generation_. O’Reilly Media. - Evans, E. (2003). _Domain-driven design: Tackling complexity in the heart of software_. Addison-Wesley Professional. - Millett, S., & Tune, N. (2015). _Patterns, principles, and practices of domain-driven design._ Wrox.