Return to index: [Subject] [Thread] [Date] [Author]

RE: Concrete design flowchart

[Subject Prev][Subject Next][Thread Prev][Thread Next]
My I suggest that Object-oriented design to be considered instead.

Our codes, not just ACI, have been getting so complicated that
flowcharts are no longer suitable to express the code requirements.
Some of the flowchart covers 4-5 pages which are extremely difficult to
use either for the understanding of the process or for preparing a

I wrote some of my own concrete programs using Fortran, Basic and C
before.  It may works for a while. Update it with code changes
(exceptions attached to the codes...) soon becomes impossible.  Sometime
a program no longer workable, it is because the material specification
has been changed.  I started to use the OOP about 8 years ago to
maintain a program which is currently used by a lot of you.  Switching
to OOP has been very rewarding to me.

I suggest that you give OOP a thought.

Szuchuan Chang

Ps:  that may be the reasons you don't see many flowcharts in the books
these days.

-----Original Message-----
From: Steven A. [mailto:cratylus(--nospam--at)]
Sent: Tuesday, January 22, 2002 1:33 PM
To: seaint(--nospam--at)
Subject: Re: Concrete design flowchart

Also try ACI publication SP-17

Steven A.
Los Angeles

George M Ghaly wrote:

> Anyone know of a technical reference/material that summarize the
> requirements
> of ACI-318 in a flowchart manner?
> Thanks in advance.

******* ****** ******* ******** ******* ******* ******* ***
*   Read list FAQ at:
*   This email was sent to you via Structural Engineers
*   Association of Southern California (SEAOSC) server. To
*   subscribe (no fee) or UnSubscribe, please go to:
*   Questions to seaint-ad(--nospam--at) Remember, any email you
*   send to the list is public domain and may be re-posted
*   without your permission. Make sure you visit our web
*   site at:
******* ****** ****** ****** ******* ****** ****** ********