Software studio: teaching professional software engineering

Authors:
Tom Nurkkala;Stefan Brandle
Affiliations:
Taylor University, Upland, IN, USA;Taylor University, Upland, IN, USA
Venue:
Proceedings of the 42nd ACM technical symposium on Computer science education
Year:
2011

Citing 3
Cited 6

Production programming in the classroom

SIGCSE '03 Proceedings of the 34th SIGCSE technical symposium on Computer science education
MUSE studio lab and innovative software engineering capstone project experience

Proceedings of the 8th annual conference on Innovation and technology in computer science education
Can humanitarian open-source software development draw new students to CS?

Proceedings of the 38th SIGCSE technical symposium on Computer science education

Emergent themes in a UI design hybrid-studio course

Proceedings of the 43rd ACM technical symposium on Computer Science Education
The entrepreneur's bootcamp: a new model for teaching web/mobile development and software entrepreneurship

Proceeding of the 44th ACM technical symposium on Computer science education
Teaching software engineering from a maintenance-centric view

Journal of Computing Sciences in Colleges
A comparison of two iterations of a software studio course based on continuous integration

Proceedings of the 18th ACM conference on Innovation and technology in computer science education
Selecting open source software projects to teach software engineering

Proceedings of the 45th ACM technical symposium on Computer science education
Comparing educational experiences and on-the-job needs of educational software designers

Proceedings of the 45th ACM technical symposium on Computer science education

Quantified Score

Hi-index	0.00

Visualization

Abstract

Software Studio is a studio-based learning (SBL) curriculum designed to train students as professional software engineers. Traditional software engineering courses remain important, but suffer significant gaps in preparing students for professional engagement. We describe our curriculum model, highlight ways in which it fills these gaps, and offer a SWOT analysis. As practical guidance, we reflect on our missteps and successes in implementing Software Studio over the past five semesters. Finally, we suggest future directions for Software Studio.