Schedule on Sunday, Oct 18 | 07:30–09:00 | Registration | 09:00–10:00 | Introduction Remarks and Activity | 10:00–11:15 | Session 1: Innovative Interface Design- Facilitating Testing and Debugging of Markov Decision Processes with Interactive Visualization
- Sean McGregor, Oregon State University, USA
- Spreadsheet interfaces for usable machine learning
- Advait Sarkar, University of Cambridge, UK
- Spreadsheet Programming for Collecting, Exploring and Publishing Web Data
- Kerry Chang, Carnegie Mellon University, USA
| 11:15–11:40 | Break (25 min) | 11:40–12:30 | Session 2: Promoting team development- Building Teams Over Distance- A Solution Through Digital Art Mediated Practices
- Mengyao Zhao, University of California, Irvine, USA
- Problem Formulation Affordances for Computer Supported Collaborative Problem Solving
- Robert Thompson, University of Washington, USA
| 12:30–14:00 | Lunch (90 min) | 14:00–15:15 | Session 3: Tool Notification and Annotations- Adapting Program Analysis Tool Notifications to the Individual Developer
- Brittany Johnson, North Carolina State, USA
- Improving Error Notification Comprehension inIDEs by Supporting Developer Self-Explanations
- Titus Barik, North Carolina State, USA
- Exploring the Usability and Effectiveness of Interactive Annotation and Code Review for the Detection of Security Vulnerabilities
- Tyler Thomas, University of North Carolina, Charlotte, USA
| 15:15–15:35 | Break (20 min) | 15:35–16:50 | Session 4: End Users and Novice Programmers- Process-Oriented Assessment of Development in App Inventor
- Mark Sherman, University of Massachusetts Lowell, USA
- Making Progress - Barriers to Success in End User Developers’ Physical Prototyping
- Tracy Booth, City University London, UK
- Blocks, Text, and the Space Between - The Role of Representations in Novice Programming Environments
- David Weintrop, Northwestern University, USA
| 16:50–17:00 | Concluding Remarks | 17:00–18:30 | Break and Walk to Dinner | 18:30–21:00 | Graduate Consortium Dinner |
Session Format and InstructionsEach student participant will have one 25-minute presentation slot (listed under the sessions above). Within each presentation slot, one panelist will be designated lead panelist, and one student participant will be designated lead peer. These assignments will be made several weeks prior to the conference, giving the leads time to review the presenter’s research abstract ahead of time. The format for each presentation slot will be as follows. Note that this format is intended to lend structure to the proceedings, but is not meant to be stifling. Thus, you may view these more as guidelines than as hard and fast rules. Presentation:You have 12 minutes to present your slides. This will be strictly enforced. Your first slide has to be 3 questions that you want help from the GC panel or your peers. Repeat these questions on the last slide, so that the panel and students know what to particularly focus on during the discussion time. As a few suggestions to help inspire you, here are some possible forms that the questions might take - Impact/relevance: I can focus my research on X or Y — which is more important?
- Risk management: I have identified X and Y as risks to the success of my work — which should I address first?
- Methodological: I want to investigate X, but I’m uncertain how to go about it — what should I do?
Role of lead peer/panelist:For each presentation, one student will play the role of "lead peer", and one panelist will play the role of "lead panelist". The lead panelist and lead peer collaboratively select and respond to one of the presenter's questions. Interactive discussion between the presenter and the leads is expected. The non-lead panelists/participants should let the leads first finish their discussion. If there is time left for the slot other questions can then be discussed. |
|
|