Revision History
| Date |
Version |
Description |
Author(s) |
| 02/12/2006 |
1.2 |
Updated to new common template. |
Andy Kant |
| 02/06/2006 |
1.1 |
Updated because of file monitoring changes. |
Corey Sullivan |
| 01/31/2006 |
1.0 |
Initial version. |
Corey Sullivan |
Use Case
Brief Description
This use case describes between the file system and the Tag project when the user makes a change in the file system through copying, moving, renaming, and deleting files.
Actors
- User The user of the Tag system and who modifies the file system.
Pre-Conditions
- Installed The user has installed the Tagging software on their system, meeting the system requirements.
- Files exist in the file system Files must exist in the file system that the user is working with.
Basic Flow
- 1. The user copies a file.
- 2. The file conduit notifies the tag software that a file copy has occurred.
- 3. The tag software copies the tags of the copied file to the copy of the file in the database (makes a new entry).
Alternate Flows
User moves a file
- In step 1, the user moves a file instead of copying a file. Step 2 occurs, but notifying the tag software with a file move event rather than a file copy. In step 3, the tag software changes the file and path name of the file to the new filename while keeping the tags associated with those tags.
User deletes a file
- In step 1, the user deletes a file instead of copying a file. In step 2, the tag software is notified with a delete event and in the third step the tag software deletes the record of the file and its association to its tags in the database. The actual tags in the database are not deleted.
User renames a file
- In step 1, the user changes a file's file name. In step 2, the tag software is notified of a rename event and in the third step, the tag software changes the name of the renamed file in the database, but keeps the association to the file's tags.
User operates on many files
- The basic flow and the alternate flows of moving a file, deleting a file, and renaming a file repeat for each file operated on rather than occurring only once.
User overwrites a file with a copy or move
- The system will follow steps 1 and 2 of the basic flow and alternate flow of "user moves a file," but in step 3, the system overwrites the copied or moved file's tags. The system will change the associations of the overwritten tags to the copy or moved file's tags.
User operates on a file with no tags
- Steps 1 and 2 will occur, but there will be no changes to teh database. There are no records of the file(s) in the database so there will be no changes necessary.
Exception Flows
User cancels file system operation
- If the file operation is an atomic operation, then there will be no changes to database when the user cancels the file operation. If the file operation is not atomic, then the database will change for every change made in the file system.
Post-Conditions
- Database reflects changes made to the file system The database's records of the files reflects the changes made to the file system.
Narrative Version
None.