15th International Conference on Advanced Computing and Communications (ADCOM 2007) 2007
DOI: 10.1109/adcom.2007.69
|View full text |Cite
|
Sign up to set email alerts
|

Use of genetic algorithm for software maintainability metrics' conditioning

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
2
1

Citation Types

0
5
0

Year Published

2010
2010
2021
2021

Publication Types

Select...
5
2
1

Relationship

0
8

Authors

Journals

citations
Cited by 11 publications
(5 citation statements)
references
References 22 publications
0
5
0
Order By: Relevance
“…However, unhappiness with internal quality standards may not necessarily outcome in low rank of maintainability although it is generally expected. In that case, it is likeable that, regardless of what internal Estimations designate, the concluding judge for the maintainability of the delivered software is the programmer [19,21,22].…”
Section: IVmentioning
confidence: 99%
“…However, unhappiness with internal quality standards may not necessarily outcome in low rank of maintainability although it is generally expected. In that case, it is likeable that, regardless of what internal Estimations designate, the concluding judge for the maintainability of the delivered software is the programmer [19,21,22].…”
Section: IVmentioning
confidence: 99%
“…This means that the software needs to be adaptable and easy to maintain. Literatures show that software maintenance takes around 70 percent of the total resource and 40-60 percent of the total life cycle efforts [1] [8]. Software maintainability can be defined as: "The ease with which a software system or component can be modified to correct faults, improve performance or other attributes, or adapt to a changed environment" [9].…”
Section: Software Maintainabilitymentioning
confidence: 99%
“…However, it is important to be reminded that high maintainable software will demand less rework and maintenance activities and, therefore, decreasing overall cost of the product at the end of the life cycle [1].…”
Section: Software Maintainabilitymentioning
confidence: 99%
See 1 more Smart Citation
“…Several models have been proposed for finding maintainability of software in different perspec-tive [9,10,23]. Earlier researchers used to consider only source code and its allied comments for program comprehension [11], but later with increased complexity of software, understanding other software artifacts such as design documents were also assumed compulsory [3,20,22]. As there are several diverse attributes collected from different artifacts of software, which are distinct in measurement and performance scale, efforts are made to integrate these, in order to get a single crisp value of maintainability.…”
Section: Introductionmentioning
confidence: 99%