www.whatsfordinner.com

Bryce RodgersKent Warner

Matt Heckman

Status Report – Nov. 8, 2010

Project Status

• Software (including classifier) design is complete.

• Database design is complete.• Progress has begun on Iteration 2 without 100%

completing Iteration 1.• Iteration 1 was scheduled to be complete Nov. 1.• However the Project is roughly 1 week behind

schedule, primarily due to problems with integrating DB and Server, and data for classifier.

System Design Doc

• Was not contained in our schedule• Completed individual parts, but not whole• Page-Flow-Interaction chart• DB-Server interactions diagram• Drafts & class diagram for Classifier – data

structures, methods, & math

Iteration 1 - 90% Complete

• Interfaces for web server to get info from DB. Status: outlined in Sys. design doc, all interfaces added to .java files for each page. DB setup & populate sample data scripted.

• blank pages up and running. Status: pages up, non-authentic login functionality.

• Primitive Bayesian Classifier. Status: outlined in Sys. design doc, classifying for arbitrary (ID) values

• Javascript to create meals/food items. Status: removed from scope for phase 1, because they were ideal for how we originally wanted users to classify food items but that has changed

• Pending task: Complete integration of Server/DB/Classifier

Iteration 2 - 20% Complete

• Web server generating GUI. Status: mostly implemented on most pages, not implemented on add new data pages.

• Displaying & interpreting information from the DB. Status: not integrated with DB yet.

• Classifier making predictions. Status: need to create domain data/attributes, only classifying arbitrary values.

• User accounts (login). Status: created in DB, partially implemented in pages, but not integrated with DB.

• Javascript for create meal/food page. Status: postponed to Iteration 3 as enhancement.

Plan to catch up• We will tackle these next 3 tasks immediately because they are

past expected completion date:• DB/site integration – already started• (predicting on) Domain data – not started• Complete System Design doc

Plan to stay caught up• In order to get back on schedule, the next few tasks

will be prioritized ASAP for Iteration 2:• Data entry for users on add meal/food pages• Generating list of possible meals for classifier• Create Test Plan• Do another integration at scheduled end of Phase 2

Risk Management• Website Hosting and Development Environment was an identified risk in

the Project Plan, cause for this risk was the lack of a cohesive vision of what is required to host properly.

• Team Distance was also identified as a risk, and has proven to be an issue, on line tools and collaboration do not facilitate discussion, and so numerous points arose long after we thought they were settled.

• Integration schedule was not explicitly there, and would have been helpful to adhere to. Integration schedule was not documented as a risk from the beginning. To date, total integration has not yet been successful.

• Using Javascript was a risk because it was more difficult than the alternative, not necessary, and was planned only because it was expected to make data entry easier for user… since we have decided it will not, it has been marked as an ‘enhancement’ for possible future development (such as in Iteration 3)

Testing

• Classifier: unit-testing is being done manually on randomly-created data displayed at run time. Unit testing complete for creation/init of all LDS, but not for last stage which calculates Bayesian probability.

• Site-testing: (non-authentic) Login functionality works, Registration works, authentic DB-required operations still giving errors.

Questions?