Hotspots: Admin Pages | Turn-in Site |
Current Links: Cases Final Project Summer 2007
Fall 2004 M4
Add a Graphical Representation and a Usable User Interface
It is now time for you to produce an interface that allows a user to see and interact with the characters and objects in your world. The style and implementation approach used is entirely up to your group, subject to the following requirements.
- You must provide a display of the physical world in which your game is taking place. Since the world may be too complex for a static display to be useful, the view presented should include a current room and some way to move the view to another room. This change of view might take place as a result of user action or when following a character to another location.
- Your GUI should support the provide a player with the following capabilities:
- Create new people and things
- View, modify and add to attribures of persons and things
- Designate a "current" person
- Direct current person to pick up or put down objects
- Direct current person to interact with another person
- Move current person to a new location
- You must provide a way to save and restore game states building on the features you implemented in previous milestones. Note that the state of a game must include some representation of the structure of the world in which the characters and objects exist. For now, that structure is static, but later on you will have to include the dynamic creation of buildings and rooms.
If you want to use wonderland then you can find objects to add to your 3-D world here: SqueakObjects.zip. You might also find the Cases helpful from Fall 2003, Spring 2002, Fall 2001
A single zip file containing all your design documents should be turned in on the cs2340turnin coweb: http://coweb.cc.gatech.edu/cs2340turnin. This file should be submitted to the coweb before class (1:30) on November 2, 2004.
- 5% Updated SCENARIOS constructed from specific examples that touch on every major function in the system from the user's point of view and Updated CRC CARDS representing a good behavior analysis: Reasonable names, understandable and clearly defined responsibilities, useful comments
- 10% Updated UML CLASS DIAGRAM reflecting your analysis and design and Updated UML SEQUENCE DIAGRAMS for the functions listed in the requirements.
- 15% Quality of the design.
- Code matched design
- Usable interface
- Clear, concise, robust, and correct design - effective distribution of responsibilities (no god classes or classes without function), high cohesion, and low coupling
- 5% Well-documented & good style source code
- Reuse of existing code
- Effective commenting
- 5% Updated TEST PLAN (About Test Plans) with clear linkages between scenarios and test cases and expected results. We should be able to verify that your test plan covers all of the system requirements. This includes also having updated SUnit Tests
- 60% Working system:
- 45% The user interface provides access to the following functionality:
- 25% Selecting a Person and being able to:
- modify his/her attributes
- direct an interaction with another person
- move the person
- make the person pick up and drop items
- 10% Creating people and things
- 10% Saving and Loading the game state
- 15% The user interface provides a display of game information
- location of people and things
- adjacency of rooms
- person and thing details (name, description, attributes, etc.)
- changes in a person's factors
Questions on Milestone 4
Link to this Page