The software enterprise

Facilitating the industry preparedness of software engineers

Barbara Gannod, Harry Koehnemann, Kevin Gary

Research output: Contribution to journalArticle

3 Citations (Scopus)

Abstract

The traditional software engineering instruction model asks students to first take survey-of-the-field style course that exposes them to a breadth of software engineering practices and processes but typically lacks depth in any given area. The results are students who can recite the basic principles, but who lack the comprehension to apply them. These types of courses are then followed by courses that delve into a specific process area in significant depth, for example a Software Design or a Software Quality Assurance course. These courses focus on deep skills development within the narrow process area. Students then complete the program with the capstone project, which asks them to apply this knowledge in a full semester project. Students do not get exposure to the full engineering process spectrum in a manner that allows them to apply the deeper skillsets they may have developed in a particular area. The results are students who can claim knowledge of a particular skill, but lack the context in which to apply this knowledge. A typical conversation an interviewer might have with a graduating student might be "well, yes I did a few use cases in my Software Requirements class, but no I have not done one of that size nor do I understand how to use that model to drive analysis and test planning." This paper presents an alternative approach underway at Arizona State University's Polytechnic campus. In this approach, students are accelerated through the knowledge, comprehension, application levels through a hybrid teaching and learning model that combines multiple pedagogical approaches with a process-guided exposure to software engineering.

Original languageEnglish (US)
JournalASEE Annual Conference and Exposition, Conference Proceedings
StatePublished - 2006

Fingerprint

Enterprise software
Students
Engineers
Industry
Software engineering
Software design
Quality assurance
Teaching
Planning

ASJC Scopus subject areas

  • Engineering(all)

Cite this

@article{8cbfc614a79a4fe28552eee519530fed,
title = "The software enterprise: Facilitating the industry preparedness of software engineers",
abstract = "The traditional software engineering instruction model asks students to first take survey-of-the-field style course that exposes them to a breadth of software engineering practices and processes but typically lacks depth in any given area. The results are students who can recite the basic principles, but who lack the comprehension to apply them. These types of courses are then followed by courses that delve into a specific process area in significant depth, for example a Software Design or a Software Quality Assurance course. These courses focus on deep skills development within the narrow process area. Students then complete the program with the capstone project, which asks them to apply this knowledge in a full semester project. Students do not get exposure to the full engineering process spectrum in a manner that allows them to apply the deeper skillsets they may have developed in a particular area. The results are students who can claim knowledge of a particular skill, but lack the context in which to apply this knowledge. A typical conversation an interviewer might have with a graduating student might be {"}well, yes I did a few use cases in my Software Requirements class, but no I have not done one of that size nor do I understand how to use that model to drive analysis and test planning.{"} This paper presents an alternative approach underway at Arizona State University's Polytechnic campus. In this approach, students are accelerated through the knowledge, comprehension, application levels through a hybrid teaching and learning model that combines multiple pedagogical approaches with a process-guided exposure to software engineering.",
author = "Barbara Gannod and Harry Koehnemann and Kevin Gary",
year = "2006",
language = "English (US)",
journal = "ASEE Annual Conference and Exposition, Conference Proceedings",
issn = "2153-5965",

}

TY - JOUR

T1 - The software enterprise

T2 - Facilitating the industry preparedness of software engineers

AU - Gannod, Barbara

AU - Koehnemann, Harry

AU - Gary, Kevin

PY - 2006

Y1 - 2006

N2 - The traditional software engineering instruction model asks students to first take survey-of-the-field style course that exposes them to a breadth of software engineering practices and processes but typically lacks depth in any given area. The results are students who can recite the basic principles, but who lack the comprehension to apply them. These types of courses are then followed by courses that delve into a specific process area in significant depth, for example a Software Design or a Software Quality Assurance course. These courses focus on deep skills development within the narrow process area. Students then complete the program with the capstone project, which asks them to apply this knowledge in a full semester project. Students do not get exposure to the full engineering process spectrum in a manner that allows them to apply the deeper skillsets they may have developed in a particular area. The results are students who can claim knowledge of a particular skill, but lack the context in which to apply this knowledge. A typical conversation an interviewer might have with a graduating student might be "well, yes I did a few use cases in my Software Requirements class, but no I have not done one of that size nor do I understand how to use that model to drive analysis and test planning." This paper presents an alternative approach underway at Arizona State University's Polytechnic campus. In this approach, students are accelerated through the knowledge, comprehension, application levels through a hybrid teaching and learning model that combines multiple pedagogical approaches with a process-guided exposure to software engineering.

AB - The traditional software engineering instruction model asks students to first take survey-of-the-field style course that exposes them to a breadth of software engineering practices and processes but typically lacks depth in any given area. The results are students who can recite the basic principles, but who lack the comprehension to apply them. These types of courses are then followed by courses that delve into a specific process area in significant depth, for example a Software Design or a Software Quality Assurance course. These courses focus on deep skills development within the narrow process area. Students then complete the program with the capstone project, which asks them to apply this knowledge in a full semester project. Students do not get exposure to the full engineering process spectrum in a manner that allows them to apply the deeper skillsets they may have developed in a particular area. The results are students who can claim knowledge of a particular skill, but lack the context in which to apply this knowledge. A typical conversation an interviewer might have with a graduating student might be "well, yes I did a few use cases in my Software Requirements class, but no I have not done one of that size nor do I understand how to use that model to drive analysis and test planning." This paper presents an alternative approach underway at Arizona State University's Polytechnic campus. In this approach, students are accelerated through the knowledge, comprehension, application levels through a hybrid teaching and learning model that combines multiple pedagogical approaches with a process-guided exposure to software engineering.

UR - http://www.scopus.com/inward/record.url?scp=85029041139&partnerID=8YFLogxK

UR - http://www.scopus.com/inward/citedby.url?scp=85029041139&partnerID=8YFLogxK

M3 - Article

JO - ASEE Annual Conference and Exposition, Conference Proceedings

JF - ASEE Annual Conference and Exposition, Conference Proceedings

SN - 2153-5965

ER -