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

Marcelo Jenkins, University of Costa Rica

Tagged Divisions

Software Engineering Constituent Committee

graduate level.1. IntroductionSoftware quality management (SQM) is defined as the set of activities to direct and control asoftware organization with regard to the quality of its processes, products, and services. SQMencompasses the planning, control, assurance, and improvement of the organizational qualitysystem, defined as the collection of policies, objectives, procedures, measurements, methods, andtools that are established and maintained by the organization to fulfill the requirements of thecustomer14.A good SQM system is an essential ingredient for software organizations to be competitive intoday’s global information technology market, but at the same time SQM is certainly one of themost complicated subjects to teach at any level for the

Conference Session

Software Engineering Topics

Collection

2007 Annual Conference & Exposition

Authors

Valentin Razmov, University of Washington

Tagged Divisions

Software Engineering Constituent Committee

the series accounts for the fact that in some offerings we did not use anadditional text and/or targeted handouts.Other problematic areas are quality assurance and testing, build processes, and documentation.Table 1 shows the class-average ratings for those over the 8 terms. Page 12.198.8Table 1. Class-average ratings of problematic areas over all 8 terms. “n/a” in a given cellindicates that we did not ask about the corresponding aspect in that term’s questionnaire. Term 1 Term 2 Term 3 Term 4 Term 5 Term 6 Term 7 Term 8Test plan n/a n/a n/a n/a 0.46 -0.14 n/a 1.14Test

Conference Session

Software Engineering Topics

Collection

2007 Annual Conference & Exposition

Authors

Sheryl Duggins, Southern Polytechnic State University

Tagged Divisions

Software Engineering Constituent Committee

engineering in a degree program with a specialtyin “software engineering”24. As a result of that lawsuit, an independent panel was establishedthat proposed a new Software Engineering Accreditation Board (SEAB) for accrediting softwareengineering programs. The accreditation criteria and procedures of the new board were to bedeveloped jointly by the Canadian Engineering Accreditation Board (CEAB) and the ComputerScience Accreditation Council. However, after the two accrediting bodies had jointly drafted anaccreditation plan for the SEAB, the CEAB “recommended a number of significant changes tothe structure and curriculum requirements of [SEAB] without consulting the [CSAC]. TheCCPE subsequently passed a motion supporting the [panel] recommendations