Best practices in code inspection for safety-critical software

Almeida, Jorge Rady de; Camargo, João Batista; Basseto, Bruno Abrantes; Paz, Sérgio Miranda

doi:10.1109/ms.2003.1196322

Cited by 34 publications

(15 citation statements)

References 13 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…Code walkthough [16] is a technique in which source code is traced by a group following a specific test case, while the state of program variables is monitored, to analyze the programmer's logic and look for issues. In bug-pattern-based reviews or checklistbased reviews [7], checklists focus the attention of the reader on places where bugs are known to exist. Static analysis tools can help these approaches [2], although a common mistake is to use the tools to replace reviews.…”

Section: Appendix: Homeworkless Review Methodologiesmentioning

confidence: 99%

Selective Homeworkless Reviews

Farchi

2008

2008 International Conference on Software Testing, Verification, and Validation

View full text Add to dashboard Cite

We describe a version of review/inspection called selective homeworkless review. In these reviews, moderators are taught how to select artifacts for review and review methodologies with little or no preparation.Many review and inspection methodologies are known in the literature and used in industry with very good results. The main issue we faced was not how to tune an existing inspection methodology, but rather how to get people to seriously and continuously inspect their artifacts. With the shrinking of the release cycle, people try to avoid front-loaded methodologies such as reviews, which seem to waste time early on. This is true both at the organizational level, where the overall cost is considered and at the dayto-day level, where time for preparation needs to be found. Because the reasons for rejecting existing inspection techniques were more organizational than technical, the way our methodology overcomes these objections is as central to the paper as the selective homeworkless review methodology itself.We introduced selective homeworkless reviews three years ago. We now have convincing evidence that this methodology can be introduced even in organizations that are resistant to formal inspections, leading to significant improvements in quality.

show abstract

Section: Appendix: Homeworkless Review Methodologiesmentioning

confidence: 99%

Selective Homeworkless Reviews

Farchi

2008

2008 International Conference on Software Testing, Verification, and Validation

View full text Add to dashboard Cite

show abstract

“…In addition, prefixes and suffixes indicating topics can be utilized for legibility instead of grouping and sorting by the topics [6]. Table 4 presents an example of this pattern and its improves version in which the deployment cost is drastically decreased by approximately 19.85% as fewer slots are occupied.…”

Section: Loose Packingmentioning

confidence: 99%

“…Note that a variable can match more than one pattern. Legibility is fundamental to code maintenance [6]; therefore, we recommend saving a copy (i.e., developer version) because steps 5 and 6 can hinder the legibility.…”

Section: Figure 1 Flow Chart Of the Proposed Solution Based On The Fmentioning

confidence: 99%

Saving Deployment Costs of Smart Contracts by Eliminating Gas-wasteful Patterns

Park¹,

Lee²,

In³

2017

IJGDC

View full text Add to dashboard Cite

show abstract

“…testing), requiring simulation. ), code inspection [20] and related verification activities, many works exist in the literature (see for example the approach developed at Verimag for the static analysis [21]): while they can automate many checks, when it comes to performing non-trivial inspections their common limitation consists in the fact that the verifier is not aided by any more or less formal model which would facilitate the work by providing proper views on the code (in practice, only function call-graphs [22] and code navigators are used).…”

Section: Related Workmentioning

confidence: 99%

“…variables are correctly ini-tialized, the number of iterations and stop conditions of cycles is correct, etc.) [20]. While some controls can be automated, many others are left to the sensibility of testers who perform code inspection (or 'walk-throughs'), and therefore are quite error prone.…”

Section: Related Workmentioning

confidence: 99%

Modeling of Railway Logics for Reverse Engineering, Verification and Refactoring

2011

View full text Add to dashboard Cite

Model-based approaches are widespread both in functional and non-functional verification activities of critical computer-based systems. Reverse engineering can also be used to support checks for correctness of system implementation against its requirements. In this paper, we show how a model-based technique, using the Unified Modeling language (UMl), suits the reverse engineering of complex control logics. UMl is usually exploited to drive the development of software systems, using an object-oriented and bottom-up approach; however, it can be also used to model legacy non-object-oriented logic processes featuring a clear distinction between data structures and related operations. Our case-study consists in the most important component of the European Railway Traffic Management System/European Train control System: the Radio Block center (RBc). The model we obtained from the logic code of the RBc significantly facilitated both structural and behavioral analyses, giving a valuable contribution to the static verification and refactoring of the software under test.

show abstract

Best practices in code inspection for safety-critical software

Cited by 34 publications

References 13 publications

Selective Homeworkless Reviews

Selective Homeworkless Reviews

Saving Deployment Costs of Smart Contracts by Eliminating Gas-wasteful Patterns

Modeling of Railway Logics for Reverse Engineering, Verification and Refactoring

Contact Info

Product

Resources

About