Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
Ducky Ethics Approval Form Draft Notes | ||||||||
Added: | ||||||||
> > | DEADLINES for minimal risk studies![]() | |||||||
Purpose: collect data on how students actually program in an IDE (Eclipse) and explore the data. If we find differences between the logs of high-scoring and low-scoring code development sessions, that could potentially be used to teaching and/or development tools. | ||||||||
Line: 43 to 44 | ||||||||
Question: who holds the id<->person mapping? Can it be destroyed after the data is submitted? Are we likely to want to do follow-up interviews? | ||||||||
Added: | ||||||||
> > | Forms needed:
13. Summary of researchPurpose and objectiveHypothesisJustificationMethodAnalysis15. Subject descriptionStudents in Computer Science XXX. Inclusion criteria: student in a computer science course which uses the Java programming language and has individually executed and graded assignments. Subjects must have at least one semester of familiarity with the the Eclipse development tool (which is already recommended) and be willing to use it again exclusively for this course.16. ExcludedPeople who are not in CSXXX are excluded. Students who use a development environment other than Eclipse (approx N% last time this class was taught) are excluded.17. Approach to subjectsAnnouncement in class?20. Method@@@22a. How much time?
23. What risks?If the plug-in is not rock-solid stable, it could crash and cause the subject to lose work. (@@@ where do I put in that we want to make damn sure it doesn't crash) Long-term, if we can correlate24. Benefits?We hope that by participating in the study, the users will benefit indirectly from
|