The Technical Architecture development process described above includes iterations. Financial and timing constraints should explicitly limit the number of iterations within steps 1 through 8, and drive to implementation. After that, a new cycle of architecture evolution may ensue.
Choosing the scope of an architecture development cycle carefully will accelerate the pay-back. In contrast, an excessively large scope is unlikely to lead to successful implementation.
"How do you eat an elephant? - One bite at a time".
Copyright © The Open Group, 1998, 1999