| |
| META TOPICPARENT |
name="DuckyHomework" |
Ducky Thesis Proposal Notes
|
| |
- Group C will be experienced programmers -- professional code developers.
Group A will have nine participants; Groups B and C will have six to ten participants each. |
|
<
< | Each of the groups will be videotaped while they use Eclipse to perform three to five different (small) programming assignments on a large code base. Their interactions with Eclipse will be logged using the Mylar Monitor, and the Mylar Monitor logs and the videotape will be synchronized. |
>
> | For each study, I will observe two people from a given cohort pair-programming -- working (and talking) together -- using the Eclipse Integrated Development Environment (IDE) to perform three to five different (small) programming assignments on a large code base. |
| | |
|
<
< | The tasks will be designed to attempt to force the users to ask specific, relatively difficult types of questions. We expect that they will also ask a number of "easier" questions in the course of answering the more complex questions. |
>
> | Before the pair-programming starts, I will give the programmers a very brief survey to determine how much experience they have with programming in general, how much experience they have with Java, and how much experience they have with the Eclipse IDE. |
| | |
|
<
< | I will run pilots of the study with people in cohort A. Three pilots will be talk-aloud done by individual collaborators (who are sophisticated enough to give good talk-aloud data). In addition to the videotaping/Mylar Monitor logs, I will perform a semi-structured interview with these three people. These three tests and interviews will be used to iteratively improve the study design. |
>
> | I will videotape their interactions with each other. Their interactions with Eclipse will be logged using the Mylar Monitor, and the Mylar Monitor logs and the videotape will be synchronized. |
| | |
|
<
< | Two studies of cohort A will use pair-programming. In all five cases, I will do a semi-structured interview with the participants to gauge the effectiveness of the study. Afterwards, I will run two pilots with people drawn from the Group A pool, where they do the same tasks, but as a pair-programming team. (In addition to the data gathered from the team, this ensures that I will be competent to run the subsequent study.) |
>
> | (Note to Gail: I sort of think I'd also like to do a screen capture. Is there any downside to doing that?) |
| | |
|
<
< | Finally, I will run the study with at least three pair-programming teams from cohort B and three from cohort C. |
>
> | I will keep the code that they develop. While I do not forsee using the code, it is easy to keep it, minimally invasive, and potentially useful in unforseen ways.
The tasks will be designed to attempt to force the users to ask specific, relatively difficult types of questions. We expect that they will also ask a number of "easier" questions in the course of answering the more complex questions.
I will pilot the study with two pair-programming teams from cohort A. In addition to the videotaping and Mylar Monitor, I will do a semi-structured interview with the participants to gauge the effectiveness of the study. |
| | |
|
>
> | Finally, I will run the study with at least three pair-programming teams from cohort B and three from cohort C. |
| | |
Copyright © 2008-2025 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.