1 / 32

CentralCampus

CentralCampus . May 13-26 Client: Google, Muthu Muthusrinivasan Advisor: Prof. Manimaran Govindarasu W . Regen Van Walbeek & Paul Wilson. Group: May1326 Project: CentralCampus Client: Google. Project History. Second year project Originally a 3 person group. Group: May1326

luka
Download Presentation

CentralCampus

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. CentralCampus May 13-26 Client: Google, Muthu Muthusrinivasan Advisor: Prof. Manimaran Govindarasu W. Regen Van Walbeek & Paul Wilson

  2. Group: May1326 Project: CentralCampus Client: Google Project History Second year project Originally a 3 person group

  3. Group: May1326 Project: CentralCampus Client: Google Problem Statement Information regarding university life is widely dispersed There is no good way for students to pass on knowledge as a whole

  4. Group: May1326 Project: CentralCampus Client: Google Objective CentralCampus aims to provide students with a website where they can exchange information with other students and professors regarding campus life

  5. Design Concept Sketch

  6. Functional Requirements The system shall have a Crawler that obtains professor/class information Professor/class rating system Student sign in with iastate.edu e-mail Customizable profile for each student who signs up Administration panel Mobile component (canceled)

  7. Non-Functional Requirements The system shall Return all requested information within 2 seconds Support upwards of 30,000 concurrent users Be modular in construction Be secure, and respect user privacy Run on Google Cloud

  8. Group: May1326 Project: CentralCampus Client: Google ScopeThe previous team Crawler – Professors and Courses Initial MS SQL Database and Schema Data Access Object Layer to access database Web UI Mockup Polled the student body

  9. Group: May1326 Project: CentralCampus Client: Google ScopeOur team Google App Engine port for crawler and database Functioning website accessible to students Professor and Course feedback system Administration functionality ISU News

  10. Group: May1326 Project: CentralCampus Client: Google Design Process Iterate on previous team’s design High level architecture was already there for us Fluid Requirements App Engine constraints Data storage Time Limits UI Design Use feedback from students, advisor, and client

  11. Group: May1326 Project: CentralCampus Client: Google Technologies Google Cloud Great scalability Google Datastore OO storage solution on Google Cloud Google RSS Reader Used to display news Java Used on the backend JSP and HTML Used on the frontend

  12. System Block Diagram

  13. Database Description

  14. Group: May1326 Project: CentralCampus Client: Google Web Scraper Java Scraper started by previous team Managed by admin Challenges Porting to Google Cloud – New tools Maintenance by user Time limits and partitioning into 10 minute department tasks

  15. Scraper Solution

  16. Group: May1326 Project: CentralCampus Client: Google Database Ported from MSSQL database to Google Datastore Easy to scale JDOs allow us to structure in an OO manner Challenges Dealing with App Engine’s quotas – Read write ops Testing scalability

  17. Database Schema

  18. Group: May1326 Project: CentralCampus Client: Google Search Search for professors and courses Used a linear search Challenges Efficiency Load professor and coursedata on cache Restructure JDOs Reverse index – Remove partial string search Matching user queries Use linear search

  19. Group: May1326 Project: CentralCampus Client: Google Web UI Iterated on previous team's implementation Used CSS for styling JSP and HTML for the bulk of the site JavaScript to streamline actions Challenges Making an easy to use site Quickly adapted the site to user feedback Code management Took a month or two to go over previous teams code

  20. Serving Content

  21. UI

  22. UI

  23. Group: May1326 Project: CentralCampus Client: Google Testing Unit Testing JUnit test suite Search retrieval Crawler results Integration Testing Done manually as modules implemented

  24. Group: May1326 Project: CentralCampus Client: Google Testing User Testing Collect feedback from advisor and client Opened beta to select group of students on April 1 2 weeks of user feedback

  25. Group: May1326 Project: CentralCampus Client: Google User Testing We found: The class rating system was extremely well received The UI needed to be clearer Added sidebar with instructions Added search bar instructions Search could at times take too long

  26. Group: May1326 Project: CentralCampus Client: Google Lessons Learned Be flexible – Requirements Deadlines are important Integrate user testing early

  27. Group: May1326 Project: CentralCampus Client: Google Future Work Professors Assignments Gradebooks Students Private Messaging and Chat Clubs Calendar and Meetings Improved Search

  28. Questions

  29. Group: May1326 Project: CentralCampus Client: Google Challenges Scope of the project Porting existing code Usability Learning new APIs

  30. Completed Tasks Migration to Google Cloud Scraper Database Student Authentication and Authorization News Feed Professor and Course Pages Professor and Course Feedback System Searching tool Administrative tools

  31. Schedule Feb 14 Login February 21 RSS News Feed Rework Styling Search Prototype February 28 Search final March 7 Calendar backend work

  32. Schedule March 14 Chat/Calendar March 21 Administration April 1 Release to Students April 14 Feedback Deadline

More Related