All my collegues at work diss UML - but then again they didn't have to take it in school. I do use cases for myself quietly on the side. Use cases I like because: 1. they capture requirements well 2. they can read like a test plan of sorts.
The other parts of UML I do not find so useful. I mean, I could just use regular flowcharts, state tables, or class declarations instead of the UMLized equivalent.
UML is just a way to describe your software requirements and design. Heck, you can even use regular English prose if you like, just like the good old days.
One of the best thing about TP was the sample programs that demonstrated their BGI. Having a set of sample programs to start from really helped me get started.
All those hours at the Street Fighter machines
are actually spent on building transferable skills. Can we all do fireball + uppercuts?
Those mouse navigation moves reads just like a moves-list!
Slashdot Mirror
The other parts of UML I do not find so useful. I mean, I could just use regular flowcharts, state tables, or class declarations instead of the UMLized equivalent.
UML is just a way to describe your software requirements and design. Heck, you can even use regular English prose if you like, just like the good old days.
What would be convenient would be something like this, but for playing poker for $$$ online. So the computer can advise (or even play for you).
"I advise you fold this marginal hand."
"There is a 45% chance that this opponent is bluffing."
etc.
The only computing device less than $100 today with a screen is a used Palm.
c om.html
Google has some interesting summary of educational computers:
http://members.aol.com/KMyersPsion/ed
One of the best thing about TP was the sample programs that demonstrated their BGI. Having a set of sample programs to start from really helped me get started.
All those hours at the Street Fighter machines are actually spent on building transferable skills. Can we all do fireball + uppercuts? Those mouse navigation moves reads just like a moves-list!