Some aspects of the Test Automation Architecture can optionally be described using a UML model, stereotyped as <<test
Where available, you may be able to make use of some part of the existing Test Automation Architectures with little
need to tailor them. However, usually each project requires some variation in approach, techniques, and tools, which
ultimately affects the Test Automation Architecture itself. In many cases, tailoring or creating an appropriate Test
Automation Architecture will occur during the Elaboration phase, and will be fine-tuned and extended with each
subsequent iteration in both the Construction and Transition phases.
For the definition of Test Automation Architecture, we recommend using a single source that maintains an outline
description of the main characteristics of the architecture. Note: you should avoid excessive and unnecessary
detail in the architectural description.
Optionally the Test Automation Architecture can be enclosed within the Software Architecture Document, either described in its own section
or as a set of concerns detailed throughout.
As an alternative to formal documentation, you might choose to simply record this information as a set of informal
architectural notes accompanied by a minimal set of explanatory diagrams, possibly maintained on a white-board readily
visible to the test team.