Why flowcharts are not good for object oriented programming?

Flowcharts not good for OO Programming

Object oriented programming requires objects generally represented as classes to "talk" to other objects via methods/functions. This is a different approach from procedural languages where a procedure i.e. steps were constructed and written in the form of a flow chart.
For object-oriented programming the "flow" between objects is more important than the construction of a program. For this we use class diagrams. (using tools like rational rose). The methods themselves where the functioning takes place are so small and simple that for constructing them a flow chart is generally not required for a seasoned programmer. Thus, flowcharts are simply not a good instrument for oo programming because here data is given much more importance than the procedures that operate on them.

• What are the serial and parallel forts?
• Compare intelligence as available today with intelligence of old telephone system when manned by human operations handling interconnections on manual boards?
• Fancy words in computer oriented?