This page is being updated--readings are subject to change

CS 4665/7465:
Educational Technology:
Design and Evaluation

Time:TTh 1:30-3:00
Location:CCB 101
Instructor: Amy Bruckman
Office:CoC 255
(Email is best way to reach me.)
Office Hours:Find me after class or email for an appointment
Teaching Assistant: TBD
TA Email:



Available at the Georgia Tech bookstore, or click here to buy them from Amazon books with the profit from the sale going to buy pizza for students in this and other classes.


In this class, you immediately begin applying your knowledge of the theory of educational technology to design a piece of software. Consequently, you must already know something about it! To take this class, you must have completed either:

If you have equivalent experience from classes in another department or at another institution, speak to the instructor to request permission to enroll. No one without a solid theoretical background in this research area may take this class. (The issue is not just that you will have difficulty--it's also difficult to have class discussions if we have to stop and explain the basics to class members without background in this area.)

Course requirements are the same for graduate and undergraduate students, but I expect more depth in papers and projects by graduate students.

Focus of the Course

The course has two parts, each with a set of questions that we will be addressing:


Objectives of this course are for students to be able to:

So what are we going to do?

During the course of the semester, students will (alone or in groups of at most two):
  1. Design a piece of educational software,
  2. Implement that software, and
  3. Evaluate it (with at least four users, preferably a whole class if available).

There are no restrictions on the KIND of software (e.g., microworlds, construction kits, intelligent tutors) implemented, as long as the developers are willing to claim that the software facilitates learning and to evaluate that claim.

Most classes will be a discussion of one or two papers. Wherever possible, I have provided links to the authors' home pages. You are encouraged at least to browse through those pages.

Papers will be available either as handouts or on the web. You may wish to print web papers out before reading them.


Your grade will be based on these assignments:
  1. Preliminary software design (5%)
  2. Revised software design: (15%)
  3. Midterm design assignment: (35%)
  4. Evaluation plan (5%)
  5. Final evaluation assignment: (35%)
  6. Class participation (5%)

Suggested assignment lengths are approximate. Some people will do a good job in less and some will require many more pages. Please don't play games with the margins or fonts to try to make it come out a certain length--no one is counting. Don't worry about the page count--just make sure that you've completed the assignment well. Please remember to double space papers so I can write comments.

You will be graded primarily on the thoughtfulness of your design and evaluation process, as documented in your papers and presentations--the emphasis is not on the quality of your software. If you are working in a group, each team member must submit separate midterm and final papers. For other assignments, one per team is sufficient. Each team member must also participate in giving the in-class presentations.

Computing Resources

If you registered for the class and you already have a CoC account, you have been given access to College of Computing machine clusters (if you didn't have access already). If you register late, you should be added later automatically. If not, mail help@cc asking to be given access.

If you need a CoC account, you can get a request form in front of CoC 213. Complete the form and return it there.

CoC computing asks that:

Course Outline

All readings are subject to change.

Late Policy

Each student may have a total of three late days over the course of the semester. Once you've used those up, late work will be penalized. I always make an effort to return papers promptly; however, late papers may be returned substantially later.

Your presentations may not be late. Your final papers may not be late.

Hints for Successful Projects

Questions welcome--email