High Level User Requirements gathered by Pranav:
User Rohan : Student in Dept of Informatics.
1> Does not know what is Sprite ???... It should have been Game Object...
2> Need to have basic properties like image selection, postion, width,height, speed.
3> Need to have score .
4> Need user friendly UI for event action mappings. Not described in detail. Pending for second meeting.
5> Most importanty should have video/document attached in the game maker so that using game maker becoming fun and not a learning platform for the user.
6> Able to pause the game, save it and load it.
7> Game Object should be controlled by user.
High Level User Requirements gathered by Ye.
User Yi: Student in SPEA.
1> user should be able to drag object (sprite) from edit panel to game play panel (instead of input coordinates).
2> Intelligent event action mapping process to make game building process simple and not tedious(after one mapping is performed, program should be able to find similar game object and bind mapping automatically).
3> auto-save currently built game in case of program crash or close the program accidentally.
4> background music and controllable object being able to response user's command by sound(like when player let object move left, it would speak "Yes, commander, I'm moving left").
5> be able to set the difficulty of game (hard – medium – easy).
6> be able to record score corresponding user name. (so when game over, there will be a ranking list)
7> A more easy way to choose event. For example, when we want to associate the action with collision, we just drag the two objects together let them collide and then associate action. When we want to associate the action with key event, we select the particular sprite, press a key and then associate action.
8> Most important: cheating mode. When cheating mode is open, player never "dies" in the game.
High Level User Requirements gathered by Vinod.
Client - Vidhya - HCI Student
1)Classify the user.
2)Not to design for everyone
3)Choose one type of user
4)Resolve Ambiguous names
5)positioning and sizing should be user friendly...
6)Make the objects clickable and selectable
7)Highlight the objects that u are going to select
8)Preview the action ,event mapping
9)Restrict the no of games and proceed, u cannot obviously decide all games in the world.Have a decent number of games in mind and proceed
10)Start simply.
11)Choosy about colour,,white is not a good option ,as everything else should be so bright then.
High Level User Requirements gathered by Srinivasa.