The automated testing solution was implemented to speed up the software testing process in projects that bring very complex schedule, cost, and quality tradeoffs. The business requirements established for acquiring the testing solution automation had very critical nonfunctional requirements necessary to achieve successful results. Evaluating and measuring the nonfunctional requirements became very critical to evaluating risks, non-risks, tradeoffs, and metrics and how each business requirement could be affected. The ATAM was chosen to create a link between business and nonfunctional requirements through a very clean scenario description language.
The presentation will focus on the process and give samples of the following aspects of the project:
1) challenges found during the software architecture evaluation
2) documentation-level definition to guide the evaluation
3) necessary process and people maturity levels to develop a good evaluation
4) registration of future analysis identified during the ATAM process
5) metrics collected during the process evaluation and how to check it against the architecture decisions