Conference Session

Software Engineering Topics

Collection

2007 Annual Conference & Exposition

Authors

Valentin Razmov, University of Washington

Tagged Divisions

Software Engineering Constituent Committee

components that worked verywell, then present the ones that did not work so well, and finish with a few that raised eyebrows.3.1.1. What Worked WellStudents appreciated large team sizes (but not too large) that allowed them to work with severalpeers while learning how to do effective group work on non-trivial projects. The class averagesfor this aspect were 1.55, 1.40, 1.62, and 1.38 for the terms when the team sizes were in therange 5-8, and 0.43, 0.12, 1.00, and 0.29 for the terms when team sizes were either bigger orsmaller (Figure 1(a)). In a free-form response, one student noted, “The experience in a largegroup project was great,” echoing the feelings of many others.Another much appreciated aspect was the incremental delivery approach. Class

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

colleagues, Recently, this latter tool has been extended to better supportdevelopment teams and customized process definitions. As a result, the Process Dashboard maywell become a de facto standard for software process data management support.Metrics, Process Design, and Support Tool FunctionalityIn designing or applying data management tools to a chosen software process, one of the firststeps is to choose appropriate product and process measures. Watts Humphrey and his SEIcolleagues, while defining the PSP and TSP processes, developed a set of four base measures,from which many derived measures can be calculated (Table 1). Base Measures Derived Measures Product size (e.g., LOC

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

constitutes cooperative learning, it generally incorporates theseelements2,3: 1. Positive interdependence: Team members rely on each other to achieve the common goal. 2. Face-to-face interaction: Team members do most of the work together. They provide assistance, encouragement and feedback to the other team members. 3. Individual accountability and personal responsibility: Each team member is responsible for doing his/her share of the work, and is expected to master all necessary material. 4. Interpersonal and small-group skills: Team members use effective communication and conflict-management skills. 5. Group processing: Team members set common goals, reflect on team accomplishments and make adjustments as

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

Sheryl Duggins, Southern Polytechnic State University

Tagged Divisions

Software Engineering Constituent Committee

that satisfy both masters: ABET and SE2004.History of Software Engineering EducationPeter Freeman et. al.1 proposed the earliest framework for software engineering education (SEE). Page 12.990.2It was for graduate software engineering, and it identified a set of criteria that any SE curriculamust follow and a set of five content areas necessary for any software engineering (SE) degree.Revisiting SEE a decade later, Freeman2 reported that few, if any, efforts since his earlier paperhad “strategically addressed the question of where SEE is or should be headed.” He furthernoted that in spite of the past ten years of development in software