Post Code Inspection, shouldn't the team also do a review classifying the kind of bugs and their frequency in the code and suggest additional coding practices to mitigate the recurrence; i.e.; refine coding standards to improve on future practice of all?
Plausibly also it can improve the capability of Code inspections to identify bug tendencies based upon the "culture" programmers.
Are there any tools for code tracing to ensure all branches or decisions are exercised i.e.; prevent overlooked inherent dependencies in code? How might traceability of dependencies best be addressed via Inspection?
Absolutely. That's the best way to run a team. For tools, LDRA has this feature.
In an age of globalization and rapid changes through scientific progress, two of our societies' (and economies') main concerns are to satisfy the needs and wishes of the individual and to save precious resources. Cloud computing caters to both of these.
For industrial control applications, or even a simple assembly line, that machine can go almost 24/7 without a break. But what happens when the task is a little more complex? That’s where the “smart” machine would come in. The smart machine is one that has some simple (or complex in some cases) processing capability to be able to adapt to changing conditions. Such machines are suited for a host of applications, including automotive, aerospace, defense, medical, computers and electronics, telecommunications, consumer goods, and so on. This discussion will examine what’s possible with smart machines, and what tradeoffs need to be made to implement such a solution.