7. ACE 2005: Newcastle, NSW, Australia

• Nicole Clark:
  Evaluating Student Teams Developing Unique Industry Projects. 21-30
  
• Nicole Clark, Pamela Davies, Rebecca Skeers:
  Self and Peer Assessment in Software Engineering Projects. 91-100
  
• Sally Clarke, Richard Thomas, Michael Adams:
  Developing Case Studies to Enhance Student Learning. 101-108
  
• Tony Clear, Diana Kassabova:
  Motivational Patterns in Virtual Team Collaboration. 51-58
  
• Quintin I. Cutts, Gregor E. Kennedy:
  Connecting Learning Environments Using Electronic Voting Systems. 181-186
  
• Ursula Dantin:
  Application of Personas in User Interface Design for Educational Software. 239-247
  
• Greg Dowling, Alan Tickle, Karen Stark, Jillian Rowe, Meredith Godat:
  Greg Dowling, Alan Tickle, Karen Stark, Jillian Rowe, and Meredith Godat. 151-154
  
• Henry Gardner, Chris Johnson, Geoff Leach, Pascal Vuylsteker:
  eScience curricula at two Australian universities. 211-216
  
• Sandy Garner, Patricia Haden, Anthony Robins:
  My Program is Correct But it Doesn t Run: A Preliminary Investigation of Novice Programmers Problems. 173-180
  
• Cecil Goldstein, Susanna Leisten, Karen Stark, Alan Tickle:
  Using a Network Simulation Tool to engage students in Active Learning enhances their understanding of complex data communications concepts. 223-228
  
• John Hamer, Kenneth T. K. Ma, Hugh H. F. Kwong:
  A Method of Automatic Grade Calibration in Peer Assessment. 67-72
  
• Barry Harper:
  Constructing High Quality Learning Settings. 3
  
• James M. Hogan, Glenn Smith, Richard Thomas:
  Tight Spirals and Industry Clients: The Modern SE Education Experience. 217-222
  
• James M. Hogan, Richard Thomas:
  Developing the Software Engineering Team. 203-210
  
• Heath A. James, Kenneth A. Hawick, Christie James:
  Teaching students how to be Computer Scientists through student projects. 259-267
  
• C. W. Johnson, Ian Barnes:
  Redesigning the Intermediate Course in Software Design. 249-258
  
• Geoffrey J. Kennedy:
  Peer-assessment in Group Projects: Is It Worth It? 59-65
  
• Raymond Lister:
  One Small Step Toward a Culture of Peer Review and Multi- Institutional Sharing of Educational Resources: A Multiple Choice Exam for First Semester Programming Students. 155-164
  
• Philip Machanick:
  Peer Assessment for Action Learning of Data Structures and Algorithms. 73-82
  
• Alistair Moffat, Baden Hughes, Harald Søndergaard, Paul Gruba:
  Making Connections: First Year Transition for Computer Science and Software Engineering Students. 229-238
  
• John Morris:
  Algorithm Animation: Using algorithm code to drive an animation. 15-20
  
• Janet Rountree, Nathan Rountree, Anthony Robins, Robert Hannah:
  Observations of Student Competency in a CS1 Course. 145-149
  
• Katherine Shaw, Julian R. Dermoudy:
  Engendering an Empathy for Software Engineering. 135-144
  
• Simon:
  Electronic Watermarks to Help Authenticate Soft-copy Exams. 7-13
  
• Richard C. Thomas, Amela Karahasanovic, Gregor E. Kennedy:
  An Investigation into Keystroke Latency Metrics as an Indicator of Programming Performance. 127-134
  
• Nghi Truong, Paul Roe, Peter Bancroft:
  Automated Feedback for "Fill in the Gap" Programming Exercises. 117-126
  
• Jodi Tutty, Barbara White, Robert Pascoe:
  Experiences from a wireless-enabled tablet classroom. 165-172
  
• Peter Vamplew, Julian R. Dermoudy:
  An Anti-Plagiarism Editor for Software Development Courses. 83-90
  
• Brian R. von Konsky, Jim Ivins, Mike Robey:
  Using PSP to Evaluate Student Effort in Achieving Learning Outcomes in a Software Engineering Assignment. 193-201
  
• Ian Warren:
  Teaching Patterns and Software Design. 39-49
  
• Marilyn A. Wells, Beverley D. Jones:
  Commonsense ISD: An empirical approach to teaching systems analysis and design. 31-37
  
• Karyn Woodford, Peter Bancroft:
  Multiple Choice Questions Not Considered Harmful. 109-116
  
• Tim Wright, James Noble, Stephen Marshall:
  Tim Wright James Noble Stephen Marshall. 187-192