Marks

Marks

- - - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript

1. Marks • Marks and stats are posted on CNET • Please check • Assignment 1 • Average is 76% • Solution code is posted • Not worth full marks, but has the algorithm • Midterm • Average is 69% • Solution with marking scheme is posted • midterm06.pdf Evalulation Feedback

2. A1 Actual Time Min = 114 min Avg = 839 min Max = 2760 min (24x, 3x) Evalulation Feedback

3. A1 Estimates to Actuals Min = 24% Avg = 136% Max = 425% (18x, 3x) Evalulation Feedback

4. My Solution to A1 • Posted on web site • slider.cpp.html • Took me 140 minutes • But I solved it once 13 years ago • My run-time: • For 5x5 boards using a 3.1 GHz Desktop • 17 moves: 2.5s • 25 moves: 32 minutes • My memory utilization: • < 4KB, independent of number of moves in solution Evalulation Feedback

5. A1 Observations • Elegance pays, C is fast: keep it simple • Heuristics? • Specification is trivial – inputs and outputs • Design: don’t do elaborate documentation at first • Sketch it on a napkin: most important for YOU to have a clear idea • Document it properly as nearing completion to avoid rework. • Code: • Having a clear design in your head saved LOTS of time Evalulation Feedback

6. A2 • See handout on web site • Work in teams of up to 3 • Do an automated regression testing environment for A1 • Use my code if you want • Get your team together and do up a preliminary release plan • Follow format of Deterministic Release Plan in Appendix A • Decide on dates • Estimate feature sizings and w’s • Due next week in lecture • Hand in at the last lecture: • Release plan updated with actuals • Your time logs • System design and description • Source code • Experience report (< 1 page). Evalulation Feedback