Welcome to the Evil Hangman User’s and Developer’s Guide. This website is designed for anyone to learn and understand the underlying mechanics of how Evil Hangman works, and what its developers put into it.
Table of Contents
Executive Summary
The purpose of Evil Hangman was to develop a game that could be marketing and theoretically sold to prospective users.
The development team started off with scoping for prospective users and what they would want to see in a game. The users that were interviewed responded with ideas that were more out of scope than the team’s development window. After user interview, pseudocode and flowchart designs were made to focus and plan the developing of the game. Then the development team split the game into two groups: one for the front-end, UI design and one for the back-end game logic. After weeks of development and individual unit testing, a final integration test was performed with both components combined.
After the final test, a major glitch was brought to light, where the game’s word list would diminish to zero word, thus causing the user to lose no matter what (see Program Description for details). As a result, the back-end development team reworked the code in time for the user play session that occurred a week after the final testing phase.