Writing Good Software Engineering Research Papers Mary Shaw

Shaw has co-authored seminal works on software architecture with David Garlan, particularly the 1996 book Software Architecture: Perspectives on an Emerging Discipline’.In 2011, Shaw and Garlan received the Outstanding Research Award from the Association of Computing Machinery’s Special Interest Group on Software Engineering, for their lasting contributions to the promotion of software architecture.

For example, of the 95 technical track papers that appeared at ICSE 2014, I counted 54 (57%) that had a section or subsection explicitly titled "Threats to Validity" (or some small variant).However, this paper advocates a discussion of the limitations of the work without prescribing a particular paper structure: I4: Specify any limitations of the study.Researchers have a responsibility to discuss any limitations of their study.Could it simply be that the idea of a "threats" section, pioneered by a few empirical researchers in the 1990s (e.g., Wohlin et al.), simply snowballed into what it is now?Overall I don't think the concept of a "Threats to Validity" section is a bad one: it often works very well. Perlis Professor of Computer Science at Carnegie-Mellon University. Between 19 she was a Fellow of the Center for Innovation in Learning.She is one of the founding members of the field of software architecture. For six years from 2001 to 2006, Shaw served as Co-Director of the Sloan Software Industry Center.But who decided that the corresponding prose must be corralled into a specific region of the paper?An obvious alternative is to discuss the implications of design decisions together with the description of the decisions. She has been a member of the faculty at Carnegie Mellon since she completed her Ph. In 1981, she co-authored another book, this time with Alan Perlis and Frederick Sayward, on software metrics. Shaw co-authored her first book with Frank Hole in 1967, much before she had finished her Ph D.