does this ever happen to you?. public life getlife (char* yourname) { ------ ----------------...
TRANSCRIPT
Does this ever happen to you?
Public life getLife (char* yourName){
<code>---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------<endcode>return yourLife;
}
c:/> run getLife(<yourName>) _.running.............
ERROR:“null pointer exception”(but it’s ok… Chuck Norris can dereference null pointers)
Get-a-LIFEcreated by:
Chester Chan, Jessan Hutchison-Quillian, Zinnia Zheng
Purpose
Get a life… o Find events
• Connect with friends
• Suggest based on interests
o Organize schedule• Daily activities
We’re special
o Suggest activities to do• Sorted by user rating, interests, time, location, etc.
o Rate users• Event quality
• Event reliability
o Categorize events• Interests
o Daily schedule
Other People – Facebook
Other People – MySpace
Continued…
US
US again!!
Feature List
PRIORITY FEATURES
o Essential • Suggest events• User account (interest list, basic schedule)• Rate users who post events
o High • Ability to add recurring events (weekly, monthly etc.)• Friend list
o Medium • Plan friend-only events• Interest group
o Low • Various visualization formats for the schedule• Privacy settings• Interfacing with other programs
Web Frameworks
o Loosely coupled components• Testability• Scalability
o Code separate from web pageso JDBCo “Friendly” URLso Listener methodso User input validationo Exception reporting
But high learning curve…
System Flowchart
Development Stageso 1.5-2 weeks after LCA
• First set of features: database designed and working, able to create a user and edit their schedule and add events to the database. Very basic GUI.
• Begin testing.o 1 week
• Able to create and edit list of interests and have the event suggestion query/display working. After this, and having some idea of the pace of development, settle on final set of features.
o 1 week• Work on implementing features, have GUI complete as much as possible with
“dummy” spots for features planned but not implemented yet.• Begin documentation.
o 1 week• Have features done, all remaining effort on testing and finishing
documentation.
Feasibility
o Standard practice
o Effective development practices• Staged delivery• Continuous testing
Don’t hesitate
Get-a-LIFE