1. Visual Schedule Finder SDS Presentation

2. Members Peter Beckfield Xia (My) Cam Rylan Hawkins Jordan Hoyt Sandra Li Devy Pranowo

3. System Architecture

4. Page & Class

5. Processes

6. Database Accounts User Admin Catalogue myUW Degree Req

7. Development Plan

8. Team Structure Project Manager / System Architect Project Manager / System Architect Rylan Rylan Responsible for maintaining the project's vision and for keeping the work of the group in line with the overall goal. In charge of leading the group by designing the system architecture for the group to work within. Responsible for maintaining the project's vision and for keeping the work of the group in line with the overall goal. In charge of leading the group by designing the system architecture for the group to work within. Team Administration / Customer Contact Team Administration / Customer Contact Xia, Sandra, Devy Xia, Sandra, Devy Responsible for upkeep of the team website, mailing list and other forms of group organization and for keeping team meetings on agenda. In charge of keeping in contact with our customer and scheduling meetings as needed. Responsible for upkeep of the team website, mailing list and other forms of group organization and for keeping team meetings on agenda. In charge of keeping in contact with our customer and scheduling meetings as needed. Database / AJAX Database / AJAX Peter, Xia Peter, Xia Responsible for designing the various aspects of the database and the AJAX that will interface with it. Responsible for designing the various aspects of the database and the AJAX that will interface with it. JavaScript / Integration Jordan, Sandra Responsible for writing JavaScript code that interacts with both the HTML of the site and the Database back-end. In charge of ensuring a smooth integration between the two. HTML / CSS Design Devy, Rylan Responsible for setting up the main skeleton of HTML code for the JavaScript to interact with and for designing CSS code that defines how the site will appear to the user Testing / Quality Assurance Everybody Each group is responsible for doing its own testing and quality control. Since most groups are made up of pairs, each member can perform this task for others with the same role.

9. Project Schedule

10. Risk Assessment

11. Test & Doc

12. Test Plan Unit Unit For each components For each components JSON objects JSON objects DB DB JSUnit JSUnit By DB & AJAX/JSON teams By DB & AJAX/JSON teams System System Integrations of multiple components Integrations of multiple components Collaboration from dev teams Collaboration from dev teams White/black box White/black box Usability Usability Contextual inquiries Contextual inquiries Based mostly use cases & functionalities Based mostly use cases & functionalities Adequacy Adequacy Ground up Ground up Pair-programming Pair-programming User-central  Usability++ (haha… ) User-central  Usability++ (haha… ) Bugzilla Bugzilla

13. Documentation Plan User Doc User Doc Help menus for different user groups Help menus for different user groups Per use case / activity Per use case / activity demo / tourProject Doc demo / tourProject Doc Project Doc Project Doc Internal Internal Follow standards Follow standards Code with good style, use straight forward, good variable names, and method names Code with good style, use straight forward, good variable names, and method names Clear layout/indentation. Clear layout/indentation. Comments on the code to explain complicated or tricky code Comments on the code to explain complicated or tricky code Comments must be up to date Comments must be up to date