Experimental evaluation of team performance in program development based on a model
Journal of Information Processing
Fault generation model and mental stress effect analysis
Journal of Systems and Software - Special issue on achieving quality in software
Experimental software engineering: a report on the state of the art
Proceedings of the 17th international conference on Software engineering
The role of experimentation in software engineering: past, current, and future
Proceedings of the 18th international conference on Software engineering
An experiment to assess different defect detection methods for software requirements inspections
ICSE '94 Proceedings of the 16th international conference on Software engineering
ICSE '94 Proceedings of the 16th international conference on Software engineering
Measuring cognitive activities in software engineering
Proceedings of the 20th international conference on Software engineering
The ramp-up problem in software projects: a case study of how software immigrants naturalize
Proceedings of the 20th international conference on Software engineering
A Replicated Experiment to Assess Requirements InspectionTechniques
Empirical Software Engineering
The Experience Factory and its Relationship to Other Improvement Paradigms
ESEC '93 Proceedings of the 4th European Software Engineering Conference on Software Engineering
An Empirical Evaluation of Three Defect-Detection Techniques
Proceedings of the 5th European Software Engineering Conference
Accumulative versioning file system Moraine and its application to metrics environment MAME
SIGSOFT '00/FSE-8 Proceedings of the 8th ACM SIGSOFT international symposium on Foundations of software engineering: twenty-first century applications
Conducting experiments on software evolution
IWPSE '01 Proceedings of the 4th International Workshop on Principles of Software Evolution
Analyzing individual performance of source code review using reviewers' eye movement
Proceedings of the 2006 symposium on Eye tracking research & applications
WebTracer: A new web usability evaluation environment using gazing point information
Electronic Commerce Research and Applications
Empirical results from using custom-made software project control centers in industrial environments
Proceedings of the Second ACM-IEEE international symposium on Empirical software engineering and measurement
Goal-Oriented Setup and Usage of Custom-Tailored Software Cockpits
PROFES '08 Proceedings of the 9th international conference on Product-Focused Software Process Improvement
Exploiting Eye Movements for Evaluating Reviewer's Performance in Software Review
IEICE Transactions on Fundamentals of Electronics, Communications and Computer Sciences
Software project control centers: concepts and approaches
Journal of Systems and Software
ESEML: empirical software engineering modeling language
Proceedings of the 2012 workshop on Domain-specific modeling
Hi-index | 0.00 |
Empirical software engineering can be viewed as a series of actions to obtain knowledge and a better understanding about some aspects of software development given a set of problem statements in the form of issues, questions or hypotheses. Our experience in conducting empirical software engineering from a variety of viewpoints for the last decade has made us aware of the criticality of integrating the various types of data that are collected and analyzed as well as the criticality of integrating the various types of activities that take place such as experiment design and the experiment itself. This has led us to develop a Computer-Aided Empirical Software Engineering (CAESE) framework as a substrate for supporting the empirical software engineering lifecycle. CAESE supports empirical software engineering in the same manner as a CASE environment serves as a substrate for supporting the software development lifecycle. This paper first presents the CAESE framework that consists of three elements. The first element is a process model for the 驴lifecycle驴 of empirical software engineering studies, including needs analysis, experiment design, actual experimentation, and analyzing and packaging results. The second element is a model that helps empirical software engineers decide how to look at the 驴world驴 to be studied in a coherent manner. The third element is an architecture based on which CAESE environments can be built, consisting of tool sets for each phase of the process model, a process management mechanism, and the two types of integration mechanism that are vital for handling multiple types of data: data integration and control integration. The second half of this paper describes the Ginger2 environment as an instantiation of our framework. The paper concludes with reports on case studies using Ginger2, which dealt with a variety of empirical data types including mouse and keystrokes, eye traces, three-dimensional movement, skin resistance level, and video-taped data.