Communication Lab 4
Draft of Functional Specifications Document

0. Before class, arrange tables in CL³ for groups.


1. (25 minutes) Groups work on milestone documents.
   
   • Instructors circulate and work with each group.
   • Communication instructors might solicit an interim draft by e-mail for further critique.
   • Final draft will be submitted under A6: Final Milestone Document. Due Sunday, March 6^th, 11:59PM.


2. (5 minutes) Preparation for presentation next week.
   
   • Communication profs will prepare groups for next week's presentations
   • The "Preliminary Presentations" will occur in Game Lab (Mon/Wed)
   • "Prelimary Presentation" Guidelines
     
     This presenation bears a certain resemblance to the "show and tell" sessions many of us encountered in kindergarten: you get to bring in a new toy, "show" it to everyone and "tell" what it does.
     
     Even though this is an informal presentation, you have a limited amount of time (10 minutes, including the Q and A) to show your toy (game) and tell us certain things about it. A few of the things you'll want to show and tell us about are:
     
     1. Your core vision
     2. Any innovations
     3. Any challenges you've encountered


3. (5 minutes) Functional Specification document:
   
   • Instructor explains FS document
     
     • programmers present clear view of program
     • high-level (pacakge, class, interface, maybe method headers)
     • data flow/structure/dependencies
     • use box diagrams (UML, ideally)


4. (15 minutes) Group works on FS
   
   • Look up CIS 300 Lecture 5 (Documents and Development)
   • See Function Specifications document


5. Submit draft of Functional Specifications Document on CMS.
   
   • Tuesday groups: due by Monday, March 1^st.
   • Friday groups: due by Friday, March 4^th.

Final version TBA (likely Sunday, March 13^th).