CSC 308 Milestones 3 and 4

• by 11:59PM Fri 30 Jan (fourth week): inspection test roster

• during Mon - Fri Week 5 labs: oral presentations

• by 11:59PM Fri 6 February (fifth week):
  • updated requirements
  • first draft of model
  • week 5 inspection test

Activities

Your work for Milestones 3 and 4 involves continuation of the work begun in Milestone 2, initial work on modeling, inspection testing, and administrative activities. The specific tasks are as follows:

1. Complete Section 1 of the requirements specification document, addressing all comments in your Milestone 1 evaluation

2. Continue to refine and add new functional requirements scenarios to Section 2, based in particular on customer feedback.

3. Present your requirements work in a formal walkthrough, to be presented during fifth week lab meetings on Monday through Friday. Some details on the presentations are in Lecture Notes Week 4. The presentation schedule is as follows:

   Time	Day	Team
   12:10 - 12:34	Mon 2 Feb	DJ Cars
   12:36 - 1:00	Mon 2 Feb	TokenCSC
   12:10 - 12:34	Wed 4 Feb	Team 0
   12:36 - 1:00	Wed 4 Feb	Fire Breathing Rubber Duckies
   12:10 - 12:34	Fri 6 Feb	Node
   12:36 - 1:00	Fri 6 Feb	Team #1

4. Begin work on the formal Java model of your system, in the form of a rough first draft of model modules, objects, and operations. In Java, these are represented respectively as packages, classes, and methods. For this milestone, the model must:

   1. be organized into packages

   2. compile with the javac compiler

   3. have minimal javadoc comments -- one simple comment per class describing the purpose of the class

   The model package directories and .java files are checked into the project specification directory.

5. Assign inspection test duties for Weeks 5 - 10 ¹. Then for week 5, complete the first round of requirements inspection testing, performed by the team member who is assigned the inspection duties for that week.
   
   Record the duties in the file administration/inspection-roster.html, in a table of the following form:
   
   

   Week No.	Team Member	Initials
   5	member a
   6	member b
   7	member c
   8	member d
   9	member e
   10	member f	1

   
   
   There are additional instructions for filling in this table in the SOP on requirements testing.

6. Refine the individual work assignments for each team member's contributions to Section 2 of the requirements specification. Record these assignments in the work-breakdown.html file in the project administration directory.

We will discuss details of tasks 2, 3, and 4 in lecture during the fourth and fifth weeks.

• By 11:59PM Wed of fourth week: Inspection test roster checked into project repository, in administration/inspection-roster.html.

• Monday through Friday during fifth week labs: requirements walkthrough

• By 11:59PM Friday of fifth week:
  • Updated and new requirements, checked into the project repository, in the requirements directory

  • For the first draft of the model:
    • A java package directory structure defined in the project specification directory.
    • At least six Java classes for each team member; put the .java model files into the appropriate package sub-directoies of the specification directory. NOTE: The model files must compile error free with javac.

    • Generated javadoc in the specification/javadoc subdirectory.

    • Updated work breakdown file. Add new requirements files for each team member in the Requirements Files column. Add model .java files in the Specification Files column. Note that if a teqm member is individually responsible for all the java files in a particular package, then the you can list the package name in the work-breakdown file instead of all the individual .java files in that package.

  Reading

  • Requirements document standards
  • Conventions for a standardized GUI
  • SOP Volume 2: Requirements Testing
  • Java as an Abstract Modeling Language
  • Lecture Notes weeks 3 , 4 , and 5
  
  
  
  

  ---

  index | lectures | handouts | examples | textbook | doc | grades

  ---

  Footnotes:

  ¹ five-person teams perform inspection testing weeks 5-9; six-person teams weeks 5-10; seven-person teams weeks 5-10, with two separate inspections (of the same documents) on week 10