In previous articles, we have explored how decisions are the foundation of architecting software systems. In “Software Architecture: It Might Not Be What You Think It Is”, we argue that software architecture is about capturing decisions, not describing structure, and in “Why You Should Care About Software Architecture”, we state that greater awareness of the implicit architectural decisions development teams are making, and forcing these decisions to be made explicitly, can help them make better, more informed decisions using the empirical data they gain from their sprints/iterations.
