Canada Spends Logo

Explorez notre analyse du budget 2026

Grant: Discovery Grants Program - Individual

École Polytechnique de Montréal

$34,000.00

Building Practical Software Quality Models

EF 2012-13

Résumé
A software total cost of ownership (TCO) includes all the costs to acquire and keep a program running, from specifications to licenses to training. Maintenance contributes between 50% and 70% of TCO. It includes the costs to change the program to fix an old feature and add new features. Companies need means to assess and improve their program maintainability to reduce their TCO. ISO9126 states that four factors impact developers when changing/maintaining a program: its analysability, changeability, stability, and testability; which form the quality characteristic of maintainability and lead to two main problems. Prb1: developers and their team leaders must assess program maintainability to decide whether it is worth changing the program. Prb2: developers need help in identifying different alternative sets of changes that would improve their program maintainability. The field of (empirical) software engineering now provides a wealth of facts and data to build maintainability assessment models for programs. Yet, no previous work put all these together to produce practical maintainability assessment models. Also, beyond assessing maintainability, developers must also identify and weigh changes necessary to improve their program maintainability before fixing/implementing features. They need practical maintainability improvement models providing different alternative sets of changes. My goal is to build a recommender system, based on practical maintainability assessment and improvement models, to quantify and increase maintainability and help developers facing Prb1 and Prb2. I will use systematic literature reviews to understand program maintainability and transformations. I will collect programs and related data pertaining to their maintainability, in particular experts' opinions, and build a database of samples with which to train quality assessment and improvements models. I will evaluate the models empirically and will develop research prototypes to collect data on programs, evaluate their maintainability, and provide suggestions of improvements using the models. The resulting recommander system will help developers and team leaders reduce maintainability costs and, thus, their program TCO.
Programme
Discovery Grants Program - Individual
Emplacement
Quebec, Canada
Type de bénéficiaire
Academia
Type
Grant
Source
NSERC's Awards Data

Tel que publié

Application id
293213-2012
Name nom
Guéhéneuc, YannGaël
Department département
Génie informatique et génie logiciel
Organization id
64
Institution établissement
École Polytechnique de Montréal
Province en
Québec
Province fr
Québec
Country en
CANADA
Country fr
CANADA
Fiscal year exercice financier
2012
Competition year année de concours
2012
Award amount
34000
Program id
RGPIN
Program name en
Discovery Grants Program - Individual
Program name fr
Programme de subventions à la découverte - individuelles
Group en
Discovery grants programs
Group fr
Programmes de subventions à la découverte
Committee code
1507
Committee name en
Computer Science
Committee name fr
Sciences informatiques
Area of application code
801
Area of application group en
Information and communication services
Area of application group fr
Services d'information et de télécommunications
Area of application en
Computer software
Area of application fr
Logiciel
Research subject code
2706
Research subject group en
Information technology
Research subject group fr
Technologie de l'information
Research subject en
Software engineering
Research subject fr
Génie logiciel
Partie
1
Nb partie
5
Application title
Building Practical Software Quality Models
Keyword
NSERC
Application summary
A software total cost of ownership (TCO) includes all the costs to acquire and keep a program running, from specifications to licenses to training. Maintenance contributes between 50% and 70% of TCO. It includes the costs to change the program to fix an old feature and add new features. Companies need means to assess and improve their program maintainability to reduce their TCO. ISO9126 states that four factors impact developers when changing/maintaining a program: its analysability, changeability, stability, and testability; which form the quality characteristic of maintainability and lead to two main problems. Prb1: developers and their team leaders must assess program maintainability to decide whether it is worth changing the program. Prb2: developers need help in identifying different alternative sets of changes that would improve their program maintainability. The field of (empirical) software engineering now provides a wealth of facts and data to build maintainability assessment models for programs. Yet, no previous work put all these together to produce practical maintainability assessment models. Also, beyond assessing maintainability, developers must also identify and weigh changes necessary to improve their program maintainability before fixing/implementing features. They need practical maintainability improvement models providing different alternative sets of changes. My goal is to build a recommender system, based on practical maintainability assessment and improvement models, to quantify and increase maintainability and help developers facing Prb1 and Prb2. I will use systematic literature reviews to understand program maintainability and transformations. I will collect programs and related data pertaining to their maintainability, in particular experts' opinions, and build a database of samples with which to train quality assessment and improvements models. I will evaluate the models empirically and will develop research prototypes to collect data on programs, evaluate their maintainability, and provide suggestions of improvements using the models. The resulting recommander system will help developers and team leaders reduce maintainability costs and, thus, their program TCO.