Assessment

From NW-DCSD

Jump to: navigation, search

Contents

Assessment Overview

Assessment is the process of gathering and analyzing data/evidence and using that information for continual improvement. The NWDCSD project community will participate in three primary types of assessment: User, Course/Module, and Project. Project participants will use a series of assessment tools adapted to this project's context and audience.


User Assessment

Questions to Answer: What does the user know prior to using the module and after? What is the student experience? What is the instructor experience in using the module in class?

Assessment Tools Currently Under Development/Being Piloted: 1) Student Pre-Module Survey; 2) Student Post-Module Survey; 3)Instructor Pre-Module Survey; 4) Instructor Post-Module Survey


Course/Module-Level Assessment

Question to Answer: Are the modules developing the intended objectives?

Assessment Tools Currently Under Development/Being Piloted: To date, all we have is a set of guidelines to follow when developing modules


Project-Level Assessment

Question to Answer: Is the project achieving its identified objectives?

Assessment Tools Currently Under Development/Being Piloted: 1) Teaching Beliefs/Practice Survey; 2) Computational Thinking Rubric


Frequently Asked Questions

What constitutes quality data?

Are there different types of assessment?

What are learning objectives?


More Information

For more on Outcomes Assessment, visit [1]

Note: Over time, this page will include links to related journal articles, templates, Barriers, surveys, IRB info, and a legal use policy for the open source modules.


Similar Projects and Their Approaches for Assessment

Sung: Game-Themed Introductory Programming Projects

Kelvin Sung, in his project (Game-Themed Introductory Programming Project) has have three categories of feedback forms each of which feeds into the overall project assessment:

  1. For independent faculty evaluating materials we have developed. Here is an example form (Word) we use for assessing our programming assignments.
  2. For students: collect per- and post- course attitude, and per-assignment opinion.
  3. For faculty: collect faculty's feedback on using the materials.

Please refer to this link on examples of forms we have used.

He discusses the rationale behind these forms in this paper and in this paper.

Personal tools