An empirical study of the object-oriented paradigm and software reuse

Lewis, John A.; Henry, Sallie M.; Kafura, Dennis; Schulman, Robert S.

doi:10.1145/117954.117969

Cited by 45 publications

(6 citation statements)

References 7 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…To control for programming language, we divided the projects' languages, using a dummy variable, into two generally accepted categories: procedural languages such as C and object‐oriented languages such as C++ (Lewis, Henry, Kafura, & Schulman, 1991). Software size was measured by the total LOC for each project at each of the defined points in time, and was collected using another PERL script.…”

Section: Methodsmentioning

confidence: 99%

Impact of license choice on Open Source Software development activity

Colazo

Fang

2009

J. Am. Soc. Inf. Sci.

View full text Add to dashboard Cite

The Open Source Software (OSS) development model has emerged as an important competing paradigm to proprietary alternatives; however, insufficient research exists to understand the influence of some OSS project characteristics on the level of activity of the development process. A basic such characteristic is the selection of the project's software license. Drawing upon social movement theory, our study examined the relationship between OSS licenses and project activity. Some OSS licenses include a "copyleft" clause, which requires that if derivative products are to be released, it must be done under the license the original product had. We hypothesize that copylefted licenses, as opposed to noncopylefted licenses, are associated with higher developer membership and coding activity, faster development speed, and longer developer permanence in the project. To test the hypotheses, we used archival data sources of working OSS projects spanning several years of development time. We discuss practical and theoretical implications of the results as well as future research ideas.

show abstract

Section: Methodsmentioning

confidence: 99%

Impact of license choice on Open Source Software development activity

Colazo

Fang

2009

J. Am. Soc. Inf. Sci.

View full text Add to dashboard Cite

show abstract

“…By "empirical study of code" we mean a study in which the artifacts under investigation consist of source code, there are multiple, unrelated, artifacts, and the artifacts were developed independently of the study. This rules out, for example, studies that included the creation of the code artifacts, such as those by Briand et al [3] or Lewis et al [4], and studies of one system, such as that by Barry [5].…”

Section: A Empirical Studies Of Codementioning

confidence: 99%

The Qualitas Corpus: A Curated Collection of Java Code for Empirical Studies

Tempero

Anslow

Dietrich

et al. 2010

2010 Asia Pacific Software Engineering Conference

333

181

View full text Add to dashboard Cite

In order to increase our ability to use measurement to support software development practise we need to do more analysis of code. However, empirical studies of code are expensive and their results are difficult to compare. We describe the Qualitas Corpus, a large curated collection of open source Java systems. The corpus reduces the cost of performing large empirical studies of code and supports comparison of measurements of the same artifacts. We discuss its design, organisation, and issues associated with its development.

show abstract

“…Experiments are useful to prove the empirical validity of metrics, but the internal and external replication of them is necessary [Brook96; Basil99; Brian00a), to obtain stronger results. As Lewis et al [Lewis91] remark, the use of precise, repeatable experiments is the hallmark of a mature scientific or engineering discipline. Only after performing a family of experiments you can build an adequate body of knowledge to extract useful measurement conclusions regarding the use of OO design metrics to be applied in real measurement projects [Basil99;Mille00].…”

Section: General Commentsmentioning

confidence: 99%

A Survey of Metrics for UML Class Diagrams.

Genero¹,

Piattini²,

Calero³

2005

JOT

116

View full text Add to dashboard Cite

The demand for increased software quality has resulted in quality being more of differentiator between products than it ever has been before. For this reason, software developers need objective and valid measures for use in the evaluation and improvement of product quality from the initial stages of development. Class diagrams are a key artifact in the development of object-oriented (OO) software because they lay the foundation for all later design and implementation work. It follows that emphasizing class diagram quality may significantly contribute to higher quality OO software systems. The primary aim of this work, therefore, is to present a survey, as complete as possible, of the existing relevant works regarding class diagram metrics. Thus, from works previously published, researchers and practitioners alike may gain broad and ready access to insights for measuring these quality characteristics. Another aim of this work is to help reveal areas of research either lacking completion or yet to undertaken. A SURVEY OF METRICS FOR UML CLASS DIAGRAMS 60 J OURNAL OF OBJECT TECHNOLOGY V OL. 4, NO. 9 Recently, paradigms such as Model-Driven Development [Atkin03] and the Model-Driven Architecture [OMG02] have emphasized the importance of "good" models from the beginning of the life cycle. For that reason, the main focus must be on the quality of models obtained in these "early" stages. In the OO paradigm one of the key artifacts is the class diagram. The class diagram constitutes the backbone of the OO development and provides a solid foundation for the design and the implementation of software. Therefore, class diagram quality has great influence over the system that is ultimately implemented. Quality in software products is characterised by the presence of different external attributes 1 such as functionality, reliability, usability, efficiency, maintainability and portability [ISO01]. But these attributes can only be measured late in the OO software development life cycle. Therefore, it is necessary to find early indicators of such qualities based, for example, on the structural properties of class diagrams [Briand00a]. This is the context where software measurement is fundamental, because measures can allow us to evaluate class diagram quality characteristics in an objective way, thus avoiding a bias in the evaluation process. Measuring class diagram quality allows OO software designers: • to identify weak design spots when it costs less to improve them, rather than repair consequent errors at later implementation phases. • to choose between design alternatives in an objective way. • to predict external quality characteristics such as, maintainability, reusability, etc., and improve resource allocation based on these predictions. Although in the OO software measurement arena the need for measures that can be applied in the early phases of the development process is emerging, up until a few years ago the work done in this sense was scarce because most software measurement researchers focused on the measurement of c...

show abstract

An empirical study of the object-oriented paradigm and software reuse

Cited by 45 publications

References 7 publications

Impact of license choice on Open Source Software development activity

Impact of license choice on Open Source Software development activity

The Qualitas Corpus: A Curated Collection of Java Code for Empirical Studies

A Survey of Metrics for UML Class Diagrams.

Contact Info

Product

Resources

About