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?
|