Proceedings of the 4th India Software Engineering Conference 2011
DOI: 10.1145/1953355.1953370
|View full text |Cite
|
Sign up to set email alerts
|

Towards assuring non-recurrence of faults leading to transaction outages

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2

Citation Types

0
2
0

Year Published

2011
2011
2022
2022

Publication Types

Select...
3

Relationship

1
2

Authors

Journals

citations
Cited by 3 publications
(2 citation statements)
references
References 4 publications
0
2
0
Order By: Relevance
“…In COBOL, additionally, the jump to a Paragraph because of a GOTO results in a fall-through of control to the subsequent Paragraph, leading to potentially incomprehensible behaviour. Agrawal et al in their paper [9] have presented a statistic that about 50% of the transaction outages are caused by undesirable GOTOs in the program. Such undesired GOTOs are the reason behind the unintended fall-throughs in the code.…”
Section: A Removal Of Bad Code Smellsmentioning
confidence: 99%
See 1 more Smart Citation
“…In COBOL, additionally, the jump to a Paragraph because of a GOTO results in a fall-through of control to the subsequent Paragraph, leading to potentially incomprehensible behaviour. Agrawal et al in their paper [9] have presented a statistic that about 50% of the transaction outages are caused by undesirable GOTOs in the program. Such undesired GOTOs are the reason behind the unintended fall-throughs in the code.…”
Section: A Removal Of Bad Code Smellsmentioning
confidence: 99%
“…We run the tool [9] developed by Agrawal et al on the large industrial programs, and fix the potential defects reported by the tool. These include removal of out-of-range GOTOs, unintended fall-throughs and dead paragraphs in the code.…”
Section: A Removal Of Bad Code Smellsmentioning
confidence: 99%