Document Version: 1.1

Revision History

Date	Version	Description	Author(s)
02/12/2006	1.1	Updated flow style to be consistent with other use cases, updated to new common template.	Andy Kant
02/06/2006	1.0	Initial version.	Andy Kant

Table of Contents

• Brief Description
• Actors
• Pre-Conditions
• Basic Flow
• Alternate Flows
• Exception Flows
• Post-Conditions
• Narrative Version

Use Case

Brief Description

This use case describes the event of a user adding tags to one or more files.

Actors

• User The user of the Tag system.

Pre-Conditions

• Installed The user has installed the Tag software on their system, meeting the system requirements.

Basic Flow

• 1. User highlights file(s).
• 2. User right-clicks the highlighted file(s), bringing up the context menu.
• 3. User chooses to manage tags for the file(s).
• 4. User enters new tags.
• 5. User chooses to save changes.

Alternate Flows

Modify tag
• 4. User clicks on existing tag.
• 5. User edits tag.
• 6. User chooses to save changes.

Remove tag(s)
• 4. User clicks on existing tag(s).
• 5. User chooses to remove tag(s).
• 6. User chooses to save changes.

Cancel
• 6. User chooses to cancel all changes.

Exception Flows

Modify more than one tag
• 4. User selects more than one existing tag to edit.
• 5. The first selected tag is the one that is allowed to be edited.

Post-Conditions

• Tags Saved All files that were initially selected will have their tags updated according to the end results of the tag modification sequence (if the changes were not cancelled).

Narrative Version

Once the user has already installed the software, the user can right-click on one or more files to and choose to manage tags via the context menu. This will pop up a dialog which will allow the user to add, edit, and remove tags for the previously selected files. These tag changes can either be committed to be updated in the storage system or all changes can be cancelled.