1 / 35

Design & Development – 2h

Learn about design documentation, game concept, screen layout, game controls, sprite behavior, and more. Get expert advice on software development and user-centered UML methods.

bracamonte
Download Presentation

Design & Development – 2h

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Design & Development – 2h

  2. Helpful Advice • It is better to have a design, and then to change it in the light of experience, than not to have a design at all

  3. Design Documentation • A description of the game concept • A sketch of the screen layout (not a screenshot of the completed game) • A description of the game controls • A description of the behaviour of the major objects • The user sprite • Any autonomous sprites

  4. A Sprite • A sprite is an image which represents one of the characters in a game • A Sprite moves as a 2D block (usually oblong) as the game progresses. • Sprites can also be animated and change their appearance.

  5. Game Concept 1/3 • Gameplay Theme • Core Objective • Core Idea • Game Objects

  6. Game Concept 2/3 • Gameplay Theme • What’s the game about ? • Core Objective • What is the overall goal ? • Core Idea • Defines overall gameplay • Develop secondary ideas to enrich experience

  7. Game Concept 3/3 • Game Objects • Primary function • Secondary Functions • Generated by gameplay features • Initiates additional gameplay features

  8. Proposed Screen Layout

  9. Description of Game Controls

  10. Description of Game Controls • During normal game play, player one’s paddle is moved up using the “3” button and down using the “9” button. When thus activated, the paddle will move up or down at a speed of 5 pixels per second.If “3” and “9” are both pressed at the same time, the paddle will not move.

  11. Sprite Behaviour • The ball will bounce off the top or bottom of the screen. I.e. on contact with the top or bottom of the screen, it will continue its horizontal speed. Vertically it will maintain its speed but reverse direction. • If the ball contacts the left paddle it will adopt the vertical speed of the paddle at the time of contact. It will change horizontal direction to move rightwards...

  12. Feedback • Visual • Audio • Action • rumble • Accumulative • heath, armour, weapons etc • Emotional • Fulfillment

  13. Software Development

  14. “You should use an iterative development method only on projects that you want to succeed” Fowler, 2000

  15. User-Centred UML Method Capture/Develop Scenarios Contextual Analysis Scenarios Contexts of Use Find Actors and use-cases Identify Objects & Relationships Use-case Model User Model Interface Design Interface Models Class Diagram (Conceptual) All activities are performed iteratively. Usability evaluation is conducted in parallel with design and implementation Interaction Diagrams from use-cases Identify Operations Interaction Diagrams Class Diagram (Specification) Examine Behaviours & Class Relationships Specify Implementation State Diagrams Class Diagram (Implementation) Implementation Functional Testing Usability Evaluation Code Test Results Usability Reports User-Centred UML Method , based on Hudson (2002)

  16. “The diagram is not the design: the diagram is a representation of (part of) a model of the design, which captures an aspect of the design in a form which can be discussed” Stevens, 2001

  17. Game Play new game Continue old game Set game parameters GamePlayer Save game View Hall of Fame Game: First Draft ?

  18. Use-case Scenarios • A scenario is an instance of a use-case - it is one path through the flow of events for the use-case. Sometimes referred to as the use-case instance.

  19. Use-case Scenarios • Scenarios speak the language of the end user and the domain expert, and therefore provide a means for them to state their expectations about the desired behaviour of a system to its developers.

  20. Use-case Scenarios • Each use-case is a web of scenarios - primary scenarios (the normal flow for the use-case) and secondary scenarios (the what if logic of the use-case).

  21. Use-case Scenario Example “The ball approaches Player 1’s side (on RHS). P1 misses. It passes P1’s paddle without touching it. It disappears off RHS of screen and wraps round to appear on LHS of screen. It maintains its original speed and direction. It goes through P2’s bat to continue towards P1. P2’s score increments.”

  22. Writing Use-Cases (Gymkhana Game) Use Case: Jump Obstacle Basic Flow 1. Horse moves towards obstacle 2. Effect sound of horse galloping 3. Horse attempts to jump obstacle 4. Horse clears obstacle 5. Sound of horse galloping away

  23. Writing use-cases (Gymkhana Game) Alternatives: A: Horse refuses to jump 3.1 Effect sound of horse juddering to a halt 3.2 Horse disqualified 3.3 Time trial is terminated B: Horse hits obstacle 4.1 Effect sound of horse hitting obstacle 4.2 Time penalty awarded 4.3 Time penalty displayed

  24. Move Horse Make SoundFX Activity diagram [refuse] Make SoundFX jump Jump Obstacle [hit] Make SoundFX Horse disqualified Penalty Awarded Clear Obstacle Penalty Displayed Make SoundFX Terminate Trial

  25. CRC cards • Class • Responsibility • Collaboration

  26. Example CRC Card

  27. Example CRC Card

  28. Example CRC Card

  29. Sound Display play() GymnkhanaWorld Class Diagram boundaries courselayout currentTime penalties horseStatus trialComplete startTrial() finishTrial() displayGameStatus() updatePenalty (0 disqualify() Horse display() position direction speed soundFX move() jump() makeSound() Obstacle position cleared hit refused soundFX jumpTest() breakApartl() makeSound() Finish trialComplete()

  30. Sequence Diagram Scenario: Basic Flow 1. Horse moves towards obstacle 2. Effect sound of horse galloping 3. Horse attempts to jump obstacle 4. Horse clears obstacle 5. Sound of horse galloping away

  31. Sequence Diagram GamePlayer : Horse : Sound :Obstacle move ( ) makeSound ( ) play (soundFX) jump ( ) jumpTest ( ) play (soundFX)

  32. A: Horse refuses to jump 3.1 Effect sound of horse juddering to a halt 3.2 Horse disqualified 3.3 Time trial is terminated

  33. GamePlayer : Horse : Sound :Obstacle :GymnkhanaWorld :Display move ( ) makeSound ( ) play (soundFX) jump ( ) jumpTest ( ) play (soundFX) [refusal] disqualify ( ) displayGameStatus ( ) display ( ) finishTrial ( )

  34. B: Horse hits obstacle 4.1 Effect sound of horse hitting obstacle 4.2 Time penalty awarded 4.3 Time penalty displayed

  35. GamePlayer : Horse : Sound :Obstacle :GymnkhanaWorld :Display move ( ) makeSound ( ) play (soundFX) jump ( ) breakApart( ) jumpTest ( ) play (soundFX) [hit] updatePenalty ( ) displayGameStatus ( ) display ( )

More Related