User:IveGoneAway/Study

Notes on George Novacek's "Software FMEA/FEMICA" in which he mentions tools. The tools he lists are not brand names but generic concepts. Even though I blipped over his list, there was nothing new to me in the list. He may have used specific tools but he does not name them. There is nothing magical about his list, most of which I have used.

Entity relationship diagram
 * This is notation for designing entities for enterprise databases, I prefer conventional UML

Data flow diagram
 * The particular notation here is for enterprise level, but data flow diagram is what we would use SCADE/Simulink/Labview for.

Control flow diagram
 * What we called a flow chart in school.

State transition diagram
 * These are EECE 241 Morris/Manno Finite state machines, I have always wanted such a tool, and long designed this way, but getting it right has long been a problem in tools. See UML

"Object relational diagram"
 * maybe he means this: Object-relational mapping?

"McCabe Logical Path"
 * See Control flow graph
 * Not a Thing at least by that name ( ok there is a diagram technique for McCabe graphs and reductions thereof. But McCabe analysis is trivial for structured code and is automated in many tools. IAR Embedded Workbench should do it.

"Software call tree"
 * maybe he means this: Call graph a properly designed block diagram is at call graph!
 * This is simple enough that Doxygen does it. The charts are prettier if you design your calls rather than rely on reverse engineering tools.  As a reverse engineering tool or code review tool, it can illustrate problems in your architecture.