Linked by Thom Holwerda on Mon 3rd Sep 2012 20:46 UTC, submitted by MOS6510
General Development I like this one: "By definition, a program is an entity that is run by the computer. It talks directly to the CPU and the OS. Code that does not talk directly to the CPU and the OS, but is instead run by some other program that does talk directly to the CPU and the OS, is not a program; it's a script." Here's the other eleven.
Permalink for comment 533903
To read all comments associated with this story, please click here.
RE[4]: OOPs
by kwan_e on Wed 5th Sep 2012 07:24 UTC in reply to "RE[3]: OOPs"
Member since:

The only UML diagram I think any one uses regularly is the UML class diagram. That is where the confusion lies.

I haven't really used UML except for class diagrams since university.

We were told not to use Flow Diagrams at University, but they are pretty good for non-developers to see a high level flow of logic and developers can just follow it through in a debugger if need be (Our codebase is very bad).

Strangely, I think UML class diagrams are perhaps the most useless UML diagram. They're pain to make, class design changes all the time, and thus they're a pain to update.

Regarding flow diagrams, I find UML sequence diagrams to be a better replacement.

For me, the trick with UML and any diagramming language is not to go into any detail. Anything more than a brief outline is even more ridiculous to maintain and keep accurate than code itself.

Reply Parent Score: 3