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

roles: clients, architects, and developers. So, we let the teams changeroles during the course. That is, for each project one team played the role of architects, whileother teams played the roles of clients and developers. Student teams rotated roles on differentprojects throughout the term. A further variation in cooperative learning is that, to succeed oneach project, three different teams also had to cooperate.These innovations kept the benefits of cooperative learning while also exposing the students to 3different perspectives as they progressed through their projects. This is especially important forsoftware architecture, where the 3 perspectives must always be kept in mind. An additionalbenefit was that each student participated in 3

Conference Session

Software Engineering Topics

Collection

2007 Annual Conference & Exposition

Authors

Marcelo Jenkins, University of Costa Rica

Tagged Divisions

Software Engineering Constituent Committee

programming. His research interests are in software engineering and software quality assurance and has authored more than 25 technical papers on the subject. As an independent consultant, he has worked with some of the largest software companies in the Central America region in establishing software quality management systems. In the last 12 years, he has taught several seminars on software quality assurance and software project management. Dr. Jenkins is an ASQ Certified Software Quality Engineer (CSQE) and a member of the ASQ Software Division. Page 12.711.1© American Society for Engineering Education

Conference Session

Software Engineering Topics

Collection

2007 Annual Conference & Exposition

Authors

Valentin Razmov, University of Washington

Tagged Divisions

Software Engineering Constituent Committee

US public university. The feedback was gathered via end-of-term course-specificquestionnaires, separate from and much more detailed than the typical university-sponsoredcourse evaluations. In total, 162 students gave feedback, while 5 different instructors wereinvolved with the course, one of whom – the author of this paper – was actively engaged in all 8offerings.To give the reader a sense of scale, the end-of-term student questionnaires featured 60-150questions – mostly multiple choice questions, as well as some free-form short-answer questions.The subject of the questions were the course structure, the instructors’ teaching approach, classsessions, readings, writing assignments, project experiences, tools, the feedback that

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

www.msoe.edu/se/AbstractData management tools are necessary for effective support of disciplined software processes thatmake use of historical data for planning and process improvement. This paper reports describestwo such tools and how they have been applied in an undergraduate software engineeringprogram and to support software process improvement initiatives in industry. One of the tools, anopen-source development project, has recently added new capabilities that may make it anattractive choice for both educators and practitioners.IntroductionSoftware engineering programs generally incorporate courses and other learning experiences thatare designed to provide breadth and depth of coverage across the discipline, addressing bothpractice and process

Conference Session

Software Engineering Topics

Collection

2007 Annual Conference & Exposition

Authors

Sheryl Duggins, Southern Polytechnic State University

Tagged Divisions

Software Engineering Constituent Committee

Engineering Disciplines? A Critical Analysis of ABET’s Software Engineering Curriculum GuidelinesAbstractSince the 1968 NATO Conference which coined the term “software engineering”, softwarepractitioners and educators alike have been fighting an uphill battle over the right to be viewed asengineers. The Association of Computing Machinery (ACM) and the Institute of Electrical andElectronic Engineers Computer Society (IEEE-CS) joined forces to try and come to terms withthe question of what exactly is software engineering? From the initial work done by theSoftware Engineering Education Project (SWEEP) that developed draft accreditation criteria forundergraduate degrees in software engineering (SWE) in 1998, to the