1 / 13

AMP: Automatic Meeting Planner Final presentation

AMP: Automatic Meeting Planner Final presentation. Team JVA Alison Hilaire - Jae Il Joo Dohan Kim – Virginie Vasselin. Contents. Project review Reflection on feedback System requirements Demonstration Achievements Remaining challenges Team management Conclusion. Project statement.

alamea
Download Presentation

AMP: Automatic Meeting Planner Final presentation

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. AMP: Automatic Meeting PlannerFinal presentation Team JVA Alison Hilaire - Jae Il Joo Dohan Kim – VirginieVasselin Spring 2011 CS408 Computer Science Project

  2. Contents • Project review • Reflection on feedback • System requirements • Demonstration • Achievements • Remaining challenges • Team management • Conclusion Spring 2011 CS408 Computer Science Project

  3. Project statement • To find a meeting time for a large group is: • time-consuming • confusing • irritating • AMP is community website to organize meeting • Group management • User calendar management • Automatic meeting time • Suggestion of meeting location Gain of time, best solution to satisfy more people • Focus on study groups but group and meeting time functions are also useful for students’ clubs, sports activities… Spring 2011 CS408 Computer Science Project

  4. Feedback • Arbitrary time preference to score time candidates • Better score for meeting starting between 7pm and 12pm • User may not agree • We implemented letting leader chose preferred time and score accordingly • Other assumptions to find meeting time and location: • Until 30 after a schedule, user location is schedule’s location, if it exists • Otherwise, user is assumed to be at usual location (filled out in user profile) • If no usual location, user location is ignored • No suggested meeting starting between 3am and 8am Spring 2011 CS408 Computer Science Project

  5. System requirements Spring 2011 CS408 Computer Science Project

  6. System requirements (2) Not implemented Spring 2011 CS408 Computer Science Project

  7. System requirements (3) Navigation bar to main modules User info management on the sidebar Spring 2011 CS408 Computer Science Project

  8. System demonstration We will now demonstrate our final system Spring 2011 CS408 Computer Science Project

  9. Achievements • Successful implementation of algorithms to find meeting time and location • Deployment of an Apache web server to serve Django and static files • Dealing with recurring events in database • Using reusable components for schedule and board Spring 2011 CS408 Computer Science Project

  10. Remaining technical challenges • Integration of external system: • Import calendar from Google Calendar, OTL • Portal authentication system is also possible: • Django provides authentication backends • Register system to IT team • Reminder involves system services • Update timetable remotely Spring 2011 CS408 Computer Science Project

  11. Team management • Schedule Conceptualization Design Implementation Requirements analysis Milestone (document or presentations) Process Spring 2011 CS408 Computer Science Project

  12. Team management (2) • Documentation: every member • Design: every member • Location and time algorithm by Dohan Kim • Implementation: Spring 2011 CS408 Computer Science Project

  13. Lessons learned • Experience in web development • HTML, CSS • Using MVC framework • Server configuration • Importance of risk and project management • Unexpected challenges (recurring events) Spring 2011 CS408 Computer Science Project

More Related