My favorites | Sign in
Project Logo
                
Search
for
Updated Dec 03, 2008 by siev...@wells.edu
Labels: Featured, Phase-Requirements
InchStones  
Deadlines, intermediate and final

Links TopDown GlobalStructs Jobs

This (Week 10) (Days 28-30). . . By following Monday (Day 31, Nov. 10) :

  • DONE: We decide whether we can do variable rows or columns.
  • Structures set WED: GETTING THERE. (See ToResolve),
  • DONE MOSTLY: Procedures allocated
  • Algorithms clear enough to disclose most cracks and inconsistencies. WED: Need work (See ToResolve)

Week 11 (Days 31-33) . . . By following Monday (Day 34, Nov. 17) :

  • Algorithms devised and vetted,
  • coding well under way, including Procedure drivers.
  • Main ready with stubs.
  • Many procedures debugged or ready to debug.
Week 12 (Days 34-36) . . . By following Monday (Day 37, Nov. 17) :
  • Coding completed,
  • Procedures debugged separately via drivers.
  • Main runs, with procedures inserted as ready
    1. Main debugged as each procedure inserted.
  • Completed program tested

Week 13 (Day 37, before thanksgiving break only) Happy Thanksgiving!

  • If it's all done Presentation this day??!NOO
  • If not done, remaining bits cleaned up by next Monday. Ha! some routines done!! some hardly started. Little/No progress outside class
Week 14 (Days 38-40. Full week after thanksgiving) "Grace days"
  • If finished, back to classroom.Not finished. Back to classroom anyway
  • Final testing and debugging.
  • Presentation Wednesday. NOOOBut most pieces are close to ready by end of Wednesday.
  • Presentation scheduled for Monday.
Week 15 (last 2 days of classes)
  • Monday, presentation. Wed. Back to the classroom.


Sign in to add a comment
Hosted by Google Code