The Experts below are selected from a list of 1485 Experts worldwide ranked by ideXlab platform
Karine Mordal-Manet - One of the best experts on this subject based on the ideXlab platform.
-
SQUALE Software Quality Enhancement
2009 13th European Conference on Software Maintenance and Reengineering, 2009Co-Authors: Alexandre Bergel, Simon Denier, Fabrice Bellingard, Philippe Vaillergues, Francoise Balmas, Jannik Laval, Stéphane Ducasse, Karine Mordal-ManetAbstract:The Squale project was born from industrial effort to control Software Quality. Its goals are to refine and enhance Qualixo Model, a Software-metric based Quality Model already used by large companies in France (Air France-KLM, PSA Peugeot-Citroen) and to support the estimation of return on investment produced by Software Quality. Qualixo Model is a Software Quality Model based on the aggregation of Software metrics into higher level indicators called practices, criterias and factors. The coordination of Squale is carried out by Qualixo.
-
SQUALE -- Software Quality Enhancement
2009Co-Authors: Alexandre Bergel, Simon Denier, Fabrice Bellingard, Philippe Vaillergues, Francoise Balmas, Jannik Laval, Stéphane Ducasse, Karine Mordal-ManetAbstract:The Squale project was born from industrial effort to control Software Quality. Its goals are to refine and enhance Qualixo Model, a Software-metric based Quality Model already used by large companies in France (Air France-KLM, PSA Peugeot-Citroën) and to support the estimation of return on investment produced by Software Quality. Qualixo Model is a Software Quality Model based on the aggregation of Software metrics into higher level indicators called practices, criterias and factors. The coordination of Squale is carried out by Qualixo .
Elli Georgiadou - One of the best experts on this subject based on the ideXlab platform.
-
in search for a widely applicable and accepted Software Quality Model for Software Quality engineering
Software Quality Journal, 2007Co-Authors: Marcalexis Cote, Witold Suryn, Elli GeorgiadouAbstract:Software Quality Engineering is an emerging discipline that is concerned with improving the approach to Software Quality. It is important that this discipline be firmly rooted in a Quality Model satisfying its needs. In order to define the needs of this discipline, the meaning of Quality is broadly defined by reviewing the literature on the subject. Software Quality Engineering needs a Quality Model that is usable throughout the Software lifecycle and that it embraces all the perspectives of Quality. The goal of this paper is to propose the characteristics of a Quality Model suitable for such a purpose, through the comparative evaluation of existing Quality Models and their respective support for Software Quality Engineering.
-
gequamo a generic multilayered customisable Software Quality Model
Software Quality Journal, 2003Co-Authors: Elli GeorgiadouAbstract:Software Quality Models have primarily been based on top down process improvement approaches. Such Models are based on the fundamental principle of empowerment of all involved and foster a questioning attitude through the active exchange of ideas and criticism ensuring that the most appropriate approach for Quality improvements is adopted. The holistic view of systems enables the incorporation of many viewpoints held by different parties within the same organisation and by the same party at different stages of development. In this paper the GEQUAMO (GEneric, multilayered and customisable) Quality Model is proposed. GEQUAMO encapsulates the requirements of different stakeholders in a dynamic and flexible manner so as to enable each stakeholder (developer, user or sponsor) to construct their own Model reflecting the emphasis/weighting for each attribute/requirement. Using a combination of the CFD (Composite Features Diagramming Technique) developed by the author, and Kiviat diagrams a multilayered and dynamic Model is constructed. Instances of Models are presented together with the algorithm for the computation of the profiles. Indications of future work conclude the paper.
-
GEQUAMO—A Generic, Multilayered, Customisable, Software Quality Model
Software Quality Journal, 2003Co-Authors: Elli GeorgiadouAbstract:Software Quality Models have primarily been based on top down process improvement approaches. Such Models are based on the fundamental principle of empowerment of all involved and foster a questioning attitude through the active exchange of ideas and criticism ensuring that the most appropriate approach for Quality improvements is adopted. The holistic view of systems enables the incorporation of many viewpoints held by different parties within the same organisation and by the same party at different stages of development. In this paper the GEQUAMO (GEneric, multilayered and customisable) Quality Model is proposed. GEQUAMO encapsulates the requirements of different stakeholders in a dynamic and flexible manner so as to enable each stakeholder (developer, user or sponsor) to construct their own Model reflecting the emphasis/weighting for each attribute/requirement. Using a combination of the CFD (Composite Features Diagramming Technique) developed by the author, and Kiviat diagrams a multilayered and dynamic Model is constructed. Instances of Models are presented together with the algorithm for the computation of the profiles. Indications of future work conclude the paper.
E.b. Allen - One of the best experts on this subject based on the ideXlab platform.
-
Ordering Fault-Prone Software Modules
Software Quality Journal, 2003Co-Authors: T.m. Khoshgoftaar, E.b. AllenAbstract:Software developers apply various techniques early in development to improve Software reliability, such as extra reviews, additional testing, and strategic assignment of personnel. Due to limited resources and time, it is often not practical to enhance the reliability of all modules. Our goal is to target reliability enhancement activities to those modules that would otherwise have problems later. Prior research has shown that a Software Quality Model based on Software product and process metrics can predict which modules are likely to have faults. A module-order Model is a quantitative Software Quality Model that is used to predict the rank-order of modules according to a Quality factor, such as the number of faults. The contribution of this paper is definition of module-order Models and a method for their evaluation and use. Two empirical case studies of full-scale industrial Software systems provide empirical evidence of the usefulness of module-order Models for targeting reliability enhancement.
-
Accuracy of Software Quality Models over multiple releases
Annals of Software Engineering, 2000Co-Authors: T.m. Khoshgoftaar, E.b. Allen, Wendell D. Jones, John P. HudepohlAbstract:Many evolving missiondcritical systems must have high Software reliability. However, it is often difficult to identify faultdprone modules early enough in a development cycle to guide Software enhancement efforts effectively and efficiently. Software Quality Models can yield timely predictions of membership in the faultdprone class on a moduledbydmodule basis, enabling one to target enhancement techniques. However, it is an open empirical question, “Can a Software Quality Model remain useful over several releasesq” Most prior Software Quality studies have examined only one release of a system, evaluating the Model with modules from the same release. We conducted a case study of a large legacy telecommunications system where measurements on one Software release were used to build Models, and three subsequent releases of the same system were used to evaluate Model accuracy. This is a realistic assessment of Model accuracy, closely simulating actual use of a Software Quality Model. A module was considered faultdprone if any of its faults were discovered by customers. These faults are extremely expensive due to consequent loss of service and emergency repair efforts. We found that the Model maintained useful accuracy over several releases. These findings are initial empirical evidence that Software Quality Models can remain useful as a system is maintained by a stable Software development process.
-
CSMR - Application of a usage profile in Software Quality Models
Proceedings of the Third European Conference on Software Maintenance and Reengineering (Cat. No. PR00090), 1999Co-Authors: Wendell D. Jones, T.m. Khoshgoftaar, J.p. Hudepohl, E.b. AllenAbstract:Faults discovered by customers are an important aspect of Software Quality. The working hypothesis of this paper is that variables derived from an execution profile can be useful in Software Quality Models. An execution profile of a Software system consists of the probability of execution of each module during operations. Execution represents opportunities for customers to discover faults. However, an execution profile over an entire customer-base can be difficult to measure directly. Deployment records of past releases can be a valuable source of data for calculating an approximation to the probability of execution. We analyze a metric derived from deployment records which is a practical surrogate for an execution profile in the context of a Software Quality Model. We define usage as the proportion of systems in the field which have a module deployed. We present a case study of a very large legacy telecommunications system. We developed Models using a standard statistical technique to predict whether Software modules will have any faults discovered by customers on systems in the field. Static Software product metrics and usage were independent variables. The significance levels of variables in logistic regression Models were analyzed, and Models with and without usage as an independent variable were compared. The case study was empirical evidence that usage can be a significant contributor to a Software Quality Model.
-
ICSM - Can a Software Quality Model hit a moving target
Proceedings. International Conference on Software Maintenance (Cat. No. 98CB36272), 1998Co-Authors: T.m. Khoshgoftaar, E.b. AllenAbstract:This paper examines factors that make accurate Quality Modeling of an evolving Software system challenging. The context of our discussion is development of a sequence of Software releases. Our goal is to predict Software Quality of a release early enough co make significant Quality improvements prior to release.
-
Can a Software Quality Model hit a moving target?
Proceedings. International Conference on Software Maintenance (Cat. No. 98CB36272), 1998Co-Authors: T.m. Khoshgoftaar, E.b. AllenAbstract:This paper examines factors that make accurate Quality Modeling of an evolving Software system challenging. The context of our discussion is development of a sequence of Software releases. Our goal is to predict Software Quality of a release early enough co make significant Quality improvements prior to release.
Tibor Gyimóthy - One of the best experts on this subject based on the ideXlab platform.
-
Software Quality Model and Framework with Applications in Industrial Context
2012 16th European Conference on Software Maintenance and Reengineering, 2012Co-Authors: Lajos Schrettner, Lajos Jeno Fülöp, Á Beszédes, Ákos Kiss, Tibor GyimóthyAbstract:Software Quality Assurance involves all stages of the Software life cycle including development, operation and evolution as well. Low level measurements (product and process metrics) are used to predict and control higher level Quality attributes. There exists a large body of proposed metrics, but their interpretation and the way of connecting them to actual Quality management goals is still a challenge. In this work, we present our approach for Modelling, collecting, storing and evaluating such Software measurements, which can deal with all types of metrics collected at any stage of the life cycle. The approach is based on the Goal Question Metric paradigm, and its novelty lies in a unified representation of the metrics and the questions that evaluate them. It allows the definition of various complex questions involving different types of metrics, while the supporting framework enables the automatic collection of the metrics and the calculation of the answers to the questions. We demonstrate the applicability of the approach in three industrial case studies: two instances at local Software companies with different Quality assurance goals, and an application to a large open source system with a question related to testing and complexity, which demonstrates the complex use of different metrics to achieve a higher level Quality goal.
-
CSMR - Software Quality Model and Framework with Applications in Industrial Context
2012 16th European Conference on Software Maintenance and Reengineering, 2012Co-Authors: Lajos Schrettner, Lajos Jeno Fülöp, Á Beszédes, Ákos Kiss, Tibor GyimóthyAbstract:Software Quality Assurance involves all stages of the Software life cycle including development, operation and evolution as well. Low level measurements (product and process metrics) are used to predict and control higher level Quality attributes. There exists a large body of proposed metrics, but their interpretation and the way of connecting them to actual Quality management goals is still a challenge. In this work, we present our approach for Modelling, collecting, storing and evaluating such Software measurements, which can deal with all types of metrics collected at any stage of the life cycle. The approach is based on the Goal Question Metric paradigm, and its novelty lies in a unified representation of the metrics and the questions that evaluate them. It allows the definition of various complex questions involving different types of metrics, while the supporting framework enables the automatic collection of the metrics and the calculation of the answers to the questions. We demonstrate the applicability of the approach in three industrial case studies: two instances at local Software companies with different Quality assurance goals, and an application to a large open source system with a question related to testing and complexity, which demonstrates the complex use of different metrics to achieve a higher level Quality goal.
-
ICSM - A probabilistic Software Quality Model
2011 27th IEEE International Conference on Software Maintenance (ICSM), 2011Co-Authors: Tibor Bakota, Péter Körtvélyesi, Rudolf Ferenc, Peter Hegedus, Tibor GyimóthyAbstract:In order to take the right decisions in estimating the costs and risks of a Software change, it is crucial for the developers and managers to be aware of the Quality attributes of their Software. Maintainability is an important characteristic defined in the ISO/IEC 9126 standard, owing to its direct impact on development costs. Although the standard provides definitions for the Quality characteristics, it does not define how they should be computed. Not being tangible notions, these characteristics are hardly expected to be representable by a single number. Existing Quality Models do not deal with ambiguity coming from subjective interpretations of characteristics, which depend on experience, knowledge, and even intuition of experts. This research aims at providing a probabilistic approach for computing high-level Quality characteristics, which integrate expert knowledge, and deal with ambiguity at the same time. The presented method copes with “goodness” functions, which are continuous generalizations of threshold based approaches, i.e. instead of giving a number for the measure of goodness, it provides a continuous function. Two different systems were evaluated using this approach, and the results were compared to the opinions of experts involved in the development. The results show that the Quality Model values change in accordance with the maintenance activities, and they are in a good correlation with the experts' expectations.
-
A probabilistic Software Quality Model
2011 27th IEEE International Conference on Software Maintenance (ICSM), 2011Co-Authors: Tibor Bakota, Péter Hegedűs, Péter Körtvélyesi, Rudolf Ferenc, Tibor GyimóthyAbstract:In order to take the right decisions in estimating the costs and risks of a Software change, it is crucial for the developers and managers to be aware of the Quality attributes of their Software. Maintainability is an important characteristic defined in the ISO/IEC 9126 standard, owing to its direct impact on development costs. Although the standard provides definitions for the Quality characteristics, it does not define how they should be computed. Not being tangible notions, these characteristics are hardly expected to be representable by a single number. Existing Quality Models do not deal with ambiguity coming from subjective interpretations of characteristics, which depend on experience, knowledge, and even intuition of experts. This research aims at providing a probabilistic approach for computing high-level Quality characteristics, which integrate expert knowledge, and deal with ambiguity at the same time. The presented method copes with “goodness” functions, which are continuous generalizations of threshold based approaches, i.e. instead of giving a number for the measure of goodness, it provides a continuous function. Two different systems were evaluated using this approach, and the results were compared to the opinions of experts involved in the development. The results show that the Quality Model values change in accordance with the maintenance activities, and they are in a good correlation with the experts' expectations.
T.m. Khoshgoftaar - One of the best experts on this subject based on the ideXlab platform.
-
Software Quality estimation with limited fault data: a semi-supervised learning perspective
Software Quality Journal, 2007Co-Authors: Naeem Seliya, T.m. KhoshgoftaarAbstract:We addresses the important problem of Software Quality analysis when there is limited Software fault or fault-proneness data. A Software Quality Model is typically trained using Software measurement and fault data obtained from a previous release or similar project. Such an approach assumes that fault data is available for all the training modules. Various issues in Software development may limit the availability of fault-proneness data for all the training modules. Consequently, the available labeled training dataset is such that the trained Software Quality Model may not provide predictions. More specifically, the small set of modules with known fault-proneness labels is not sufficient for capturing the Software Quality trends of the project. We investigate semi-supervised learning with the Expectation Maximization (EM) algorithm for Software Quality estimation with limited fault-proneness data. The hypothesis is that knowledge stored in Software attributes of the unlabeled program modules will aid in improving Software Quality estimation. Software data collected from a large NASA Software project is used during the semi-supervised learning process. The Software Quality Model is evaluated with multiple test datasets collected from other NASA Software projects. Compared to Software Quality Models trained only with the available set of labeled program modules, the EM-based semi-supervised learning scheme improves generalization performance of the Software Quality Models.
-
Ordering Fault-Prone Software Modules
Software Quality Journal, 2003Co-Authors: T.m. Khoshgoftaar, E.b. AllenAbstract:Software developers apply various techniques early in development to improve Software reliability, such as extra reviews, additional testing, and strategic assignment of personnel. Due to limited resources and time, it is often not practical to enhance the reliability of all modules. Our goal is to target reliability enhancement activities to those modules that would otherwise have problems later. Prior research has shown that a Software Quality Model based on Software product and process metrics can predict which modules are likely to have faults. A module-order Model is a quantitative Software Quality Model that is used to predict the rank-order of modules according to a Quality factor, such as the number of faults. The contribution of this paper is definition of module-order Models and a method for their evaluation and use. Two empirical case studies of full-scale industrial Software systems provide empirical evidence of the usefulness of module-order Models for targeting reliability enhancement.
-
Accuracy of Software Quality Models over multiple releases
Annals of Software Engineering, 2000Co-Authors: T.m. Khoshgoftaar, E.b. Allen, Wendell D. Jones, John P. HudepohlAbstract:Many evolving missiondcritical systems must have high Software reliability. However, it is often difficult to identify faultdprone modules early enough in a development cycle to guide Software enhancement efforts effectively and efficiently. Software Quality Models can yield timely predictions of membership in the faultdprone class on a moduledbydmodule basis, enabling one to target enhancement techniques. However, it is an open empirical question, “Can a Software Quality Model remain useful over several releasesq” Most prior Software Quality studies have examined only one release of a system, evaluating the Model with modules from the same release. We conducted a case study of a large legacy telecommunications system where measurements on one Software release were used to build Models, and three subsequent releases of the same system were used to evaluate Model accuracy. This is a realistic assessment of Model accuracy, closely simulating actual use of a Software Quality Model. A module was considered faultdprone if any of its faults were discovered by customers. These faults are extremely expensive due to consequent loss of service and emergency repair efforts. We found that the Model maintained useful accuracy over several releases. These findings are initial empirical evidence that Software Quality Models can remain useful as a system is maintained by a stable Software development process.
-
ICSM - Can a Software Quality Model hit a moving target
Proceedings. International Conference on Software Maintenance (Cat. No. 98CB36272), 1998Co-Authors: T.m. Khoshgoftaar, E.b. AllenAbstract:This paper examines factors that make accurate Quality Modeling of an evolving Software system challenging. The context of our discussion is development of a sequence of Software releases. Our goal is to predict Software Quality of a release early enough co make significant Quality improvements prior to release.
-
Can a Software Quality Model hit a moving target?
Proceedings. International Conference on Software Maintenance (Cat. No. 98CB36272), 1998Co-Authors: T.m. Khoshgoftaar, E.b. AllenAbstract:This paper examines factors that make accurate Quality Modeling of an evolving Software system challenging. The context of our discussion is development of a sequence of Software releases. Our goal is to predict Software Quality of a release early enough co make significant Quality improvements prior to release.