1. Sudoku Taryn, Jin, Jehsang, Phil, and Matt

2. Outline What is Sudoku? –The game of Sudoku –The website Sudoku UI Prototype How to use the site (use cases) What makes us unique Tools/Technology we’ll be using Group Structure Risk Management

3. Sudoku: The Game Popular numbers and logic game Start with a board that’s partially filled in, fill the empty cells according to: –One through nine in each row and column –One through nine in each box Multiple levels of difficulty –Daily has “Apprentice” through “Emperor”

4. Sudoku: User Registration Once a user is done, he or she clicks the SUBMIT button successful extension

5. Sudoku: User Registration(cont’d) If everything was successful, the user is directed to registration confirmation page. Otherwise, the user is directed to the same page with the indication where errors occurred. Successful scenario extention

6. What Makes Sudoku (the website) Unique We will: –Record best times for each level of difficulty for registered users –Record global best times and display them on the website –Make non-traditional game boards available for play (e.g. samurai sudoku, diamond shaped-puzzles)

7. Tools and Technology Server: –Tomcat –Use java servlets to process incoming requests, forward to JSPs Client: –Javascript for playing sudoku, verifying fields in regestration, etc. Puzzle Generator: –Java Database: –MySQL

8. Group Structure Three subteams for each of the modules: –User Interface Jin Phil –Puzzle Generator Taryn Jehsang –Server side applications Matt Subteam membership determined by interest and skillset (e.g. all members on UI have some experience with javascript and HTML) Roles: –No specific testing, tool-writing, documentation, etc. roles –To be divided among all members as needed. –Team Manager: Matt Subteam membership subject to change as the project evolves

9. Risk Management Three different strategies as risk increases: –Slightly behind schedule: Swap personnel to modules that are running behind schedule –Behind schedule: Cut “tenuous” features (e.g. different board types, etc.) –Seriously behind schedule: Cut important but non-critical features of the site (e.g. user registration and best time logging)