190 likes | 359 Vues
The Classmate Sharable Social Scheduler, presented by Team 9, addresses the chaotic nature of schedule management faced by college students. By integrating a fully socialized scheduling system, users can create, share, and edit their calendars easily, fostering better collaboration among classmates. The platform offers significant marketability to both students and advertisers, providing personalized, relevant ads based on user data. Our solution emphasizes usability, security, and immediate updates while overcoming challenges in technology and user engagement.
E N D
The Classmate Sharable Social Scheduler System Presented by Team 9
Table of Contents • Problem • Schedule Problem • Online Calendar ?! • Scheduler vs. Diary • Sharing Schedules • Cloud Media • A “Social” Network • System Description • Marketability • Use-case Analysis • Requirements • Challenges • Justifications
Schedule Problem • Schedule management is messy! • KAIST calendar • Moodle • Noah • KLMS • Lab course page • So on... • Solution: Centralize into a calendar!
Online Calendar ?! Yes, calendar is pretty good. … but…
Scheduler vs. Diary • However, it is too personalized! • There is no advantage to manage my own schedule! VS …?
Sharing Schedules • Solution: Share my calendar with classmates! … but how …?
Cloud Media • Important issues • Freely create & edit details • Notify changes quickly • Solution: Calendar w/ editing and syndicating a schedule!
System Description • Fully socialized schedule management • Fully personalized schedule confirmation • To form social networks!
Marketability • Two major stakeholders benefits: • Users: A useful schedule system. *Main target: College students • Ad providers: Easily provide relevant ads based on the users • Easy to print a relevant ad using course list! • by courses, by location, by degree…
Quality Attributes • Usability • Within 3 clicks! • Immediate update to any changes • Security • Portability • Reliability
Challenges • Technical challenges: lack of knowledge, time • Platform knowledge:facebook app, RSS • Numerous Subcomponents • Test period: One semester → REUSE AS MUCH AS POSSIBLE • User-related challenges • “Social” – huge user pool required! → Easy use, Marketing • Vandalism expected → Minimal Authorization
Justification • Mostly, WE WOULD BE THE VERY USER OF THIS SYSTEM • General SW engineering experience • Learn many things! • DB, Web service (e.g. Wiki, RSS), platforms (e.g. facebook Apps)… and more things! • We aim to launch this project for actual payback 1) Launch the service 2) Insert ads 3) ??? 4) PROFIT!
Thank you! Q & A Session