1 / 4

Hangman : apps , webpages,adverts,scams , …but usually just a fun game

Hangman : apps , webpages,adverts,scams , …but usually just a fun game. Variations: Clues/ Themes Number of errors Types of error Real-time Arcade style/Interactive Multiplayer. Hangman PBL: Learning Objectives. Understanding the structural relationships between : Code

verne
Download Presentation

Hangman : apps , webpages,adverts,scams , …but usually just a fun game

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. Hangman: apps, webpages,adverts,scams, …but usuallyjust a fun game • Variations: • Clues/Themes • Number of errors • Types of error • Real-time • Arcade style/Interactive • Multiplayer CSC7302: Testing & Metrics

  2. Hangman PBL: Learning Objectives • Understanding the structural relationshipsbetween: • Code • Test (code) • Problem/Requirements • Can we have objective measurementsthatcorrelatewith the quality of code: • Correctness • Understandibility/Maintainability/Testability • Understand the impact of OO on the quality of the code and tests • Composition • Inheritance • Polymorphism CSC7302: Testing & Metrics

  3. HangmanProblem • You are to produce multiple versions of the hangmangame (all in Java): • Unstructured (non OO): 1 class and 1 method • You can use standard library classes but are allowed to defineonly one • class and one method of yourown • Overlystructured (too OO): over-use of high-level OO programming concepts • Toomuchinheritance and/or composition and/or … • Well-designed(perfectly OO): a solution thatis as high-quality as youcan manage You must produceat least one examplefromeach of thesethree types of solution (but may have multiple versions of each type) • DevelopmentRules: • All versions must passexactly the same set of tests. • The tests shouldbedevelopedbefore the solutions are coded. • The test code canbestructured in whateverwayyouwish but it must not containany code uponwhich the correct functioning of the gamedepends CSC7302: Testing & Metrics

  4. HangmanProblem • All remaining sessions (from me) are built on top of thisproblemsoyou must have solutions ASAP (individually or collectively): • Today – great • Beforenext class – fine • End of next class – the practicallimit • Wecannotproceedunlessyourdifferent versions all pass the same test code, and the test code isbothcomplete and consistent with respect to the gamerules. • Note: please document the order in whichyoudevelopyour solutions. This willbe important in ourlateranalysis. CSC7302: Testing & Metrics

More Related