Forcing discussions
In some ways, the primary benefit of architecture Garlan is that it forces discussions of some critical issues
- The Xerox PARC Mesa/Cedar group did roughly the equivalent by spending enormous amounts of times in defining and clarifying interfaces, before coding
Finding errors earlier is generally considered to be better, of course
I’m unsure the degree to which the formalism per se helps, although there are surely some supporting examples