Overview

The team-specific tasks for the Milestone 3 are the following:

1. Requirements Team:

   1. Produce scenarios suitable for review by the rest of the class, in particular the product manager and executive directory.

   2. Complete and commit weeks 2 and 3 interview transcripts (clerical).

   3. Review and collate 308 milestone 1 submissions (clerical).

2. Prototyping Team:

   1. Produce two prototypes, suitable for review by the rest of the class, in particular the product manager and executive director.

   2. Produce a planning white paper on deployment options and procedures.

3. Infrastructure Team:

   1. Marketing Group: Produce an approximately five-page planning white paper on the nature of product marketing for the Scheduling tool, including product "branding".

   2. Usability Group: Produce an approximately five-page planning white paper on the nature of usability testing for the Scheduling tool, including use of the lab in 14-257.

   3. Maintenance Group: Produce an approximately two-page planning white paper on alternatives for long-term maintenance of the Scheduling tool.

   4. Core Infrastructure Group: Have at least one forum tool operational on the Scheduler VM, suitable for use by the rest of the class.

   5. Management Group: Prepare a presentation of the schedule and possible resource vulnerabilities.

Task 1a -- Produce Requirements Scenarios

Using the scenario methodology discussed in CSC 308 Lecture Notes 1-3, produce UI pictures and accompanying narrative for the core features of the scheduler tool. The target audience for these scenarios is comprised primarily of the outside clients who will have been interviewed by the end of Week 3. If you have any particular ideas about the delivery format for these scenarios, we will discuss them in class during week 3.

Here are a couple examples of what I would call "particular ideas" in this area:

1. Consider having scenarios be targeted at individual clients, including use of individual client names. This might be automated with some for of persona parameterization.

2. Consider a less verbose form of scenario, where narrative delivered on-demand from the user, in pop-up window form and/or audio.

Store the scenarios in requirements/*.html.

Task 1b -- Complete and Commit Weeks 2 and 3 Interview Transcripts.

The interview script handout describes the specific work to do.

Store the transcripts in requirements/interviews/DEPT/*.html

Task 1c -- Review and Collate 308 Milestone 1 Submissions

For 308 Milestone 1, each class member did a simple review of an existing scheduling software product. The 402 task is to collate all of these reviews, where "collate" means:

1. copy the files from the 308 team directories

2. take a first-pass read through all of the reviews

Copy the reviews from the five 308 team librarian directories librarianprojects/work/scheduler/requirements/*-review.html, for librarian = rmckelvi, sdthai, keli, mhenry02, and nalereza. Store the reviews in requirements/PRODUCT-review.html. Use "-a,b,c" root file name suffix if more than one review per product.

Task 2a -- Produce Two Working Prototypes

Tune up the app-based prototype to remove fully non-functioning features. Also, make it "fail soft", in that catches all exceptions, and produces a user-meaningful message before returning to the main UI of the tool.

Build a proof-of-concept web-based prototype.

Move the app-based prototype from the implementation directory to the prototype directory. Store the web-based view code in prototype/scheduler/*_webui packages.

Store the white paper in deploy/prototype/plan.html.

Task 3a -- Marketing Plan

Produce an approximately five-page planning white paper on the nature of product marketing for the Scheduling tool, including product branding and identity. The branding aspects includes project name and logo. Consider if we should outsource this work to GRC, e.g., in the form of a student project.

Store the white paper in requirements/marketing/plan.html.

Task 3b -- Usability Plan

Produce an approximately five-page planning white paper on the nature of usability testing for the Scheduling tool, including use of the lab in 14-257. Address the issues and questions in the meeting minutes from the Kurfess meeting from 28 September, in administration/minutes/usability-28sep11.html.

Store the white paper in testing/usability/plan.html.

Task 3c -- Maintenance Plan

Produce an approximately two-page planning white paper on alternatives for long-term maintenance of the Scheduling tool. Consider these possibilities for how the project will be maintained beyond Spring 2012:

1. picked up by the open-source community (this is where the process research comes in)

2. maintained by campus or department staff

3. maintained by students, in some form of organization

4. unmaintained; most likely, this is not a viable option

Store the white paper in deploy/maintenance/plan.html.

Tasks 3d and 3e -- Operational Forum Tool and Project Scheduling Report

Present to class on Friday.