Bring the producers and consumers together to ensure that there are no discrepancies.
Write Risk Themes early at least start risk themes documentations early – and try to stick to 5. Not all risks map to a theme, there can be some outliers. The following are two groups of activities in Phase 2:
1. Testing – involves checking the results to date against the needs of all relevant stakeholders
2. Reporting –involves presenting the results of the ATAM
Phase 2 involves bottom-up information gathering and analysis.
- Consumers of the system
o End users
o Application builder
o External entities
- Servicers of the system
o System Admin
o Network Admin
Review Step 1 -6 with the Phase 2 group. Why? This helps Step 7 because these materials are useful in brainstorming. Do not constrain the group, and changes can be made to the utility tree and other artifacts.
Note: Ask for any documentation (architecture) that was requested in Phase 1. Do accept new documentation created “just for Phase 2”. Just a new view, ensure that existing views are not changed/upgraded or modifying the architecture.
A risk theme is a summarization of multiple similar risks discovered during the analysis of qualified attribute scenarios.
The point out bigger issues in the architecture and are
- Either Commission – i.e. multiple questionable decisions made in the architecture
- Or Omission – i.e. decisions NOT made or requirements not included in the architecture
E.g. Risk Theme: “There is no holistic approach to resource management…” Impacts Business Goals: “Cost, time-to-market, ability to compete with competitors”.