Brought to you by: Jason Corso, Anya Kanevsky, Jeremy Mullendore, Lewis Raszewski.
Use Cases
Use case list (click each for elaboration)
Use cases for the Code-Walkthrough
Here is the activity for Use Case 9 to better explain the domain level-progress meeting.
UC1: User Sign In
Actor: Team Member
Trigger: External Trigger - Program Launches
Procedure:
1. A User-Validation dialog pops up to perform any user-authentication.
2. A message is passed into the system alerting every other user that this developer has signed on.
3. User enters normal work-mode in window.
UC2: User Sign Off
Actors: Team Member
Trigger: In Normal-Op mode, select Sign Off
Procedure:
1. User selects sign-off button
2. System alerts the user with a dialog if there are any impending tasks the user must complete (file transfers, etc).
3. System logs the user's sign-off
4. User has signed off
UC3: Check Calender
Actor: Developer, Manager, Consultant
Trigger: Calender window is viewed
Procedure:
1. User A selects the calendar window to be shown.
2. A scrolls the calendar to the day in question.
3. If the time is free for the user to use, the user enters their task in the calendar.
4. If there is a current meeting, the user joins the meeting.
Variations:
3.1 If there is no time free for the user and their task is important, the user might initiate contact with the person who has already scheduled a task at the current time.
UC4: Normal Operation
Actor: Team Member
Trigger: No explicit trigger.
Procedure:
1. User is logged into the system, but using other external systems at the current moment
UC5: Communicate with a Co-Worker
Actors: Developer A and B
Trigger: A message sent from A to B
Procedure:
1. A sends an initial message to B alerting B that he needs help.
2. B either responds that she is free.
3. If B is free, they both enter the white-board mode
Variations:
2.1 B responds that she is busy upon which B and A check calendar and schedule a meeting.
2.1.1 B responds that she is busy but can easily post a file onto the common space for A to refer to.
3.1 White-board mode is not enough for their needs, and they enter the meeting space and being an impromptu code-walkthrough session.
3.1.1 The meeting space is currently occupied by other team-members. If so, they decide to set a meeting in the calendar at a later date.
3.2 B must send A a file. She drags it to the common-space where A retrieves it from.
UC6: Set a meeting
Actors: Manager A or Developer A
Trigger: In Calendar mode, select "Set Meeting"
Procedure:
1. A dialog pops up which allows the meeting attibutes to be set. These include, date, time, type of meeting (code-walkthrough, status, brainstorm, etc), players involved, leader of meeting.
2. The meeting is added to the calendar.
3. Each team member receives a private "System Message" indicating that a meeting has been scheduled and he/she should make note of it. (Note that since the calendar is common to all team members, the actual date/time has already been set in the calendar.
4. Meeting is set.
UC7: Distribute a memo or file
Actors: Manager A or Deverloper A or Consultant A
Trigger: In Normal-Op mode, select distribute object
Procedure:
1. A dialog pops up which allows the user to select the file (memo, source code, image) which is to
be distributed.
2. The system copies this file to the common space.
3. Each team member receives a private "System Message" indicating that the file distribution has been requested, and that the file is waiting to be picked up in the common space.
4. Each team member retrieves the file.
5. Once all team members have retrieves the file, the initiator gets a message from the system indicating such and that the file should be removed if need by from the commonspace.
UC8: Meeting (Domain level use-case)
Actors: Developers, Manager, temporary role of leader
Trigger: Meeting scheduled on calendar
Procedure:
1. Leader (usually person who called meeting) gives intro on
goals of meeting and its agenda
2. Leader follows the agenda of the meeting (which is
available to all participants)
3. Participants comment/contribute/brainstorm using the
whiteboard as necessary
4. When leader is finished with agenda, conclude meeting
Variations:
2.1 The meeting may not be a formal one, & therefore not have a preset agenda -
just a purpose
UC9: Progress Meeting (Domain level use-case)
Actors: Developers, Manager, temporary roles of speaker and leader
Trigger: Meeting scheduled on calendar
Procedure:
1. Leader (usually manager) selects speaker.
2. Speaker reports current status and progress using
whiteboard if necessary.
3. Speaker lists any blockers
4. Developers/manager offer ideas/suggestions
5. Leader selects next speaker
6. Repeat steps 2 - 5 untill all group memebers (including
leader) have reported.
7. Leader closes meeting.
Variations:
3.1 Speaker doesn't have any current blockers
4.1 A meeting is scheduled between speaker & another group
member(s) to discuss ideas/suggestions regarding speaker's report.
5.1 Leader may have decided on a time limit for each speaker,
in which case he will interrupt at some point to select next speaker.
Code-Walkthrough Use Cases
UC-CW1: Present a code walkthrough
Actors: presenter, viewer(s)
Trigger: Presenter activates the code walkthrough module and waits for
his audience to join
Procedure:
1. The presenter is shown a file selection dialogue, from which he
selects the file for his presentation
2. The codewalker display appears, showing the source file in the code
view window
3. The presenter selects a line of code, and makes comments on it
using the chat window. Each comment is prefaced by the presenter's
name, and the number of the currently selected source line.
4. Step 3 is repeated until the walkthrough is completed
5. The presenter exits the codewalker interface by pressing the "End
Session" button.
Variations:
In place of any iteration of step 3, insert any of use cases CW2-CW6,CW9-CW11
UC-CW2: Write a visual cue onto the code
Actors: presenter
Procedure:
1. Using the pointing device, the presenter "draws" the pen strokes he
wishes to appear
2. The strokes appear on the overlay panel atop the code
Variations:
Optionally, the presenter may select a color for drawing by pressing
the "overlay color" button
If the user finds he has made a mistake, he may use the "erase mode"
or "clear overlay" buttons to erase part or all of the display
UC-CW3: Add a note to the source
Actors: Presenter
Procedure:
1. The presenter presses the "add note" button
2. The presenter clicks at a position in the code view window
3. The "Edit note" dialogue appears, allowing the presenter to type in
a textual note
4. The presenter presses the "OK" button
5. A Note symbol appears in the code view window
UC-CW4: Answer a question from the audience
Actors: Presenter, viewer
Trigger: A user has posed a question (see case CW) which the presenter
wishes to answer
Procedure:
1. The presenter selects the question from the question display
2. The relevant line of source code is highlighted
3. The presenter presses the "Answer" button
4. The question is copied to the chat window
5. The question disappears from the question display
6. The presenter composes a response in the same method as giving a
comment on a line of source.
Variations:
2b. The user may change his mind, and end this case here, or he may
select several questions in rapid succession, viewing the line
highlighted for each. Only the question selected when the "Answer"
button is pressed is considered "answered"
UC-CW5: Change the current file
Actors: Presenter
Procedure:
1. The presenter presses the "change file" button
2. A file selection dialogue appears
3. The presenter selects the new file
4. The new file appears in the code view window. The overlay is
cleared, and the current line is reset to 1.
Variations:
2b. The user may cancel the operation instead of selecting a new file.
UC-CW6: Allow another user to take over the presentation
Actors: (old) presenter, viewer (presenter-to-be)
Procedure:
1. The presenter selects a user from the list to take over as presenter
2. The presenter presses the "Yield floor" button
3. The selected user becomes the new presenter
UC-CW7: Watch a code walkthrough
Trigger: A code walkthrough is in progress. THe user wants to join
Actors involved: Presenter, viewers
Procedure:
1. The user activates the code walkthrough module, becoming a viewer
2. The user watches the code view display and chat window as the code
is explained by the presenter
Variations:
During step 2, the user may engage in any of CW8-CW11
UC-CW8: Ask a question about the current walkthrough
Actors: viewer, presenter
Procedure:
1. The viewer selects a line of code in the code view
2. The viewer presses the "question" button
3. A text dialog appears, wherein the user types his question
4. The question appears in the question display
5. The user waits for his question to be answered
UC-CW9: Get user information
Actors: one or more users
Trigger: One user wishes to know public information (Name, location,
etc) about another user
Procedure:
1. The user selects another user from the list of users
2. The user presses the "User Info" button
3. A text window appears showing the information available on the
requested user
UC-CW10: Conduct a private chat with another user
Actors: At least two users
Trigger: a user wishes to speak with another user during the meeting
outside of the public channel.
Procedure:
1. The initiating user selects another user's name from the user list.
2. The user presses "Private chat"
3. A dialogue appears wherein text can be entered and received between
the users
4. When the user tires of the chat, he closes the dialogue.
UC-CW11: View a source note
Actors: any user in the walkthrough
Procedure:
1. The user presses the "view note" button
2. The user clicks the note symbol corresponding to the desired note
3. A text window appears with the note's text
Variations:
3: If the user is the writer of the note, the window which appears
allows him to edit the text of the note, or delete it.