some goals can be achieved in a single sitting.

for instance “buy some IBM stock over the web”.

some goals take multiple encounters with a system.

for instance “getting an MBA”

Primary Actor

Scope

Level

Stakeholders And Interests

Precondition

Minimal Guarantee

Success Guarantee

Main Success Scenario

A use case is a contract for the behavior of the system under discussion:

• scope
• primary actor
• level
• actor
• stakeholder
• primary actor
• scope
• preconditions
• guarantees
• main success scenario
• extensions

the main success scenario is a case in which nothing goes wrong.

a use case describes a system’s behavior under various conditions as the system responds to a request from one of the stakeholders, called the primary actor.

sentences should be written in a simple action step format.

the actor achieves a result

or

the actor passes information to another actor.

Primary Actor

• initiator of the METANOTES space in the group

Scope

• student segment
• useful for enterprise segments, professional segments

Level

• group goal

Stakeholders And Interests

• initiator of space
  • wants to use the very best collaboration platform
  • wants to limit or at least optimize face to face meetings
  • wants to set the tone for the project
  • wants the group to get it done fast and well
  • wouldn’t mind props for introducing them to METANOTES
• other students in the group
  • wants the group to get it done fast and well
  • wants to limit or at least optimize face to face meetings
  • want to contribute
  • want to feel acknowledged
  • want to feel their input is well blended into the result
  • want to be notified about any changes
  • want to react to the ideas and research of others in the group
• other students in the class
• professors and teaching assistants
  • want their students to collaborate smoothly
  • requires topnotch ethics from students
  • wants the project to be smooth and great
  • maybe wants to be able to contribute insight if asked
• university
  • needs to be seen as technologically forward
  • wants to provide students with great “official” tools”

Precondition

• Students are in a class together.
• Students get a group assignment.
• Students are aware of METANOTES as a solution.

Minimal Guarantee

• METANOTES provides students a shared whiteboard for
  • writing
  • brainstorming
  • research
• METANOTES doesn’t crash or lose information between sessions.
• information accessed by METANOTES can be copied into a word processor (or tinymce) for final editing.
• METANOTES lets users log in easily.
• You can create a space and invite people in easily.

Success Guarantee

• The students invited by the space initiator will immediately grasp what is going on and jump right in.
  • This means maybe sub-assignments are delegated.
  • This means some kind of “accountability system”.
• The students will know what’s going on in the project at all times.
  • This means notifications.
• The students will hand in an incredible paper that they made in METANOTES alone.
• The students will ENJOY the learning, writing, debating and brainstorming process provided by METANOTES.
• The students will learn a lot about the topic, how to conduct such projects in the future, and METANOTES in general.

Main Success Scenario

• Because they used METANOTES, the students got an A.
• They credit their collaboration on METANOTES for their success.
• The initiating student has now turned each of the other students into initiating students for future projects – “users for life”
• The initiating student knew about METANOTES and knew it was the right tool for the job.
  • Sort of implies a lot of specs
• The initiating student had no problem learning METANOTES and could easily teach it to other students.
• The initiating student found it very easy to create a space for the paper.
• The initiating student found it very easy and cool to invite the others to the space.
• The other students really felt like contributing on METANOTES immediately.
• The collaboration itself goes smoothly.