Download
visual schedule finder n.
Skip this Video
Loading SlideShow in 5 Seconds..
Visual Schedule Finder PowerPoint Presentation
Download Presentation
Visual Schedule Finder

Visual Schedule Finder

104 Views Download Presentation
Download Presentation

Visual Schedule Finder

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

  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. Accounts User Admin Catalogue myUW Degree Req Database

  7. Development Plan

  8. Project Manager / System Architect 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. Team Administration / Customer Contact 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. Database / AJAX Peter, Xia 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. Team Structure

  9. Project Schedule

  10. Risk Assessment

  11. Test & Doc

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

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