Conference Session

Accreditation and Assessment in SE Programs

Collection

2011 ASEE Annual Conference & Exposition

Authors

Janet E. Burge, Miami University; Paul V. Anderson, Miami University, Ohio; Michael Carter, North Carolina State University; Gerald C. Gannod, Miami University; Mladen A. Vouk, North Carolina State University

Tagged Divisions

Software Engineering Constituent Committee

pts if some points are missing, 3 pts if the overall summary is missing or if some peer evaluation comments are not given a thoughtful response, 0 otherwise. In addition, significant point reductions may occur if any of the following are detected: 1. Use of any graphics, pictures, text without appropriate citations (the source MUST be given for any graphics used, etc.) 2. Lack of sensitivity towards the clients using the project 3. Inappropriate responses to audience questions5.3 Instructor supportsThe August 2010 workshop contained four sessions on teaching each of the fourcommunication skills—reading, writing, speaking, and teaming. These were designed tohelp project

Conference Session

Software Engineering Projects

Collection

2011 ASEE Annual Conference & Exposition

Authors

James N. Long, Oregon Institute of Technology; Linda Sue Young, Oregon Institute of Technology

Tagged Divisions

Software Engineering Constituent Committee

from the University of Virginia. She has served as department chair of the Communication Department and has taught a wide range of writing and communication courses. She was instrumental in the design of the bachelor’s degree in Communication Studies at OIT. Areas of interest include the overlap of game design and learning systems, media and the communication styles of Japan, creativity and communication, and conversation analysis. Page 22.1091.1 c American Society for Engineering Education, 2011 Multiplayer On-Line Role Playing Game Style Gradingin a Project Based Software Engineering

Conference Session

Software Engineering Projects

Collection

2011 ASEE Annual Conference & Exposition

Authors

Thomas Reichlmayr, Rochester Institute of Technology

Tagged Divisions

Software Engineering Constituent Committee

criteria. We elected not to have all teams develop the same app, but to let the teamscollaboratively define their own apps. In doing so the teams spent the initial part of the projectwriting their own user stories. One member of the team was appointed Product Owner to resolveproposed feature conflicts. This activity allowed everyone to participate in the writing andestimation of user stories. We included the initial development of user stories and Android bootcamp as Iteration Zero activities, with the exit criteria from Iteration Zero being that there wouldbe sufficient work defined to support the start of Sprint 1. Page 22.1712.5The instructor