The Role of Urban Design in Strategic Planning. The Case of Rio de Janeiro

Purpose: Check quality, correctness, and conformance of the application design. Reviewing: Use cases, actors, domain class diagram, screen flows, screen designs, class tables (if any), and interaction diagrams (if any). Outcome: Factual corrections to the domain model, to the screen details. Suggestions or requirements for improved UI or application design, based on either quality or conformance considerations. With these short paragraphs in place, the methodology can be summarized by role (as the following two examples show). The written form of the methodology, summarized by role, is a checklist for each person that can be fit onto one sheet of paper and pinned up in the person’s workspace. That sheet of paper contains no surprises (after the first reading) but serves to remind team members of what they already know. Here is a slightly abridged example for the programmers: Designer-Programmer Writes Weekly status sheet Source code Unit tests Release notes ... Reads:Actor descriptions UI style guide ... Reviews: Application design review (etc.) Publishes: Application. configuration Test cases (etc.) Declares: UI Stable You can see that this is not a methodology used to stifle creativity ...»