Building Memory Notes from class on 4407 The

Building Memory… Notes from class on 4/4/07

The Game • First understand what we are trying to build. • Then, create a list of requirements/functionality for our game

A Section Functionality • • • Even number of cards appears Front & back images on cards Cards have to turn Recognize a match (2 like images) Match found? Keep face up Timer for game

A Section Functionality • No match? Turn face down again • Keep track of how many turns a player’s had • Keep track of which player goes next • Keep track of how many matches each player has made

A Section Functionality • • Determine a winner Shuffle cards on board All cards face up, end game How does user select cards? (Mouse, keyboard)

What do we do first? • THINK!!!!!

What do we do first? • Perhaps the more appropriate answer is design – Sketch a design for the user interface – Decide on what objects are needed for the game – Create a small UML for the relationships between those objects

What do we do first? • More design issues – What happens when the user starts the game – How does the user interact with the game

What do we do first? • All of these issues should be considered and will give us a place to begin creating our classes and building our relationships. • While working on the project, we will often need to come back and redesign or further design different aspects of the game.

Separation • We will note a separation of graphical concerns and what we will call our game engine. • Getting the program to “look” a certain way will take time • Getting the program to execute correctly will take some more of our time.