1

Gilese 581

(GLEE-ZA)Iteration 2

Presentation

Jan Horjus, Abebe Woreta, Neil Chu, Ritik

Ray & Patrick Logan

CS673 – Introduction to Software Engineering –

Tues. April 2nd 2013

2

Iteration 2 progress

New Player Screen

Main Menu Screen Game Setup Screen

Map Screen (actual game)

New Game Load Game

Options Exit

Start

End

Options Screen

Cancel

Apply

Army Setup Screen

Cancel Start Game

Escape Menu

Iteration 2: Actual Progress

Change Resolution

Adjust Volume

Full-Screen Mode

FUN!

Choose Players

3

Project Design

4

Partial View of Class Diagram

5

Partial View of Class Diagram – cont’d

6

Project Management

• Using Pivotal Tracker as our primary feature tracking utility.

• Very useful in keeping track of who is doing.

• Keeps us accountable to pass through the proper development stages for each feature.

• Also using the Issue-tracking functionality of our Google code repository.

7

Evolution of Group Roles

From Specialists •During the first iteration many group members were assigned to

specialized tasks based on their existing skill-sets. •This was because of a product-focused mindset and was meant to

increase the efficiency of development.

To Generalists

•During this iteration we have made a special effort to ensure that each group member is involved in each type of task – those who previously focused on code also helped with documentation, art, and product management, and vice versa.

• This was part of a transition to a more process focused mindset and was meant to maximize the amount that each group member would learn.

8

Design Patterns

Factory •The Unit Class•The Cursor Class

Singleton •The TextureStore•The ConfigManager

Strategy •Relationship of a MenuButton to an Event object

9

Design Patterns (cont.)

Template •The GameScreen class’s Draw method.•The ClickableSprite class’s Update method.

Composite •The Draw Interface•The Update Interface

State•The GameMap’s behavior determined by TurnStage

10

Template Design Pattern

11

Composite Design Pattern

12

Singleton Design Pattern

13

Risk Management

Risk 1 •The MapScreen (the most important screen in the project) was not functional at the end of Iteration 1

Risk 2 •Project integration work threatened to throw off our schedule.

Risk 3 •Management overhead increased somewhat as a result of evolving group roles.

14

Stop

Demo Time•Break it down.

15

References• Rob Miles: Introduction to Programming through

Game Development using Microsoft XNA Game Studio.

• XNA Game Programming Adventures: http://xnagpa.net/index.php

16

Questions?