Improving Quality In Software Engineering Through Emphasis On Communication

Barbara Mirel, Atul Prakash, Leslie A. Olsen, Elliot Soloway2020 · DOI

Abstract

This paper describes the integration of a communication component into a senior-level design course in software engineering, the structure of the component, and methods for testing its effects. The goal is to improve the usability of the software product, to overcome some problems due to time constraints of a school term, and to bring the course more in step with industry approaches by emphasizing user-centered design and iterative documentation.

Introduction

A persistent gap exists between academic software engineering (SE) and the realities of the professional industry. In a typical classroom setting, students often become preoccupied with the technical "how" of coding—focusing on internal team collaboration and technical implementation. In contrast, the professional landscape places a dominant emphasis on the "who" and "why": user requirements, stakeholder needs, and continuous involvement.

At the University of Michigan, researchers identified that students rarely graduate with robust User-Centered Design (UCD) skills because the intense time pressure of a single semester forces them to prioritize functional code over usable code. Without a structured intervention, students fail to develop the "alternative perspective" necessary to view software through the eyes of a client or end-user. This paper details a curriculum overhaul designed to bridge this gap by pairing a capstone engineering course with a dedicated technical communication course.

The Communication-Across-the-Curriculum (CAC) Model

To address these pedagogical challenges, the researchers implemented a "Communication-Across-the-Curriculum" (CAC) model. This integrated a 3-credit course, "Technical Communication for Software Products," directly with the senior-level SE capstone project. The integration is not merely parallel but deeply structural, characterized by several key features:

  • Synchronized Logistics: The communication course is restricted to students enrolled in the SE design class. Students work in the same 10-person teams across both courses. To prevent "double work," assignments are synchronized in content and deadlines.
  • Living Documentation via Hyperdocuments: Moving away from static, end-of-term reports, students create "hyperdocuments" on a shared website. These artifacts—including vision statements, task analyses, and specifications—are designed to evolve alongside the codebase, serving as a real-time map of the project.
  • User-Centered Milestones: The curriculum mandates activities that students might otherwise bypass under pressure, such as contextual inquiry, activity-based planning, and early iterative usability testing.
  • Perspective Shifting: Assignments require students to translate technical features into user benefits for diverse audiences, including managers, marketing specialists, and trainers. This forces a move away from jargon toward functional value.

Methodology and Assessment

As this study focuses on pedagogical implementation, the "data" consists of qualitative and quantitative artifacts generated throughout the term. The researchers established an assessment framework to evaluate the impact of the integrated communication component:

  1. Student Artifacts: Analysis of vision statements and requirements specifications to track the evolution of project goals.
  2. Communication Logs: Transcripts of team email exchanges and meetings are analyzed to determine the depth and frequency of design-related discussions.
  3. Expert Evaluations: UCD experts perform blind assessments of the final software interfaces, comparing them against products from standard SE courses.
  4. Student Feedback: Retrospective essays and targeted questionnaires provide insight into the students' perceived value of the communication requirements.

Key Insights: Writing as Design

The core philosophy of this integration is that writing is not merely a method for reporting results, but a primary tool for generating ideas. By documenting trade-offs and design decisions early, teams are less likely to fall victim to "groupthink" or settle for the easiest technical solution at the expense of the user.

Furthermore, the "growable" specification addresses a common industry failure: the tendency for documentation to drift from the actual product. By training students to treat documentation as a living entity, the course instills professional habits that prevent teams from "coding themselves into a corner" before the design is fully vetted.

Preliminary Results and Future Work

While the authors were in the process of final data collection at the time of publication, preliminary observations suggest that the writing requirements significantly sharpen team discussions regarding design trade-offs. The integrated approach appears to help teams focus earlier in the term, potentially increasing the rate of successful project completion.

Future research will focus on a comparative analysis between the integrated communication teams and "control" teams in standard SE tracks. Additionally, the researchers plan to investigate the long-term professional impact of these UCD habits and refine the web-based tools used to manage the hyperdocument system.

Summary updated

Abstract

We will describe the integration of a communication component into a senior-level design course in software engineering, the structure of the component, and methods for testing its effects. The goal is to improve the usability of the software product, to overcome some problems due to time constraints of a school term, and to bring the course more in step with industry approaches by the following:
BibTeX
@misc{mirel2020improving,
  author = {Barbara Mirel and Atul Prakash and Leslie A. Olsen and Elliot Soloway},
  title = {{Improving Quality In Software Engineering Through Emphasis On Communication}},
  year = {2020},
  doi = {10.18260/1-2--6609},
}
Figure