1. The Neighborhood is brought to you by: Oren Hacohen Livnat Jerby Effi Zachut Gili Vaturi

2. Primary Use Case (Reminder) • Effi, Livnat , Gili & Oren are 25 years old Co-Workers who fill a toto form out every week. • Unfortunately, there’s no way they can share their form online and express their opinions on it. They must get together to do it. • The Neighborhood application will allow them to fill out the form online, share their opinions (“No, Hapoel is not going to win the derby, I don’t care what they’re saying on TV!”)

3. Current Features- The Basic Form • This feature was developed by all four of us as it is the key to the client application. • Time Frame: an estimated 80 hours. • Difficulties: • Knowing where to start from • Lack of basic HTML/Javascript understanding • Google Wave’s stability and architechture • Not to many WAVE applications out there • Creating a proper work environment (JS,SVN) • Easy: • Wave API documentation • Many JS tutorials online

4. Current Features- Get External Sources Information • This Feature was Owned by Gili Vaturi (Server) and EffiZachut (Client) • Time Frame: an estimated 70 hours • Difficulties: • Lack of App Engine/Web Services understanding • Parsing the XML from Dapper • App engine limitation for a URL fetch • QA • Easy: • Familiarity with Java • Dapper did most of the parsing work • App Engine documentation

5. Current Features- User Interface • This Feature was owned by Oren Hacohen and EffiZachut. • Time Frame: an estimated 70 hours. • Difficulties: • Designing an intuitive, user friendly UI. • Lack of HTML/Javascript understanding • Javascript Program Flow • Team Work- Getting the proper objects for display from the other team members. • Easy: • Form look& feel is pretty straight forward (we advised the site). • Many JS/HTML tutorials online

6. CURRENT FEATURES- LAST WEEK’s RESULTS, WINNINGS, COST, WHO’s FAULT • These Features were owned by LivnatJerby and Gili Vaturi • Time Frame: an estimated 40 hours. • Difficulties: • Features’ Design • Team Work- Creating the proper objects for display for other team members. • Audit Wave participants actions • Easy: • Simple functions logic

7. Features List (To Be Developed)

8. Our Roadmap • Milestone 2: • Head to Head mode complete • Final User Interface • Features from the previous slide • A lot of QA  • Few exceptions: • Haven’t decided whether to develop “nearest station” • Haven’t decided whether to develop Payment Turns • Need to check feasibility of “talkback interface per match” • Differences from original plan: • New Features: (statistics, tips, totomat, talkback interface, who’s fault is it etc…) • Removed(?) features: • Nearest Toto Station • Payment Turns