U02: Has Access
1. Characteristic Information
Goal In Context: / Determine whether a particular ID has access to a given roomScope: / Labs in the computer science building
Level: / Secondary
Pre-Condition: / none
Success End Condition: / “Yes” if student on the list and “No” if student not on the list
Failed End Condition: / “Yes” if student not on the list and “No” if student on the list
Primary Actor: / UI: user interface
Trigger Event: / request from UI
2. Main Success Scenario
Step / Actor / Action Description1 / UI / provides ID and room number
2 / System / verifies format of ID
3 / System / verifies format of room number
4 / System / compares ID to list associated with the room
5 / System / returns “Yes” if ID on list and return “No” if ID not on list
3. Scenario Extensions
Step / Condition / Action Description2a / invalid ID format / returns status INVALID_ID_FORMAT
3a / invalid room number / returns status NVALID_ROOM_NUMBER
4. Scenario Variations
If a variation can occur in how a step is performed it will be listed here.
Step / Variable / Possible Variations5. Related Information
The following table gives the information that is related to the Use Case.
Schedule:Priority: / Must
Performance Target: / less than 1 second
Frequency:
Super Use Case: / U01: RequestAccess
Sub Use Case(s):
Channel To Primary Actor:
Secondary Actor(s): / Data manager
Channel(s) To Secondary Actor(s):
6. Open Issues
The following table provides insight to any unresolved problems or questions. These are the things that seem to apply but could not be fit into this use case on this pass.
Issue ID / Issue Description1 / How is the access list managed/stored?
2 / What is the interface to the data manager?
Author: P. Grabow / Page 1 of 2
July 12, 2005