Conference Session

Accreditation and Assessment in SE Programs

Collection

2011 ASEE Annual Conference & Exposition

Authors

Susan E. Conry, Clarkson University

Tagged Divisions

Software Engineering Constituent Committee

similarities. To theextent that these factors seem to be correlated with administrative housing, perhaps theinstitutional context has shaped the character of the program more.Table 2 summarizes the data relative to the overall content of the technical curricular componentand the degree to which it reflects required coursework. Table 2(a) gives the relevant data forcomputer engineering programs, while Table 2(b) and Table 2(c) summarize this information forcomputer science and software engineering programs. Some interesting patterns emerge whenthis data is analyzed. First, the relative size of the technical component in the computerengineering and software engineering programs is similar – an average of about 51% of the totalcurriculum is technical in

Conference Session

SE Tools and Techniques

Collection

2011 ASEE Annual Conference & Exposition

Authors

John C. Georgas, Northern Arizona University

Tagged Divisions

Software Engineering Constituent Committee

early as possible.For effective group operation, it is also critical to provide evaluative feedback at both the groupand individual levels12. For this project, each deliverable element was accompanied by a student-provided peer-evaluation that is used in a zero-sum grading methodology. This allowed us toassign individual grades that are a better representation of individual student contributions thanthe quality of final deliverables alone. As a result, individual grades reflect high or low levels ofcontribution by students, based on the evaluations of their teammates.Each student is required to provide a peer evaluation along with project deliverables: this peerevaluation provides a scaling factor for the score of the submitting student and

Conference Session

Software Engineering Projects

Collection

2011 ASEE Annual Conference & Exposition

Authors

Thomas Reichlmayr, Rochester Institute of Technology

Tagged Divisions

Software Engineering Constituent Committee

Iteration Zero) that is needed at the beginning of the project to create the initialversion of the Product Backlog, develop the architecture or high level design and perform anyother activities needed to support the start of the first sprint. It is during this period that requiredproject artifacts and their content are identified.The Product Backlog is prioritized by the order in which features are to be added to a sprint fordevelopment. There may be a variety of characteristics influencing the backlog priority –business value, time to market, technical dependencies, etc., but the Product Owner is ultimatelyresponsible for the ordering of the backlog. The completeness of user stories in the ProductBacklog reflects their relative priority. Stories

Conference Session

Software Engineering Projects

Collection

2011 ASEE Annual Conference & Exposition

Authors

Massood Towhidnejad, Embry-Riddle Aeronautical University, Daytona Beach; Thomas B. Hilburn, Embry-Riddle Aeronautical University, Daytona Beach; Joseph E. Urban, Texas Tech University; Gregory W. Hislop, Drexel University; Richard Stansbury, Embry-Riddle Aeronautical University, Daytona Beach

Tagged Divisions

Software Engineering Constituent Committee

. CNS-0939059, CNS-0939088, and CNS-0939028. Any opinions, findings, andconclusions or recommendations expressed in this material are those of the author(s) and do notnecessarily reflect the views of the National Science Foundation.References1. [CRA 2009] Computing Research Association, Computing Degree and Enrollment Trends, Computing Research Association Washington, DC, 2009.2. [NSF 2008] Science and Engineering Degrees: 1966–2006, Detailed Statistical Tables NSF 08-321, National Science Foundation, Division of Science Resources Statistics, Arlington, VA, 2008.3. [DOL 2010] U.S. Department of Labor, Occupational Outlook Handbook – Occupational Projections and Training Data, 2010-2011 Edition, U.S. Department of Labor, Bureau

Conference Session

Software Engineering Projects

Collection

2011 ASEE Annual Conference & Exposition

Authors

James N. Long, Oregon Institute of Technology; Linda Sue Young, Oregon Institute of Technology

Tagged Divisions

Software Engineering Constituent Committee

a student’s project. e. Productive feedback or thoughtful reflection about the course and process. f. Any other tasks that the instructor deems worthy. 5. KG may be lost by: a. Coming in late to class. b. Showing up late for or missing scheduled presentations. c. Being rude. d. Any other thing the instructor deems worthy of penalizing with a loss. 6. KG can be traded to other members of the class. All trade must be accompanied by a formal contract, signed by both parties, and then a copy given to the instructor. Examples exchanges include: a. Tasks such as programming or other project based help. b. Use of tools not possessed by the individual or group

Conference Session

SE Tools and Techniques

Collection

2011 ASEE Annual Conference & Exposition

Authors

Robert W. Hasker, University of Wisconsin, Platteville; Mike Rowe, University of Wisconsin, Platteville

Tagged Divisions

Software Engineering Constituent Committee

itsusefulness.As part of our preliminary evaluation, we requested written feedback from students using thetool in a sophomore/junior-level course. A number of comments reflect the need for additionalwork on the tool: making it more robust when syntactic errors are found in input files,improving the identification of defects in diagrams, and the need to include illustrations of theerror types. Comments about the effectiveness of the tool include • “Fixed numerous errors that [the instructor] did not address in class such as using ∗ instead of 0..∗. Also found errors in the syntax of the classes. attributes, operations, and the documentation of them.” • “The tool helps with discovering some errors, for example in the Associations. We found a

Conference Session

Accreditation and Assessment in SE Programs

Collection

2011 ASEE Annual Conference & Exposition

Authors

Nan Niu, Mississippi State University; Donna Reese, Mississippi State University; Kui Xie, Mississippi State University; Chris Smith, Mississippi State University

Tagged Divisions

Software Engineering Constituent Committee

other to achieve the common goal. • Face-to-face interaction: Team members do most of the work together. They provide assistance, encouragement, and feedback to the other team members. • 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. • Interpersonal and small-group skills: Team members use effective communication and conflict-management skills. Page 22.1254.6 • Group processing: Team members set common goals, reflect on team accomplishments, and make adjustments as

Conference Session

Accreditation and Assessment in SE Programs

Collection

2011 ASEE Annual Conference & Exposition

Authors

Janet E. Burge, Miami University; Paul V. Anderson, Miami University, Ohio; Michael Carter, North Carolina State University; Gerald C. Gannod, Miami University; Mladen A. Vouk, North Carolina State University

Tagged Divisions

Software Engineering Constituent Committee