Computer Science Education

Russell Turpin deafbox@hotmail.com
Tue, 28 Jan 2003 15:36:34 +0000


Tomwhore:
>Might I sugest the Nassi Schniderman Diagraming method.

I found one of these on the Web, and it
took me back a quarter century.

One diagramming technique I would
recommend is statecharts. They are a
generalization of state diagrams, and if
I recall correctly, they are now
sanctioned as a part of UML.

BTW, one of the drawbacks to UML is that
it lacks a rigorous semantics, in contrast
to other techniques such as Shlaer-Mellor.
This is a real drawback for teaching,
because there isn't really a good answer
to the question: "what does this model
MEAN?"

In the OOA wars, the kitchen-sink approach
won out over the more rigorous approaches.
It hardly matters now, but a rigorous
semantics enables some fairly interesting
and useful technology. In a past life, I
managed a CASE product that did animation,
simulation, and retargetable code generation
from OOA diagrams, aimed mostly at the
real-time and embedded market. It's pretty
neat when your OOA models ARE the software,
and design is done in parallel by defining
how different categories of objects are mapped
to code.



_________________________________________________________________
The new MSN 8: smart spam protection and 2 months FREE*  
http://join.msn.com/?page=features/junkmail