Relevant bibliographies by topics / Software Metric

Academic literature on the topic 'Software Metric'

Author: Grafiati
Published: 4 June 2021
Last updated: 19 February 2022

Create a spot-on reference in APA, MLA, Chicago, Harvard, and other styles

Select a source type:

Contents

Consult the lists of relevant articles, books, theses, conference reports, and other scholarly sources on the topic 'Software Metric.'

Next to every source in the list of references, there is an 'Add to bibliography' button. Press on it, and we will generate automatically the bibliographic reference to the chosen work in the citation style you need: APA, MLA, Harvard, Chicago, Vancouver, etc.

You can also download the full text of the academic publication as pdf and read online its abstract whenever available in the metadata.

Journal articles on the topic "Software Metric"

1

Kaur, Sandeep. "Software Metrics and Metric Tools A Review." International Journal on Recent and Innovation Trends in Computing and Communication 3, no. 4 (2015): 2076–79. http://dx.doi.org/10.17762/ijritcc2321-8169.150468.

Full text
APA, Harvard, Vancouver, ISO, and other styles
2

Xiang, Yiming, Weifeng Pan, Haibo Jiang, Yunfang Zhu, and Hao Li. "Measuring Software Modularity Based on Software Networks." Entropy 21, no. 4 (March 28, 2019): 344. http://dx.doi.org/10.3390/e21040344.

Full text
Abstract:
Modularity has been regarded as one of the most important properties of a successful software design. It has significant impact on many external quality attributes such as reusability, maintainability, and understandability. Thus, proposing metrics to measure the software modularity can be very useful. Although several metrics have been proposed to characterize some modularity-related attributes, they fail to characterize software modularity as a whole. A complex network uses network models to abstract the internal structure of complex systems, providing a general way to analyze complex systems as a whole. In this paper, we introduce the complex network theory into software engineering and employ modularity, a metric widely used in the field of community detection in complex network research, to measure software modularity as a whole. First, a specific piece of software is represented by a software network, feature coupling network (FCN), where methods and attributes are nodes, couplings between methods and attributes are edges, and the weight on the edges denotes the coupling strength. Then, modularity is applied to the FCN to measure software modularity. We apply the Weyuker’s criteria which is widely used in the field of software metrics, to validate the modularity as a software metric theoretically, and also perform an empirical evaluation using open-source Java software systems to show its effectiveness as a software metric to measure software modularity.
APA, Harvard, Vancouver, ISO, and other styles
3

Masárová, Renáta. "Fréchet Metric for Space of Binary Coded Software." Research Papers Faculty of Materials Science and Technology Slovak University of Technology 22, no. 35 (December 1, 2014): 17–21. http://dx.doi.org/10.2478/rput-2014-0030.

Full text
Abstract:
Abstract As stated in (7), binary coded computer programs can be shown as a metric space. Therefore, they can be measured by metric in a sense of metric space theory. This paper presents the proof that Fréchet metric is a metric on the space of all sequences of elements M={0,1t} Therefore, it is usable to build a system of software metrics based on the metric space theory
APA, Harvard, Vancouver, ISO, and other styles
4

Kim, Jungho, Sungwon Kang, Jongsun Ahn, and Seonah Lee. "EMSA: Extensibility Metric for Software Architecture." International Journal of Software Engineering and Knowledge Engineering 28, no. 03 (March 2018): 371–405. http://dx.doi.org/10.1142/s0218194018500134.

Full text
Abstract:
Software extensibility, the capability of adding new functions to a software system, is established based on software architecture. Therefore, developers need to evaluate the capability when designing software architecture. To support the evaluation, researchers have proposed metrics based on quality models or scenarios. However, those metrics are vague or subjective, depending on specific systems and evaluators. We propose the extensibility metric for software architecture (EMSA), which represents the degree of extensibility of a software system based on its architecture. To reduce the subjectivity of the metric, we first identify a typical task of adding new functions to a software system. Second, we define the metrics based on the characteristics of software architecture and its changes and finally combine them into a single metric. The originality of EMSA comes from defining metrics based on software architecture and extensibility tasks and integrating them into one. Furthermore, we made an effort to translate the degree into effort estimation expressed as person-hours. To evaluate EMSA, we conducted two types of user studies, obtaining measurements in both a laboratory and a real-world project. The results show that the EMSA estimation is reasonably accurate [6.6% MMRE and 100% PRED(25%)], even in a real-world project (93.2% accuracy and 8.5% standard deviation).
APA, Harvard, Vancouver, ISO, and other styles
5

SHARMA, ARUN, RAJESH KUMAR, and P. S. GROVER. "EMPIRICAL EVALUATION AND VALIDATION OF INTERFACE COMPLEXITY METRICS FOR SOFTWARE COMPONENTS." International Journal of Software Engineering and Knowledge Engineering 18, no. 07 (November 2008): 919–31. http://dx.doi.org/10.1142/s0218194008003957.

Full text
Abstract:
The major drivers for complex applications are cost, efficiency, development time, understandability, usability and more importantly the maintainability. Due to their black box nature, complexity of software components is more crucial for component-based systems. This paper discusses various complexity concerns for these systems and reviews a number of complexity metrics for software components and component-based systems. As interfaces are the only source of information to know about the black-box components, this paper proposes a new interface complexity metric for these components. This metric is based on the information available in the interfaces like interface methods and properties. It also discusses the methodology to assign the weight values to these methods and properties to finally evaluate the complexity of the component. This paper validates the proposed metric against standard Weyukar's properties and empirically evaluates the metric for several Java Bean components. Finally a correlation analysis between proposed metrics and several other metrics like performance, customizability and readability is done to validate the metric.
APA, Harvard, Vancouver, ISO, and other styles
6

Sabbani, Sarachyuth, Kiran Kumar Reddi, and S. V. Achuta Rao. "Software Quality: Issues, Concerns and New Directions." INTERNATIONAL JOURNAL OF COMPUTERS & TECHNOLOGY 11, no. 8 (November 27, 2013): 2887–94. http://dx.doi.org/10.24297/ijct.v11i8.3007.

Full text
Abstract:
Software metrics and quality models have a very important role to play in measurement of software quality. A number of well-known quality models and software metrics are used to build quality software both in industry and in academia. Development of software metrics is an ongoing process with new metrics being continuously tried out. However, during our research on measuring software quality using object oriented design patterns, we faced many issues related to existing software metrics and quality models. For a particular situation of interest, any established metric can be used. If none is found to be appropriate, a new metric can be devised. In this paper, we discuss some of these issues and present our approach to software quality assessment.
APA, Harvard, Vancouver, ISO, and other styles
7

Phani Sheetal, A., and K. Ravindranath. "Software metric evaluation on cloud based applications." International Journal of Engineering & Technology 7, no. 1.5 (December 31, 2017): 13. http://dx.doi.org/10.14419/ijet.v7i1.5.9071.

Full text
Abstract:
Unbound growth in the cloud computing service models have motivated the companies building traditional software to be migrated into the clouds. During the high demand of the traditional applications, the performance and quality of the software were evaluated by the popular and globally accepted metrics. Nevertheless, after the migration of the same applications into the cloud, the expectation and definition of performance and quality has been changed. The beneficiaries of these applications are setting new milestones for the applications. Hence, the recent demand of the research trend is to build new software metric models to match the trade of between the new expectations from the beneficiaries and the software quality policies for organization or individual or state. Thus this work makes an attempt to understand the traditional software quality metrics and try to justify the applicability of these parameters in the trend of cloud based software applications. This work also proposes a novel metric method for performance evaluation for the migrated applications into the cloud, with the intension of formalizing and standardizing the cloud based metric methods unlike the recent trends.
APA, Harvard, Vancouver, ISO, and other styles
8

Srivastava, Varun Kar Lal, and Dr Amit Asthana. "An Efficient Universal Software Metric Tool for C#." Journal of Advanced Research in Dynamical and Control Systems 11, no. 10 (October 31, 2019): 75–81. http://dx.doi.org/10.5373/jardcs/v11i10/20193008.

Full text
APA, Harvard, Vancouver, ISO, and other styles
9

CHAN, VICTOR K. Y., W. ERIC WONG, and T. F. XIE. "A STATISTICAL METHODOLOGY TO SIMPLIFY SOFTWARE METRIC MODELS CONSTRUCTED USING INCOMPLETE DATA SAMPLES." International Journal of Software Engineering and Knowledge Engineering 17, no. 06 (December 2007): 689–707. http://dx.doi.org/10.1142/s0218194007003495.

Full text
Abstract:
Software metric models predict the target software metric(s), e.g., the development work effort or defect rates, for any future software project based on the project's predictor software metric(s), e.g., the project team size. Obviously, the construction of such a software metric model makes use of a data sample of such metrics from analogous past projects. However, incomplete data often appear in such data samples. Moreover, the decision on whether a particular predictor metric should be included is most likely based on an intuitive or experience-based assumption that the predictor metric has an impact on the target metric with a statistical significance. However, this assumption is usually not verifiable "retrospectively" after the model is constructed, leading to redundant predictor metric(s) and/or unnecessary predictor metric complexity. To solve all these problems, we derived a methodology consisting of the k-nearest neighbors (k-NN) imputation method, statistical hypothesis testing, and a "goodness-of-fit" criterion. This methodology was tested on software effort metric models and software quality metric models, the latter usually suffers from far more serious incomplete data. This paper documents this methodology and the tests on these two types of software metric models.
APA, Harvard, Vancouver, ISO, and other styles
10

Shao, Yanli, Jingru Zhao, Xingqi Wang, Weiwei Wu, and Jinglong Fang. "Research on Cross-Company Defect Prediction Method to Improve Software Security." Security and Communication Networks 2021 (August 24, 2021): 1–19. http://dx.doi.org/10.1155/2021/5558561.

Full text
Abstract:
As the scale and complexity of software increase, software security issues have become the focus of society. Software defect prediction (SDP) is an important means to assist developers in discovering and repairing potential defects that may endanger software security in advance and improving software security and reliability. Currently, cross-project defect prediction (CPDP) and cross-company defect prediction (CCDP) are widely studied to improve the defect prediction performance, but there are still problems such as inconsistent metrics and large differences in data distribution between source and target projects. Therefore, a new CCDP method based on metric matching and sample weight setting is proposed in this study. First, a clustering-based metric matching method is proposed. The multigranularity metric feature vector is extracted to unify the metric dimension while maximally retaining the information contained in the metrics. Then use metric clustering to eliminate metric redundancy and extract representative metrics through principal component analysis (PCA) to support one-to-one metric matching. This strategy not only solves the metric inconsistent and redundancy problem but also transforms the cross-company heterogeneous defect prediction problem into a homogeneous problem. Second, a sample weight setting method is proposed to transform the source data distribution. Wherein the statistical source sample frequency information is set as an impact factor to increase the weight of source samples that are more similar to the target samples, which improves the data distribution similarity between the source and target projects, thereby building a more accurate prediction model. Finally, after the above two-step processing, some classical machine learning methods are applied to build the prediction model, and 12 project datasets in NASA and PROMISE are used for performance comparison. Experimental results prove that the proposed method has superior prediction performance over other mainstream CCDP methods.
APA, Harvard, Vancouver, ISO, and other styles
More sources

Dissertations / Theses on the topic "Software Metric"

1

Rodríguez, Martínez Cecilia. "Software quality studies using analytical metric analysis." Thesis, KTH, Kommunikationssystem, CoS, 2013. http://urn.kb.se/resolve?urn=urn:nbn:se:kth:diva-120325.

Full text
Abstract:
Today engineering companies expend a large amount of resources on the detection and correction of the bugs (defects) in their software. These bugs are usually due to errors and mistakes made by programmers while writing the code or writing the specifications. No tool is able to detect all of these bugs. Some of these bugs remain undetected despite testing of the code. For these reasons, many researchers have tried to find indicators in the software’s source codes that can be used to predict the presence of bugs. Every bug in the source code is a potentially failure of the program to perform as expected. Therefore, programs are tested with many different cases in an attempt to cover all the possible paths through the program to detect all of these bugs. Early prediction of bugs informs the programmers about the location of the bugs in the code. Thus, programmers can more carefully test the more error prone files, and thus save a lot of time by not testing error free files. This thesis project created a tool that is able to predict error prone source code written in C++. In order to achieve this, we have utilized one predictor which has been extremely well studied: software metrics. Many studies have demonstrated that there is a relationship between software metrics and the presence of bugs. In this project a Neuro-Fuzzy hybrid model based on Fuzzy c-means and Radial Basis Neural Network has been used. The efficiency of the model has been tested in a software project at Ericsson. Testing of this model proved that the program does not achieve high accuracy due to the lack of independent samples in the data set. However, experiments did show that classification models provide better predictions than regression models. The thesis concluded by suggesting future work that could improve the performance of this program.
Idag spenderar ingenjörsföretag en stor mängd resurser på att upptäcka och korrigera buggar (fel) i sin mjukvara. Det är oftast programmerare som inför dessa buggar på grund av fel och misstag som uppkommer när de skriver koden eller specifikationerna. Inget verktyg kan detektera alla dessa buggar. Några av buggarna förblir oupptäckta trots testning av koden. Av dessa skäl har många forskare försökt hitta indikatorer i programvarans källkod som kan användas för att förutsäga förekomsten av buggar. Varje fel i källkoden är ett potentiellt misslyckande som gör att applikationen inte fungerar som förväntat. För att hitta buggarna testas koden med många olika testfall för att försöka täcka alla möjliga kombinationer och fall. Förutsägelse av buggar informerar programmerarna om var i koden buggarna finns. Således kan programmerarna mer noggrant testa felbenägna filer och därmed spara mycket tid genom att inte behöva testa felfria filer. Detta examensarbete har skapat ett verktyg som kan förutsäga felbenägen källkod skriven i C ++. För att uppnå detta har vi utnyttjat en välkänd metod som heter Software Metrics. Många studier har visat att det finns ett samband mellan Software Metrics och förekomsten av buggar. I detta projekt har en Neuro-Fuzzy hybridmodell baserad på Fuzzy c-means och Radial Basis Neural Network använts. Effektiviteten av modellen har testats i ett mjukvaruprojekt på Ericsson. Testning av denna modell visade att programmet inte Uppnå hög noggrannhet på grund av bristen av oberoende urval i datauppsättningen. Men gjordt experiment visade att klassificering modeller ger bättre förutsägelser än regressionsmodeller. Exjobbet avslutade genom att föreslå framtida arbetet som skulle kunna förbättra detta program.
Actualmente las empresas de ingeniería derivan una gran cantidad de recursos a la detección y corrección de errores en sus códigos software. Estos errores se deben generalmente a los errores cometidos por los desarrolladores cuando escriben el código o sus especificaciones.  No hay ninguna herramienta capaz de detectar todos estos errores y algunos de ellos pasan desapercibidos tras el proceso de pruebas. Por esta razón, numerosas investigaciones han intentado encontrar indicadores en los códigos fuente del software que puedan ser utilizados para detectar la presencia de errores. Cada error en un código fuente es un error potencial en el funcionamiento del programa, por ello los programas son sometidos a exhaustivas pruebas que cubren (o intentan cubrir) todos los posibles caminos del programa para detectar todos sus errores. La temprana localización de errores informa a los programadores dedicados a la realización de estas pruebas sobre la ubicación de estos errores en el código. Así, los programadores pueden probar con más cuidado los archivos más propensos a tener errores dejando a un lado los archivos libres de error. En este proyecto se ha creado una herramienta capaz de predecir código software propenso a errores escrito en C++. Para ello, en este proyecto se ha utilizado un indicador que ha sido cuidadosamente estudiado y ha demostrado su relación con la presencia de errores: las métricas del software. En este proyecto un modelo híbrido neuro-disfuso basado en Fuzzy c-means y en redes neuronales de función de base radial ha sido utilizado. La eficacia de este modelo ha sido probada en un proyecto software de Ericsson. Como resultado se ha comprobado que el modelo no alcanza una alta precisión debido a la falta de muestras independientes en el conjunto de datos y los experimentos han mostrado que los modelos de clasificación proporcionan mejores predicciones que los modelos de regresión. El proyecto concluye sugiriendo trabajo que mejoraría el funcionamiento del programa en el futuro.
APA, Harvard, Vancouver, ISO, and other styles
2

Sigfusson, Johann Tor. "Software metric extension of the Enterprisemodelling technique." Thesis, University of Skövde, Department of Computer Science, 1997. http://urn.kb.se/resolve?urn=urn:nbn:se:his:diva-243.

Full text
Abstract:

Abstract The objective of this project is to make it possible to evaluate real-time operating systems. A requirement specification for real-time operating system is represented with the help of the Enterprise Modelling technique. What is needed is to measure if the requirements, defined in the requirement specification, can be fulfilled by existing real-time operating system.

This dissertation is concerned with if it is possible to extend the Enterprise Modelling (EM) technique with software metrics. An emphasis is put on integrating an existing metrics paradigm with the EM technique.

The study shows that a paradigm, called Goal Question Metrics (GQM) can be used to extending the EM technique with software metrics.

Other results are that the extended EM model is good to identify metrics, because of its goal-oriented technique, with strong coupling to the enterprise, and actors and activities related to the product. This can be used to validate that relevant metrics are chosen, based on the need of components related to the enterprise.

APA, Harvard, Vancouver, ISO, and other styles
3

Matthews, S. G. "Metric domains for completeness." Thesis, University of Warwick, 1985. http://wrap.warwick.ac.uk/60775/.

Full text
Abstract:
Completeness is a semantic non-operational notion of program correctness suggested (but not pursued) by W.W.Wadge. Program verification can be simplified using completeness, firstly by removing the approximation relation from proofs, and secondly by removing partial objects from proofs. The dissertation proves the validity of this approach by demonstrating how it can work in the class of metric domains. We show how the use of Tarski's least fixed point theorem can be replaced by a non-operational unique fixed point theorem for many well behaved Programs. The proof of this theorem is also non-operational. After this we consider the problem of deciding what it means f or a function to be "complete". It is shown that combinators such as function composition are not complete, although they are traditionally assumed to be so. Complete versions for these combinators are given. Absolute functions are proposed as a general model for the notion of a complete function. The theory of mategories is introduced as a vehicle for studying absolute functions.
APA, Harvard, Vancouver, ISO, and other styles
4

Gonzalez, Marco A. "A new change propagation metric to assess software evolvability." Thesis, University of British Columbia, 2013. http://hdl.handle.net/2429/44607.

Full text
Abstract:
The development of software-intensive systems faces many challenges; one of the most important from an economic perspective is to reduce their maintenance costs. This thesis proposes a modified change propagation metric as a tool to assist the analysis of evolvability and maintainability of a software system and to ultimately support the reduction of its maintenance cost. The technical complexity of software systems has a great impact on their ability to make increased functionality and adaptability to the environment possible. One approach to understand and master the complexity of large software systems, varying from thousands to millions of lines of source code, is through software architecture. This study examines a sample of software systems from the dependencies of their static structural view. The dependencies and their importance are expressed as a design structure matrix (DSM) that is used as an indicator to reflect the strength of dependence and connection among the different modules. In this thesis, we propose a “modified change propagation” metric as a set of incremental improvements over the original Propagation Cost (PC) metric proposed by MacCormack (2008). Our improved metric uses dependencies weighted with strength to convey more information about the incidence of strongly connected relationships and it discounts weak dependencies. Moreover the original propagation metrics considered that the system should be acyclical; but we found that in practice a very few real systems are exempt of cycles. Furthermore, if cyclic dependencies are heavy rather than weak then these cycles should be treated differently. Finally, our metric is normalized to minimize the effect of both change in the total depth of the dependency graph, and increases in the size of the code. Our modified change propagation metric can help software designers assess the maintainability of a software system at design time and over a proposed release sequence by comparing change propagation measures for different designs of software architecture. For instance, after refactoring. We validated our metric both on a system developed at UBC, and on several large open-source repositories for which we were able to obtain long release histories.
APA, Harvard, Vancouver, ISO, and other styles
5

Gray, Christopher L. "A Coupling-Complexity Metric Suite for Predicting Software Quality." DigitalCommons@CalPoly, 2008. https://digitalcommons.calpoly.edu/theses/14.

Full text
Abstract:
Coupling Between Objects and Cyclomatic Complexity have long been used to measure software quality and predict maintainability and reliability of software systems prior to release. In particular, Coupling Between Objects has been shown to correlate with fault-proneness and maintainability of a system at the class level. We propose a new set of metrics based on a fusion of Coupling Between Objects and Cyclomatic Complexity that can be superior to Coupling Between Objects alone at predicting class quality. The new metrics use Cyclomatic Complexity to 1) augment Coupling Between Objects counting to assign a strength of a coupling between two classes and 2) determine the complexity of a method invocation chain through the transitive relation of invocations involved in a coupling. This results in a measure that identifies objects that are coupled to highly complex methods or method invocation chains. The metrics were implemented as an Eclipse Plug-in and an analysis of two industry Java projects, ConnectorJ and Hibernate, demonstrates the correlation between the new metrics and post-release defects identified in system change logs.
APA, Harvard, Vancouver, ISO, and other styles
6

Lincke, Rüdiger. "Validation of a standard- and metric-based software quality model /." Växjö : Växjö University Press, 2009. http://urn.kb.se/resolve?urn=urn:nbn:se:vxu:diva-5846.

Full text
APA, Harvard, Vancouver, ISO, and other styles
7

Konuralp, Zeynep. "Software Process Improvement In A Software Development Environment." Master's thesis, METU, 2007. http://etd.lib.metu.edu.tr/upload/12609059/index.pdf.

Full text
Abstract:
A software process improvement study is presented. The literature on software development processes and their improvement is reviewed. The current peer review process at Software Engineering Directorate of the X Company, Ankara, Tü
rkiye (XCOM) is studied and the static software development metrics based on a recent proposal have been evaluated. The static software metrics based improvement suggestions and the author&rsquo
s improvement suggestions discussed with the senior staff are compared. An improved peer review process is proposed. The static software development metrics have been evaluated on the improved process to see the impacts of the improvements. The improved process has been already implemented at XCOM and preliminary results have been obtained.
APA, Harvard, Vancouver, ISO, and other styles
8

Dahmann, Franz-Dietmar. "Correlation between quality management metric and people capability maturity model." Thesis, Monterey, Calif. : Springfield, Va. : Naval Postgraduate School ; Available from National Technical Information Service, 2003. http://library.nps.navy.mil/uhtbin/hyperion-image/03sep%5FDahmann.pdf.

Full text
Abstract:
Thesis (M.S. in Information Technology Management)--Naval Postgraduate School, September 2003.
Thesis advisor(s): John Osmundson, J. Bret Michael. Includes bibliographical references (p. 83-84). Also available online.
APA, Harvard, Vancouver, ISO, and other styles
9

Gray, Christopher L. Janzen David. "A coupling-complexity metric suite for predicting software quality : a thesis /." [San Luis Obispo, Calif. : California Polytechnic State University], 2008. http://digitalcommons.calpoly.edu/theses/14/.

Full text
Abstract:
Thesis (M.S.)--California Polytechnic State University, 2008.
Major professor: David Janzen, Ph.D. "Presented to the faculty of California Polytechnic State University, San Luis Obispo." "In partial fulfillment of the requirements for the degree [of] Master of Science in Computer Science." "June 2008." Includes bibliographical references (leaves 57-62). Also available online. Also available on microfiche (1 sheet).
APA, Harvard, Vancouver, ISO, and other styles
10

Long, Cary D. "A proposed software maintenance metric for the object oriented programming paradigm." Master's thesis, This resource online, 1995. http://scholar.lib.vt.edu/theses/available/etd-02022010-020231/.

Full text
APA, Harvard, Vancouver, ISO, and other styles
More sources

Books on the topic "Software Metric"

1

Breugel, Franck. Comparative Metric Semantics of Programming Languages: Nondeterminism and Recursion. Boston, MA: Birkhäuser Boston, 1996.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
2

Watson, Arthur Henry. Structured testing: A testing methology using the cyclomatic complexity metric. Edited by Wallace Dolores R and McCabe Thomas J. 1941-. Gaithersburg, MD: U.S. Dept. of Commerce, Technology Administration, National Institute of Standards and Technology, 1996.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
3

Lehner, Franz, Reiner Dumke, and Alain Abran, eds. Software Metrics. Wiesbaden: Deutscher Universitätsverlag, 1997. http://dx.doi.org/10.1007/978-3-322-99929-0.

Full text
APA, Harvard, Vancouver, ISO, and other styles
4

Software Metrics. London: Taylor & Francis Inc, 2003.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
5

library, Wiley online, ed. Software metrics and software metrology. Hoboken, N.J: Wiley, 2010.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
6

Abran, Alain. Software Metrics and Software Metrology. Hoboken, NJ, USA: John Wiley & Sons, Inc., 2010. http://dx.doi.org/10.1002/9780470606834.

Full text
APA, Harvard, Vancouver, ISO, and other styles
7

Schneidewind, Norman F. Validating software metrics. Monterey, Calif: Naval Postgraduate School, 1990.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
8

1956-, Fenton Norman E., and Littlewood B, eds. Software reliability and metrics. London: Elsevier Applied Science, 1991.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
9

Software metrics: Measurement for software process improvement. Oxford, UK: NCC Blackwell, 1996.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
10

Franklin, Daniel J. Software metrics using experimental design. Boston, MA: Boston University, School of Management, 1992.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
More sources

Book chapters on the topic "Software Metric"

1

Shin, Won, Tae-Wan Kim, Doo-Hyun Kim, and Chun-Hyon Chang. "Parametric Software Metric." In Software Engineering and Computer Systems, 266–73. Berlin, Heidelberg: Springer Berlin Heidelberg, 2011. http://dx.doi.org/10.1007/978-3-642-22203-0_23.

Full text
APA, Harvard, Vancouver, ISO, and other styles
2

Kichenamourty, Vedha. "Metric for Effective Test Coverage." In Software Measurement, 127–40. Wiesbaden: Deutscher Universitätsverlag, 1999. http://dx.doi.org/10.1007/978-3-663-08949-0_8.

Full text
APA, Harvard, Vancouver, ISO, and other styles
3

Jaspan, Ciera, and Caitlin Sadowski. "No Single Metric Captures Productivity." In Rethinking Productivity in Software Engineering, 13–20. Berkeley, CA: Apress, 2019. http://dx.doi.org/10.1007/978-1-4842-4221-6_2.

Full text
APA, Harvard, Vancouver, ISO, and other styles
4

Misra, Sanjay, and Ferid Cafer. "A Software Metric for Python Language." In Computational Science and Its Applications – ICCSA 2010, 301–13. Berlin, Heidelberg: Springer Berlin Heidelberg, 2010. http://dx.doi.org/10.1007/978-3-642-12165-4_24.

Full text
APA, Harvard, Vancouver, ISO, and other styles
5

Podgorelec, Vili, Peter Kokol, and Milan Zorman. "A Fractal Software Complexity Metric Analyser." In Computer Aided Systems Theory - EUROCAST’99, 486–93. Berlin, Heidelberg: Springer Berlin Heidelberg, 2000. http://dx.doi.org/10.1007/10720123_42.

Full text
APA, Harvard, Vancouver, ISO, and other styles
6

Chen, Yih Farn, Balachander Krishnamurthy, and Kiem Phong Vo. "An objective reuse metric: Model and methodology." In Software Engineering — ESEC '95, 109–23. Berlin, Heidelberg: Springer Berlin Heidelberg, 1995. http://dx.doi.org/10.1007/3-540-60406-5_10.

Full text
APA, Harvard, Vancouver, ISO, and other styles
7

Pola, Giordano, Elena De Santis, and Maria Domenica Di Benedetto. "On Approximate Diagnosability of Metric Systems." In Software Engineering and Formal Methods, 269–83. Cham: Springer International Publishing, 2017. http://dx.doi.org/10.1007/978-3-319-66197-1_17.

Full text
APA, Harvard, Vancouver, ISO, and other styles
8

Jones, Capers. "Function Points as a Universal Metric." In Software Development Patterns and Antipatterns, 369–466. Boca Raton: Auerbach Publications, 2021. http://dx.doi.org/10.1201/9781003193128-16.

Full text
APA, Harvard, Vancouver, ISO, and other styles
9

Mizuno, Osamu, and Hideaki Hata. "Yet Another Metric for Predicting Fault-Prone Modules." In Advances in Software Engineering, 296–304. Berlin, Heidelberg: Springer Berlin Heidelberg, 2009. http://dx.doi.org/10.1007/978-3-642-10619-4_36.

Full text
APA, Harvard, Vancouver, ISO, and other styles
10

Ambriola, V., R. Meglio, V. Gervasi, and B. Mercurio. "Applying a metric framework to the software process: an experiment." In Software Process Technology, 207–26. Berlin, Heidelberg: Springer Berlin Heidelberg, 1994. http://dx.doi.org/10.1007/3-540-57739-4_27.

Full text
APA, Harvard, Vancouver, ISO, and other styles

Conference papers on the topic "Software Metric"

1

Berardi, Rita Cristina Galarraga, and Duncan Dubugras Alcoba Ruiz. "Fuzzy-Provenance Architecture for Effort Metric Data Quality Assessment." In Simpósio Brasileiro de Qualidade de Software. Sociedade Brasileira de Computação - SBC, 2009. http://dx.doi.org/10.5753/sbqs.2009.15500.

Full text
Abstract:
Software companies rely on stored metric data in order to track and manage their projects, through analyzing, monitoring and estimating software metrics. If managers cannot believe the metrics data, the product that is being developed is fated to fail. Currently, the assessment of software effort is subjective and derived mainly through managers’ assumptions, which is fundamentally an error-prone process. We present an architecture for assessing data quality of software effort metric based on data provenance associated with a mechanism of logical inference (fuzzy logic). The contribution is to provide an assessment to search evident reasons for a low quality in order to ensure that the metrics can be used with sufficient reliability.
APA, Harvard, Vancouver, ISO, and other styles
2

Byelas, Heorhiy, and Alexandru Telea. "The Metric Lens: Visualizing Metrics and Structure on Software Diagrams." In 2008 15th Working Conference on Reverse Engineering (WCRE). IEEE, 2008. http://dx.doi.org/10.1109/wcre.2008.26.

Full text
APA, Harvard, Vancouver, ISO, and other styles
3

Needham, D., and S. Jones. "A Software Fault Tree Metric." In 22nd IEEE International Conference on Software Maintenance. IEEE, 2006. http://dx.doi.org/10.1109/icsm.2006.8.

Full text
APA, Harvard, Vancouver, ISO, and other styles
4

Buse, Raymond P. L., and Westley R. Weimer. "A metric for software readability." In the 2008 international symposium. New York, New York, USA: ACM Press, 2008. http://dx.doi.org/10.1145/1390630.1390647.

Full text
APA, Harvard, Vancouver, ISO, and other styles
5

Pandey, Amit. "Stall estimation metric: An architectural metric for estimating software complexity." In 2016 5th International Conference on Reliability, Infocom Technologies and Optimization (Trends and Future Directions) (ICRITO). IEEE, 2016. http://dx.doi.org/10.1109/icrito.2016.7784987.

Full text
APA, Harvard, Vancouver, ISO, and other styles
6

"Proceedings Seventh International Software Metrics Symposium." In Proceedings Seventh International Software Metrics Symposium. METRICS 2001. IEEE, 2001. http://dx.doi.org/10.1109/metric.2001.915509.

Full text
APA, Harvard, Vancouver, ISO, and other styles
7

Risi, M., G. Scanniello, and G. Tortora. "Metric Attitude." In 2013 17th European Conference on Software Maintenance and Reengineering (CSMR 2013). IEEE, 2013. http://dx.doi.org/10.1109/csmr.2013.59.

Full text
APA, Harvard, Vancouver, ISO, and other styles
8

Bukhari, Zubaidah, Jamaiah Yahaya, and Aziz Deraman. "Software metric selection methods: A review." In 2015 International Conference on Electrical Engineering and Informatics (ICEEI). IEEE, 2015. http://dx.doi.org/10.1109/iceei.2015.7352540.

Full text
APA, Harvard, Vancouver, ISO, and other styles
9

Wang, Xiaowei. "The Metric System about Software Maintenance." In 2011 International Conference on Information Technology, Computer Engineering and Management Sciences (ICM). IEEE, 2011. http://dx.doi.org/10.1109/icm.2011.382.

Full text
APA, Harvard, Vancouver, ISO, and other styles
10

Chandra, S., and R. A. Khan. "Software security metric identification framework (SSM)." In the International Conference. New York, New York, USA: ACM Press, 2009. http://dx.doi.org/10.1145/1523103.1523250.

Full text
APA, Harvard, Vancouver, ISO, and other styles

Reports on the topic "Software Metric"

1

Needham, D. M., and S. A. Jones. Software Fault Tree Key Node Metric Test Cases. Fort Belvoir, VA: Defense Technical Information Center, April 2006. http://dx.doi.org/10.21236/ada460760.

Full text
APA, Harvard, Vancouver, ISO, and other styles
2

Kothe, Douglas B., Kenneth J. Roche, and Ricky A. Kendall. FY 2009 Annual Report of Joule Software Metric SC GG 3.1/2.5.2, Improve Computational Science Capabilities. Office of Scientific and Technical Information (OSTI), January 2010. http://dx.doi.org/10.2172/977116.

Full text
APA, Harvard, Vancouver, ISO, and other styles
3

Mills, Everald E. Software Metrics. Fort Belvoir, VA: Defense Technical Information Center, December 1988. http://dx.doi.org/10.21236/ada236140.

Full text
APA, Harvard, Vancouver, ISO, and other styles
4

Schultz, Herman P. Software Management Metrics. Fort Belvoir, VA: Defense Technical Information Center, May 1988. http://dx.doi.org/10.21236/ada196916.

Full text
APA, Harvard, Vancouver, ISO, and other styles
5

Budlong, Faye, and Judi Peterson. Software Metrics Capability Evaluation Guide,. Fort Belvoir, VA: Defense Technical Information Center, October 1995. http://dx.doi.org/10.21236/ada325385.

Full text
APA, Harvard, Vancouver, ISO, and other styles
6

Coles, R. J., J. A. Kasputys, K. L. Lasko, T. F. Saunders, and H. P. Schultz. Software Reporting Metrics. Revision 2. Fort Belvoir, VA: Defense Technical Information Center, November 1985. http://dx.doi.org/10.21236/ada163756.

Full text
APA, Harvard, Vancouver, ISO, and other styles
7

Yule, H. P., and C. A. Riemer. Program for implementing software quality metrics. Office of Scientific and Technical Information (OSTI), April 1992. http://dx.doi.org/10.2172/10166209.

Full text
APA, Harvard, Vancouver, ISO, and other styles
8

Yule, H. P., and C. A. Riemer. Program for implementing software quality metrics. Office of Scientific and Technical Information (OSTI), April 1992. http://dx.doi.org/10.2172/7233625.

Full text
APA, Harvard, Vancouver, ISO, and other styles
9

Grable, Ross. Software Metrics for Total Development Cycle Evaluation. Fort Belvoir, VA: Defense Technical Information Center, November 1991. http://dx.doi.org/10.21236/ada246477.

Full text
APA, Harvard, Vancouver, ISO, and other styles
10

Kurt G. Vedros. SAPHIRE 8 Quality Assurance Software Metrics Report. Office of Scientific and Technical Information (OSTI), August 2011. http://dx.doi.org/10.2172/1031699.

Full text
APA, Harvard, Vancouver, ISO, and other styles
You might also be interested in the extended bibliographies on the topic 'Software Metric' for particular source types:
Journal articles Dissertations / Theses Books
We offer discounts on all premium plans for authors whose works are included in thematic literature selections. Contact us to get a unique promo code!

To the bibliography