Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Corrected links that should have been relative instead of absolute.
Gliffy Diagram
sizeL
nameBreadcrumbz BucketList - domain analysis
alignleft
version2

GR1 - Task analysis

Our objective for BucketList is to create a simple, easy-to-use resource for categorizing and sharing to-do lists among multiple users.

  • CRUD "buckets," or groups of tasks, that can be shared between users.
  • CRUD tasks and assign them to multiple users.
  • Write notes related to tasks for other people working on the task or in the bucket to see.
  • People who keep track of group projects / tasks shared among groups 
  • People who have a set way of organizing their tasks
  • People who want a simple interface for personal to-do lists and task management

...

Based on our background research and interviews, we created personas for two target BucketList users. Both personas belong to the same user group, and interact with BucketList in the same fundamental way.

Meet Jake...

Jake is a junior in college. He lives a fast paced life serving as editor of his school news- paper newspaper in addition to taking six classes and searching for summer internships. He’s an active user of multiple social networking sites and enjoys applications that allow him to compete with friends. BucketList will fulfill Jake’s organizational needs by allowing him to create task lists for group projects and the newspaper staff, then divvy up the work onto individual group members’ task lists. Additionally it will help him keep track of his own tasks by allowing him to categorize them into homework, job search, etc.

...

  1. Create a bucket
    1. Precondition: User must have an account.
    2. Navigate to “Create Bucket” option“My Buckets” 
    3. Type in bucket name
    4. Optional: add others to bucket
      1. Enter the usernames of other users.
    5. Click “Create”
    6. Hit enter
  2. Create a task
    1. Preconditions: 
      1. The bucket that will contain that task must already have been created.
       
      1.   
      2. Users who will be added to task must be members of that bucket already.
    2. Navigate to “Create New Task”Choose bucket for new task (if the user navigated to the “Create New Task” screen from viewing a particular bucket, that bucket should be the default choice.  However, the user should still have the option to change it.)that bucket's paper
    3. Enter task name in 'New Task' field
    4. Optional: add users to task
      1. Click '+' by "Collaborators"
      2. Type name or email Enter usernames of those users
      3. Hit enter
      4. Click “Create”
    5. Optional: add due-date to task
      1. Click calendar icon beside task name
      2. Select required date in calendar 
  3. 3) Add or Remove Users from a Task or Bucket
    1. Preconditions: 
      1. All users involved must already have accounts.  
      2. Task or bucket must already exist.  
      3. If it’s a task, the users to be added to the task must already be in the tasks’ bucket.  
      4. If we’re trying to remove a person, that person must already have been added at some earlier point.
    2. Select the relevant bucket or task
      1. If you are adding or deleting users from a task, select the task within that bucket.
    3. Select “Add/Delete Users from this Bucket/Task” option
      1. If delete, select the users you want to delete from a list of users in the bucket/task
      2.  If add, enter the username of the user you want to add to the bucket/task.
    4. Click “Add” or “Delete”
    1. If adding users: 
      1. Click '+' by "Collaborators"
      2. Type name or email of those users
      3. Hit enter
    2. If deleting users:
      1. Click 'x' beside user's name

Image Added
 

  • Each user will have exactly one Breadcrumbz Each user (by which we mean the physical person of the user) must be associated with exactly one account, which is in turn associated with a single username and password.  Each username is associated with exactly one accountmust be unique.
  • Every account is associated with 0+ buckets.  In turn, An account can have multiple buckets, and each of these buckets is bucket can be associated with 1+ multiple accounts.  This is because buckets can be shared between users.  We do not distinguish between a bucket’s creator and the other users who are sharing it, but if a bucket were to be associated with zero accounts at any point, it would cease to exist.
  • Every bucket contains a set of 0+ tasks.  Each of these tasks is associated with 0+ accounts, all of which must also be associated with the bucket that contains that task.  (A task is allowed to be “unassigned”---in other words, not associated with any account.)
  • Every task is also associated as well with a number of notes.  Each note is associated with exactly one account – that of the user who wrote it.

...

...