Two controlled experiments assessing the usefulness of design pattern documentation in program maintenance

Abstract

ÐUsing design patterns is claimed to improve programmer productivity and software quality. Such improvements may manifest both at construction time (in faster and better program design) and at maintenance time (in faster and more accurate program comprehension). This paper focuses on the maintenance context and reports on experimental tests of the following question: Does it help the maintainer if the design patterns in the program code are documented explicitly (using source code comments) compared to a well-commented program without explicit reference to design patterns? Subjects performed maintenance tasks on two programs ranging from 360 to 560 LOC including comments. Both programs contained design patterns. The controlled variable was whether the use of design patterns was documented explicitly or not. The experiments thus tested whether pattern comment lines (PCL) help during maintenance if patterns are relevant and sufficient program comments are already present. It turns out that this question is a challenge for the experimental methodology: A setup leading to relevant results is quite difficult to find. We discuss these issues in detail and suggest a general approach to such situations. The experiment was performed with Java by 74 German graduate students and then repeated with C++ by 22 American undergraduate students. A conservative analysis of the results supports the hypothesis that pattern-relevant maintenance tasks were completed faster or with fewer errors if redundant design pattern information was provided. Redundant means that the information carried in pattern comments is also available in different form in other comments. The contribution of this article is twofold: It provides the first controlled experiment results on design pattern usage and it presents a solution approach to an important class of experiment design problems for experiments regarding documentation.

The Role of Cognitive Fit in the Relationship between Software Comprehension and Modification

“…Despite the early establishment of a tradition of studying software developers, relatively few studies have examined performance on software maintenance tasks. Prior maintenance research has considered the impact of various factors on maintainers' ability to modify software including program structure (Boehm-Davis et al 1992;Daly et al 1996;Prechelt et al 2001;Sheppard et al 1979;Shneiderman et al 1977), the use of different documentation formats (Curtis et al 1989;Prechelt et al 2002), and the cognitive processes used by software maintainers (Littman et al 1986). …”

Do background colors improve program comprehension in the #ifdef hell?

“…We decided to use maintenance tasks, because, if subjects could offer a solution for a bug, then program comprehension must have taken place. Additionally, a lot of experiments described in the literature use tasks, as well, so we can relate our results to other experiments (e.g., Boysen (1977); Hanenberg (2010); Prechelt et al (2002)). …”

A software architecture for monitoring big data storage platforms

“…Here, the subsystem is a cluster of various NoSQL systems. It defines a higher-level interface that makes the subsystem easier to use and wraps a complicated subsystem up in a simpler interface [12]. In the proposed architecture, a resource handler module is used for each subsystem.…”