What am I supposed to be doing? And who was I supposed to send my assignments to? Hopefully, this page will help answer these kinds of questions for you.

Who should I send my designs and critiques to?

What were the domains we voted on during the first class meeting?

What software will we be looking at over the quarter?

What’s the assignment for…

Who should I send my designs and critiques to?

Each week, you should send your design to either Danny or Michael, along with two other students for critiques. Use the following class list to determine who your student critiquers will be; exactly who you send your design to depends on which design cycle we’re in.

K. C. Angus

Isabella Borrero

Betsy Denious

Lorelle Falk

Robert Harris

Piper Joseph

Heather Kay

Rachel Kern

Ashley LaFrenais

Elliot Malkin

Gabrielle Matese

Eva Marie Restel

Herbert Wang

Sandra Worley

What were the domains we voted on during the first class meeting?

During the first meeting, we sort-of voted on five domains that would be used for the design cycles. These domains were: mechanical troubleshooting (for a device of your choosing), taxonomy (biology), conflict resolution, art, and literature analysis.

What software will we be looking at over the quarter?

Check out the software schedule for the entire list or the assignments below for this week’s software.

Assignment For Week 2 (1/12/99) (revised 1/8)

• Go through the Create-a-World activity, available via anonymous ftp from Danny’s Mac, using WorldWatcher. Read the handout analyzing the Create-A-World framework using the Design Framework. Be prepared to discuss the activity with respect to the framework. Is the activity properly described? Does the framework capture the important elements of the activity? How does the framework work?
• Begin the first design cycle by analyzing the domain of mechanical troubleshooting in the context of a mechanical device of your choice. In other words, apply the first four questions listed in the D37 Design Framework to your mechanical troubleshooting domain.
• Make sure your write-up is in Word 6/95, html, or plain text formats. Make sure your name, the name of your two critiquers, and your assigned instructor are at the top of your write-up.
• To determine which students should critique your design, look at the class list above and e-mail your designs to the two people who follow you in the list (wrapping around to the beginning of the list if you’re near the end).
• Also e-mail your design to Michael, if your last name begins with A-K, or Danny, if your last name begins with L-W.
• When you complete your critiques, mail them back to the appropriate student and to that student’s associated instructor for that assignment, not necessarily to the same instructor that you sent your own design to.
• In order to make bookkeeping easier, please be sure to include "D37" in the header of your e-mail to your instructor. In addition, be sure to name your attached files appropriately – with the appropriate design cycle (1 for this assignment), whether your file is a design or a critique (and whose design it’s critiquing), and your initials or last name.

Assignment For Week 3 (1/19/99)

• Use Crisis in Krasnovia and the Knowledge Integration Environment (KIE) and complete the readings listed on their respective pages. Be prepared to discuss the software from an architectural perspective.
• Revise and extend your mechanical troubleshooting design, and then e-mail your assignments to the same people you did in the previous week.
• Reminder: Make sure your write-up is in Word 6/95, html, or plain text formats. Make sure your name, the name of your two critiquers, and your assigned instructor are at the top of your write-up.
• Reminder: In order to make bookkeeping easier, please be sure to include "D37" in the header of your e-mail to your instructor. In addition, be sure to name your attached files appropriately – with the appropriate design cycle (1rev1 for this assignment, or something like that), whether your file is a design or a critique (and whose design it’s critiquing), and your initials or last name.

Assignment For Week 4 (1/27/99)

• Use StarLogo and complete the necessary readings. (We were unable to acquire a copy of HyperGami, which was originally scheduled for this week). Be prepared to discuss the software from an architectural perspective.
• Complete your mechanical troubleshooting design, and then e-mail your assignments to the same people you did in the previous week.

Assignment For Week 5 (2/2/99)

• Use Rembrandt and BGuILE, completing the necessary readings. Be prepared to discuss the software from an architectural perspective.
• Do a domain analysis of your project topic approved by Danny.
• To determine which students should critique your design, look at the class list above, skip the two people you follow you, and e-mail your designs to the next two people on the list (wrapping around to the beginning of the list if you’re near the end).
• Also e-mail your design to Danny, if your last name begins with A-K, or to Michael, if your last name begins with L-W.
• When you complete your critiques, mail them back to the appropriate student and to that student’s associated instructor for that assignment, not necessarily to the same instructor that you sent your own design to.
• Two students will give design presentations each week, in the order of the alphabetical class list. So K. C. and Isabella will be giving presentations on 2/2, followed by Betsy and Lorelle…and so on.

Assignment For Week 6 (2/9/99) (Revised 2/2)

• Use the evaporation lab and GenScope, completing the necessary readings. Be prepared to discuss the software from an architectural perspective.
• Revise your domain analysis from last week; you do not need to answer any additional questions from the framework.
• Send your designs to the same critiquers as last week.
• When you complete your critiques, mail them back to the appropriate student and to that student’s associated instructor for that assignment, not necessarily to the same instructor that you sent your own design to.
• Two students will give design presentations each week, in the order of the alphabetical class list. Lorelle and Robert will be presenting on 2/9; Betsy had already presented with K. C. Gabrielle and Herb are also working together, so please keep that in mind when looking ahead to your presentation date. 

Assignment For Week 7 (2/16/99)

• Use Fire Commander and SimCity 2000. Be prepared to discuss the software from an architectural perspective.
• Move forward with your design project by completing the task analysis (all but the last question in the design framework).
• To determine which students should critique your design, look at the class list above, skip the four people you follow you, and e-mail your designs to the next two people on the list (wrapping around to the beginning of the list if you’re near the end).
• Also e-mail your design to Michael, if your last name begins with A-K, or to Danny, if your last name begins with L-W.
• When you complete your critiques, mail them back to the appropriate student and to that student’s associated instructor for that assignment, not necessarily to the same instructor that you sent your own design to.
• Piper and Heather will be presenting this week (with Rachel and Ashley on deck). 

Assignment For Week 8 (2/23/99)

• No software to play with this week; instead, three readings were handed out in class. Come prepared to discuss the pros and cons of the approaches to supporting learning that are described in the readings.
• Revise your design from the previous week. You do not need to add anything about feedback yet (that will come next week).
• E-mail your designs to the same critiquers you did last week.
• When you complete your critiques, mail them back to the appropriate student and to that student’s associated instructor for that assignment, not necessarily to the same instructor that you sent your own design to.
• Rachel and Ashley will be presenting this week (with Elliot and Gabrielle/Herb on deck).

Assignment For Week 9 (3/2/99)

• Use Choices Choices: On the Playground and EPA, completing the necessary readings. Be prepared to discuss the software from an architectural perspective.
• We’ve posted two short documents on designing educational software: Myths, Lures, Traps and Pitfalls and The 6 Habits of Highly Effective Course Designers. You should probably take a glance at both of these.
• Complete your design project, making revisions from the previous week and answering the last question in the framework.
• To determine which students should critique your design, look at the class list above, skip the six people you follow you, and e-mail your designs to the next two people on the list (wrapping around to the beginning of the list if you’re near the end).
• Also e-mail your design to Danny, if your last name begins with A-K, or to Michael, if your last name begins with L-W.
• When you complete your critiques, mail them back to the appropriate student and to that student’s associated instructor for that assignment, not necessarily to the same instructor that you sent your own design to.
• Elliot and Gabrielle/Herb will be presenting this week (with Eva Marie and Sandra on deck).

Assignment For Week 10 (3/9/99)

• Use the Collaboratory Notebook and the Progress Portfolio, completing the necessary readings. Be prepared to discuss the software from an architectural perspective.
• Make your final revisions on your design project.
• E-mail your designs to the same students and instructor as last week.
• Eva Marie and Sandra will be presenting this week.