Purpose: Partnership & Preparation: Usually present the ATAM to a small group. Get the Business Drivers.
Step 1: Purpose to ensure that the client understands the mechanics of the evaluation method; make sure the client understands the CBA of an architecture evaluation. Record questions for possible FAQ list. Consultants may write up work plans. 75 man days for evaluation team effort– duration best case is 3 weeks.
Step 2: Initial description of the candidate system. Client provides existing documentation describing the system. Client conveys main architectural drivers e.g. business goals, requirements, constraints etc.
Client and evaluation organization agree on necessary architecture documentation – “3 main views”.
NDA – for evaluation team is done at this step.
Evaluators record general business goals, quality attributes, architectural constraints and list of architecture documentation to be delivered to the evaluation team.
Step 3: Go/No-Go decision with respect to conducting ATAM.
Evaluation organization representatives understand the state of the architecture well enough to make a decision and ensure that the candidate system is ready for evaluation.
Evaluation team takes a look at the context drawing and multiple views of the system (e.g. run time etc.)
The list of named participants and their roles with respect to the system must be provided.
Step 4: SOW presentation and negotiation.
Step 5: Form core evaluation team. Aim for 4-6 evaluators.
Modifiability – coupling, encapsulation, contract based interactions, cohesion etc.
Step 6: Conduct evaluation team kick-off meeting.
Team Leader: establishes the time and place for the meeting.
Stickies on a board that can be grouped by risk themes are helpful…or use “Mind Maps”.
Tools like “Enterprise Architect” are used for evaluation in some companies.
Step 7: Prepare and Plan for Phase 1.
Review the purpose of the ATAM phases with the client.
Confirm the time and place for the evaluation for the client to present the system architecture & business goals, architect to present the system architecture and arrange for supplies.
Step 8: Preliminary review of the system’s software architecture.
Hold a brief post-mortem.