Proceedings 17th IEEE International Conference on Automated Software Engineering, 2002
DOI: 10.1109/ase.2002.1115012
|View full text |Cite
|
Sign up to set email alerts
|

Model-based tests of truisms

Abstract: Software engineering (SE) truisms capture broadlyapplicable principles of software construction. The trouble with truisms is that such general principles may not apply in specific cases. This paper tests the specificity of two SE truisms: (a) increasing software process level is a desirable goal; and (b) it is best to remove errors during the early parts of a software lifecycle. Our tests are based on two well-established SE models: (1) Boehm et.al.'s COCOMO II cost estimation model; and(2) Raffo's discrete ev… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
19
0

Year Published

2007
2007
2024
2024

Publication Types

Select...
6
3
1

Relationship

1
9

Authors

Journals

citations
Cited by 25 publications
(19 citation statements)
references
References 38 publications
0
19
0
Order By: Relevance
“…Textile dyeing industries in Malaysia was important and was ranked as the first in the colouration of fiber [4]. Wastewater from the textile industries was declared as one of the major sources of wastewater pollutions in ASEAN countries, after considering both volumes discharge and effluent composition [5].…”
Section: Introductionmentioning
confidence: 99%
“…Textile dyeing industries in Malaysia was important and was ranked as the first in the colouration of fiber [4]. Wastewater from the textile industries was declared as one of the major sources of wastewater pollutions in ASEAN countries, after considering both volumes discharge and effluent composition [5].…”
Section: Introductionmentioning
confidence: 99%
“…Code reviews, are labor-intensive and one member can inspect only 8 to 20 LOC/minute. Same review process will be repeated for all members of the review team, which can be as large as four or six [7]. One effective approach for early identification of faulty modules is software fault prediction which investigates and learns the characteristics of individual code and design segments to predict the fault-prone modules [4].…”
Section: Related Workmentioning
confidence: 99%
“…By contrast, other methods such as manual code reviews are laborintensive. Depending on the review methods 8 to 20 LOC/minute can be inspected and this effort repeats for all members of the review team, which can be as large as four or six [22].…”
Section: But Does It Work?mentioning
confidence: 99%