共查询到20条相似文献,搜索用时 15 毫秒
1.
In this paper we explore how the software engineering research community is currently dealing with the ethical issues that some empirical research presents. We discuss how the immaturity of the software engineering discipline is reflected in an approach to ethical issues that compares unfavourably with other more mature disciplines.We show that an analysis of recent published work measures an increase in empirical software engineering research currently being undertaken. We also discuss our survey of UK University Department Heads which explores how the software engineering research community is dealing with the ethical issues related to empirical work. Overall we found that whilst some UK Universities have taken ethical issues very seriously, others have not considered the issues. 相似文献
2.
3.
4.
R. Harrison L. Briand J. Daly M. Kellner D. M. Raffo M. J. Shepperd 《Empirical Software Engineering》1997,2(4):381-403
Much progress is being made in both the areas of process modelling and software metrics. However, neither of these concepts is complete without the other: processes cannot be improved if no assessment of quality is available, and metrics are useless if they cannot be applied in order to assess the evolution of systems. The PMESSE (Process Modelling and Empirical Studies of Software Evolution) Workshop, held in Boston MA, on May 18, 1997, brought together researchers and practitioners from both of these fields, and stimulated some very lively debate on these issues. This collection of reports reflects the work done by the Workshops five Working Groups.Dialogue between the software metrics and process modelling communities is essential. This workshop succeeded in bringing together researchers with a wide range of research interests, and the resulting discussions were very animated. Perhaps the most contentious point of discussion lay in the 'level of granularity' question; some suggested that only high-level measurements were sensible, whereas others preferred to 'divide and conquer' the system, providing detailed process measurement schemas. No doubt this debate will continue. 相似文献
5.
Rebecca E. Grinter 《Computer Supported Cooperative Work (CSCW)》2003,12(3):297-327
In this paper, I revisit theconcept of recomposition – all the work thatdevelopment organizations do to make sure thattheir product fits together and into a broaderenvironment of other technologies. Technologies, such as Configuration Management(CM) systems, can ameliorate some of a softwaredevelopment team's need to engage inrecomposition. However, technologicalsolutions do not scale to address other kindsof recomposition needs. This paper focuses onvarious organizational responses to the needfor recomposition. By organizational response,I mean how individuals engage in recompositionso that the organization can assemble softwaresystems from parts. Specifically, I describehow those responses are manifested in theday-to-day communications and responsibilitiesof individuals throughout the organization. Ialso highlight how changes in an organizationcomplicate recomposition. The paper concludeswith a discussion of three features of softwaredevelopment work that are revealed byrecomposition: the affects of environmentaldisturbances on development work, the types ofdependencies that require recomposition, andthe images of organizations required to managethe recomposition. 相似文献
6.
Software engineering is an intensively people-oriented activity, yet too little is known about how designers, maintainers, requirements analysts and all other types of software engineers perform their work. In order to improve software engineering tools and practice, it is therefore essential to conduct field studies, i.e. to study real practitioners as they solve real problems. To do so effectively, however, requires an understanding of the techniques most suited to each type of field study task. In this paper, we provide a taxonomy of techniques, focusing on those for data collection. The taxonomy is organized according to the degree of human intervention each requires. For each technique, we provide examples from the literature, an analysis of some of its advantages and disadvantages, and a discussion of how to use it effectively. We also briefly talk about field study design in general, and data analysis.The authors appear in alphabetical order and contributed equally. 相似文献
7.
The role of replications in Empirical Software Engineering 总被引:1,自引:1,他引:1
Forrest J. Shull Jeffrey C. Carver Sira Vegas Natalia Juristo 《Empirical Software Engineering》2008,13(2):211-218
Replications play a key role in Empirical Software Engineering by allowing the community to build knowledge about which results
or observations hold under which conditions. Therefore, not only can a replication that produces similar results as the original
experiment be viewed as successful, but a replication that produce results different from those of the original experiment
can also be viewed as successful. In this paper we identify two types of replications: exact replications, in which the procedures of an experiment are followed as closely as possible; and conceptual replications, in which the same research question is evaluated by using a different experimental procedure. The focus of this paper is
on exact replications. We further explore them to identify two sub-categories: dependent replications, where researchers attempt to keep all the conditions of the experiment the same or very similar and independent replications, where researchers deliberately vary one or more major aspects of the conditions of the experiment. We then discuss the role
played by each type of replication in terms of its goals, benefits, and limitations. Finally, we highlight the importance
of producing adequate documentation for an experiment (original or replication) to allow for replication. A properly documented
replication provides the details necessary to gain a sufficient understanding of the study being replicated without requiring
the replicator to slavishly follow the given procedures.
相似文献
Natalia JuristoEmail: |
8.
《Computer》2009,42(1):74-80
The authors identify, categorize, and name nine specific ethical and professional dilemmas in software engineering, placing them in the context of the IEEE code of conduct, with the hope that giving such behavior a name will increase awareness and decrease the frequency with which these dilemmas occur. 相似文献
9.
Forrest Shull Manoel G. Mendoncça Victor Basili Jeffrey Carver José C. Maldonado Sandra Fabbri Guilherme Horta Travassos Maria Cristina Ferreira 《Empirical Software Engineering》2004,9(1-2):111-137
Recently the awareness of the importance of replicating studies has been growing in the empirical software engineering community. The results of any one study cannot simply be extrapolated to all environments because there are many uncontrollable sources of variation between different environments. In our work, we have reasoned that the availability of laboratory packages for experiments can encourage better replications and complementary studies. However, even with effectively specified laboratory packages, transfer of experimental know-how can still be difficult. In this paper, we discuss the collaboration structures we have been using in the Readers’ Project, a bilateral project supported by the Brazilian and American national science agencies that is investigating replications and transfer of experimental know-how issues. In particular, we discuss how these structures map to the Nonaka–Takeuchi knowledge sharing model, a well-known paradigm used in the knowledge management literature. We describe an instantiation of the Nonaka–Takeuchi Model for software engineering experimentation, establishing a framework for discussing knowledge sharing issues related to experimental software engineering. We use two replications to illustrate some of the knowledge sharing issues we have faced and discuss the mechanisms we are using to tackle those issues in Readers’ Project. 相似文献
10.
Filippo Lanubile 《Empirical Software Engineering》1997,2(2):97-108
Technology evaluation is part of the decision-making process of any software organization. Unlike conventional wisdom, empirical
evaluation strives to avoid biased conclusions by relying on observation and looking for pitfalls in the evaluation process.
In this paper, we provide a summary of the maintenance studies presented in the session ‘Study and assessment of (new) technologies’
of the International Workshop on Empirical Studies of Software Maintenance (WESS '96), and also report on the working group
discussion which focused on common problems and open issues in the field of technology evaluation. These empirical studies
are then classified according to a multi-dimensional framework to synthesize the state of the research in technology evaluation
and ultimately discover interesting patterns.
This revised version was published online in July 2006 with corrections to the Cover Date. 相似文献
11.
12.
《IEEE transactions on pattern analysis and machine intelligence》1981,(4):333-342
Software engineering project management (SEPM) has been the focus of much recent attention because of the enormous penalties incurred during software development and maintenance resulting from poor management. To date there has been no comprehensive study performed to determine the most significant problems of SEPM, their relative importance, or the research directions necessary to solve them. We conducted a major survey of individuals from all areas of the computer field to determine the general consensus on SEPM problems. Twenty hypothesized problems were submitted to several hundred individuals for their opinions. The 294 respondents validated most of these propositions. None of the propositions was rejected by the respondents as unimportant. A number of research directions were indicated by the respondents which, if followed, the respondents believed would lead to solutions for these problems. 相似文献
13.
In this paper we discuss our study of the problems 12 software companies experienced in software development. In total we present qualitative data collected from 45 focus groups that involved over 200 software staff. We look at how different practitioner groups respond to software process improvement problems. We show our classification and analysis of this data using correspondence analysis. Correspondence analysis is a graphical data representation method new to software development research. The aim of the work we present is to develop a more holistic understanding of the problems practitioners are experiencing in their attempts to improve their software processes. Our main finding is that there is an association between a company's capability maturity and patterns of reported problems. Organizational problems are more associated with high maturity companies than with low maturity companies. Low maturity companies are closely linked to problems relating directly to projects such as documentation, timescales, tools and technology. Our findings also confirm differences in practitioner group problems. Senior managers cite problems with goals, culture and politics. Project managers are concerned with timescales, change management, budgets and estimates. Developers are experiencing problems with requirements, testing, documentation, communication, tools and technology. These associations are displayed graphically through correspondence analysis maps. 相似文献
14.
Editorial Commentary
Editorial: Open Source and Empirical Software Engineering 相似文献15.
16.
17.
Hints for Reviewing Empirical Work in Software Engineering 总被引:4,自引:3,他引:1
Walter F. Tichy 《Empirical Software Engineering》2000,5(4):309-312
18.
19.
Warren Sack Françoise Détienne Nicolas Ducheneaut Jean-Marie Burkhardt Dilan Mahendran Flore Barcellini 《Computer Supported Cooperative Work (CSCW)》2006,15(2-3):229-250
Open Source Software (OSS) development challenges traditional software engineering practices. In particular, OSS projects are managed by a large number of volunteers, working freely on the tasks they choose to undertake. OSS projects also rarely rely on explicit system-level design, or on project plans or schedules. Moreover, OSS developers work in arbitrary locations and collaborate almost exclusively over the Internet, using simple tools such as email and software code tracking databases (e.g. CVS).All the characteristics above make OSS development akin to weaving a tapestry of heterogeneous components. The OSS design process relies on various types of actors: people with prescribed roles, but also elements coming from a variety of information spaces (such as email and software code). The objective of our research is to understand the specific hybrid weaving accomplished by the actors of this distributed, collective design process. This, in turn, challenges traditional methodologies used to understand distributed software engineering: OSS development is simply too “fibrous” to lend itself well to analysis under a single methodological lens.In this paper, we describe the methodological framework we articulated to analyze collaborative design in the Open Source world. Our framework focuses on the links between the heterogeneous components of a project’s hybrid network. We combine ethnography, text mining, and socio-technical network analysis and visualization to understand OSS development in its totality. This way, we are able to simultaneously consider the social, technical, and cognitive aspects of OSS development. We describe our methodology in detail, and discuss its implications for future research on distributed collective practices.The order of the co-authors names is not significant. 相似文献
20.
Objective: To improve the qualitative data obtained from software engineering experiments by gathering feedback during experiments. Rationale: Existing techniques for collecting quantitative and qualitative data from software engineering experiments do not provide sufficient information to validate or explain all our results. Therefore, we would like a cost-effective and unobtrusive method of collecting feedback from subjects during an experiment to augment other sources of data. Design of study: We formulated a set of qualitative questions that might be answered by collecting feedback during software engineering experiments. We then developed a tool to collect such feedback from experimental subjects. This feedback-collection tool was used in four different experiments and we evaluated the usefulness of the feedback obtained in the context of each experiment. The feedback data was triangulated with other sources of quantitative and qualitative data collected for the experiments. Results: We have demonstrated that the collection of feedback during experiments provides useful additional data to: validate the data obtained from other sources about solution times and quality of solutions; check process conformance; understand problem solving processes; identify problems with experiments; and understand subjects perception of experiments. Conclusions: Feedback collection has proved useful in four experiments and we intend to use the feedback-collection tool in a range of other experiments to further explore the cost-effectiveness and limitations of this technique. It is also necessary to carry out a systematic study to more fully understand the impact of the feedback-collecting tool on subjects performance in experiments. 相似文献