Final Fantasy ½ : IOC Overview

1. Final Fantasy ½: IOC Overview I’ve got something special for you. Team Q CSE 403 Winter ‘03

2. Software Preparation – Operational Software • Midlet Features Completed - • Simple interface with intuitive controls • Maze screen adapts its size to fit your cell-phone • Customizable player with 10 different icons available • Support for doors, keys, coins, teleporters, and chat orbs • Helpful error messages if the server goes down • Interactive chat screen for talking to other players • Maze updates happen in real-time! • Support for “fog of war” (hides far away items)

3. Software Preparation – Operational Software • Servlet Features Completed - • Persistent Gaming World • SQL Server database backend for Player storage • Support for multi-player gaming • Persistent, personalized player profiles • Intelligent timeout policy, allows quick recovery from connection interruptions. • Maze configuration variables in web.xml, read dynamically on restart • Flexible message passing facility between players. • Items periodically re-spawn through multithreading

4. Software Preparation – Operational Software • Features Not Completed - • In the initial concept of the game, we were going to have multiple mazes, in which teleporters and doors would lead to other mazes. In the actual implementation, there is one large maze in which teleporters and doors lead the Player to other areas of the one large maze (i.e. teleportation within the maze and doors blocking paths in the maze). This was done for implementation simplicity and was justified because it does not significantly impact the overall game play or game functionality. • Mazes are randomly generated as of now, whereas before they were planned to be read from a file. The problem was that the mazefile format is not human readable, and we did not have time to generate tools (editors) to work with this format in a way that would enable good level design. The support is there, and can be easily implemented in a 2.0 release.

5. Software Preparation – Support Software • Requirements - • MS SQL Server 2000 database with a table of definition: PersonData(Name, Password, NumKeys, Coins, ImageFile, RoomX, RoomY). Game. • JDBC Driver for MS SQL Server 2000 (Service Pack 1) • Tomcat Server

6. Software Preparation – Readiness Testing • Readiness testing is complete and has passed. The product has been tested both on the Midlet and Servlet side, as well as a combined test with the Midlet running with the Servlet. Throughout our testing 28 defects were found on the Servlet side and 25 defects were found on the Midlet side. Of the total 53 bugs, 50 were fixed and 3 are still open. The three remaining bugs are very minor and were either not reproducible, or extreme corner cases. Perhaps they will get fixed in version 2.0 if further testing warrants it. Initial usability testing also passed our requirements.

7. Site Preparation – Requirements • The site resources necessary for a successful deployment of Final Fantasy ½ will scale depending on the amount of players at peak times that are playing the game. As the amount of players increases, the amount of site resources will increase. Therefore, only the minimum requirements for a smaller scale game will be laid out here. • Requirements – For the Game • Tomcat Server for running of the Servlet. • A database server with Microsoft SQL Server 2000 • 1 Mbps Internet connection and at least a 100 Mbps internal network connection.

8. Site Preparation – Requirements • Requirements – For the Employees • Source Control software for code and documentation. • A Defect database to track defects over the products life. • Standard client machines (Windows based) with standard office and development tools. • E-mail access for employees (whether with MS Exchange, free web based e-mail, etc.)

9. People Preparation – Requirements • The human resources necessary for a successful deployment of Final Fantasy ½ will scale depending on the amount of future improvements and functionality that are planned to be added. • People resource requirement - • At least two Server Administrators. • At least two developers (one Midlet and one Servlet). • There will need to be lab and system support personal. • At least one Quality Assurance employee for Product and Performance testing. • At least one manager, depending on the total number of employees that need to be managed.

10. People Preparation – Requirements • Training Requirement - • All employees that do not have the full knowledge required for their given job, will also need to be trained appropriately. With careful selection of employees given their skill sets, the amount of training can be minimized.