Revision History
Name Date Reason For Changes Version
Ben Dunton, Jason 2/2/10 Initial Version 1.0
Gum, Mike Phillips
Jason Gum 2/4/10 Added details to OT-01 and created OT-02 use cases. 1.1
Jason Gum 2/5/10 Editing existing use case details and added 1.2
remaining use case details
Use Cases
Actors
User – The person using the tool.
Moderator – A user overseeing an instance of a tool.
Administrator – A person overseeing the use of FACETs.
Use Case Descriptions
1. Number of Child Nodes – An administrator sets the maximum number of child nodes per node
in the Objective Tree.
2. Maximum Nodes Error Message – A user adds a child node to a node with the maximum
number of children.
3. Hide Children – A user hides the children of a node in the Objective Tree.
4. Show Children – A user shows the children of a node in the Objective Tree.
5. Hide Node Authors – A user hides node authors.
6. Show Node Authors – A user shows node authors.
7. Delete Node – A moderator deletes a node and its children.
8. Edit Node – A user edits a node.
Detailed Use Cases
Use Case #1
Name: Number of Child Nodes
Requirement: OT-01
Actors: Administrator
Description: An administrator sets the maximum number of child nodes per node in the Objective Tree.
Preconditions: None
Post conditions: The number of nodes for each level has a maximum value specified by the
administrator.
Primary scenario of events:
1. The administrator opens up the configuration file with a text editor.
2. The administrator changes the number of child nodes per node.
3. The administrator saves the changes to the configuration file.
4. The administrator restarts the server.
Secondary (alternative and exceptional scenarios):
1. No Change to Configuration File – On step 2, the administrator decides not to change the
maximum number of nodes and the use case ends.
Use Case #2
Name: Maximum Nodes Error Message
Requirement: OT-02
Actors: User
Description: The user adds a child node to a node that has the maximum number of nodes for that level.
Preconditions: There is a node with the maximum number of child nodes. There is a node that is not yet
a child of the first node.
Post conditions: There is no change to the structure of the tree.
Primary scenario of events:
1. The user drags a node onto a node with the maximum number of children.
2. The system displays a popup box stating, “Cannot add a child to a node with maximum number
of children.”
3. The user clicks “OK”.
Secondary (alternative and exceptional scenarios):
No secondary scenarios exist for this case.
Use Case #3
Name: Hide children
Requirement: OT-03
Actors: User
Description: A user hides the children of a node in the Objective Tree.
Preconditions: There is node that has children and its children are not hidden.
Post conditions: The children of a node are hidden.
Primary scenario of events:
1. The user clicks the minus sign on a node that has children.
2. The system hides all of that node's children.
3. The minus sign is turned into a plus sign.
Secondary (alternative and exceptional scenarios):
No secondary scenarios exist for this case.
Use Case #4
Name: Show children
Requirement: OT-03
Actors: User
Description: A user shows the children of a node in the Objective Tree.
Preconditions: There is node that has children and its children are hidden.
Post conditions: The children of a node are shown.
Primary scenario of events:
1. The user clicks the plus sign on the collapsed node.
2. The system shows the children for that node.
3. The plus sign becomes a minus sign.
Secondary (alternative and exceptional scenarios):
No secondary scenarios exist for this case.
Use Case #5
Name: Hide Node Authors
Requirement: OT-04
Actors: User
Description: A user hides node authors in the Objective Tree.
Preconditions: Node author names are shown.
Post conditions: Node author names are hidden.
Primary scenario of events:
1. The moderator activates the "toggle node metadata" option.
2. The system hides the authors of all nodes.
Secondary (alternative and exceptional scenarios):
No secondary scenarios exist for this case.
Use Case #6
Name: Show Node Authors
Requirement: OT-04
Actors: User
Description: A user shows node authors in the Objective Tree.
Preconditions: Node author names are hidden.
Post conditions: Node author names are shown.
Primary scenario of events:
1. The moderator activates the "toggle node metadata" option.
2. For all nodes, the system shows the node’s author by the node.
Secondary (alternative and exceptional scenarios):
Use Case #7
Name: Delete Node
Requirement: OT-07
Actors: Moderator
Description: The moderator deletes a node and its children.
Preconditions: There is at least one node in the Objective Tree.
Post conditions: A node and its children have been removed from the objective tree.
Primary scenario of events:
1. The moderator selects a node.
2. The moderator chooses to delete the selected node.
3. The moderator is asked to confirm deleting the selected node.
4. The moderator confirms deleting the selected node.
5. The selected node, and all of its child nodes, is removed from the Objective Tree.
Secondary (alternative and exceptional scenarios):
1. Confirm Not Selected – On step 4, the moderator does not confirm, and the use case ends with
no nodes removed.
Use Case #8
Name: Edit a Node
Requirement: OT-08
Actors: User
Description: A user edits a node.
Preconditions: There is at least one node in the Objective Tree.
Post conditions: The content of a node has been changed.
Primary scenario of events:
1. The user selects a node.
2. The user opens the node for editing.
3. The user enters new content for the node.
4. The user confirms the changes to the node.
5. Changes to the node are saved.
Secondary (alternative and exceptional scenarios):
No secondary scenarios exist for this case.