






UC8 - Iteration 3
UC8: User visualizes meta information contained in request / response connections.
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 meta data out of the ONA file.
All Actors:
Want to see what queries and responses are being carried by the peer to peer network.
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 meta data contained in the desired connection types is displayed on the screen.
Main Success Scenario
- User generates an ONA file with the desired meta data at the end of a connection log line.
- (OPTIONAL) User opens "Advanced Options" tab on the left infobar.
- (OPTIONAL) User edits the Request Connection Type and Response Connection Type fields as desired.
- (OPTIONAL) User clicks "Save" button, closing the tab and saving the changes.
- User goes back to main infobar screen.
- When a connection of the desired type occurs, its meta data is color coded and displayed on the info bar.
Extensions (Alternative Flows):
None
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:
The meta data will be displayed at each request / response. This could be many times over the course of the whole ONA file.
Open Issues:
- To prevent too much meta data from being displayed (there is only a finite amount of space on the screen), it will be necessary to hardcode a maximum number of response meta lines to the one request meta line. When the maximum is reached we have to decide whether to truncate old responses or stop added new responses.
Links to this Page