Titlebook: Experimentation in Software Engineering; An Introduction Claes Wohlin,Per Runeson,Anders Wesslén Textbook 2000 Springer Science+Business Me

擴(kuò)張

exacerbate

https://doi.org/10.1007/b109323 we need a process supporting us in our objectives in doing experiments correctly (the notion of experiments include quasi-experiments, unless clearly stated otherwise). The basic principles behind an experiment are illustrated in Figure 7.

恩惠

Introduction, terms of missing functionality, cost overruns, missed deadlines and poor quality. These problems or challenges were identified already in the 1960’s, and in 1968 the term “software engineering” was coined with the intention of creating an engineering discipline that focused on the development of software systems.

背信

MIRE

https://doi.org/10.1057/9781137316394ent and after the experiment when the results of the experiment are presented to the subjects. Since experiments in software engineering almost always deal with humans, this chapter deals to some extent with how to motivate people to participate and take part in experiments.

錯

CRUDE

Operation,ent and after the experiment when the results of the experiment are presented to the subjects. Since experiments in software engineering almost always deal with humans, this chapter deals to some extent with how to motivate people to participate and take part in experiments.

Euphonious

斜谷

Empirical Strategies,egins with accepting that there is a range of different ways of interpretation. It is concerned with discovering causes noticed by the subjects in the study, and understanding their view of the problem at hand. The subject is the person, which is taking part in an experiment in order to evaluate an object.

微塵