






UC7 - Iteration 3
UC7: User modifies request and/or response connection type.
Primary Actor: Peer-to-peer Researcher / ODIN Developer.
Secondary Actor: Students, peer reviewers of ODIN research.
Stakeholders and Interests:
ODIN Developer:
Wants the network viewer to display connection information out of the ONA file that is different from the default connection values.
All Actors:
Want to see other aspects of network request/response activity than the default view.
Preconditions:
- The network viewer is already up and running, and an ONA (ODIN Network Activity) file has been loaded.
- The viewer may or may not be currently running a simulation.
Success Guarantee (Postconditions):
The graph will be reset as if the "reset" button were pressed. The simulation will now reflect the newly specified request and response types from the ONA file, and the resulting tree will match that data. If the simulation had been running, it will continue to run at the same speed as before.
Main Success Scenario
- User opens "Advanced Options" tab on the left infobar.
- User edits the Request Connection Type and Response Connection Type fields as desired.
- User clicks "Save" button, closing the tab and saving the changes.
Extensions (Alternative Flows):
- If the user wishes to restore the default settings, they may click "Restore Defaults" to automatically place the application defaults in the text fields.
- If the user decides to abort the procedure, they may click "Cancel" to restore the original state.
Special Requirements:
NONE
Technology and Data Variation List:
- If the ONA file does not contain the specified connection types, then the user will not be able to visualize them.
Frequency of Occurrence:
Infrequent. The user will likely only change these values once in any given session, and in the majority of sessions not at all. However, if the user is working on data with connection types different from the default they will run through this use case at the beginning of every session.
Open Issues:
- Data validation for the connection types is a problem, because verifying that a given ONA file contains the given connection types in the worst case requires the application to scan the entire file, which is often very large. Omitting data validation does not cause any major problems with the application, but the output could very easily confuse the user if it is not what they expect. These anomalous display conditions are easily detected, though, so it would be feasible to pop up an informative message explaining why e.g. no response messages have been displayed yet and how to fix it, so that the user can decide whether this is desirable behavior or not.
Links to this Page