ACM Home Page
Please provide us with feedback. Feedback
Large team projects in software engineering courses
Full text PdfPdf (63 KB)
Source Technical Symposium on Computer Science Education archive
Proceedings of the 36th SIGCSE technical symposium on Computer science education table of contents
St. Louis, Missouri, USA
SESSION: Software engineering projects table of contents
Pages: 137 - 141  
Year of Publication: 2005
ISBN:1-58113-997-7
Also published in ...
Authors
David Coppit  The College of William and Mary, Williamsburg, VA
Jennifer M. Haddox-Schatz  Daniel H. Wagner Associates, Inc., Hampton, VA
Sponsors
SIGCSE: ACM Special Interest Group on Computer Science Education
ACM: Association for Computing Machinery
Publisher
ACM  New York, NY, USA
Bibliometrics
Downloads (6 Weeks): 11,   Downloads (12 Months): 63,   Citation Count: 5
Additional Information:

abstract   references   cited by   index terms   collaborative colleagues  

Tools and Actions: Request Permissions Request Permissions    Review this Article  
DOI Bookmark: Use this link to bookmark this Article: http://doi.acm.org/10.1145/1047344.1047400
What is a DOI?

ABSTRACT

A key goal of educators teaching software engineering is to provide students with useful experience that will benefit them after graduation. A key component of this experience is usually a class project that is meant to expose students to the issues associated with real software development efforts. Unfortunately, educators rarely have the time required to manage software projects in addition to their normal pedagogical duties. As a result, many software engineering courses compromise the project experience by reducing the team sizes, project scope, and risk. In this paper, we present an approach to teaching a one-semester software engineering course in which approximately 30 students work together to construct a moderately sized (22 KLOC) software system. This approach provides a more realistic project experience for the students, without incurring significant managerial overhead for the instructor. We present our experiences using the approach for the spring 2004 software engineering course at The College of William and Mary.


REFERENCES

Note: OCR errors may be found in this Reference List extracted from the full text article. ACM has opted to expose the complete List rather than only correct and linked references.

 
1
 
2
Bertrand meyer. Software engineering in the academy. URL: BiBTeXhttp://archive.eiffel.com/doc/manuals/technology/bmarticles/computer/teaching.pdf.
3
 
4
 
5
 
6
M. Shaw and J. Tomayko. Models for undergraduate project courses in software engineering. Technical Report CMU/SEI-91-TR-010, Software Engineering Institute, 1991.
 
7
Mary Shaw. We can teach software better. Computing Research News, 4(4):2--4, 12, September 1992.
8
 
9
TuxMonkey.com. The issue tracker homepage. URL: BiBTeXhttp://www.issue-tracker.com/.


Collaborative Colleagues:
David Coppit: colleagues
Jennifer M. Haddox-Schatz: colleagues