< session />
Describing and Documenting Your Architecture
Fri, 25 April
You’ve created an architecture and have plenty of diagrams to illustrate your solution. Now, you need to communicate that architectural solution to various stakeholders—developers, other architects, product owners, business stakeholders, and operations teams. How do you effectively convey your architectural solution? It turns out that diagrams are only a small part of the overall picture. In this session, Mark Richards introduces the concept of an Architecture Narrative—a way of effectively describing your solution—and shows you how to create one.
Target Audience: This session is primarily aimed at Software Architects, as it focuses on effectively documenting and communicating architectural decisions to various stakeholders, a critical part of their role. Product Owners and Business Stakeholders are the secondary audience, as they need to understand the architecture in a way that aligns with business goals and operational requirements.
< speaker_info />
About the speaker
Mark Richards
Founder, DeveloperToArchitect.com
Mark Richards is an experienced, hands-on software architect involved in the architecture, design, and implementation of microservices architectures and other distributed systems in a variety of technologies. He has been in the software industry since 1983 and has significant experience and expertise in application, integration, and enterprise architecture. Mark is the founder of DeveloperToArchitect.com, a free website devoted to helping developers in the journey to becoming a software architect. In addition to hands-on consulting, Mark has authored numerous technical books and videos, including his two latest books Fundamentals of Software Architecture and Software Architecture: The Hard Parts that he co-authored with Neal Ford. Mark has spoken at hundreds of conferences and user groups around the world on a variety of enterprise-related technical topics.
