         |
|---|
| Project Name | TriPlanner |
| Project Type | Database Web Application |
| Languages | JSP, HTML, Java-Script, CSS, Java |
| Modules, APIs | MySQL, Assembla, Prettyfaces, Facebook API, Google Map API |
| IDEs | Netbeans, MySQL Workbench, Dreamweaver |
| Team & Role | Steve Park : Sever setup, JSP developing Brook Zhou: JSP developing, Database design Sunny Manaktala: UI, Documentation |
| Dev. Period | 3 months |
| Description | user: the main target of the app, they can do anything with their own accounts create, share, and view trips of friends except edit other user data. Users can login with Facebook accounts through oAuth. Users are only allowed to share with users are friends with them. There will be a utility to search for other users who are using this application at the top that will invoke Facebook Graph API. superuser: make administrative and antivandalism actions like flagging explicit content, and deleting accounts. Only one of this kind of user. Superuser also has all the privileges of the regular user for easy testing. nonUser : While not the main target of the app, much of the traffic that will come to the website will be those that are new to the site, those that have not registered and are using the site. These users have limited access to the website without signing in or registering; they will only be able to access trips that are made public. Until the actual release, this feature will not be available, and hence nonusers will not be in any of our essential use cases. |
| Supporting Document | Use Cases |