Save Run Data Use Case Detailed Description

Use Case Name	Save Run Data
Scenario	N/A
Triggering Event	Runner requests run data is saved.
Brief Description	The runner elects to save the calculated and/or input data. The system saves the data in the requested file..
Actors	Runner
Related Use Cases	Enter Run Data
Stakeholders	N/A
Preconditions	The Application is running, data must be entered. Pace must be entered in MM:SS.ss or MM.mm format. Time of run must be entered in HH:MM:SS.ss or HH.hh format. Distance must be entered in Meters, kilometers or Miles.
Postconditions	Data must be saved in the appropriate file, in the appropriate file format (i.e. a database or spreadsheet).
Flow of Events	Actor	System
	1. Runner enters the appropriate data for saving.
	2. Runner requests the system to save the data.	2. Requests the file name and location for saving the data (or shows the location of the current file where last saved data resides).
	3. Enters the file name and location.	3. Saves the data.
	3.1 Informs the user the data was saved.
Exception Conditions	1. If the runner does not enter any data for saving, then the System informs the user that data is needed for saving: either a) The Time of Run, b) The Runner's Pace or c) The Run Distance.
	2. If the runner enters the time in the wrong format or mis-enters the time, then the System informs the user of the proper format for time entry.
	2. If the runner enters the pace in the wrong format or mis-enters the pace, then the System informs the user of the proper format for pace entry.
	2. If the runner enters the distance in the wrong format, then the System informs the user of the proper format for distance entry.
	3. If the System cannot save the data, then the System informs the user the data could not be saved.