Definition of software metrics for software project development by using fuzzy sets and logic

2012

Closed access Metadata (CSL-JSON)
DOI 10.1109/scis-isis.2012.6505336
Data confidence 70 medium
How this score is calculated

It is built from checkable properties of the record itself: whether the article has a DOI, how many independent sources confirmed its data, whether the required fields are filled in, and how recent the latest confirmation is. Disagreement between sources and a missing identifier lower it. A value of 80 or above means the record was published without further checking; 60 to 79 means it is published at reduced confidence, with a manual check advisable. A record verified by an editor by hand is never pushed below 90 by a recalculation. This scores our data about the article, not the article itself.

Abstract

Software metrics measure certain properties of the software or its specifications. As quantitative measurements are required in all the sciences, there are ongoing efforts among computer science practitioners and academics to apply analogous approaches to software development process. The main aim is to provide objective, reproducible and quantitative measure that can have many useful applications in such important parts of software project management as the schedule and budget planning, cost estimation, quality assurance, software debugging, performance optimization and optimal staff task assignments as well as in the whole software development life cycle. There exist a number of techniques for modeling software metrics including FPA estimation (mean-based, median-based), LS regression, LMS regression, Neural Networks, and Fuzzy Logic. In this paper we are going to talk about singularities of applying Fuzzy Logic approach to the software metrics modeling.