Conference Session

Software Engineering Topics

Collection

2007 Annual Conference & Exposition

Authors

Valentin Razmov, University of Washington

Tagged Divisions

Software Engineering Constituent Committee

8 Term Term(a) (b)Figure 1. (a) Student perception of team sizes. Each dot in the graph is labeled with the range ofteam sizes for the respective term. Most welcome were teams of size 5-8 (corresponding to thered square dots), while smaller or larger teams (corresponding to the blue circle dots) receivedless favorable ratings in the respective terms when they occurred.(b) Student perception of the incremental delivery approach. In the first two terms the approachwas recommended, while subsequently its use was required. In the graph, the lower early

Conference Session

Software Engineering Topics

Collection

2007 Annual Conference & Exposition

Authors

Sheryl Duggins, Southern Polytechnic State University

Tagged Divisions

Software Engineering Constituent Committee

andobjectives of the program and institution. The professional component must include: (a) oneyear of a combination of college level mathematics and basic sciences (some with experimentalexperience) appropriate to the discipline and (b) one and one-half years of engineeringtopics…”30 This appears to be clear enough, with the most important part being “appropriate tothe discipline” which, since the SEEK specifies what that knowledge is and SE2004 specifiescurricula “to help accreditation agencies… make decisions about various institutions’ programs”,the two agencies should be working together, with ABET deferring to SE2004 for what specificsubjects are appropriate to the discipline. But that doesn’t seem to be happening.Of the 13 ABET accredited

Conference Session

Software Engineering Topics

Collection

2007 Annual Conference & Exposition

Authors

Marcelo Jenkins, University of Costa Rica

Tagged Divisions

Software Engineering Constituent Committee

(Comprehension) Yes 3. Organizational and process benchmarking (Analysis) Yes B. Standards, specifications, and models. Identify and use software process and assessment Yes models, including ISO 9001, ISO 15504, IEEE software standards, IEEE/EIA 12207, SEI Capability Maturity Model Integrated (CMMI), etc., in a variety of situations. (Application) C. Leadership tools and skills No D. Ethical conduct and professional development No II

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

having cooperation extend beyond these teams. Figure 1 pictures the resulting two scales ofinteractions – cooperative learning across teams and cooperative learning within a team. Cooperative Learning Across Teams Team 1 Team 2 Team 3 A B C Cooperative Learning Within a Team Figure 1. Cooperative learning within teams and across teamsTraditional cooperative learning uses small teams of students that stay together over several daysor weeks of activity. We did that, forming teams of 2-5 students for the duration of their projects.However, we also formed small meta-teams---teams of teams. As described above, a particulararchitecture project would have a

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

AC 2007-1432: TOOL SUPPORT FOR SOFTWARE PROCESS DATAMANAGEMENT IN SOFTWARE ENGINEERING EDUCATION AND INDUSTRYTRAININGMark Sebern, Milwaukee School of Engineering MARK J. SEBERN is a Professor in the Electrical Engineering and Computer Science Department at the Milwaukee School of Engineering (MSOE), and was the founding program director for MSOE's undergraduate software engineering program. He has served as an ABET program evaluator for software engineering and computer engineering.Mark Hornick, Milwaukee School of Engineering MARK L. HORNICK has been an Assistant Professor in the Electrical Engineering and Computer Science Department at the Milwaukee School of Engineering (MSOE) since 2004