Presentations
A presentation is an informal explanation of the proposed architecture to stakeholders.
The presentation should be carefully structured so that the audience considers the implications of architectural decisions.
Purpose of Presentations
- Communicate the proposed architecture to stakeholders.
- Help explain and promote the architecture.
- Encourage stakeholders to think about important architectural issues.
Limitations of Presentations
Only a shallow level of analysis is possible through presentations.
Presentations are useful for communication, but they do not provide the same depth of analysis as more structured evaluation techniques.
Formal Reviews and Structured Walkthroughs
A formal review involves gathering a group of people to examine a document page by page.
The purpose is to identify concerns, discuss them, and agree on any actions that need to be taken.
Formal Review Process
A formal review generally involves:
- Reviewing the document page by page.
- Raising comments and concerns.
- Discussing the concerns as a group.
- Agreeing on the actions that need to be taken, if any.
Participant Roles
Each attendee is assigned a role before the review meeting.
Examples include:
- Moderator Organizes and manages the review.
- Presenter Presents the material being reviewed.
- Reviewers Examine the material and raise concerns.
Preparation for a Review
The materials to be reviewed are typically sent to reviewers a few days before the meeting.
These materials may include:
- Specifications
- Design documents
- Code
Providing the materials in advance allows participants to prepare for the review.
Comparing the Two Techniques
| Technique | Main Purpose | Key Characteristic |
|---|---|---|
| Presentation | Communicate the proposed architecture to stakeholders. | Informal; supports only shallow analysis. |
| Formal Review | Examine documents, discuss concerns, and agree on actions. | Structured group examination with assigned roles. |