Reporting about Industrial Strength Software Engineering Courses for Undergraduates (bibtex)
by , , , , , ,
Abstract:
How do you organize an �industrial strength� one semester educational programming project for up to 200 second year students? This paper reports on four years of experience with such projects at the University of Paderborn and the University of Braunschweig. Key properties of our project design are: starting with an existing large application, regular hard deadlines with peer reviews and presentations to a large audience, working in groups, applying project and configuration management tools, a standard system architecture with interchangeable components and competing software agents, quality assurance and standard conformance testing through final overall system integration spanning all groups, and exposure to real-world project threats.
Reference:
Reporting about Industrial Strength Software Engineering Courses for Undergraduates (Matthias Gehrke, Holger Giese, Ulrich A. Nickel, Jörg Niere, Matthias Tichy, Jörg P. Wadsack, Albert Zündorf), In Proc. of the $24^th$ International Conference on Software Engineering (ICSE), Orlando, Florida, USA, ACM Press, 2002.
Bibtex Entry:
@InProceedings{GGN+02_ag,
AUTHOR = {Gehrke, Matthias and Giese, Holger and Nickel, Ulrich A. and Niere, Jörg and Tichy, Matthias and Wadsack, Jörg P. and Zündorf, Albert},
TITLE = {{Reporting about Industrial Strength Software Engineering Courses for Undergraduates}},
YEAR = {2002},
BOOKTITLE = {Proc. of the $24^th$ International Conference on Software Engineering (ICSE), Orlando, Florida, USA},
PAGES = {395-405},
PUBLISHER = {ACM Press},
URL = {http://www.upb.de/cs/ag-schaefer/Veroeffentlichungen/Quellen/Papers/2002/Edu_ICSE2002_Final.pdf},
ABSTRACT = {How do you organize an \^{a}��industrial strength\^{a}�� one semester educational programming project for up to 200 second year students? This paper reports on four years of experience with such projects at the University of Paderborn and the University of Braunschweig. Key properties of our project design are: starting with an existing large application, regular hard deadlines with peer reviews and presentations to a large audience, working in groups, applying project and configuration management tools, a standard system architecture with interchangeable components and competing software agents, quality assurance and standard conformance testing through final overall system integration spanning all groups, and exposure to real-world project threats.}
}
Powered by bibtexbrowser