Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
Ducky Ethics Approval Form Draft NotesDEADLINES for minimal risk studies![]() | ||||||||
Line: 120 to 120 | ||||||||
13. Summary of researchBackground | ||||||||
Changed: | ||||||||
< < | Integrated Development Environments (IDEs) are the principal tools used by computer scientists to write and/or modify software. | |||||||
> > | Integrated Development Environments (IDEs) are the principal tools used by computer scientists to write and/or modify software. Developers edit, share, delete, rename, and view files, generate executables, and debug those executables with their IDE(s). In other research by the PI, a plug-in (MylarMonitor) was developed for the popular Eclipse IDE that can log user interactions with Eclipse. While the actual source code is not logged, MylarMonitor can log every time a developer presses a button, pulls down a menu, presses a keyboard shortcut, etc. | |||||||
Purpose and objective | ||||||||
Changed: | ||||||||
< < | We hope to learn to recognize specific techniques that software developers use that correlate with the quality of the code that they generate. | |||||||
> > | We hope to learn to recognize specific patterns that developers use that correlate with the skill of the programmer as measured by the quality of their code submissions. Understanding these patterns can potentially be used to improve the teaching/training of computer scientists and the usability of IDEs. | |||||||
Changed: | ||||||||
< < | HypothesisHypothesis: when developers interact with IDEs, there are usage patterns whose appearance or frequency correlate with the skill of the programmer as measured by the quality of their code submissions. | |||||||
> > | Hypothesis: when developers interact with IDEs, there are usage patterns whose appearance and/or frequency correlate with the quality of the code generated. | |||||||
Changed: | ||||||||
< < | JustificationMethodAnalysis | |||||||
> > | 14. how many20-200 subjects, 0 controls | |||||||
15. Subject description | ||||||||
Changed: | ||||||||
< < | Students 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. Excluded | ||||||||
Changed: | ||||||||
< < | People 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. | |||||||
> > | People who do not meet the above criteria are excluded. | |||||||
17. Approach to subjects | ||||||||
Changed: | ||||||||
< < | Announcement in class? | |||||||
> > | The co-investigator will make an announcement in class requesting participation. Via the course staff, a notice will also be posted in the course newsgroup. | |||||||
20. MethodIn all experiments, students will be asked to download a plug-in for Eclipse, to turn on logging when they work on their assignments for the particular class, turn off logging when they are working on a different assignment, and to hand in their log file when they hand in their assignment. | ||||||||
Changed: | ||||||||
< < | We will also need cooperation from the instructor and/or teaching assistant to provide us with the assignment submission, log file, and grade for the assignment. | |||||||
> > | We will also need cooperation from the CS @@@ instructor and/or teaching assistant to provide us with the assignment submission, log file, and grade for the assignment. | |||||||
22a. How much time?
|
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
Ducky Ethics Approval Form Draft NotesDEADLINES for minimal risk studies![]() | ||||||||
Line: 49 to 49 | ||||||||
| ||||||||
Added: | ||||||||
> > | Where are the dang forms??? @@@ | |||||||
| ||||||||
Added: | ||||||||
> > | 1. PIMurphy, Gail C. Professor Science/Computer Science N/A N/A N/A +1-604/822-5169 ph +1-604/822-5485 fax murphy at cs.ubc.ca2. minimal risk@@@ Is this minimal risk? The Tri-Council Policy Statement sure seems to imply that, but this is not a questionnaire or use of prior information. Wolfman's paper seems to imply that we are minimal risk.3. fundingNOT funded by for-profit sponsor4. whereUBC (also UVic?)5. titleDeveloper interaction patterns as predictors of code quality @@@ maybe just Finding developer interaction patterns no additional title proposed period: 2007/01/01 to 2007/05/01 @@@?6. requirements@@@ need to know if this is minimal risk or not I need to do a consent form... DuckyEthicsConsentForm see about getting other consent forms from Gail7. Signaturesneed Gail and Bill8. ContactI assume Gail is the contact, see info from 1. address: 201-2366 Main Mall, V6T 1Z49. Co-investigatorSHERWOOD Kaitlin Duck Graduate Science @@@?/CPSC N/A Vancouver N/A N/A9c qualificationsThe principal investigator (Gail Murphy) and co-investigator (Kaitlin Sherwood) will conduct the studies. Dr. Murphy totally rocks@@@. Ms. Sherwood is currently a graduate student at UBC and has been a teaching assistant for two upper-division Human-Computer Interaction classes (CPSC 344 and 444), both of which include instruction on both human subjects procedures and experimental procedures. (@@@More?@@@: She has approximately fifteen years of industrial experience and has authors two books.)9d TCPS tutorialyep10 Funding source@@@ not sure11 peer reviewno? supposed to get committee approval?12 other institutions@@@ don't know | |||||||
13. Summary of research | ||||||||
Added: | ||||||||
> > | BackgroundIntegrated Development Environments (IDEs) are the principal tools used by computer scientists to write and/or modify software. | |||||||
Purpose and objective | ||||||||
Added: | ||||||||
> > | We hope to learn to recognize specific techniques that software developers use that correlate with the quality of the code that they generate. | |||||||
Hypothesis | ||||||||
Added: | ||||||||
> > | Hypothesis: when developers interact with IDEs, there are usage patterns whose appearance or frequency correlate with the skill of the programmer as measured by the quality of their code submissions. | |||||||
JustificationMethodAnalysis | ||||||||
Line: 92 to 164 | ||||||||
| ||||||||
Added: | ||||||||
> > |
<--
|
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
Ducky Ethics Approval Form Draft NotesDEADLINES for minimal risk studies![]() | ||||||||
Line: 71 to 71 | ||||||||
Announcement in class?
20. Method | ||||||||
Changed: | ||||||||
< < | @@@ | |||||||
> > | In all experiments, students will be asked to download a plug-in for Eclipse, to turn on logging when they work on their assignments for the particular class, turn off logging when they are working on a different assignment, and to hand in their log file when they hand in their assignment. We will also need cooperation from the instructor and/or teaching assistant to provide us with the assignment submission, log file, and grade for the assignment. | |||||||
22a. How much time?
| ||||||||
Line: 82 to 84 | ||||||||
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) | ||||||||
Changed: | ||||||||
< < | Long-term, if we can correlate | |||||||
> > | Long-term, if we can correlate patterns in usage logs to coding performance, there are two dangers:
| |||||||
24. Benefits? | ||||||||
Changed: | ||||||||
< < | We hope that by participating in the study, the users will benefit indirectly from
| |||||||
> > | We hope that by participating in the study, the users will benefit indirectly from improvements in development tools and/or teaching methods that result from this study.
| |||||||
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
|
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
Added: | ||||||||
> > |
Ducky Ethics Approval Form Draft NotesPurpose: 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. Subjects: students in a computer science class which uses Eclipse/Java for individual programming assignments. Question: which level? 200 or 300 or both? which class? Needed from subjects: logs of their coding activity for each assignment plus the assignment handed in plus the grade that they got for the assignment. Also needed: someone to obfuscate identities, so that we don't know who did which assignment. Question: do we need to obfuscate what code is being modified? I don't think so, tho we probably want them to use Mylar to only give us that assignment's context. Question: do we want to keep track of which assignments belong to which students, or have each trace/handin/grade tuple be separate? Possible downsides for the student: slightly slower performance on Eclipse; feeling self-conscious while coding? Compensation: ? Possible follow-ons: look at differences between logs of professionals and students; between IDEs; between languages. Or if the logs say that the mechanics aren't that important, that the thinking is, then maybe diverge into testing thinking ability in various ways and seeing if we can do some remedial thinking training. (?) Potential harms:
|