70 likes | 84 Views
This scenario analysis table breaks down each step of a normal use case, determining necessary screens and reports. It aids in identifying screens, reports, and data storage requirements for a specific use case. The table facilitates information gathering, screen navigation, and designing navigation flow between screens. The key focus is on functional requirements rather than aesthetics. Screens must be designed for Membership Info, User Name & Password, and Confirmation, with navigation flow facilitated through a navigation matrix.
E N D
Scenario Analysis Table • Analysis of each step in the normal scenario in a specific use case • Primary use is to determine screens and reports needed to accomplish this step • Why useful: • Beneficial for identifying for a specified use case: • Screens and reports • Data stored (i.e., database classes used in design)
Scenario Analysis Table • Results from scenario analysis table • Purpose: • Information gathering through screens • Navigational flow between screens • Not purpose at this time: • Prettiness of screens or GUI
Scenario Analysis Table • Results from scenario analysis table • Need to design screens for • MembershipInfoScreen • UserNameAndPasswordScreen • ConfirmationScreen • Need to design navigation flow between screens (accomplished through navigation matrix)