swarm-support
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Standard for pseudo code


From: Theodore C. Belding
Subject: Re: Standard for pseudo code
Date: Thu, 10 Apr 1997 00:57:33 -0400 (EDT)

Do you mean pseudocode, or diagrams?  If you mean pseudocode, I don't 
know of any standards or good examples for object-oriented (OO) code.  Maybe 
someone else has a suggestion. 

For normal (non-OO) pseudocode, take a look at a standard algorithms text
like: 
Cormen, T. H., Leiserson, C. E., and R. L. Rivest. (1990). Introduction 
to Algorithms. MIT Press. 
or 
Knuth, D. E. (1968, 1981, 1973). The Art of Computer Programming. Volumes 
1, 2, and 3. Addison-Wesley.

People usually use object diagrams, class diagrams, and interaction 
diagrams for OO code, instead of pseudocode. One of the best books on 
OOP ever written is Design Patterns, which has lots of examples of these 
diagrams:
Gamma, E., Helm, R., Johnson, R., and J. Vlissides. (1995). Design 
Patterns. Addison-Wesley. 

There are 3 major notations for object diagrams: Booch, Rumbaugh (OMT), 
and Jacobson's Objectory. Design Patterns uses parts of all 3.  The methods 
are currently being unified; I don't know what the status of that is.  Here
are the original sources:
Booch, G. (1994). Object-oriented analysis and design. 2nd edition. Cummings.

Rumbaugh, J., Blaha, M., Premerlani, W., Eddy, F., and W. Lorenson. 
(1991). Object-oriented modeling and design. Prentice-Hall.

Jacobson, I., M. Christerson, P. Jonnson, and G. Overgaard. (1992). 
Object-oriented software engineering --- A use case driven approach. 
Addison-Wesley.

You can apparently get a free reference card for the Booch notation by 
sending email to: address@hidden

Hope that helps.
-Ted

--
Ted Belding                      <mailto:address@hidden> 
University of Michigan Program for the Study of Complex Systems
<http://www-personal.engin.umich.edu/~streak/>

On Wed, 9 Apr 1997, Naga C. Krothapalli wrote:

> Hi group
> 
> I'm just wondering if there is any standard way of showing pseudo code for
> methods and implementation of objects. I used Swarm for simulating
> manufacturing systems and
> I want to document how I did it. So, can any one please suggest a good way
> writing pseudo code. I don't want to go into greater details, but I want
> the readers to be able to understand the logic in it and implement it by
> themselves. I appreciate if any one can guide me. Thanks
> 
> -Naga Krothapalli
> 
> Dept. of Industrial Engineering
> FAMU-FSU College of Engineering
> Florida State University
> 
> 
>                   ==================================
>    Swarm-Support is for discussion of the technical details of the day
>    to day usage of Swarm.  For list administration needs (esp.
>    [un]subscribing), please send a message to <address@hidden>
>    with "help" in the body of the message.
>                   ==================================
> 

                  ==================================
   Swarm-Support is for discussion of the technical details of the day
   to day usage of Swarm.  For list administration needs (esp.
   [un]subscribing), please send a message to <address@hidden>
   with "help" in the body of the message.
                  ==================================


reply via email to

[Prev in Thread] Current Thread [Next in Thread]