Usage Guidance |
The work is best done in several sessions, perhaps performed over a few days (or weeks and months for very large
systems), with iteration between architectural analysis and use-case analysis. Perform an initial pass at the
architecture in while doing architectural analysis, then choose architecturally significant use cases, performing
use-case analysis on each one. After (or as) each use case is analyzed, update the architecture as needed to reflect
adaptations required to accommodate new behavior of the system and to address potential architectural problems which
are identified.
Where the architecture already exists (either from a prior project or iteration), change requests may need to be
created to change the architecture to account for the new behavior the system must support. These changes may be to any
artifact in the process, depending on the scope of the change.
|