Note: If you are reading this during the current semester, use the syllabus from my website




Contact Information(top)

Instructor: Dan Fleck
   Email:  dfleck (at) gmu.edu
   Phone: 703-993-4198
   AOL IM: danpf1

   Office: Engineering Building - 4440
   Office Hours: Thurs 3-4pm, or anytime by appointment


Class Location(top)

   CS    426 - 001 - 20952 -  1:30-4:10 Fri -  Innovation Hall 319
      

Course Outcomestop)

a) Become familiar with code maintenance

b) Realize the manner with which team work may be achieved in a programming environment

c) Understand the business processes required to complete a game for end use

d) Implement industry approaches to code testing and evaluation

e) Exhibit skills that demonstrate the ability to present a video game appropriately to business

partners


Textbooks (top)

None


Tools(top)
Grading Policy (top)


Game Project 50% Due during the last class period
Presentations  15% In class presentations
Final Exam 35% Fri. 5/7 1:30 pm – 4:15 pm
Total: 100%
Grades will be posted to courses.gmu.edu


GRADE APPEAL POLICY:
If you feel you deserve a better grade on an assignment, you can appeal your grade in writing. Written grade appeals will only be accepted within 7 days of you receiving the grade. The appeal should clearly explain why you feel you deserve a higher grade. I will never lower your grade due to an appeal, but I may or may not raise your grade depending on your justification.

LATE POLICY:
All work must be received by the deadline. No late homeworks will be accepted.

HONOR CODE STATEMENT:
As with all GMU courses, this course is governed by the GMU Honor Code. In this course, all assignments, exams, and project submissions carry with them an implicit statement that it is the sole work of the author, unless joint work is explicitly authorized. Help may be obtained from the instructor or other students to understand the description of the problem and any technology, but the solution, particularly the design portion, must be the student's own work. If joint work is authorized, all contributing students must be listed on the submission. Any deviation from this is considered an Honor Code violation, and as a minimum, will result in failure of the submission and as a maximum, failure of the class.

PLAGIARISM:
Plagiarism is stealing the work of others and presenting it as your own. This includes written papers, but also computer programs, presentations, etc... anything that was not created by you should be referenced. When in doubt, add a reference. If you have any questions about whether you can or cannot use something you've found ask your professor or TA. If another student let you copy their work you are BOTH guilty. Any plagiarism violations will be sent to the Honor Committee. If you are found guilty of plagiarism twice in your university career you will be expelled. This is a very serious offense! More information about plagiarism is on the writing center website and at plagiarism.org. If you feel the need to do this for any reason, come talk to your professor and we'll work out a better plan. There is ALWAYS a better plan than plagiarizing!

This class may use automated tools to detect plagiarism (including written materials and source code).

DISABILITY STATEMENT:
If you are a student with a disability and you need academic accommodations, please see me and contact the Disability Resource Center (DRC) at 703.993.2474. All academic accommodations must be arranged through that office.