






Revised UC1
UC1: Export peer-to-peer network activity from ODIN run.
Primary Actor: Peer-to-peer Researcher / ODIN Developer.
Stakeholders and Interests:
Peer-to-peer Researcher / ODIN Developer:
Wants to design and run a peer-to-peer network simulation and have a log of all peer activity that can be used in post porcessing to visualize the network.
Preconditions:
ODIN is properly configured.
Sufficient disk space exists to run the simulation and store the logfile.
Any ODIN user would need a properties file, trace file, and content map.
Success Guarantee (Postconditions):
An output log of all network activity is stored upon termination of the ODIN simulation.
Main Success Scenario
1. User configures property file, trace file, and content map to their liking.
2. User executes ODIN with log level 3 (the minimum level for visualization).
3. Simulation is run and output is redirected to the log file.
4. Simulation is successfully terminated.
5. Log file contains all node creations, link establishments, and message sending.
Extensions (Alternative Flows):
- File Permissions Error: User lacks permission to create or write to desired log file. See UC1.1.
- Diskspace Error: Filesystem selected for log file is out of disk space. See UC1.2.
- General Error: There is an error writing events to log file after execution is underway. See UC1.3.
Special Requirements:
ODIN must run at the proper log level in order to output data sufficient to visualize.
The ODIN base code must be patched with visualization hooks using a batch file.
Technology and Data Variation List:
Trace files can have an arbitrary number of peers and queries.
Content maps can have different keyword-peer mappings.
Estimated disk space required is 1000x the size of the tracefile.
Must have enough memory and processing power to properly run the simulation.
Frequency of Occurrence:
Every time the user wishes to run an ODIN simulation and graphically view the results.
Open Issues:
None at this time
Links to this Page