https://wiki.expertiza.ncsu.edu/api.php?action=feedcontributions&feedformat=atom&user=DjbleakiExpertiza_Wiki - User contributions [en]2026-06-25T23:28:27ZUser contributionsMediaWiki 1.41.0https://wiki.expertiza.ncsu.edu/index.php?title=CSC_216/s08/esteem_patriotism&diff=11406CSC 216/s08/esteem patriotism2008-04-22T23:26:24Z<p>Djbleaki: </p>
<hr />
<div>===Formatting Resources===<br />
[http://meta.wikimedia.org/wiki/Help:Wikitext_examples Formatting Help Guide from MetaWiki]<br />
<br />
==Family Feud Java Style==<br />
<br />
It's Family Feud with a Java twist, what more could you ask for in a Java learning exercise?<br />
<br />
===The Problem===<br />
<br />
Every student has their problem with memory recall, this game is designed to help eliminate that process. It gets the entire class involved so that no one is left out and can be preformed in a feasible amount of time!<br />
<br />
===Participants and Props===<br />
<br />
Anyone can participate in the row style competition all you need is a working computer with Microsoft .NET framework in order to run the game.<br />
<br />
===Uses!===<br />
NOTE: This game can be used for more than just vocabulary!!!<br/> <br />
-> It can also be used to enhance association of certain topics, in other words, helping understand what goes with what!<br/><br />
-> Since answer length is unlimited, the game can be used for more than just vocabulary in that sense as well. The only thing to remember about that is the game only displays the first 50 characters of the answer but the answer can be any desired length.<br/><br />
<br />
This game can be used in many different ways to help aid in the teaching of Java subjects. This program can be used as an evaluation of class knowledge on the current topic. For instance, one of the questions in this game is Name 7 common Stack and Queue methods. This type of questions gets students to remember and recall all of the common methods of Stack and Queue thereby effectively reassuring that each student has a good understanding of how to write and format Stack and Queue classes. Below is a list of the current questions included with the game: <br/><br />
<br/><br />
Please note that questions, answers, and points can be changed to fit the classes needs whenever the game is used, so essentially, the game can be used to help teach any subject.<br/><br />
<br/><br />
Name 7 Errors Java Programmers Make<br/><br />
Name 7 Characteristics of linked lists and recursion<br/><br />
Name 7 Common Stack and Queue Methods<br/><br />
Name 7 FSM and Binary Search Tree components<br/><br />
Name 7 Common Exceptions<br/><br />
<br />
===The Script===<br />
<br />
Family Fued Java Style Rules:<br/><br />
<br/><br />
(1) - Each team's turn is indicated by the label in the top right of the screen<br/><br />
(2) - The team will have 30 seconds to come up with an answer to the question<br/><br />
(3) - Each team has 3 wrong answers before their turn is over<br/><br />
(4) - The game continues until all of the answers have been given or the give up button is clicked<br/><br />
(5) - The game ends when the participating parties choose to end it as long as each group has had a turn! This game can be preformed in 20 minutes or less!!!<br/><br />
(6) - The team with the highest score at the end of the game is the winner<br />
<br />
===Read Me===<br />
<br />
PLEASE READ THIS! <br/><br />
This game link comes as a zip file with all the required files in order to run the game. I have also included the source files for those interested, but they are not necessary in order to change the game information, etc.<br/><br />
<br/><br />
Note: All files are pre-formatted! This information is only for those who want to make their own changes to the game information!<br />
<br />
Questions.txt:<br/><br />
The questions file should be formatted with one question per line and each question may be no more than 100 characters long.<br/><br />
<br/><br />
Answers.txt:<br/><br />
There must be 7 answers per question, no more, no less<br/><br />
Each answer should be on one line and to distinguish between questions "&&&" should be entered as a delimiter.<br/><br />
<br/><br />
Points.txt:<br/><br />
Same as the answers, there must be 7 point values<br/><br />
Each point value should be on one line and to distinguish between questions "&&&" should be entered as a delimiter.<br/><br />
<br />
===Game Link===<br />
Please test out the game for yourself!!!<br/><br />
<br/><br />
[http://www.hopewellheadliners.com/java/dotnetfx.exe Microsoft .NET Framework]<br/><br />
[http://www.hopewellheadliners.com/java/familyfeudjavastyle.zip Family Feud Java Style]<br />
<br />
===Example===<br />
For example, let's say that your Java class is learning about common exceptions.<br/> <br />
Before class, complete the following: <br/> <br />
First, write the question into the Questions.txt file. Ensure that it is the only question.<br/> <br />
Next, write down your top seven answers, in order, in the Answers.txt file.<br/> <br />
Ensure that the point values are properly entered in the Points.txt file. <br/> <br />
<br/> <br />
Now, when you wish to review common exceptions in your class, do the following:<br/> <br />
First divide the class into teams.<br/> <br />
Begin the program, and allow the teams to play through the game.<br/> <br />
End the game when each team gives up, or all answers have been found.<br/> <br />
<br />
===Screenshots===<br />
Note: Screenshots have been changed!!! The previous ones were from my testing period when I was using any question to make sure the game worked.<br/><br />
The following are from the final stages<br/><br />
<br/><br />
[[Image:Ss1.gif|Screenshot 1]]<br/><br />
<br/><br />
[[Image:Ss2.gif|Screenshot 2]]<br/><br />
<br/><br />
[[Image:Ss3.gif|Screenshot 3]]<br/><br />
<br/><br />
[[Image:Ss4.gif|Screenshot 4]]<br/><br />
<br />
===Video Example===<br />
<br />
[http://courses.ncsu.edu/csc216/lec/002/video/t15/ Video Example]<br />
<br />
===Credits===<br />
<br />
Created By:<br/><br />
Jonathan Rupert<br/><br />
Nicholas Jones<br/><br />
David Bleaking<br/><br />
<br/><br />
Note: Game coded from scratch, not found on web!</div>Djbleakihttps://wiki.expertiza.ncsu.edu/index.php?title=CSC_216/s08/esteem_patriotism&diff=11365CSC 216/s08/esteem patriotism2008-04-21T02:39:27Z<p>Djbleaki: </p>
<hr />
<div>===Formatting Resources===<br />
[http://meta.wikimedia.org/wiki/Help:Wikitext_examples Formatting Help Guide from MetaWiki]<br />
<br />
==Family Feud Java Style==<br />
<br />
It's Family Feud with a Java twist, what more could you ask for in a Java learning exercise?<br />
<br />
===The Problem===<br />
<br />
Every student has their problem with memory recall, this game is designed to help eliminate that process. It gets the entire class involved so that no one is left out and can be preformed in a feasible amount of time!<br />
<br />
===Participants and Props===<br />
<br />
Anyone can participate in the row style competition all you need is a working computer with Microsoft .NET framework in order to run the game.<br />
<br />
===Uses!===<br />
NOTE: This game can be used for more than just vocabulary!!!<br/> <br />
-> It can also be used to enhance association of certain topics, in other words, helping understand what goes with what!<br/><br />
-> Since answer length is unlimited, the game can be used for more than just vocabulary in that sense as well. The only thing to remember about that is the game only displays the first 50 characters of the answer but the answer can be any desired length.<br/><br />
<br />
This game can be used in many different ways to help aid in the teaching of Java subjects. This program can be used as an evaluation of class knowledge on the current topic. For instance, one of the questions in this game is Name 7 common Stack and Queue methods. This type of questions gets students to remember and recall all of the common methods of Stack and Queue thereby effectively reassuring that each student has a good understanding of how to write and format Stack and Queue classes. Below is a list of the current questions included with the game: <br/><br />
<br/><br />
Please note that questions, answers, and points can be changed to fit the classes needs whenever the game is used, so essentially, the game can be used to help teach any subject.<br/><br />
<br/><br />
Name 7 Errors Java Programmers Make<br/><br />
Name 7 Characteristics of linked lists and recursion<br/><br />
Name 7 Common Stack and Queue Methods<br/><br />
Name 7 FSM and Binary Search Tree components<br/><br />
Name 7 Common Exceptions<br/><br />
<br />
===The Script===<br />
<br />
Family Fued Java Style Rules:<br/><br />
<br/><br />
(1) - Each team's turn is indicated by the label in the top right of the screen<br/><br />
(2) - The team will have 30 seconds to come up with an answer to the question<br/><br />
(3) - Each team has 3 wrong answers before their turn is over<br/><br />
(4) - The game continues until all of the answers have been given or the give up button is clicked<br/><br />
(5) - The game ends when the participating parties choose to end it as long as each group has had a turn! This game can be preformed in 20 minutes or less!!!<br/><br />
(6) - The team with the highest score at the end of the game is the winner<br />
<br />
===Read Me===<br />
<br />
PLEASE READ THIS! <br/><br />
This game link comes as a zip file with all the required files in order to run the game. I have also included the source files for those interested, but they are not necessary in order to change the game information, etc.<br/><br />
<br/><br />
Note: All files are pre-formatted! This information is only for those who want to make their own changes to the game information!<br />
<br />
Questions.txt:<br/><br />
The questions file should be formatted with one question per line and each question may be no more than 100 characters long.<br/><br />
<br/><br />
Answers.txt:<br/><br />
There must be 7 answers per question, no more, no less<br/><br />
Each answer should be on one line and to distinguish between questions "&&&" should be entered as a delimiter.<br/><br />
<br/><br />
Points.txt:<br/><br />
Same as the answers, there must be 7 point values<br/><br />
Each point value should be on one line and to distinguish between questions "&&&" should be entered as a delimiter.<br/><br />
<br />
===Game Link===<br />
Please test out the game for yourself!!!<br/><br />
<br/><br />
[http://www.hopewellheadliners.com/java/dotnetfx.exe Microsoft .NET Framework]<br/><br />
[http://www.hopewellheadliners.com/java/familyfeudjavastyle.zip Family Feud Java Style]<br />
<br />
===Example===<br />
For example, let's say that your Java class is learning about common exceptions.<br/> <br />
Before class, complete the following: <br/> <br />
First, write the question into the Questions.txt file. Ensure that it is the only question.<br/> <br />
Next, write down your top seven answers, in order, in the Answers.txt file.<br/> <br />
Ensure that the point values are properly entered in the Points.txt file. <br/> <br />
<br/> <br />
Now, when you wish to review common exceptions in your class, do the following:<br/> <br />
First divide the class into teams.<br/> <br />
Begin the program, and allow the teams to play through the game.<br/> <br />
End the game when each team gives up, or all answers have been found.<br/> <br />
<br />
===Screenshots===<br />
Note: Screenshots have been changed!!! The previous ones were from my testing period when I was using any question to make sure the game worked.<br/><br />
The following are from the final stages<br/><br />
<br/><br />
[[Image:Ss1.gif|Screenshot 1]]<br/><br />
<br/><br />
[[Image:Ss2.gif|Screenshot 2]]<br/><br />
<br/><br />
[[Image:Ss3.gif|Screenshot 3]]<br/><br />
<br/><br />
[[Image:Ss4.gif|Screenshot 4]]<br/><br />
<br />
===Credits===<br />
<br />
Created By:<br/><br />
Jonathan Rupert<br/><br />
Nicholas Jones<br/><br />
David Bleaking<br/><br />
<br/><br />
Note: Game coded from scratch, not found on web!</div>Djbleakihttps://wiki.expertiza.ncsu.edu/index.php?title=CSC_216/s08/esteem_patriotism&diff=11364CSC 216/s08/esteem patriotism2008-04-21T02:38:17Z<p>Djbleaki: Example</p>
<hr />
<div>===Formatting Resources===<br />
[http://meta.wikimedia.org/wiki/Help:Wikitext_examples Formatting Help Guide from MetaWiki]<br />
<br />
==Family Feud Java Style==<br />
<br />
It's Family Feud with a Java twist, what more could you ask for in a Java learning exercise?<br />
<br />
===The Problem===<br />
<br />
Every student has their problem with memory recall, this game is designed to help eliminate that process. It gets the entire class involved so that no one is left out and can be preformed in a feasible amount of time!<br />
<br />
===Participants and Props===<br />
<br />
Anyone can participate in the row style competition all you need is a working computer with Microsoft .NET framework in order to run the game.<br />
<br />
===Uses!===<br />
NOTE: This game can be used for more than just vocabulary!!!<br/> <br />
-> It can also be used to enhance association of certain topics, in other words, helping understand what goes with what!<br/><br />
-> Since answer length is unlimited, the game can be used for more than just vocabulary in that sense as well. The only thing to remember about that is the game only displays the first 50 characters of the answer but the answer can be any desired length.<br/><br />
<br />
This game can be used in many different ways to help aid in the teaching of Java subjects. This program can be used as an evaluation of class knowledge on the current topic. For instance, one of the questions in this game is Name 7 common Stack and Queue methods. This type of questions gets students to remember and recall all of the common methods of Stack and Queue thereby effectively reassuring that each student has a good understanding of how to write and format Stack and Queue classes. Below is a list of the current questions included with the game: <br/><br />
<br/><br />
Please note that questions, answers, and points can be changed to fit the classes needs whenever the game is used, so essentially, the game can be used to help teach any subject.<br/><br />
<br/><br />
Name 7 Errors Java Programmers Make<br/><br />
Name 7 Characteristics of linked lists and recursion<br/><br />
Name 7 Common Stack and Queue Methods<br/><br />
Name 7 FSM and Binary Search Tree components<br/><br />
Name 7 Common Exceptions<br/><br />
<br />
===The Script===<br />
<br />
Family Fued Java Style Rules:<br/><br />
<br/><br />
(1) - Each team's turn is indicated by the label in the top right of the screen<br/><br />
(2) - The team will have 30 seconds to come up with an answer to the question<br/><br />
(3) - Each team has 3 wrong answers before their turn is over<br/><br />
(4) - The game continues until all of the answers have been given or the give up button is clicked<br/><br />
(5) - The game ends when the participating parties choose to end it as long as each group has had a turn! This game can be preformed in 20 minutes or less!!!<br/><br />
(6) - The team with the highest score at the end of the game is the winner<br />
<br />
===Read Me===<br />
<br />
PLEASE READ THIS! <br/><br />
This game link comes as a zip file with all the required files in order to run the game. I have also included the source files for those interested, but they are not necessary in order to change the game information, etc.<br/><br />
<br/><br />
Note: All files are pre-formatted! This information is only for those who want to make their own changes to the game information!<br />
<br />
Questions.txt:<br/><br />
The questions file should be formatted with one question per line and each question may be no more than 100 characters long.<br/><br />
<br/><br />
Answers.txt:<br/><br />
There must be 7 answers per question, no more, no less<br/><br />
Each answer should be on one line and to distinguish between questions "&&&" should be entered as a delimiter.<br/><br />
<br/><br />
Points.txt:<br/><br />
Same as the answers, there must be 7 point values<br/><br />
Each point value should be on one line and to distinguish between questions "&&&" should be entered as a delimiter.<br/><br />
<br />
===Game Link===<br />
Please test out the game for yourself!!!<br/><br />
<br/><br />
[http://www.hopewellheadliners.com/java/dotnetfx.exe Microsoft .NET Framework]<br/><br />
[http://www.hopewellheadliners.com/java/familyfeudjavastyle.zip Family Feud Java Style]<br />
<br />
===Example===<br />
For example, let's say that your Java class is learning about common exceptions.<br />
Before class, complete the following: <br />
First, write the question into the Questions.txt file. Ensure that it is the only question.<br />
Next, write down your top seven answers, in order, in the Answers.txt file.<br />
Ensure that the point values are properly entered in the Points.txt file. <br />
<br />
Now, when you wish to review common exceptions in your class, do the following:<br />
First divide the class into teams.<br />
Begin the program, and allow the teams to play through the game.<br />
End the game when each team gives up, or all answers have been found.<br />
<br />
===Screenshots===<br />
Note: Screenshots have been changed!!! The previous ones were from my testing period when I was using any question to make sure the game worked.<br/><br />
The following are from the final stages<br/><br />
<br/><br />
[[Image:Ss1.gif|Screenshot 1]]<br/><br />
<br/><br />
[[Image:Ss2.gif|Screenshot 2]]<br/><br />
<br/><br />
[[Image:Ss3.gif|Screenshot 3]]<br/><br />
<br/><br />
[[Image:Ss4.gif|Screenshot 4]]<br/><br />
<br />
===Credits===<br />
<br />
Created By:<br/><br />
Jonathan Rupert<br/><br />
Nicholas Jones<br/><br />
David Bleaking<br/><br />
<br/><br />
Note: Game coded from scratch, not found on web!</div>Djbleakihttps://wiki.expertiza.ncsu.edu/index.php?title=CSC_216/s08/make_clear&diff=11068CSC 216/s08/make clear2008-04-04T03:32:00Z<p>Djbleaki: </p>
<hr />
<div>Formatting Resources:<br />
[http://meta.wikimedia.org/wiki/Help:Wikitext_examples Formatting Help Guide from MetaWiki]<br />
<br />
<br />
=Javadash: Inheritance Edition=<br />
<br />
This is a game designed to aid students of Java with learning newly introduced topics, inluding methods and terminology. For this particular example, we chose to teach Inheritance.<br />
<br />
==Why play this game instead of another?==<br />
<br />
Javadash is a game meant to focus on the introductory terms associated with any given Java topic. We believe that it is beneficial to a student's learning because it promotes the early learning of definitions relating to the topic. We chose Inheritance for our example because it is a difficult topic for students to understand since linear code has been the standard for many generations in programming, and can benefit any programmer by improving your program's flexibility and robustness.<br />
<br />
==Number of players==<br />
<br />
Javadash can either be played with individuals for their own review, or in a classroom setting. We reccomend that Javadash be played by three or four even teams. <br />
<br />
==Items needed to play==<br />
<br />
The only props that you will need to play this game is a stack of index cards. It is convenient to have prepared "official" cards in advance on the same style index cards that will be used by the participants. While this step is largely unnecessary, it allows you to anticipate the content and be able to focus on the lesson involved with the game.<br />
<br />
<br />
==Rules of the game==<br />
<br />
===Time required===<br />
This game is played in rounds, each typically lasting about 3 minutes, and should be played for at least 5 rounds to ensure fairness in scoring and to encourage optimal learning. Ensure every player/team has adequate index cards for the number of rounds you intend to play.<br />
<br />
===A typical round===<br />
<br />
Pick your first term, method, concept, etc to be defined by the players. Announce the term to the class, then instruct them to come up with their definition of the term. Give them 2 minutes to write down (note: teams may discuss the answer amongst themselves) their imitation of a textbook definition that might be found in the Java manual. When time is up, remind all players to put a group number on the index cards before you collect them. The idea with this game is for the players to make their definitions as real and accurate as possible so that another player or team will pick on their definition over the others.<br />
<br />
Shuffle the cards received with your official card, and read each one out slowly and confidently to the players. The players should be listening to determine which one they think is the official definition.<br />
<br />
Read the cards a second time. After each card is read, ask each player to write down which definition they believe was the official one. This is where you will score as follows:<br />
<br />
===Scoring===<br />
<br />
* Each player gets as many points as the number of votes that their team's definition recieved. <br />
* Additionally, each player who chose the official card receives one point.<br />
<br />
Continue playing for the specified number of rounds.<br />
<br />
Upon completion, the player with the highest score is the winner. Prizes are up to the game organizer, however they are highly suggested as it aids with the willingness to participate and learn.<br />
<br />
===Follow-up===<br />
<br />
After each round, repeat the term and its official definition. You may wish to prompt a discussion about the term to ensure that the students have learned the correct meaning of the term.<br />
<br />
<br />
==Game cards (prepared for you)==<br />
<br />
Here are some sample terms and their official definitions that you can use to play Javadash: Inheritance Edition.<br />
<br />
<br />
Inheritance - A mechanism for extending existing classes by adding methods and fields.<br />
<br />
Subclass - A more specialized class that inherits from the superclass.<br />
<br />
Superclass - A more generalized class from which a subclass inherits.<br />
<br />
Super - A keyword used to call a method of the superclass.<br />
<br />
Instanceof - An operator that tests whether an object belongs to a particular type.<br />
<br />
Abstract Method - A method whose implementation is not specified.<br />
<br />
Abstract Class - A class that cannot be instantiated.<br />
<br />
Protected - Designates a feature that can be accessed by all subclasses and all classes in the same package.<br />
<br />
Clone - A method that makes a new object with the same state as an existing object.<br />
<br />
==Video Example==<br />
Here is a link to a video that demonstrates a round of the game:<br />
[http://courses.ncsu.edu/csc216/lec/002/video/g4/ Video Example]<br />
<br />
==References==<br />
This game was inspired by:<br />
#Balderdash [http://en.wikipedia.org/wiki/Balderdash]<br />
#GLOSSARY: A Framegame for Reviewing Concepts [http://www.thiagi.com/game-glossary.html]</div>Djbleakihttps://wiki.expertiza.ncsu.edu/index.php?title=CSC_216/s08/make_clear&diff=11061CSC 216/s08/make clear2008-04-03T19:26:52Z<p>Djbleaki: </p>
<hr />
<div>Formatting Resources:<br />
[http://meta.wikimedia.org/wiki/Help:Wikitext_examples Formatting Help Guide from MetaWiki]<br />
<br />
<br />
=Javadash: Inheritance Edition=<br />
<br />
This is a game designed to aid students of Java with learning newly introduced topics, inluding methods and terminology. For this particular example, we chose to teach Inheritance.<br />
<br />
==Why play this game instead of another?==<br />
<br />
Inheritance can be a difficult topic for students to understand since linear code has been the standard for many generations in programming. This game attempts to remedy that by causing the students to analyze different definitions of varying degrees--from funny to serious to real--about the methodologies and concepts behind using inheritance to improve your program's flexibility and robustness.<br />
<br />
<br />
==Number of players==<br />
<br />
Javadash can either be played with individuals for their own review, or in a classroom setting. We reccomend that Javadash be played by three or four even teams. <br />
<br />
==Items needed to play==<br />
<br />
The only props that you will need to play this game is a stack of index cards. It is convenient to have prepared "official" cards in advance on the same style index cards that will be used by the participants. While this step is largely unnecessary, it allows you to anticipate the content and be able to focus on the lesson involved with the game.<br />
<br />
<br />
==Rules of the game==<br />
<br />
===Time required===<br />
This game is played in rounds, each typically lasting about 3 minutes, and should be played for at least 5 rounds to ensure fairness in scoring and to encourage optimal learning. Ensure every player/team has adequate index cards for the number of rounds you intend to play.<br />
<br />
===A typical round===<br />
<br />
Pick your first term, method, concept, etc to be defined by the players. Announce the term to the class, then instruct them to come up with their definition of the term. Give them 2 minutes to write down (note: teams may discuss the answer amongst themselves) their imitation of a textbook definition that might be found in the Java manual. When time is up, remind all players to put a group number on the index cards before you collect them. The idea with this game is for the players to make their definitions as real and accurate as possible so that another player or team will pick on their definition over the others.<br />
<br />
Shuffle the cards received with your official card, and read each one out slowly and confidently to the players. The players should be listening to determine which one they think is the official definition.<br />
<br />
Read the cards a second time. After each card is read, ask each player to write down which definition they believe was the official one. This is where you will score as follows:<br />
<br />
===Scoring===<br />
<br />
* Each player gets as many points as the number of votes that their team's definition recieved. <br />
* Additionally, each player who chose the official card receives one point.<br />
<br />
Continue playing for the specified number of rounds.<br />
<br />
Upon completion, the player with the highest score is the winner. Prizes are up to the game organizer, however they are highly suggested as it aids with the willingness to participate and learn.<br />
<br />
===Follow-up===<br />
<br />
After each round, repeat the term and its official definition. You may wish to prompt a discussion about the term to ensure that the students have learned the correct meaning of the term.<br />
<br />
<br />
==Game cards (prepared for you)==<br />
<br />
Here are some sample terms and their official definitions that you can use to play Javadash: Inheritance Edition.<br />
<br />
<br />
Inheritance - A mechanism for extending existing classes by adding methods and fields.<br />
<br />
Subclass - A more specialized class that inherits from the superclass.<br />
<br />
Superclass - A more generalized class from which a subclass inherits.<br />
<br />
Super - A keyword used to call a method of the superclass.<br />
<br />
Instanceof - An operator that tests whether an object belongs to a particular type.<br />
<br />
Abstract Method - A method whose implementation is not specified.<br />
<br />
Abstract Class - A class that cannot be instantiated.<br />
<br />
Protected - Designates a feature that can be accessed by all subclasses and all classes in the same package.<br />
<br />
Clone - A method that makes a new object with the same state as an existing object.<br />
<br />
==Video Example==<br />
Here is a link to a video that demonstrates a round of the game:<br />
[http://courses.ncsu.edu/csc216/lec/002/video/g4/ Video Example]<br />
<br />
==References==<br />
This game was inspired by:<br />
#Balderdash [http://en.wikipedia.org/wiki/Balderdash]<br />
#GLOSSARY: A Framegame for Reviewing Concepts [http://www.thiagi.com/game-glossary.html]</div>Djbleakihttps://wiki.expertiza.ncsu.edu/index.php?title=CSC_216/s08/make_clear&diff=11060CSC 216/s08/make clear2008-04-03T19:23:39Z<p>Djbleaki: </p>
<hr />
<div>Formatting Resources:<br />
[http://meta.wikimedia.org/wiki/Help:Wikitext_examples Formatting Help Guide from MetaWiki]<br />
<br />
<br />
=Javadash: Inheritance Edition=<br />
<br />
This is a game designed to aid students of Java with learning inheritance methods and terminology. The game can be applied to many different concepts, but for this example, we chose Inheritance.<br />
<br />
==Why play this game instead of another?==<br />
<br />
Inheritance can be a difficult topic for students to understand since linear code has been the standard for many generations in programming. This game attempts to remedy that by causing the students to analyze different definitions of varying degrees--from funny to serious to real--about the methodologies and concepts behind using inheritance to improve your program's flexibility and robustness.<br />
<br />
<br />
==Number of players==<br />
<br />
Javadash can either be played with individuals for their own review, or in a classroom setting. We reccomend that Javadash be played by three or four even teams. <br />
<br />
==Items needed to play==<br />
<br />
The only props that you will need to play this game is a stack of index cards. It is convenient to have prepared "official" cards in advance on the same style index cards that will be used by the participants. While this step is largely unnecessary, it allows you to anticipate the content and be able to focus on the lesson involved with the game.<br />
<br />
<br />
==Rules of the game==<br />
<br />
===Time required===<br />
This game is played in rounds, each typically lasting about 3 minutes, and should be played for at least 5 rounds to ensure fairness in scoring and to encourage optimal learning. Ensure every player/team has adequate index cards for the number of rounds you intend to play.<br />
<br />
===A typical round===<br />
<br />
Pick your first term, method, concept, etc to be defined by the players. Announce the term to the class, then instruct them to come up with their definition of the term. Give them 2 minutes to write down (note: teams may discuss the answer amongst themselves) their imitation of a textbook definition that might be found in the Java manual. When time is up, remind all players to put a group number on the index cards before you collect them. The idea with this game is for the players to make their definitions as real and accurate as possible so that another player or team will pick on their definition over the others.<br />
<br />
Shuffle the cards received with your official card, and read each one out slowly and confidently to the players. The players should be listening to determine which one they think is the official definition.<br />
<br />
Read the cards a second time. After each card is read, ask each player to write down which definition they believe was the official one. This is where you will score as follows:<br />
<br />
===Scoring===<br />
<br />
* Each player gets as many points as the number of votes that their team's definition recieved. <br />
* Additionally, each player who chose the official card receives one point.<br />
<br />
Continue playing for the specified number of rounds.<br />
<br />
Upon completion, the player with the highest score is the winner. Prizes are up to the game organizer, however they are highly suggested as it aids with the willingness to participate and learn.<br />
<br />
===Follow-up===<br />
<br />
After each round, repeat the term and its official definition. You may wish to prompt a discussion about the term to ensure that the students have learned the correct meaning of the term.<br />
<br />
<br />
==Game cards (prepared for you)==<br />
<br />
Here are some sample terms and their official definitions that you can use to play Javadash: Inheritance Edition.<br />
<br />
<br />
Inheritance - A mechanism for extending existing classes by adding methods and fields.<br />
<br />
Subclass - A more specialized class that inherits from the superclass.<br />
<br />
Superclass - A more generalized class from which a subclass inherits.<br />
<br />
Super - A keyword used to call a method of the superclass.<br />
<br />
Instanceof - An operator that tests whether an object belongs to a particular type.<br />
<br />
Abstract Method - A method whose implementation is not specified.<br />
<br />
Abstract Class - A class that cannot be instantiated.<br />
<br />
Protected - Designates a feature that can be accessed by all subclasses and all classes in the same package.<br />
<br />
Clone - A method that makes a new object with the same state as an existing object.<br />
<br />
==Video Example==<br />
Here is a link to a video that demonstrates a round of the game:<br />
[http://courses.ncsu.edu/csc216/lec/002/video/g4/ Video Example]<br />
<br />
==References==<br />
This game was inspired by:<br />
#Balderdash [http://en.wikipedia.org/wiki/Balderdash]<br />
#GLOSSARY: A Framegame for Reviewing Concepts [http://www.thiagi.com/game-glossary.html]</div>Djbleakihttps://wiki.expertiza.ncsu.edu/index.php?title=CSC_216/s08/make_clear&diff=11059CSC 216/s08/make clear2008-04-03T19:21:50Z<p>Djbleaki: </p>
<hr />
<div>Formatting Resources:<br />
[http://meta.wikimedia.org/wiki/Help:Wikitext_examples Formatting Help Guide from MetaWiki]<br />
<br />
<br />
=Javadash: Inheritance Edition=<br />
<br />
This is a game designed to aid students of Java with learning inheritance methods and terminology. The game can be applied to many different concepts, but for this example, we chose Inheritance.<br />
<br />
==Why play this game instead of another?==<br />
<br />
Inheritance can be a difficult topic for students to understand since linear code has been the standard for many generations in programming. This game attempts to remedy that by causing the students to analyze different definitions of varying degrees--from funny to serious to real--about the methodologies and concepts behind using inheritance to improve your program's flexibility and robustness.<br />
<br />
<br />
==Number of players==<br />
<br />
We reccomend that Javadash be played by groups of classmates. Ideally, the game should be played with three or four even teams. <br />
<br />
==Items needed to play==<br />
<br />
The only props that you will need to play this game is a stack of index cards. It is convenient to have prepared "official" cards in advance on the same style index cards that will be used by the participants. While this step is largely unnecessary, it allows you to anticipate the content and be able to focus on the lesson involved with the game.<br />
<br />
<br />
==Rules of the game==<br />
<br />
===Time required===<br />
This game is played in rounds, each typically lasting about 3 minutes, and should be played for at least 5 rounds to ensure fairness in scoring and to encourage optimal learning. Ensure every player/team has adequate index cards for the number of rounds you intend to play.<br />
<br />
===A typical round===<br />
<br />
Pick your first term, method, concept, etc to be defined by the players. Announce the term to the class, then instruct them to come up with their definition of the term. Give them 2 minutes to write down (note: teams may discuss the answer amongst themselves) their imitation of a textbook definition that might be found in the Java manual. When time is up, remind all players to put a group number on the index cards before you collect them. The idea with this game is for the players to make their definitions as real and accurate as possible so that another player or team will pick on their definition over the others.<br />
<br />
Shuffle the cards received with your official card, and read each one out slowly and confidently to the players. The players should be listening to determine which one they think is the official definition.<br />
<br />
Read the cards a second time. After each card is read, ask each player to write down which definition they believe was the official one. This is where you will score as follows:<br />
<br />
===Scoring===<br />
<br />
* Each player gets as many points as the number of votes that their team's definition recieved. <br />
* Additionally, each player who chose the official card receives one point.<br />
<br />
Continue playing for the specified number of rounds.<br />
<br />
Upon completion, the player with the highest score is the winner. Prizes are up to the game organizer, however they are highly suggested as it aids with the willingness to participate and learn.<br />
<br />
===Follow-up===<br />
<br />
After each round, repeat the term and its official definition. You may wish to prompt a discussion about the term to ensure that the students have learned the correct meaning of the term.<br />
<br />
<br />
==Game cards (prepared for you)==<br />
<br />
Here are some sample terms and their official definitions that you can use to play Javadash: Inheritance Edition.<br />
<br />
<br />
Inheritance - A mechanism for extending existing classes by adding methods and fields.<br />
<br />
Subclass - A more specialized class that inherits from the superclass.<br />
<br />
Superclass - A more generalized class from which a subclass inherits.<br />
<br />
Super - A keyword used to call a method of the superclass.<br />
<br />
Instanceof - An operator that tests whether an object belongs to a particular type.<br />
<br />
Abstract Method - A method whose implementation is not specified.<br />
<br />
Abstract Class - A class that cannot be instantiated.<br />
<br />
Protected - Designates a feature that can be accessed by all subclasses and all classes in the same package.<br />
<br />
Clone - A method that makes a new object with the same state as an existing object.<br />
<br />
==Video Example==<br />
Here is a link to a video that demonstrates a round of the game:<br />
[http://courses.ncsu.edu/csc216/lec/002/video/g4/ Video Example]<br />
<br />
==References==<br />
This game was inspired by:<br />
#Balderdash [http://en.wikipedia.org/wiki/Balderdash]<br />
#GLOSSARY: A Framegame for Reviewing Concepts [http://www.thiagi.com/game-glossary.html]</div>Djbleakihttps://wiki.expertiza.ncsu.edu/index.php?title=CSC_216/s08/make_clear&diff=11058CSC 216/s08/make clear2008-04-03T19:17:56Z<p>Djbleaki: </p>
<hr />
<div>Formatting Resources:<br />
[http://meta.wikimedia.org/wiki/Help:Wikitext_examples Formatting Help Guide from MetaWiki]<br />
<br />
<br />
=Javadash: Inheritance Edition=<br />
<br />
This is a game designed to aid students of Java with learning inheritance methods and terminology. The game can be applied to many different concepts, but for this example, we chose Inheritance.<br />
<br />
==Why play this game instead of another?==<br />
<br />
Inheritance can be a difficult topic for students to understand since linear code has been the standard for many generations in programming. This game attempts to remedy that by causing the students to analyze different definitions of varying degrees--from funny to serious to real--about the methodologies and concepts behind using inheritance to improve your program's flexibility and robustness.<br />
<br />
<br />
==Number of players==<br />
<br />
We reccomend that Javadash be played by groups of classmates. Ideally, the game should be played with three or four even teams. <br />
<br />
==Items needed to play==<br />
<br />
The only props that you will need to play this game is a stack of index cards. It is convenient to have prepared "official" cards in advance on the same style index cards that will be used by the participants. While this step is largely unnecessary, it allows you to anticipate the content and be able to focus on the lesson involved with the game.<br />
<br />
<br />
==Rules of the game==<br />
<br />
===Time required===<br />
This game is played in rounds, each typically lasting about 3 minutes, and should be played for at least 5 rounds to ensure fairness in scoring and to encourage optimal learning. Ensure every player/team has adequate index cards for the number of rounds you intend to play.<br />
<br />
===A typical round===<br />
<br />
Pick your first term, method, concept, etc to be defined by the players. Announce the term to the class, then instruct them to come up with their definition of the term. Give them 2 minutes to write down (note: teams may discuss the answer amongst themselves) their imitation of a textbook definition that might be found in the Java manual. When time is up, remind all players to put a group number on the index cards before you collect them. The idea with this game is for the players to make their definitions as real and accurate as possible so that another player or team will pick on their definition over the others.<br />
<br />
Shuffle the cards received with your official card, and read each one out slowly and confidently to the players. The players should be listening to determine which one they think is the official definition.<br />
<br />
Read the cards a second time. After each card is read, ask each player to write down which definition they believe was the official one. This is where you will score as follows:<br />
<br />
===Scoring===<br />
<br />
* Each player gets as many points as the number of votes that their team's definition recieved. <br />
* Additionally, each player who chose the official card receives one point.<br />
<br />
Continue playing for the specified number of rounds.<br />
<br />
Upon completion, the player with the highest score is the winner. Prizes are up to the game organizer, however they are highly suggested as it aids with the willingness to participate and learn.<br />
<br />
===Follow-up===<br />
<br />
After each round, repeat the term and its official definition. You may wish to prompt a discussion about the term <br />
<br />
<br />
==Game cards (prepared for you)==<br />
<br />
Here are some sample terms and their official definitions that you can use to play Javadash: Inheritance Edition.<br />
<br />
<br />
Inheritance - A mechanism for extending existing classes by adding methods and fields.<br />
<br />
Subclass - A more specialized class that inherits from the superclass.<br />
<br />
Superclass - A more generalized class from which a subclass inherits.<br />
<br />
Super - A keyword used to call a method of the superclass.<br />
<br />
Instanceof - An operator that tests whether an object belongs to a particular type.<br />
<br />
Abstract Method - A method whose implementation is not specified.<br />
<br />
Abstract Class - A class that cannot be instantiated.<br />
<br />
Protected - Designates a feature that can be accessed by all subclasses and all classes in the same package.<br />
<br />
Clone - A method that makes a new object with the same state as an existing object.<br />
<br />
==Video Example==<br />
Here is a link to a video that demonstrates a round of the game:<br />
[http://courses.ncsu.edu/csc216/lec/002/video/g4/ LINK]<br />
<br />
==References==<br />
This game was inspired by:<br />
#Balderdash [http://en.wikipedia.org/wiki/Balderdash]<br />
#GLOSSARY: A Framegame for Reviewing Concepts [http://www.thiagi.com/game-glossary.html]</div>Djbleakihttps://wiki.expertiza.ncsu.edu/index.php?title=CSC_216/s08/make_clear&diff=11057CSC 216/s08/make clear2008-04-03T19:14:47Z<p>Djbleaki: </p>
<hr />
<div>Formatting Resources:<br />
[http://meta.wikimedia.org/wiki/Help:Wikitext_examples Formatting Help Guide from MetaWiki]<br />
<br />
<br />
=Javadash: Inheritance Edition=<br />
<br />
This is a game designed to aid students of Java with learning inheritance methods and terminology. The game can be applied to many different concepts, but for this example, we chose Inheritance.<br />
<br />
==Why play this game instead of another?==<br />
<br />
Inheritance can be a difficult topic for students to understand since linear code has been the standard for many generations in programming. This game attempts to remedy that by causing the students to analyze different definitions of varying degrees--from funny to serious to real--about the methodologies and concepts behind using inheritance to improve your program's flexibility and robustness.<br />
<br />
<br />
==Number of players==<br />
<br />
We reccomend that Javadash be played by groups of classmates. Ideally, the game should be played with three or four even teams. <br />
<br />
==Items needed to play==<br />
<br />
The only props that you will need to play this game is a stack of index cards. It is convenient to have prepared "official" cards in advance on the same style index cards that will be used by the participants. While this step is largely unnecessary, it allows you to anticipate the content and be able to focus on the lesson involved with the game.<br />
<br />
<br />
==Rules of the game==<br />
<br />
===Time required===<br />
This game is played in rounds, each typically lasting about 3 minutes, and should be played for at least 5 rounds to ensure fairness in scoring and to encourage optimal learning. Ensure every player/team has adequate index cards for the number of rounds you intend to play.<br />
<br />
===A typical round===<br />
<br />
Pick your first term, method, concept, etc to be defined by the players. Announce the term to the class, then instruct them to come up with their definition of the term. Give them 2 minutes to write down (note: teams may discuss the answer amongst themselves) their imitation of a textbook definition that might be found in the Java manual. When time is up, remind all players to put a group number on the index cards before you collect them. The idea with this game is for the players to make their definitions as real and accurate as possible so that another player or team will pick on their definition over the others.<br />
<br />
Shuffle the cards received with your official card, and read each one out slowly and confidently to the players. The players should be listening to determine which one they think is the official definition.<br />
<br />
Read the cards a second time. After each card is read, ask each player to write down which definition they believe was the official one. This is where you will score as follows:<br />
<br />
===Scoring===<br />
<br />
* Each player gets as many points as the number of votes that their team's definition recieved. <br />
* Additionally, each player who chose the official card receives one point.<br />
<br />
Continue playing for the specified number of rounds.<br />
<br />
Upon completion, the player with the highest score is the winner. Prizes are up to the game organizer, however they are highly suggested as it aids with the willingness to participate and learn.<br />
<br />
===Follow-up===<br />
<br />
After each round, repeat the term and its official definition. You may wish to prompt a discussion about the term <br />
<br />
<br />
==Game cards (prepared for you)==<br />
<br />
Here are some sample terms and their official definitions that you can use to play Javadash: Inheritance Edition.<br />
<br />
<br />
Inheritance - A mechanism for extending existing classes by adding methods and fields.<br />
<br />
Subclass - A more specialized class that inherits from the superclass.<br />
<br />
Superclass - A more generalized class from which a subclass inherits.<br />
<br />
Super - A keyword used to call a method of the superclass.<br />
<br />
Instanceof - An operator that tests whether an object belongs to a particular type.<br />
<br />
Abstract Method - A method whose implementation is not specified.<br />
<br />
Abstract Class - A class that cannot be instantiated.<br />
<br />
Protected - Designates a feature that can be accessed by all subclasses and all classes in the same package.<br />
<br />
Clone - A method that makes a new object with the same state as an existing object.<br />
<br />
==Video Example==<br />
Here is a link to a video that demonstrates a round of the game:<br />
[http://courses.ncsu.edu/csc216/lec/002/www/video/g4 LINK]<br />
<br />
==References==<br />
This game was inspired by:<br />
#Balderdash [http://en.wikipedia.org/wiki/Balderdash]<br />
#GLOSSARY: A Framegame for Reviewing Concepts [http://www.thiagi.com/game-glossary.html]</div>Djbleakihttps://wiki.expertiza.ncsu.edu/index.php?title=CSC_216/s08/make_clear&diff=11056CSC 216/s08/make clear2008-04-03T19:11:28Z<p>Djbleaki: </p>
<hr />
<div>Formatting Resources:<br />
[http://meta.wikimedia.org/wiki/Help:Wikitext_examples Formatting Help Guide from MetaWiki]<br />
<br />
<br />
=Javadash: Inheritance Edition=<br />
<br />
This is a game designed to aid students of Java with learning inheritance methods and terminology. The game can be applied to many different concepts, but for this example, we chose Inheritance.<br />
<br />
==Why play this game instead of another?==<br />
<br />
Inheritance can be a difficult topic for students to understand since linear code has been the standard for many generations in programming. This game attempts to remedy that by causing the students to analyze different definitions of varying degrees--from funny to serious to real--about the methodologies and concepts behind using inheritance to improve your program's flexibility and robustness.<br />
<br />
<br />
==Number of players==<br />
<br />
We reccomend that Javadash be played by groups of classmates. Ideally, the game should be played with three or four even teams. <br />
<br />
==Items needed to play==<br />
<br />
The only props that you will need to play this game is a stack of index cards. It is convenient to have prepared "official" cards in advance on the same style index cards that will be used by the participants. While this step is largely unnecessary, it allows you to anticipate the content and be able to focus on the lesson involved with the game.<br />
<br />
<br />
==Rules of the game==<br />
<br />
===Time required===<br />
This game is played in rounds, each typically lasting about 3 minutes, and should be played for at least 5 rounds to ensure fairness in scoring and to encourage optimal learning. Ensure every player/team has adequate index cards for the number of rounds you intend to play.<br />
<br />
===A typical round===<br />
<br />
Pick your first term, method, concept, etc to be defined by the players. Announce the term to the class, then instruct them to come up with their definition of the term. Give them 2 minutes to write down (note: teams may discuss the answer amongst themselves) their imitation of a textbook definition that might be found in the Java manual. When time is up, remind all players to put a group number on the index cards before you collect them. The idea with this game is for the players to make the definitions as real and accurate as possible so that another player or team will pick on their definition over anyone other including the official one.<br />
<br />
Shuffle the cards received with your official card, and read each one out slowly and confidently to the players. The players should be listening to determine which one they think is the official definition.<br />
<br />
Read the cards a second time. After each card is read, ask each player to write down which definition they believe was the official one. This is where you will score as follows:<br />
<br />
===Scoring===<br />
<br />
* Each player gets as many points as the number of votes that their team's definition recieved. <br />
* Additionally, each player who chose the official card receives one point.<br />
<br />
Continue playing for the specified number of rounds.<br />
<br />
Upon completion, the player with the highest score is the winner. Prizes are up to the game organizer, however they are highly suggested as it aids with the willingness to participate and learn.<br />
<br />
===Follow-up===<br />
<br />
After each round, repeat the term and its official definition. You may wish to prompt a discussion about the term <br />
<br />
<br />
==Game cards (prepared for you)==<br />
<br />
Here are some sample terms and their official definitions that you can use to play Javadash: Inheritance Edition.<br />
<br />
<br />
Inheritance - A mechanism for extending existing classes by adding methods and fields.<br />
<br />
Subclass - A more specialized class that inherits from the superclass.<br />
<br />
Superclass - A more generalized class from which a subclass inherits.<br />
<br />
Super - A keyword used to call a method of the superclass.<br />
<br />
Instanceof - An operator that tests whether an object belongs to a particular type.<br />
<br />
Abstract Method - A method whose implementation is not specified.<br />
<br />
Abstract Class - A class that cannot be instantiated.<br />
<br />
Protected - Designates a feature that can be accessed by all subclasses and all classes in the same package.<br />
<br />
Clone - A method that makes a new object with the same state as an existing object.<br />
<br />
==Video Example==<br />
Here is a link to a video that demonstrates a round of the game:<br />
[http://courses.ncsu.edu/csc216/lec/002/www/video/g4 LINK]<br />
<br />
==References==<br />
This game was inspired by:<br />
#Balderdash [http://en.wikipedia.org/wiki/Balderdash]<br />
#GLOSSARY: A Framegame for Reviewing Concepts [http://www.thiagi.com/game-glossary.html]</div>Djbleakihttps://wiki.expertiza.ncsu.edu/index.php?title=CSC_216/s08/make_clear&diff=11055CSC 216/s08/make clear2008-04-03T19:11:04Z<p>Djbleaki: Re-Write!</p>
<hr />
<div>Formatting Resources:<br />
[http://meta.wikimedia.org/wiki/Help:Wikitext_examples Formatting Help Guide from MetaWiki]<br />
<br />
<br />
=Javadash: Inheritance Edition=<br />
<br />
This is a game designed to aid students of Java with learning inheritance methods and terminology. The game can be applied to many different concepts, but for this example, we chose Inheritance.<br />
<br />
==Why play this game instead of another?==<br />
<br />
Inheritance can be a difficult topic for students to understand since linear code has been the standard for many generations in programming. This game attempts to remedy that by causing the students to analyze different definitions of varying degrees--from funny to serious to real--about the methodologies and concepts behind using inheritance to improve your program's flexibility and robustness.<br />
<br />
<br />
==Number of players==<br />
<br />
We reccomend that Javadash be played by groups of classmates. Ideally, the game should be played with three or four even teams. <br />
<br />
==Items needed to play==<br />
<br />
The only props that you will need to play this game is a stack of index cards. It is convenient to have prepared "official" cards in advance on the same style index cards that will be used by the participants. While this step is largely unnecessary, it allows you to anticipate the content and be able to focus on the lesson involved with the game.<br />
<br />
<br />
==Rules of the game==<br />
<br />
===Time required===<br />
This game is played in rounds, each typically lasting about 3 minutes, and should be played for at least 5 rounds to ensure fairness in scoring and to encourage optimal learning. Ensure every player/team has adequate index cards for the number of rounds you intend to play.<br />
<br />
===A typical round===<br />
<br />
Pick your first term, method, concept, etc to be defined by the players. Announce the term to the class, then instruct them to come up with their definition of the term. Give them 2 minutes to write down (note: teams may discuss the answer amongst themselves) their imitation of a textbook definition that might be found in the Java manual. When time is up, remind all players to put a group number on the index cards before you collect them. The idea with this game is for the players to make the definitions as real and accurate as possible so that another player or team will pick on their definition over anyone other including the official one.<br />
<br />
Shuffle the cards received with your official card, and read each one out slowly and confidently to the players. The players should be listening to determine which one they think is the official definition.<br />
<br />
Read the cards a second time. After each card is read, ask each player to write down which definition they believe was the official one. This is where you will score as follows:<br />
<br />
===Scoring===<br />
<br />
* Each player gets as many points as the number of votes that their team's definition recieved. <br />
* Additionally, each player who chose the official card receives one point.<br />
<br />
Continue playing for the specified number of rounds.<br />
<br />
Upon completion, the player with the highest score is the winner. Prizes are up to the game organizer, however they are highly suggested as it aids with the willingness to participate and learn.<br />
<br />
===Follow-up===<br />
<br />
After each round, repeat the term and its official definition. You may wish to prompt a discussion about the term <br />
<br />
<br />
==Game cards (prepared for you)==<br />
<br />
Here are some sample terms and their official definitions that you can use to play Javadash: Inheritance Edition.<br />
<br />
<br />
Inheritance - A mechanism for extending existing classes by adding methods and fields.<br />
<br />
Subclass - A more specialized class that inherits from the superclass.<br />
<br />
Superclass - A more generalized class from which a subclass inherits.<br />
<br />
Super - A keyword used to call a method of the superclass.<br />
<br />
Instanceof - An operator that tests whether an object belongs to a particular type.<br />
<br />
Abstract Method - A method whose implementation is not specified.<br />
<br />
Abstract Class - A class that cannot be instantiated.<br />
<br />
Protected - Designates a feature that can be accessed by all subclasses and all classes in the same package.<br />
<br />
Clone - A method that makes a new object with the same state as an existing object.<br />
<br />
==Video Example==<br />
Here is a link to a video that demonstrates a round of the game:<br />
[http://courses.ncsu.edu/csc216/lec/002/www/video/g4]<br />
<br />
==References==<br />
This game was inspired by:<br />
#Balderdash [http://en.wikipedia.org/wiki/Balderdash]<br />
#GLOSSARY: A Framegame for Reviewing Concepts [http://www.thiagi.com/game-glossary.html]</div>Djbleakihttps://wiki.expertiza.ncsu.edu/index.php?title=CSC_216/s08/make_clear&diff=10932CSC 216/s08/make clear2008-03-28T02:48:32Z<p>Djbleaki: </p>
<hr />
<div>Formatting Resources:<br />
[http://meta.wikimedia.org/wiki/Help:Wikitext_examples Formatting Help Guide from MetaWiki]<br />
<br />
<br />
=Javadash: Inheritance Edition=<br />
<br />
This is a game designed to aid students of Java with remembering inheritance methods and terminology. The original game with over-arching content was never produced since the related project detailed a topic choice of one and not all. If you would like to play the original game, please pick a topic or all topics and create the game in a similar fashion to this one.<br />
<br />
<br />
==Why play this game instead of another?==<br />
<br />
Inheritance can be a difficult topic for students to understand since linear code has been the standard for many generations in programming. This game attempts to remedy that by causing the students to analyze different definitions of varying degrees--from funny to serious to real--about the methodologies and concepts behind using inheritance to improve your program's flexibility and robustness.<br />
<br />
<br />
==Number of players==<br />
<br />
Javadash can be played with an array of players not less than 3, however the participants become more dissociated when there are greater than 30. The game may be played by individuals for up to 6 people, however for groups larger than 6 the game should be turned into teams of a mostly evenly divided player count. It is best played with three or four equal teams.<br />
<br />
<br />
==Items needed to play==<br />
<br />
The only props that you will need to play this game is a stack of index cards. It is convenient to have prepared "official" cards in advance on the same style index cards that will be used by the participants. While this step is largely unnecessary, it allows you to anticipate the content and be able to focus on the lesson involved with the game.<br />
<br />
<br />
==Rules of the game==<br />
<br />
===Time required===<br />
This game is played in rounds, each typically lasting about 3 minutes, and should be played for at least 5 rounds to ensure fairness in scoring and to encourage optimal learning. Ensure every player/team has adequate index cards for the number of rounds you intend to play.<br />
<br />
===A typical round===<br />
<br />
Pick your first term, method, concept, etc to be defined by the players. Give them 2 minutes to write down (note: teams may discuss the answer amongst themselves) their imitation of a textbook definition that might be found in the Java manual. When time is up, remind all players to put an identifying name on the index cards before you collect them. The idea with this game is for the players to make the definitions as real and accurate as possible so that another player or team will pick on their definition over anyone other including the official one.<br />
<br />
Shuffle the cards received with your official card, and read each one out slowly and confidently to the players. The players should be listening to determine which one they think is the official definition.<br />
<br />
Read the cards a second time. After each card is read, ask the players (or team) to raise their hand if they believe it was the official definition. This is where you will score as follows:<br />
<br />
===Scoring===<br />
<br />
*Each card gets as many points as the number of players who claimed it as official. These points go to the related player or team that created the definition.<br />
*If a player chooses a card that is not official, they lose a point.<br />
*Likewise, players who chose the official card receive a point.<br />
<br />
Continue playing for the specified number of rounds.<br />
<br />
Upon completion, the player or team with the highest score is the winner. Prizes are up to the game organizer, however they are highly suggested as it aids with the willingness to participate and learn.<br />
<br />
<br />
==Game cards (prepared for you)==<br />
<br />
Here are some sample terms and their official definitions that you can use to play Javadash: Inheritance Edition.<br />
<br />
<br />
Inheritance - A mechanism for extending existing classes by adding methods and fields.<br />
<br />
Subclass - A more specialized class that inherits from the superclass.<br />
<br />
Superclass - A more generalized class from which a subclass inherits.<br />
<br />
Super - A keyword used to call a method of the superclass.<br />
<br />
Instanceof - An operator that tests whether an object belongs to a particular type.<br />
<br />
Abstract Method - A method whose implementation is not specified.<br />
<br />
Abstract Class - A class that cannot be instantiated.<br />
<br />
Protected - Designates a feature that can be accessed by all subclasses and all classes in the same package.<br />
<br />
Clone - A method that makes a new object with the same state as an existing object.<br />
<br />
<br />
==References==<br />
This game was inspired by:<br />
#Balderdash [http://en.wikipedia.org/wiki/Balderdash]<br />
#GLOSSARY: A Framegame for Reviewing Concepts [http://www.thiagi.com/game-glossary.html]</div>Djbleakihttps://wiki.expertiza.ncsu.edu/index.php?title=CSC_216/s08/make_clear&diff=10931CSC 216/s08/make clear2008-03-28T02:48:08Z<p>Djbleaki: </p>
<hr />
<div>Formatting Resources:<br />
[http://meta.wikimedia.org/wiki/Help:Wikitext_examples Formatting Help Guide from MetaWiki]<br />
<br />
<br />
=Javadash: Inheritance Edition=<br />
<br />
This is a game designed to aid students of Java with remembering inheritance methods and terminology. The original game with over-arching content was never produced since the related project detailed a topic choice of one and not all. If you would like to play the original game, please pick a topic or all topics and create the game in a similar fashion to this one.<br />
<br />
<br />
==Why play this game instead of another?==<br />
<br />
Inheritance can be a difficult topic for students to understand since linear code has been the standard for many generations in programming. This game attempts to remedy that by causing the students to analyze different definitions of varying degrees--from funny to serious to real--about the methodologies and concepts behind using inheritance to improve your program's flexibility and robustness.<br />
<br />
<br />
==Number of players==<br />
<br />
Javadash can be played with an array of players not less than 3, however the participants become more dissociated when there are greater than 30. The game may be played by individuals for up to 6 people, however for groups larger than 6 the game should be turned into teams of a mostly evenly divided player count. It is best played with three or four equal teams.<br />
<br />
<br />
==Items needed to play==<br />
<br />
The only props that you will need to play this game is a stack of index cards. It is convenient to have prepared "official" cards in advance on the same style index cards that will be used by the participants. While this step is largely unnecessary, it allows you to anticipate the content and be able to focus on the lesson involved with the game.<br />
<br />
<br />
==Rules of the game==<br />
<br />
===Time required===<br />
This game is played in rounds, each typically lasting about 3 minutes, and should be played for at least 5 rounds to ensure fairness in scoring and to encourage optimal learning. Ensure every player/team has adequate index cards for the number of rounds you intend to play.<br />
<br />
===A typical round===<br />
<br />
Pick your first term, method, concept, etc to be defined by the players. Give them 2 minutes to write down (note: teams may discuss the answer amongst themselves) their imitation of a textbook definition that might be found in the Java manual. When time is up, remind all players to put an identifying name on the index cards before you collect them. The idea with this game is for the players to make the definitions as real and accurate as possible so that another player or team will pick on their definition over anyone other including the official one.<br />
<br />
Shuffle the cards received with your official card, and read each one out slowly and confidently to the players. The players should be listening to determine which one they think is the official definition.<br />
<br />
Read the cards a second time. After each card is read, ask the players (or team) to raise their hand if they believe it was the official definition. This is where you will score as follows:<br />
<br />
===Scoring===<br />
<br />
*Each card gets as many points as the number of players who claimed it as official. These points go to the related player or team that created the definition.<br />
*If a player chooses a card that is not official, they lose a point.<br />
*Likewise, players who chose the official card receive a point.<br />
<br />
Continue playing for the specified number of rounds.<br />
<br />
Upon completion, the player or team with the highest score is the winner. Prizes are up to the game organizer, however they are highly suggested as it aids with the willingness to participate and learn.<br />
<br />
<br />
==Game cards (prepared for you)==<br />
<br />
Here are some sample terms and their official definitions that you can use to play Javadash: Inheritance Edition.<br />
<br />
Term: Definition:<br />
<br />
Inheritance - A mechanism for extending existing classes by adding methods and fields.<br />
<br />
Subclass - A more specialized class that inherits from the superclass.<br />
<br />
Superclass - A more generalized class from which a subclass inherits.<br />
<br />
Super - A keyword used to call a method of the superclass.<br />
<br />
Instanceof - An operator that tests whether an object belongs to a particular type.<br />
<br />
Abstract Method - A method whose implementation is not specified.<br />
<br />
Abstract Class - A class that cannot be instantiated.<br />
<br />
Protected - Designates a feature that can be accessed by all subclasses and all classes in the same package.<br />
<br />
Clone - A method that makes a new object with the same state as an existing object.<br />
<br />
<br />
==References==<br />
This game was inspired by:<br />
#Balderdash [http://en.wikipedia.org/wiki/Balderdash]<br />
#GLOSSARY: A Framegame for Reviewing Concepts [http://www.thiagi.com/game-glossary.html]</div>Djbleakihttps://wiki.expertiza.ncsu.edu/index.php?title=CSC_216/s08/make_clear&diff=10930CSC 216/s08/make clear2008-03-28T02:46:48Z<p>Djbleaki: Added sample terms</p>
<hr />
<div>Formatting Resources:<br />
[http://meta.wikimedia.org/wiki/Help:Wikitext_examples Formatting Help Guide from MetaWiki]<br />
<br />
<br />
=Javadash: Inheritance Edition=<br />
<br />
This is a game designed to aid students of Java with remembering inheritance methods and terminology. The original game with over-arching content was never produced since the related project detailed a topic choice of one and not all. If you would like to play the original game, please pick a topic or all topics and create the game in a similar fashion to this one.<br />
<br />
<br />
==Why play this game instead of another?==<br />
<br />
Inheritance can be a difficult topic for students to understand since linear code has been the standard for many generations in programming. This game attempts to remedy that by causing the students to analyze different definitions of varying degrees--from funny to serious to real--about the methodologies and concepts behind using inheritance to improve your program's flexibility and robustness.<br />
<br />
<br />
==Number of players==<br />
<br />
Javadash can be played with an array of players not less than 3, however the participants become more dissociated when there are greater than 30. The game may be played by individuals for up to 6 people, however for groups larger than 6 the game should be turned into teams of a mostly evenly divided player count. It is best played with three or four equal teams.<br />
<br />
<br />
==Items needed to play==<br />
<br />
The only props that you will need to play this game is a stack of index cards. It is convenient to have prepared "official" cards in advance on the same style index cards that will be used by the participants. While this step is largely unnecessary, it allows you to anticipate the content and be able to focus on the lesson involved with the game.<br />
<br />
<br />
==Rules of the game==<br />
<br />
===Time required===<br />
This game is played in rounds, each typically lasting about 3 minutes, and should be played for at least 5 rounds to ensure fairness in scoring and to encourage optimal learning. Ensure every player/team has adequate index cards for the number of rounds you intend to play.<br />
<br />
===A typical round===<br />
<br />
Pick your first term, method, concept, etc to be defined by the players. Give them 2 minutes to write down (note: teams may discuss the answer amongst themselves) their imitation of a textbook definition that might be found in the Java manual. When time is up, remind all players to put an identifying name on the index cards before you collect them. The idea with this game is for the players to make the definitions as real and accurate as possible so that another player or team will pick on their definition over anyone other including the official one.<br />
<br />
Shuffle the cards received with your official card, and read each one out slowly and confidently to the players. The players should be listening to determine which one they think is the official definition.<br />
<br />
Read the cards a second time. After each card is read, ask the players (or team) to raise their hand if they believe it was the official definition. This is where you will score as follows:<br />
<br />
===Scoring===<br />
<br />
*Each card gets as many points as the number of players who claimed it as official. These points go to the related player or team that created the definition.<br />
*If a player chooses a card that is not official, they lose a point.<br />
*Likewise, players who chose the official card receive a point.<br />
<br />
Continue playing for the specified number of rounds.<br />
<br />
Upon completion, the player or team with the highest score is the winner. Prizes are up to the game organizer, however they are highly suggested as it aids with the willingness to participate and learn.<br />
<br />
<br />
==Game cards (prepared for you)==<br />
<br />
Here are some sample terms and their official definitions that you can use to play Javadash: Inheritance Edition.<br />
<br />
Term:<br />
Inheritance - A mechanism for extending existing classes by adding methods and fields.<br />
Subclass - A more specialized class that inherits from the superclass.<br />
Superclass - A more generalized class from which a subclass inherits.<br />
Super - A keyword used to call a method of the superclass.<br />
Instanceof - An operator that tests whether an object belongs to a particular type.<br />
Abstract Method - A method whose implementation is not specified.<br />
Abstract Class - A class that cannot be instantiated.<br />
Protected - Designates a feature that can be accessed by all subclasses and all classes in the same package.<br />
Clone - A method that makes a new object with the same state as an existing object.<br />
<br />
<br />
==References==<br />
This game was inspired by:<br />
#Balderdash [http://en.wikipedia.org/wiki/Balderdash]<br />
#GLOSSARY: A Framegame for Reviewing Concepts [http://www.thiagi.com/game-glossary.html]</div>Djbleakihttps://wiki.expertiza.ncsu.edu/index.php?title=CSC_216/s08/make_clear&diff=10705CSC 216/s08/make clear2008-03-26T19:13:20Z<p>Djbleaki: Update on participants and props</p>
<hr />
<div>Formatting Resources:<br />
[http://meta.wikimedia.org/wiki/Help:Wikitext_examples Formatting Help Guide from MetaWiki]<br />
<br />
=Javadash: Inheritance Edition=<br />
<br />
This is a game designed to aid students of Java with remembering inheritance methods and terminology. The original game with over-arching content was never produced since the related project detailed a topic choice of one and not all. If you would like to play the original game, please pick a topic or all topics and create the game in a similar fashion to this one.<br />
<br />
==Why play this game instead of another?==<br />
<br />
Inheritance can be a difficult topic for students to understand since linear code has been the standard for many generations in programming. This game attempts to remedy that by causing the students to analyze different definitions of varying degrees--from funny to serious to real--about the methodologies and concepts behind using inheritance to improve your program's flexibility and robustness.<br />
<br />
==Participants and props==<br />
<br />
The only props that you will need to play this game is a stack of index cards. Also, you will need to split the class into three or four equal teams. <br />
<br />
==The script==<br />
<br />
Describe how to do your exercise.<br />
<br />
<br />
<br />
==References==<br />
This game was inspired by:<br />
#Balderdash [http://en.wikipedia.org/wiki/Balderdash]<br />
#GLOSSARY: A Framegame for Reviewing Concepts [http://www.thiagi.com/game-glossary.html]</div>Djbleaki