CS Contest: Games 2007GAMES2007 gives high school students a chance to demonstrate their computer science skills in a game design contest. Teams of up to 5 students will put together a game design and structure. In doing this, students will test their skills in areas fundamental to computer science and computer engineering. In the open-ended contest, students may focus on many aspects of the game structure, ranging from architecture, graphics and user interface, networking and user interaction, and game play and artificial intelligence. The teams that can put together the best designs and plans will win prizes. The contest is designed to be open-ended, and allow teams to expand on whichever areas of the game design they feel most comfortable with. Teams with graphics interest might develop the graphics/display aspects more than others, teams with networking interest might discuss the networked play options in more detail, teams with business interest might discuss that aspect in more detail, etc. Judging will be based on how thoroughly the students address all aspects of the program, as well as the creativity and originality involved in designing new aspects of the game or its implementation. Texas A&M Computer Science Contest: Games 2007Saturday, October 13, 2007Background: A key aspect of computer science is taking a large complex problem, subdividing it into more manageable parts, and describing how those parts will work together. This basic process happens across a wide range of computer science disciplines, from the design and development of large software projects, down to the design and implementation of small algorithms. In our contest, we'll focus on how this happens at the early design stages of computer game development. Usually, the earliest stage of game development involves the creation of a "design document." These design documents can take many forms, ranging from a few pages, to hundreds of pages of detailed information. Sometimes the document is split into several parallel parts. For example, there might be a "technical document" focusing on the implementation/programming aspects, an "artistic document" focusing on the art aspects, and an overall design document that includes other topics such as the philosophy behind the design. To get a better sense of what is involved in a design document, a few links are provided below. Your team's task is to create a game design document. You will be given a rough concept for a game. You will be expected to design a computer game based on that concept, and develop (something similar to) a design document for your proposed game. While a typical design document is a written document (with some figures), your team's design document will be created instead in a poster format. Your team will also have a short period of time to give an oral presentation overview of your design. Your team's design document may focus on only a part of the overall design - for example, a "technical" document. Regardless, however, your design document should be thorough, addressing all of the relevant components of the game design, and how those components work together. Design document links: Reviewing the following should help you to understand what is involved in a design document:
Judging: Judging will be based on three main criteria: Schedule: 8:15 - 9:00 Registration 9:00 - 9:30 Welcome and rules 9:30 - 9:45 Team room assignments 9:45 - 3:00 Teams compete 3:00 - 4:00 Oral presentations 4:00 - 4:30 Judges confer, Department presentation 4:30 - 5:00 Awards |
| ||||
| ||||