Lengthy design phases for software architecture and systems used to be a required step and sometimes an enterprise prerequisite before engineering teams began developing applications and systems. Architects would review high-level requirements, consider enterprise standards, and diagram an architecture on the platforms, design patterns, and components to use in the software development process.
Some organizations take architecture planning one step further if new technologies or software components are required. They've established architecture review boards to provide transparency in decision making, highlight architecture risk, align budgets, and examine other considerations that impact sustainable development practices. Others challenge the effectiveness of architecture review boards because they hinder autonomy, disrupt development flow, and can lead to excessive documentation.