As the teacher of this class, I see ECoDE as a useful tool and activity. It requires the same kind of design process as what I require, but with a greater level of specificity. People tend to put anything down for scenarios, while scenarios are important in ECoDE. ECoDE also encourages you to update your design as you code, which is what you have to do in real coding and design efforts in serious software development. (For example, in Enterprise software, sequence diagrams are used to describe object interactions, and they must be updated when methods are written differently than the design.) For these reasons, I'm requiring the use of ECoDE, at least for P3, P4, and P5. At P6 and P7, you have the option of hardcopy or ECoDE turnin.
As a researcher, we would like to gather information on how ECoDE works. That's the part where you have an option. You do NOT have to be a subject of the studies. If you say so, we throw all your usage data away and you can ignore all surveys. However, you still DO have to use ECoDE for at least three milestones.
|Thanks, Mark. I'm sure that relieves some of the pressure! I will make myself extra available in the States cluster/Commons area to help anyone with ECoDE: Tuesday, 3:00 - 4:30, Thursday, 1:45 - 4:15. Jonathan has office hours Wednesday from 11 - 1. Kathy Gray|