Modeling for architects
Nathaniel Schutta discusses a basic set of architectural diagrams. Drawing on a case study, Nathaniel walks attendees through constructing a set of diagrams that will effectively communicate their designs. In addition, Nathaniel covers stakeholdersexplaining who might benefit from each type of diagramand explores how to constructively review an architectural model.
Talk Title | Modeling for architects |
Speakers | Nathaniel Schutta (Pivotal) |
Conference | O’Reilly Software Architecture Conference |
Conf Tag | Engineering the Future of Software |
Location | New York, New York |
Date | April 11-13, 2016 |
URL | Talk Page |
Slides | Talk Slides |
Video | |
In some organizations, architects are dismissed as people who draw box-and-arrow diagrams (the dreaded whiteboard architect). While we don’t want to foster that stereotype, it is important for an architect to be able to construct basic architectural diagrams. An architect must also be able to separate the wheat from the chaff, eliminating those models that don’t help tell the story. Nathaniel Schutta discusses a basic set of architectural diagrams. Drawing on a case study, Nathaniel walks attendees through constructing a set of diagrams that will effectively communicate their designs. In addition, Nathaniel covers stakeholders—explaining who might benefit from each type of diagram—and explores how to constructively review an architectural model.