Creative professional users musical relevance criteria

Although known item searching for music can be dealt with by searching metadata using existing text search techniques, human subjectivity and variability within the music itself make it very difficult to search for unknown items. This paper examines these problems within the context of text retrieval and music information retrieval. The focus is on ascertaining a relationship between music relevance criteria and those relating to relevance judgements in text retrieval. A data-rich collection of relevance judgements by creative professionals searching for unknown musical items to accompany moving images using real world queries is analysed. The participants in our observations are found to take a socio-cognitive approach and use a range of content and context based criteria. These criteria correlate strongly with those arising from previous text retrieval studies despite the many differences between music and text in their actual content

An empirical investigation of an object-oriented software system

This is the post print version of the article. The official published version can be obtained from the link below.This paper describes an empirical investigation into an industrial object-oriented (OO) system comprised of 133,000 lines of C++. The system was a subsystem of a telecommunications product and was developed using the Shlaer-Mellor method. From this study, we found that there was little use of OO constructs such as inheritance and, therefore, polymorphism. It was also found that there was a significant difference in the defect densities between those classes that participated in inheritance structures and those that did not, with the former being approximately three times more defect-prone. We were able to construct useful prediction systems for size and number of defects based upon simple counts such as the number of states and events per class. Although these prediction systems are only likely to have local significance, there is a more general principle that software developers can consider building their own local prediction systems. Moreover, we believe this is possible, even in the absence of the suites of metrics that have been advocated by researchers into OO technology. As a consequence, measurement technology may be accessible to a wider group of potential users

Software Metrics in Boa Large-Scale Software Mining Infrastructure: Challenges and Solutions

In this paper, we describe our experience implementing some of classic software engineering metrics using Boa - a large-scale software repository mining platform - and its dedicated language. We also aim to take an advantage of the Boa infrastructure to propose new software metrics and to characterize open source projects by software metrics to provide reference values of software metrics based on large number of open source projects. Presented software metrics, well known and proposed in this paper, can be used to build large-scale software defect prediction models. Additionally, we present the obstacles we met while developing metrics, and our analysis can be used to improve Boa in its future releases. The implemented metrics can also be used as a foundation for more complex explorations of open source projects and serve as a guide how to implement software metrics using Boa as the source code of the metrics is freely available to support reproducible research.Comment: Chapter 8 of the book "Software Engineering: Improving Practice through Research" (B. Hnatkowska and M. \'Smia{\l}ek, eds.), pp. 131-146, 201

Comparison Study and Review on Object-Oriented Metrics

The best elucidations to software development problems are regularly touted as object-oriented processes. The popularity of object-oriented design metrics is essential in software engineering for measuring the software complexity, estimating size, quality and project efforts. There are various approaches through which we can find the software cost estimation and predicates on various kinds of deliverable items. Object-oriented metrics assures to reduce cost and the maintenance effort by serving as early predictors to estimate software faults. Such an early quantification augments the quality of the final software. This paper reviews object-oriented metrics. A comparison table is maintained via which we can analyze the difference between all the object-oriented metrics effectively

A Review of Metrics for Object-Oriented Design

The ever-evolving body of empirical results do confirmation on the theoretical perspective the validity of OOD metrics whose validity is determined by them demonstrating that [1] they measure what they purport to measure. Quite often OOD metrics have been used as indicators of both the internal and external behaviors in the software development process. Software metrics especially for Object Oriented Systems literature often describe complex models with the focus to help predict various properties of software products and processes by measuring other properties. Usually designers are met with challenges to work with these measures especially when and how to use them. The very process of collecting these measurements leads to a better organization of the software process and a better understanding of what designers do as long as they confine to measurements that are meaningful. To this end therefore, the initiation of these metrics during the initial software development process is important. This paper elicits an understanding of the OOD metrics used in OOS development

A Review of Metrics for Object-Oriented Design

The ever-evolving body of empirical results do confirmation on the theoretical perspective the validity of OOD metrics whose validity is determined by them demonstrating that [1] they measure what they purport to measure. Quite often OOD metrics have been used as indicators of both the internal and external behaviors in the software development process. Software metrics especially for Object Oriented Systems literature often describe complex models with the focus to help predict various properties of software products and processes by measuring other properties. Usually designers are met with challenges to work with these measures especially when and how to use them. The very process of collecting these measurements leads to a better organization of the software process and a better understanding of what designers do as long as they confine to measurements that are meaningful. To this end therefore, the initiation of these metrics during the initial software development process is important. This paper elicits an understanding of the OOD metrics used in OOS development

Penerapan Dominance-based Rough Set Approach Dalam Pemeringkatan Kualitas Desain Software Berorientasi Objek

Penerapan Dominance-based Rough Set Approach (DRSA) untuk menentukan peringkat kualitas sejumlah aplikasi berbasis objek telah dipelajari. DRSA diterapkan untuk memformulasikan satu set klasifikasi dimana kualitas software aplikasi digolongkan. Klasifikasi dibentuk berdasarkan hasil pengukuran Metrics of Object Oriented Design (MOOD) terhadap properti software berbasis Java. Pemanfaatan DRSA merupakan metode alternatif untuk menginterpretasikan nilai-nilai metrics dan menentukan sebuah nilai kuantitatif yang merepresentasikan kualitasnya relatif terhadap software yang lain. Studi eksperimental menunjukkan bahwa akurasi hasil DRSA bergantung pada jumlah sample aplikasi yang dijadikan referensi dalam menurunkan satu set definisi aturan untuk mengklasifikasikan properti software. Sample aplikasi dalam eksperimen diambil dari library Java yang telah teruji modularity, USAbility dan maintainability-nya. Secara umum, hasil eksperimen menyimpulkan bahwa DRSA dapat diterapkan untuk menentukan peringkat kualitas relatif dari sejumlah aplikasi dalam populasi sample. Application of Dominance-based Rough Set Approach (DRSA) to rank the quality of a number of object-based applications have been studied. DRSA applied to formulate a set of software quality classification in which the application is classified. Classification established by the results of measurements Metrics of Object Oriented Design (MOOD) against the property of Java-based software. Utilization of DRSA is an alternative method for interpreting the values of metrics and determine a quantitative value that represents the quality relative to other software. Experimental studies indicate that the accuracy of the DRSA depends on the number of sample applications that are used as reference in the definition set down one rule for classifying software properties. Sample applications in the experiment was taken from a proven library Java modularity, USAbility and maintainability of his. In general, the experimental results concluded that the DRSA can be applied to rank the relative quality of a number of applications in the sample population

Generation of Formal Model Metrics for MOF based Domain Specific Languages

The assessment of quality in a software development process is vital for the quality of the final system. A number of approaches exist, which can be used to determine such quality properties. In a model-driven development process models are the primary artifacts. Novel technologies are needed in order to assess the quality of those artifacts. Often, the Object Constraint Language is used to formulate model metrics and to compute them automatically afterwards. This paper describes an approach for the generation of model metrics expressed as OCL statements based on a set of generic rules. These rules can be applied on any domain specific modeling languages for creating a basic set of metrics which can be tailored for the specific needs of a development process. The paper also briefly describes a prototype of a tool for the generation, computation, and management of these model metrics by using the Software Metrics Meta-model - SMM