Predicting software project effort: A grey relational analysis based method

This is the post-print version of the final paper published in Expert Systems with Applications. The published article is available from the link below. Changes resulting from the publishing process, such as peer review, editing, corrections, structural formatting, and other quality control mechanisms may not be reflected in this document. Changes may have been made to this work since it was submitted for publication. Copyright @ 2011 Elsevier B.V.The inherent uncertainty of the software development process presents particular challenges for software effort prediction. We need to systematically address missing data values, outlier detection, feature subset selection and the continuous evolution of predictions as the project unfolds, and all of this in the context of data-starvation and noisy data. However, in this paper, we particularly focus on outlier detection, feature subset selection, and effort prediction at an early stage of a project. We propose a novel approach of using grey relational analysis (GRA) from grey system theory (GST), which is a recently developed system engineering theory based on the uncertainty of small samples. In this work we address some of the theoretical challenges in applying GRA to outlier detection, feature subset selection, and effort prediction, and then evaluate our approach on five publicly available industrial data sets using both stepwise regression and Analogy as benchmarks. The results are very encouraging in the sense of being comparable or better than other machine learning techniques and thus indicate that the method has considerable potential.National Natural Science Foundation of Chin

Bis(μ-diethyl­phosphido-κ2 P:P)bis­[bis(2,4,6-trimethyl­phen­yl)indium(III)]

The title compound, [In2(C9H11)4(C4H10P)2], contains a centrosymmetric In2P2 core with short inter­molecular In—P bonds. This core has acute P—In—P and obtuse In—P—In bond angles compared with other [R 2InPR′2]2 analogues, due to the presence of the bulky aromatic substituents on the In atom and the non-sterically demanding ethyl substituents on the P atom

Locomotion speed of the benthic foraminifer Ammonia tepida exposed to different nitrogen and carbon sources

Ammonia tepida is a dominant benthic foraminifer colonizing intertidal mudflat sediments. Horizontal locomotion speeds were monitored using time-lapse image analysis over 6 and 24 h. Experimental conditions were based on foraminifera exposed to dry sediment re-suspended in artificial sea water (ASW) without any nutrient addition (condition DS), to combusted sediment re-suspended in in ASW also without any nutrient addition (condition CS), or to combusted sediment re-suspended in ASW enriched with either: nitrate, urea, glucose, soil extract (SE), extracellular polymeric substances (EPS), benthic diatoms (Entomoneis paludosa) or natural microphytobenthic assemblages (MPB). Significant differences were already measured after 6 h between A. tepida mean locomotion speeds at the different experimental conditions. However, differences were clearer after 24 h where the slowest A. tepida mean locomotion speed was measured in specimens placed in CS (1.00 ± 0.30 mm h− 1) and the highest mean locomotion speed in DS (2.99 ± 0.22 mm h− 1). Three different groups were defined according to their locomotion speed, (1) foraminifera exposed to DS had a locomotion speed significantly higher than all other conditions, (2) foraminifera placed in conditions enriched in SE, Glucose, Urea and EPS had intermediary locomotion speeds (1.8–2.5 mm h− 1), and (3) conditions with foraminifera showing the lowest locomotion speeds (1–1.6 mm h− 1) were CS, nitrate, MPB and E. paludosa. Thus, foraminifera exposed to organic matter (DS, SE, Glucose and Urea) showed faster locomotion speeds than foraminifera exposed to inorganic matter (CS, nitrate) or live preys (E. paludosa, MPB). Dissolved organic matter enrichment enhanced foraminifera locomotion speed, which might be a behavioural response to satisfy their carbon and/or nitrogen requirements, and the lowest locomotion speed observed when feeding on live preys might be a consequence of longer time required for live prey phagocytosis

Can k-NN imputation improve the performance of C4.5 with small software project data sets? A comparative evaluation

Missing data is a widespread problem that can affect the ability to use data to construct effective prediction systems. We investigate a common machine learning technique that can tolerate missing values, namely C4.5, to predict cost using six real world software project databases. We analyze the predictive performance after using the k-NN missing data imputation technique to see if it is better to tolerate missing data or to try to impute missing values and then apply the C4.5 algorithm. For the investigation, we simulated three missingness mechanisms, three missing data patterns, and five missing data percentages. We found that the k-NN imputation can improve the prediction accuracy of C4.5. At the same time, both C4.5 and k-NN are little affected by the missingness mechanism, but that the missing data pattern and the missing data percentage have a strong negative impact upon prediction (or imputation) accuracy particularly if the missing data percentage exceeds 40%

UML Consistency Rules:a Case Study with Open-Source UML Models

UML models are standard artifacts used by software engineers for designing software. As software is designed, different UML diagram types (e.g., class diagrams and sequence diagrams) are produced by software designers. Since the various UML diagram types describe different aspects of a software system, they are not independent but strongly depend on each other, hence they must be consistent. Inconsistencies cause faults in the final software systems. It is, therefore, paramount that they get detected, analyzed, and fixed. Consistency rules are a useful tool proposed in the literature to detect inconsistencies. They categorize constraints that help in identifying inconsistencies when violated. This case study aims at collecting and analyzing UML models with OCL consistency rules proposed in the literature and at promoting the development of a reference benchmark that can be reused by the (FM-)research community. We collected 33 UML consistency rules and 206 different UML diagrams contained in 34 open-source UML models presented in the literature. We propose an FM-based encoding of the consistency rules in OCL. This encoding allows analyzing whether the consistency rules are satisfied or violated within the 34 UML models. To assess the proposed benchmark, we analyzed how the UML models, consistency rules, diagram types contained in the benchmark help in assessing the consistency of UML models, and the consistency of diagrams across the different software development phases. Our results show that the considered UML models and consistency rules allowed identifying 2731 inconsistencies and that those inconsistencies refer to different software development phases. We concluded that the considered UML models and consistency rules could be considered as an initial benchmark that can be further extended by the research community

Environmental determinism of year to year recruitment variability of European eel in a small coastal catchment, the Frémur river, north-west France

The influence of environmental factors (mainly the river flow) on the year-to-year variability of European eel Anguilla anguilla fluvial recruitment in a small coastal River (north-west France) was examined. A comprehensive survey of catches from fixed traps at two weirs located at 4·5 km (Pont es Omnes Dam) and 6·0 km (Bois Joli Dam) above the river mouth was carried out between 1997 and 2004. Young pigmented elvers (mean ± s.d. total length, 133·7 ± 29·6 mm) were recruited in eel-passes from February to October, but the main runs followed a modal curve from April to September with a peak centred in May to June. Catches varied greatly between years, from 381 to 26 765 elvers. For each trap, a positive linear relationship between monthly mean river flow that preceded the maximal intensity of captures and annual total catches was observed. These relationships explained 73·1% (P <0.01) and 89·0% (P <0.001) of the year-to-year variability of the recruitment observed in the Pont es Omnes and Bois Joli traps respectively. A significant increase in river flow at the beginning of the migration peak would thus trigger a greater proportion of A. anguilla settled in the estuary and in the downstream zone of the Fremur River to begin their freshwater colonization. The physicochemical roles of changes in river discharge in stimulating upstream migration are discussed. It is concluded that fluvial recruitment in the Fremur River is mainly determined by environmental factors

Assessing architectural evolution: A case study

This is the post-print version of the Article. The official published can be accessed from the link below - Copyright @ 2011 SpringerThis paper proposes to use a historical perspective on generic laws, principles, and guidelines, like Lehman’s software evolution laws and Martin’s design principles, in order to achieve a multi-faceted process and structural assessment of a system’s architectural evolution. We present a simple structural model with associated historical metrics and visualizations that could form part of an architect’s dashboard. We perform such an assessment for the Eclipse SDK, as a case study of a large, complex, and long-lived system for which sustained effective architectural evolution is paramount. The twofold aim of checking generic principles on a well-know system is, on the one hand, to see whether there are certain lessons that could be learned for best practice of architectural evolution, and on the other hand to get more insights about the applicability of such principles. We find that while the Eclipse SDK does follow several of the laws and principles, there are some deviations, and we discuss areas of architectural improvement and limitations of the assessment approach

Software Quality Objectives for Source Code

International audienceThe MathWorks - Renault SA - PSA Peugeot Citroën - Delphi Diesel System - Valeo group wrote together a code quality standard from scratch. This document describes how the code standard places the proof of absence of run-time errors at the centre of its software quality model. It details how the following elements of the quality model co-exist together with the supplier code life cycle: MISRA-C coding standard, the absence of run-time errors and some code complexity metrics. Additionally, this document describes how the Automotive manufacturers and the suppliers have to agree on and achieve different Software Quality Objectives according to the code life cycle stage and the safety aspects of the application.Finally, the document illustrates that standard with the PolySpace product and details how the product can help both the automotive manufacturer and the supplier working with this standard