Have you ever been confused by an arrow in a box-and-line design diagram? Do you use the Unified Modeling Language (UML) in your software architecture? Have you ever wondered, “Where is the line between architecture and detailed design?” If you answered yes to any of these questions, this tutorial has practical and valuable information for you.
The goal is to show you what information about an architecture to capture so that others can successfully use it, maintain it, and build a system from it. Important takeaways from this talk include the multiple views of architecture; how we can use UML in each view and when other notations work better; what views we can use to evaluate performance, availability, modifiability, and other qualities; how to complement structural diagrams with sequence diagrams, statecharts, and other behavior diagrams; and guidelines and templates to make your architecture documentation more effective.