Conference Session

Software Engineering Topics

Collection

2007 Annual Conference & Exposition

Authors

Valentin Razmov, University of Washington

Tagged Divisions

Software Engineering Constituent Committee

. We also share a few surprisesfound in the data.Our main contributions are the analysis of the rich body of collected data, as well as distillinggroups of questions that have yielded particularly useful results, and categorizing those by targetoutcome: questions for evolving the course, for “reading” students’ moods, and for gettingstudents to reflect on their experiences. Many of these questions may be broadly applicable.The remainder of the paper is structured as follows. Section 2 elaborates on relevant aspects ofthe course structure and describes our mechanism for collecting feedback data. Section 3discusses what we have learned from our data analysis – first about the course, and then aboutthe process of doing student surveys. We

Conference Session

Software Engineering Topics

Collection

2007 Annual Conference & Exposition

Authors

Steve Chenoweth, Rose-Hulman Institute of Technology; Mark Ardis, Rochester Institute of Technology; Cheryl Dugas, Rochester Institute of Technology

Tagged Divisions

Software Engineering Constituent Committee

. Cooperative learning isa pedagogy that directly supports this type of teamwork. Through cooperative learning studentsrealize their interdependence, practice face-to-face communication, recognize their individualaccountability to the success of the group, practice interpersonal and small-group skills, andengage in frequent reflective processing of their achievements.We have adapted cooperative learning to teach software architecture in two undergraduatesoftware engineering programs. In traditional cooperative learning, students work on one teamfor an extended period. This helps foster acceptance of individual differences and promotessuccessful teamwork. In our courses we kept students together on the same teams, but we wantedstudents to play multiple

Conference Session

Software Engineering Topics

Collection

2007 Annual Conference & Exposition

Authors

Sheryl Duggins, Southern Polytechnic State University

Tagged Divisions

Software Engineering Constituent Committee

tosoftware engineering. If software engineering is so different than all other types of engineering,should ABET guidelines reflect more of these differences? But the real problem is thateducators must choose between the advice of software engineers and the ABET guidelines. Thisauthor is positing that perhaps we should not have to make that choice.This paper will examine relevant developments that have shaped our current understanding ofwhat constitutes software engineering; the distinct nature of the Software Engineering EducationKnowledge (SEEK); how the SEEK should affect SWE curriculum development; and currentABET curricular guidelines for SWE programs. Finally, the paper will explore the conflicts thatarise when trying to design SWE curricula

Conference Session

Software Engineering Topics

Collection

2007 Annual Conference & Exposition

Authors

Mark Sebern, Milwaukee School of Engineering; Mark Hornick, Milwaukee School of Engineering

Tagged Divisions

Software Engineering Constituent Committee

estimates (in minutes) foreach assigned team member, as shown in Figure 2. Each task is then assigned a starting andending week, relative to the current development cycle; this permits the system to generate aworkload summary by week and team member, to facilitate load balancing within the team andacross the cycle. The development schedule can take into account external dependencies; inFigure 2, for example, weeks 3 and 4 correspond to a holiday break period when no work isplanned (though some may actually be done). Figure 2. LEIA Schedule PlanLEIA supports tracking of team and individual progress, as shown in the effort report of Figure3. The time values reflect only “task time”, not total time spent on the