Refine the key abstractions into concrete design elements (such as classes and subsystems) and provide at least a name and brief description for each. Add them to the Design.

Refine each prioritized architectural mechanism into a design state (see Concept: Architectural Mechanism). 

Review the objectives of the current iteration to identify which mechanisms actually need to be delivered in software. Work with the Developer to those refine mechanisms into an implementation state.

Ensure that the development and test architectures are defined. Note any architecturally significant differences between these environments and work with the team to devise strategies to mitigate any risks these may introduce.

Update the Architecture Notebook to reflect any changes made during development.

Make sure that the architecture supports the requirements and the needs of the team.

Development work should be performed to produce a Build that shows that the software architecture is viable. This should provide the definitive basis for validating the suitability of the architecture. As the software should be developed iteratively, more than one increment of the build may be required to prove the architecture. During the early stages of the project it may be acceptable for the software to have a incomplete or prototypical feel, as it will be primarily concerned with baselining the architecture to provide a stable foundation for the remaining development work.

Ensure that those who need to act upon the architectural work understand it and are able to work with it. Make sure that the description of the architecture clearly conveys not only the solution but also the motivation and objectives related to the decisions that have been made in shaping the architecture. This will make it easier for others to understand the architecture and to adapt it over time.