Susan S. Brilliant
- {1} Avritzer, A.; Weyuker, E. J.; Monitoring smoothly degrading systems for increased dependability. In: Empirical Software Engineering. Vol. 2, no. 1; 1997; p. 59-77. Google Scholar
Digital Library
- {2} Basili, V. R; Green, S; Laitenberger, O.; Shull, F.; Sorumgard, S.; Zelkowitz, M. V.; The empirical investigation of perspective-based reading In: Empirical Software Engineering, vol. 1, no. 2; 1996; p. 133-64.Google Scholar
- {3} Bertolino, A.; Marre, M; Automatic generation of path covers based on the control flow anatysis of computer programs. In: IEEE Transactions on Software Engineering. vol. 20, no. 12; Dec. 1994; p. 885-99. Google ScholarDigital Library
- {4} Bowdidge, R. W.; Griswold, W. G.; How software engineering tools organize programmer behavior during the task of data encapsulation. In: Empirical Software Engineering. Vol. 2,no. 3; 1997; p. 221-67. Google ScholarDigital Library
- {5} Briand, L. C.; Bunse, C.; Daly, J. W.; Differding, C.; An experimental comparison of the maintainability of object-oriented and structured design documents. In: Empirical Software Engineering. Vol. 2, no. 3; 1997; p. 291-312. Google ScholarDigital Library
- {6} Briand, L. C.; Daly, J. W.; Wust, J. A unified framework for cohesion measurement in object-oriented systems. In: Empirical Software Engineering. Vol. 3, no. 1, 1998, p. 65-117. Google ScholarDigital Library
- {7} Brooks, A.; Meta analysis-a silver bullet-for meta-analysts. In: Empirical Software Engineering Vol. 2, no. 4; 1997; p. 333-8. Google ScholarDigital Library
- {8} Brown, A. W.; Carney, D. J.; Clements, P. C.; Meyers, B. C.; Smith, D. B.; Weidennan, N. H. Wood, W. G.; Assessing the quality of large, software-intensive systems: a case study. In: Software Engineering - ESEC Ô95. 5th European Software Engineering Conference. Proceedings. Springer-Verlag, Berlin, Germany; 1995; p. 384-404. Google ScholarDigital Library
- {9} Bruegge, B.; Dutoit, A. H.; Communication metrics for software development. In: Proceedings of the 1997 International Conference on Software Engineering, ICSE 97. ACM, New York, NY, USA, 1997, p. 271-81. Google ScholarDigital Library
- {10} Daly, J.; Brooks, A. Miller, J.; Roper, M.; Wood, M.; Evaluating inheritance depth on the maintainability of object-oriented software. In: Empirical Software Engineering. vol. 1, no. 2; 1996; p. 109-32.Google Scholar
- {11} El Emam, K.; Hoeltje, D.; Qualitative analysis of a requirements change process. In: Empirical Software Engineering. vol. 2, no. 2; 1997; p. 143-52. Google ScholarDigital Library
- {12} El Emam, K.; Madhavji, N. H.; An instrument for measuring the success of the requirements engineering process in information systems development. In: Empirical. Software Engineering. vol. 1, no. 3; 1996; p. 201-40.Google Scholar
- {13} EuroSTAR '94, the Second European Conference on Software Testing, Analysis and Review Software Quality Eng, Jacksonville, FL, USA; 1994; 716 pp.Google Scholar
- {14} Fusaro, P.; Lanubile, F.; Visaggio, G.; A replicated experiment to assess requirements inspection techniques. In: Empirical Software Engineering. Vol. 2, no. 1; 1997. p. 39-57. Google ScholarDigital Library
- {15} Graham, D.; Software testing paradoxes, panaceas and engineering. In: Software Quality and Business Opportunities. Fifth European Conference on Software Quality Conference Proceedings. Irish Quality Assoc, Dublin, Ireland; 1996; p. 239-45.Google Scholar
- {16} Jankowski, D.; Computer-aided systems engineering methodology support and its effect on the output of structured analysis. In: Empirical Software Engineering. Vol. 2, no. 1; 1997; p. 11-38. Google ScholarDigital Library
- {17} Johnson, P. M.; Tjahjono, D.; Does every inspection really need a meeting? In: Empirical Software Engineering. Vol. 3, no. 1; 1998; p. 9-35. Google ScholarDigital Library
- {18} Kiper, J. D.; Auemheimer, B.; Ames, C. k; Visual depiction of decision statements: what is best for programmers and non-programmers? In: Empirical Software Engineering. Vol. 2, no. 4; 1997; p. 361-79. Google ScholarDigital Library
- {19} Koike, H; Hui-Chu-Chu. How does 3-D visualization work in software engineering?: empirical study of a 3-D version/module visualization system. In: Proceedings of the 1998 International Conference on Software Engineering: Forging New Links. IEEE Comput. Soc, Los Alamitos, CA, USA, 1998, p. 516-19. Google ScholarDigital Library
- {20} Lott, C. M.; A controlled experiment to evaluate on-line process guidance. In: Empirical Software Engineering. Vol. 2, no. 3; 1997; p. 269- 89. Google ScholarDigital Library
- {21} Millerl, L; Daly, J.; Wood, M.; Roper, M; Brooks, A.; Statistical power and its subcomponents-missing and misunderstood concepts in empirical software engineering research. In: Information and Software Technology. vol. 39,no. 4; April 1997; p. 285-95.Google Scholar
- {22} Miller. J; Wood. M; Roper, M. Further experiences with scenarios and checklists {software inspection}. In: Empirical Software Engineering. Vol. 3, no. 1; 1998; p. 37-64. Google ScholarDigital Library
- {23} Morasca, S.; Applying QIP/GQM in a maintenance project. In: Empirical Software Engineering. Vol. 2, no. 2; 1997; p. 163-6. Google ScholarDigital Library
- {24} Munson, J. C.; Hall, G. A.; Estimating test effectiveness with dynamic complexity measurement. In: Empirical Software Engineering. vol. 1, no. 3; 1996; p. 279-305.Google Scholar
- {25} Ohlsson, N.; Eriksson, A. C.; Helander, M.; Early risk-management by identification of fault-prone modules. In: Empirical Software Engineering. Vol. 2, no. 2; 1997; p. 166-73. Google ScholarDigital Library
- {26} Pitschinetz, R.; Wegener, J.; TESSY-management of software tests. In: Experience with the Management of Software Projects 1995 (MSPS'95). A Proceedings Volume from the 5th IFAC/IFIP/GI/GMA Workshop. Pergamon, Oxford, UK; 1996; p. 11-16.Google Scholar
- {27} Rosenblun, D. S.; Weyuker, E. J.; Lessons learned from a regression testing case study. In: Empirical Software Engineering, Vol. 2, no. 2; 1997; p. 188-91. Google ScholarDigital Library
- {28} Rothermel, G; Harrold, M. J.; Experience with regression test selection. In: Empirical Software Engineering. Vol. 2, no. 2; 1997; p. 178-88. Google ScholarDigital Library
- {29} Schneidewind, N.; NASA shuttle software maintenance evolution. In: Empirical Software Engineering. Vol. 2, no. 2; 1997; p. 192-6. Google ScholarDigital Library
- {30} Seaman, C. B.; Basili, V. R.; The study of software maintenance organizations and processes. In: Empirical Software Engineering. Vol. 2, no. 2; 1997; p. 197-201. Google ScholarDigital Library
- {31} Silverman, B. G.; Mehzer, T.; A study of strategies for computerized critiquing of programmers. In: Empirical Software Engineering. Vol. 2, no. 4; 1997; p. 339-59. Google ScholarDigital Library
- {32} Sova, D. W.; Smidts, C.; Increasing testing productivity and software quality: a comparison of software testing methodologies within NASA. In: Empirical Software Engineering. vol. 1, no. 2; 1996; p. 165-88.Google Scholar
- {33} Tryggeseth, E.; Report from an experiment: impact of documentation on maintenance. In: Empirical Software Engineering. Vol. 2, no. 2; 1997; p. 201-7. Google ScholarDigital Library
- {34} Von Mayrhauser, A.; Vans, A. M.; On increasing our knowledge of large-scale software comprehension. In: Empirical Software Engineering. Vol. 2, no. 2; 1997; p. 159-63. Google ScholarDigital Library
- {35} Zuse, H.; Comments to the paper: Briand, Eman, Morasca: on the application of measurement theory in software engineering. In: Empirical Software Engineering. Vol. 2, no. 3; 1997; p. 313-16. Google ScholarDigital Library
Index Terms
- Empirical research in software engineering: a workshop
Recommendations
Software engineering research versus software development
Engineering research differs greatly, both in its aims and in its methods, from traditional "scientific" research. While Sciences deal with the study of existing objects and phenomena, be it physically, metaphysically or conceptually, Engineering is ...
Software, software engineering and software engineering research: some unconventional thoughts
Software engineering is broadly discussed as falling far short of expectations. Data and examples are used to justify how software itself is often poor, how the engineering of software leaves much to be desired, and how research in software engineering ...
Comments