CSC 308 Milestone 2

Activities and Tasks

This milestone is a first rough draft of Section 2 of the requirements. The specific tasks are the following:

1. Produce an initial rough draft table of contents for Section 2, along the lines of the Milestone 2 Calendar Tool example. This needs to be worked on by the team as a whole.

2. Produce a rough draft top-level user interface(s) for your tool, with command menubar/toolbar(s) and initial window(s). This also is done by the team as a whole.

3. Once a draft table of contents is done, each team member does one or more rough-draft scenarios, that show major aspects of system operation. Each scenario must have at least one interface picture, and some accompanying narrative. For Milestone 2 only, the interface pictures can be on paper, with the text part of the document in html files. If pictures are on paper, they must be clearly labeled with a figure number that is referred to in the html text.

4. Update administration/work-breakdown.html with the work assignments for Section 2 of the requirements. Specifically, list the .html file assigned to each team member. If two or more team members work on the same file, indicate the percentage of work performed by each member.

Discussion

Section 2 of the document defines functional requirements in a user-oriented form. The requirements are described in scenarios of typical use, that show how the system will appear to end users when it is ultimately operational. The scenarios show snapshots of users screens, with accompanying explanatory text. For Milestone 2, you will produce an initial very rough draft of these scenarios and they will be refined throughout the quarter. When your work is finished at the end of the quarter, the scenarios will present a complete definition of all functional requirements for the proposed system.

During lecture in the second and third weeks of class, we will go over the content of the Milestone 2 example. We will also discuss details of the structure of the electronic version of the requirements specification document. In lecture and lab of the second and third weeks, we will review the organization and structure of the project directory where the requirements specification document resides.

For example viewing purposes during class, you may choose from the following alternatives:

• view the HTML version of the example on an in-class computer (lab machine or your laptop)
• view the pdf version of the example on an in-class computer
• print yourself a paper copy of the example, from ~gfisher/classes/308/examples/m2-print.pdf

Summary of Deliverables

• Draft table of contents and Section 2.1 of the requirements specification document.
• Drafts of sections 2.2 through 2.x of the requirements specification document, appropriately project-specific.
• For each team member, at least one draft scenario section, with at least three distinct user interface pictures in total. All three pictures can be in one scenario, or in two or three different scenarios. The important point is that each team member must produce at least three UI pictures, for a total of 18 pictures per team. Examples of "distinct" UI pictures are:
  • a menubar or tool bar
  • a menu that drops down from a menu bar or a tool pallete that opens from a toolbar
  • any particular UI dialog or output display
  If a dialog has a number of options that substantially changes its displayed content, then two different pictures of that dialog with different option settings are considered distinct.
• Updated work breakdown file.
• Checked-in meeting minutes.

Reading

• Milestone 2 example
• Requirements specification document outline (again)
• Requirements document standards
• Conventions for a standardized GUI
• Lecture Notes week 3