Basili, V.R., The Role of Experimentation in Software Engineering: Past, Current, and Future. in 18th International Conference on Software Engineering (ICSE 18), (Berlin, Germany, 1996), IEEE Computer Society Press, 442-449.  Home/Search   Document Not in Database   Summary   Related Articles   Check

....subprojects of the SFB 501 in team1. This resulted in a lot of different knowledge within the team. The initial goal of team1was also quite 1. This work was supported by the Deutsche Forschungsgemeinschaft, Sonderforschungsbereich 501, Entwicklung groer Systeme mit generischen Methoden . 2. See [Bas96] for an overview of the use of experiments in software engineering. ambitious because all its members could be regarded more or less as novices in the application of formal methods. In order to get acquainted with their use, a simulator for heat flow within buildings was specified as a first ....

V. R. Basili, The role of experimentation in software engineering: Past, current, and future. In Proc. of the 18th Intl. Conf. on Software Engineering, pp. 442-449. IEEE Computer Society Press, 1996.

....application context (e.g. personnel experience, skill, and goals) are taken into account. The background of the work reported on here includes: a feature analysis centred framework for empirically evaluating software technologies [1] the milestones of software engineering experimentation [2,3], both the efforts made to establish Experimental Software Engineering groups world wide [4] and to reach practitioners [5,6] Differently from other papers, this work refers to the whole system of organisations that are involved in SW technology transfer, and not to SW developers only. Such a ....

Basili, V. R., "The Role of Experimentation in Software Engineering, Past, Current and Future", in Proceedings of the 18th ICSE. IEEE Computer Society Press, 1996.

....occasions we identified. 2. The Experience Engine Vs. the Experience Factory We believe that in applying the experience factory approach, the same applies with the software engineering discipline these are laboratory sciences and we must experiment with techniques to see if they really work[2]. We realized rather quickly that we could not implement the entire approach, at least not directly. The name, Experience Factory can lead to associations with industrial production. But software engineering is not about reproducing the same things every product is different than all others ....

....We realized rather quickly that we could not implement the entire approach, at least not directly. The name, Experience Factory can lead to associations with industrial production. But software engineering is not about reproducing the same things every product is different than all others [2] so we renamed our application The Experience Engine . We wanted to create an engine that would continuously work to recycle and transfer the collective experience within the company. The experience factory focuses on process improvement. And it should not be part of any project organization, ....

V. R. Basili, "The Role of Experimentation in Software Engineering: Past, Current, and Future", Proceedings of ICSE `96, 1996, pp 442-449

....Over the last 30 years there have been significant developments in software engineering methods and technology.However, the empirical evidence necessary to quantify their relative merits is not available. In recentyears there have been a number of high profile pleas for more empirical research [1,23,25]. More specifically, the International Software Engineering Research Network (ISERN) has been established to foster collaborative empirical research. One of the main reasons that there is a lack of empirical research is that it is difficult. The human intensivenatureofsoftware engineering, ....

V. Basili. The role of experimentation in software engineering: Past, current, and future. In Proceedings of the IEEE International Conference on Software Engineering, pages 442--449, 1996.

.... criteria, their risk (Kitchenham, 1996) Principles of SW feature analysis (Kitchenham, 1996; Kitchenham, 1996 1997) A method for developing SW quantitative case studies (Kitchenham, 1996) Moreover, many papers reported about lessons learned while running new or replicated experiments (Basili, et al. 1996; Briand, et al. 1996; Ciolkowsky, et al. 1997; Kamstie and Lott, 1995; Porter, et al. 1995; Visaggio, 1997; and see the ISERN web page for further references) Finally, a Process Improvement Experiment project (PIE) was launched in Europe, to develop a standard like TT meta model (see the ESI ....

Basili V R. 1996. The role of experimentation in software engineering: past, current and future. In Proceedings 18 th International Conference on Software Engineering. IEEE Computer Society Press: Los Alamitos CA; 442-449.

....application context (e.g. personnel experience, skill, and goals) are taken into account. The background of the work reported on here includes: a feature analysis centered framework for empirically evaluating software technologies [1] the milestones of software engineering experimentation [2,3], both the efforts made to establish Experimental Software Engineering groups worldwide [4] and to reach practitioners [5,6] Differently from other papers, this work refers to the whole system of organizations that are involved in SW technology transfer, and not to SW developers only. Such a ....

Basili, V. R., "The Role of Experimentation in Software Engineering, Past, Current and Future", in Proceedings of the 18th ICSE. IEEE Computer Society Press, 1996.

....of defining terms pre12 cisely becomes accepted. The community is also beginning to accept that software metrics must be not only validated theoretically, but also empirically, through observation of their use during software development projects both in the laboratory and in the real world [22]. Our empirical results indicate that the MOOD metrics operate at the systems level. Comparing them with those of Chidamber and Kemerer [11] we see that the two sets are complementary, offering different assessments of a system. For example, the coupling metrics (CBO and CF) are closely related, ....

V. Basili, "The role of experimentation in software engineering: past, present and future," in Proc 18th ICSE, pp. 442--449, 1996. 15

....design need to invest more effort in understanding the design than those who are given a natural language design. Keywords: Quantitative experiment, formal user interface design, Object Z 1 Introduction There is a lack of experimentation in assessing software engineering development methods [1]. This may be because model builders leave this work to experimenters or it may be because the model builders view their work as self evident. Software engineering researchers need to build, analyse and evaluate software processes, as well as various aspects of the environment in which the ....

....model builders leave this work to experimenters or it may be because the model builders view their work as self evident. Software engineering researchers need to build, analyse and evaluate software processes, as well as various aspects of the environment in which the software is being built [1]. We can improve the artifacts that we produce in software engineering by experimenting with variations in the software process and analysing the effect on the revised product. Quantitative (formal or controlled) experiments generate stronger statistical confidence in their conclusions than do ....

V. R. Basili. The Role of Experimentation in Software Engineering: Past, Current, and Future. In Proceedings of ICSE-18, pages 442--449. IEEE, 1996.

....the tools. At this time, we have little understanding of the factors that influence productivity and quality of software development and interaction between them. A lot of experimental work is required to create the knowledge base that will allow us to start in depth studies of such interactions [1]. The choice of programming language affects productivity of software development. To characterize the relationship between the language and productivity, Jones ranked programming languages with respect to their level [3] Jones level is inversely proportional to the size of the program in ....

Basili V., The Role of Experimentation in Software Engineering: Past, Present, and Future. Proceedings of the 18th International Conference on Software Engineering, Berlin, Germany, 1996.

....detection is an individual rather than a group activity. Individual defect detection is performed by one or more inspectors identifying potential defects in the document using a particular reading technique. Yet, even though reading is one of the key activities for individual defect detection [2], few techniques or tools are available to support it. Ad hoc and Checklist reading probably are the most popular reading techniques used today for defect detection in inspections [6] 7] Ad hoc reading offers no reading support at all since a document is simply given to inspectors without any ....

....Using a scenario should lead to a focused understanding of the document. We hypothesize that this understanding supports individual defect detection more effectively than many other approaches. 1. 2 Related Work Work on reading techniques and their experimental validation has previously been done [2], 4] 10] For instance, Reading by Stepwise Abstraction (RSA) was one of the first reading techniques developed and experimentally validated [16] Such an experiment conducted with students of the University of Maryland from 1982 to 1984 found that RSA is more effective in detecting defects than ....

Victor Basili, The Role of Experimentation in Software Engineering: Past, Present, and Future, Keynote Address, 18th International Conference on Software Engineering, Berlin 1996.

....is easily possible just by analyzing it. But there are also several criteria that require empirical data, for example the one mentioned above dealing with the effort needed to learn to write good system descriptions. In such cases we suggest to perform controlled experiments in the sense of [Bas96] in order to acquire the data needed. 3.2 Application of the Criteria Catalogue When applying the criteria catalogue to a formal method two tasks have to be performed: the tailoring of the criteria catalogue and the acquisition of data. Because of the current representation of the criteria ....

....modularity concepts are not supported. With respect to the very important criterion Readability 38 , SDL and statecharts are rated better than tRTTL. Note, that the attributes are assigned on the subjective experience of the authors and have to be confirmed by controlled experiments, see e.g. Bas96] Due to the large number of important criteria, here only a few of them are discussed that reveal differences among the formal methods. With respect to the criterion Degree of Formality 4 tRTTL and SDL are better than statecharts, since we have established the ordering formal rigorous. For ....

V. R. Basili. The role of experimentation in software engineering: Past, current, and future. In Proc. of 18th Intl. Conf. on Software Engineering, pages 442--449. IEEE Computer Society Press, 1996.

....I devoured both of these books. I highly recommend reading at least one of them. The following literature concerns experimentation in computer science. For an appreciation of how software researchers experiment, sample the material cited in the main article and the papers by Basili and Frankl [1, 8]. A good example of a repeated experiment in compiling is Brett [2] Denning [6] argues that performance evaluation is an excellent form of experimentation in computer science. A landmark in making computer architecture research quantitative is Hennesey s and Patterson s classic book Computer ....

Victor R. Basili. The role of experimentation in software engineering: Past, current, and future. In Proc. of the 18th International Conference on Software Engineering, pages 442--449. IEEE Computer Society Press, March 1996.

....and by NSF grant CCR9706151. 2 studies in the domain of software engineering, and (2) suggest how to package this experience in a form that supports multiple replication studies around common questions of interest. For the purpose of this paper, we use the definitions of some key terms from [1]. An empirical study, in a broad sense, is an act or operation for the purpose of discovering something unknown or of testing a hypothesis, involving an investigator gathering data and performing analysis to determine what the data mean. This covers various forms of research strategies, including ....

V. R. Basili, "The role of experimentation in software engineering: past, current and future", in Proc. of the 18th Int. Conf. on Software Engineering, Berlin, Germany, pp. 442-449, 1996.

....I devoured both of these books. I highly recommend reading at least one of them. The following literature concerns experimentation in computer science. For an appreciation of how software researchers experiment, sample the material cited in the main article and the papers by Basili and Frankl [1, 8]. A good example of a repeated experiment in compiling is Brett [2] Denning [6] argues that performance evaluation is an excellent form of experimentation in computer science. A landmark in making computer architecture research quantitative is Hennesey s and Patterson s classic book Computer ....

Victor R. Basili. The role of experimentation in software engineering: Past, current, and future. In Proc. of the 18th International Conference on Software Engineering, pages 442--449. IEEE Computer Society Press, March 1996.

No context found.

Basili, V.R., The Role of Experimentation in Software Engineering: Past, Current, and Future. in 18th International Conference on Software Engineering (ICSE 18), (Berlin, Germany, 1996), IEEE Computer Society Press, 442-449.

No context found.

Basili, V.R., The Role of Experimentation in Software Engineering: Past, Current, and Future. in 18th International Conference on Software Engineering (ICSE 18), (Berlin, Germany, 1996), IEEE Computer Society Press, 442-449.

No context found.

V. R. Basili. The role of experimentation in software engineering: past, current, and future. In Proceedings of the 18th International Conference on Software Engineering, pages 442--449, Berlin, Germany, Mar. 25--29, 1996.

No context found.

Basili, V. The role of experimentation in software engineering: past, current, and future. Proceedings of the ICSE '96, pp442-449.

No context found.

Basili V. R.: "The Role of Experimentation in Software Engineering: Past, Current and Future", in Proceedings of the 18th ICSE. IEEE Computer Society Press, 1996.

No context found.

V.R. Basili.The Role of Experimentation in Software Engineering: Past, Current, and Future. Proceedings of ICSE-18, 1996.

Online articles have much greater impact   More about CiteSeer.IST   Add search form to your site   Submit documents   Feedback  

CiteSeer.IST - Copyright Penn State and NEC