CSC 509 Milestone 1, Addendum
Specification Review and Group Formation

1. When prioritizing the parts of the project that you will work on in 509, use the following levels of completion:
   • LEVEL 0: fully design and fully implement
   • LEVEL 1: fully design but no implementation
   • LEVEL 2: provide design hooks
   Real numbers are can be used. For example, level 0.5 means design and implement 50%.

   Provide a completion level for at least each numbered (sub...)section of the requirements. If necessary, you can prioritize individual paragraphs within a (sub...)section. See the template work breakdown file in

   kdat.csc.calpoly.edu/~gfisher/classes/509/admin/work-breakdown-template.html
   

2. Begin work on SCOs, per the SCO file template in

   kdat.csc.calpoly.edu/~gfisher/classes/509/admin/scos-template.html
   

3. Attend project meeting with Fisher for initial customer interview, per the schedule worked out in Wednesday class. Here is the current (preliminary) 509 group organization:
   • Infrastructure (librarian: Fisher)
     • Process Nav: Fisher
     • Artifact Nav: Klo
     • Artifact Repository: Metzger
   • Main Line (librarian: Sparling)
     • Requirements: Cram, Sosinski
     • Prototyping: Ames, Lanaghan
     • Design: Magdub, ?
     • Implementation: Sparling, Wasito

   • Pervasive (librarian: Bruno)
     • Testing: Bruno, Chen
     • Config: Fricks, Gilkeson, Macias
     • Admin: Ashford, Huang, Maddy