An analysis of research in computing disciplines

By Robert L. Glass, Venkataraman Ramesh, Iris Vessey. CACM, 2004

311 citations recorded by the source corpus.

Subfields: Computer Science Applications, Information Systems

View Paper: https://www.semanticscholar.org/paper/b4a3ef6da5d4a818619dff11b1eaeaee76c7ad2e

How researchers see this paper

The researchers whose trusted networks rank it highest, strongest advocate first. Every researcher gets a different order.

In Computer Science Applications

In Information Systems

Citations in the corpus

Systematic literature reviews in software engineering - A systematic literature review (2009, unknown): “[9] 2004 Research trends Comparative CS, IS and SE S5 Grimstad et al.”
A survey of controlled experiments in software engineering (2005, background): “…of Glass et al. is aimed at positioning software engineering research relative to a backdrop of overall computing disciplines, i.e., computer science, software engineering, and information systems, and their classification categories are meant to give uniformity across all three fields [19] .”
Lessons from applying the systematic literature review process within the software engineering domain (2007, unknown): “One of the criticisms that can be levelled at researchers in software engineering and computer science, particularly in contrast with those in information systems, is that they make little or no use of the methods and experiences available from other ‘reference disciplines’ (Glass et al., 2004).”
Requirements engineering paper classification and evaluation criteria: a proposal and a discussion (2005, background): “[12] show that papers in information systems tend to be empirical and propose no solutions for the problems they cover.”
The “Physics” of Notations: Toward a Scientific Basis for Constructing Visual Notations in Software Engineering (2009, background): “One reason for the lack of progress in establishing a science of visual notation design may be the strong Not Invented Here (NIH) effect in SE research, which draws on research from other fields to only a minimal extent (it has a self-referencing rate of 98.1 percent [34]).”
Using Mapping Studies in Software Engineering (2008, methodology): “Computing in general, and software engineering in particular, has a very weak track record of using empirical data to support the development of models and methods, as well as of adopting practices from other disciplines (Whitley 1997, Glass et al. 2002, Glass et al. 2004 ).”
Knowledge management in software engineering: A systematic review of studied concepts, findings and research methods used (2008, background): “[50] found that empirical studies constitute about 5% of published research in software engineering as a whole.”
Reconstructing the giant: On the importance of rigour in documenting the literature search process (2009, unknown): “Finally, our analysis also revealed that review articles in IS research differ considerably in terms of length, reaching from six pages (Glass et al. 2004) to 143 pages (Fjermestadt and Hiltz 1998).”
Standing on the Shoulders of Giants: Challenges and Recommendations of Literature Search in Information Systems Research (2015, methodology): “…IT business value they developed at the outset of their review, and Communications of the Association for Information Systems 213 Volume 37 Paper 9 Glass, Ramesh, and Vessey (2004) began analyzing the computing science literature by developing a classification scheme that later guided their…”
Performing systematic literature reviews in software engineering (2006, background): “Indeed, a survey of publications in Software Engineering journals has indicated that the research methods employed by Software Engineers are not drawn from a particularly wide set of reference disciplines [3, 2].”