Examining the Use Cases
One of the activities of the architecture team is to examine the use case model from a technical viewpoint. The use case model, as a view of the desired system's dynamic behavior, is prioritized according to perceived risk. The process is to address the use cases with the most risk early and thus prevent unwanted "gotchas" later. A risky use case might involve the use of a technology or require a high degree of performance. Take, for example, an Internet-based commerce application. The use case writers might describe the collection of customer information in the following way:
The system then prompts the customer for name and address information. The customer enters in his or her first and last name, then tabs to the address ...
Get Building Web Applications with UML now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.