Conference Session

Software Engineering Topics

Collection

2007 Annual Conference & Exposition

Authors

Sheryl Duggins, Southern Polytechnic State University

Tagged Divisions

Software Engineering Constituent Committee

. http://www.swebok.org/documents/stoneman06/[11] Tripp, L. & Frailey, D. J. (Feb. 2, 1999) IEEE Computer Society and ACM Software Engineering Page 12.990.8 Coordinating Committee (SWECC) Overview.[12] Duggins, S. (March 2001) "Curriculum Impact of the Maturing Software Engineering Profession" in Proceedings in the 2001 ASEE Southeastern Section Conference.[13] ACM Council “A Summary of the ACM Position on Software Engineering as a Licensed Engineering Profession” (July 17, 2000) http://www.acm.org/serving/se_policy/selep_main.html[14] Notkin, D., Gorlick, M., & Shaw, M. (May 2000) An Assessment of Software

Conference Session

Software Engineering Topics

Collection

2007 Annual Conference & Exposition

Authors

Marcelo Jenkins, University of Costa Rica

Tagged Divisions

Software Engineering Constituent Committee

12.711.11http://www.sei.cmu.edu/pub/documents/99.reports/pdf/99tr032.pdf. Downloaded from the Web January 5, 2007.[6] M.L. Jaccheri, P. Lago, “Applying software process modeling and improvement in academic setting”, 10thConference on Software Engineering Education & Training (CSEET´97), 1997, IEEE Computer Society Press, pp:13-27.[7] B. Gannod, H. Koehnemann, K. Gary. “The Software Enterprise: Facilitating the Industry Preparedness ofSoftware Engineers”. Proceedings ASEE 2006, 2006.[8] B. Meyer, “Software engineering in the academy”, IEEE Computer, Vol. 34, Issue 5, May 2001, pp. 28-35.[9] http://www.asq.org/software/getcertified/index.html. Retrieved from the Web January 10, 2007.[10] B. S. Bloom, Taxonomy of Educational Objectives, Pearson

Conference Session

Software Engineering Topics

Collection

2007 Annual Conference & Exposition

Authors

Valentin Razmov, University of Washington

Tagged Divisions

Software Engineering Constituent Committee

students (instead of smaller teams, like many other CS courses have)MC Different teams working on different project ideas (as opposed to working on the same project)MC The project idea that your team developedMC The shared project space of your team (e.g., wiki pages, repositories, etc.)MC The official course website: announcements, course schedule (with slides and videos) resources, milestone submissionsFF Which portion(s) of the course website were most useful to you?MC The class mailing listMC Your team’s mailing list (or other electronic communication medium you used)MC Your team’s project scheduleMC Your team’s project specificationMC Your team’s architecture and design documentsMC Your team’s test