Instructor recommendations for running a module-development course project¶
Strategy · All strategies
Evidence · no claims cited
Description¶
The authors distill their AY201b experience into implementable steps: "we recommend beginning the module development project by providing students with brief in-class tutorials of the software technologies"; hold regular consultations with an initial proposal and early in-class presentations for feedback and peer-teaching; require written explanatory material; and make a narrated video tour available. For computationally inexperienced classes they recommend lower-barrier technologies (WWT and Wolfram CDF).
Design Implications¶
Context¶
Requirements¶
- Teaching staff time for tutorials (the authors spent two hours over two class periods) and for regular consultations evaluating project scope.
Constraints¶
- Technical barriers may halt progress; instructors may need to help students find workarounds or contact other experts.
Target Learners¶
- graduate students in science courses
Target Learning Goals¶
- project-based learning
- scientific communication
- software development for education
Related Strategies¶
Examples¶
-
Key Sources¶
- Nathan E. Sanders, Chris Faesi, Alyssa A. Goodman. (2013). A New Approach to Developing Interactive Software Modules through Graduate Education. https://arxiv.org/abs/1308.1908
Page metadata
| Field | Value |
|---|---|
type |
strategy |
id |
module-development-course-recommendations |
title |
Instructor recommendations for running a module-development course project |
description |
The authors distill their AY201b experience into implementable steps: "we recommend beginning the module development project by providing students with brief in-class tutorials of the software technologies"; hold regu... |
status |
review |
generated |
by process:wiki-ingest on 2026-09-26 |
trust |
unverified — no one has confirmed this page's content |
sources |
1 — nathan-e-sanders-2013 |
Frontmatter is the page's machine-readable record — see the Schema & Guide.