Tree [r71] /
History



File Date Author Commit
Hangman.Net 2008-10-26 rboehm00 [r5]
multiplayer.hangman.HTML 2008-11-10 rboehm00 [r66]
single.hangman.HTML 2008-11-11 rboehm00 [r71]
GameCore.js 2008-10-30 rboehm00 [r13]
Readme.txt 2008-11-09 jzhong01 [r59]

Read Me

This is the readme.txt file for the Team JAR Hangman project.

Team JAR contains:
	Ron Boehm - Team Leader
	Aravind Hosadurga
	Jiuning Zhong


The project can be found in a SVN repository at SourceForge.

The URL to access the project is:
	https://hangman8450.svn.sourceforge.net/svnroot/hangman8450

If a user/password is needed use teamjar/teamjar

The repository includes three projects, each in its own folder

	multiplayer.hangman.HTML	Original multiplayer version in HTML
	single.hangman.HTML		Single/multiplayer version in HTML
	Hangman.Net			prototype written in C#


Build/Startup instructions for multiplayer.hangman.HTML:

Double clicking the file Hangman.htm in the folder multiplayer.hangman.HTML
will launch The original multiplayer version of the game.
This program was written and tested using Firefox to run it.
Less complete testing with IE 6.0 has not discovered any errors, but this is 
not yet a supported browser for this project.
This project uses our original graphics.
Project Folders:
	\Images		Contains the graphics used in the project
	\js		Contains the GameCore.js Javascript file
			This contain all the code that "models" the game. 


Build/Startup instructions for single.hangman.HTML:

Double clicking the file HangmanPlus.htm in the folder single.hangman.HTML
will launch The upgrades single / multiplayer version of the game.
This program was written and tested using Firefox to run it.
Less complete testing with IE 6.0 has not discovered any errors, but this is 
not yet a supported browser for this project.
This project uses the graphics created by the team to follow the guidlines 
specified by the customer during the enhancement design discussion.
Project Folders:
	\Images		Contains the graphics used in the project
	\js		Contains the Javascript files
			GameCore.js - This contain all the code that 
					"models" the game. 
			WordLibrary.js - contains the words to guess 
					for the single player game.
			X_core.js, y_Tabs.js & ylib.js - this files
					were downloaded from the internet
					to support overlaid windows in HTML.



Build/Startup instructions for Hangman.Net:

The Windows Hangman.exe file is in the folder Hangman.Net\Hangman\bin\Debug.
Double clicking this file will run the prototype.

The project can be opened in Visual Studio 2003 by opening the project file
Hangman.sln in the Hangman.Net folder.




Hangman project notes

 
Original spec was provided online in classroom system.
The basic goal is to create a hangman game,

In our organizational meeting:
            We decided to create a throwaway prototype.
            We decided to implement the program in HTML with JavaScript.
                Although no one on the team was an expert in this environment, 
		we made this choice as it was an environment that everyone was 
		able to function in.

            Unfortunately, we had no options that were known by all three members 
		of the team with any depth. 

We decided on an informal process with incremental milestones with the basic 
	design done up front.


A prototype was created in C#, with a separate class for the game model.
The view and controller code were intermixed with the GUI.
We decided to follow the same approach in the actual program.
The model was ported from C# to JavaScript.
The initial allocation of GUI and functions were divided among the team.
A project was created on SourceForge under the teamjar account.
The SourceForge Project was called 8450-Hangman.
We ran into a number of difficulties with SVN.  
First, none of the team was familiar with it.
SourceForge itself was having some difficulties and this also caused some delays.
Finally, there was an enabling setting in the admin that was not obvious and was 
not found until some assistance was received from the SourceForce support team.

We decided to use the SorceForge tracker to facilitate communication within the team.
This included bug tracking and other changes.

On 10/28, we met with the customer for a status review meeting:
We demonstrated the program as it existed and received the positive feedback that 
	we were on track.

Earlier that day, the scope of the project was expanded with additional 
	requirements and optional functionality.
The additional requirements were clarifications of item that we had assumed, 
	but had not been specified:
                        The criteria for a legal guess.
                        How to handle invalid?characters in the word to guess. 
            The optional functionality included the following describe features:
                        A single user version of the game.
                        A hint feature.
                        A buy a vowel feature.
                        The addition of graphics.