This week's book giveaway is in the Design forum.
We're giving away four copies of Building Microservices and have Sam Newman on-line!
See this thread for details.
The moose likes OO, Patterns, UML and Refactoring and the fly likes Regarding OO Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login

Win a copy of Building Microservices this week in the Design forum!
JavaRanch » Java Forums » Engineering » OO, Patterns, UML and Refactoring
Bookmark "Regarding OO" Watch "Regarding OO" New topic

Regarding OO

Greedy thomas
Ranch Hand

Joined: May 15, 2003
Posts: 37
Hello All

I've been asked to model a design of a chess game. I have written out flowchart for the showing out the procedure flow using rectangles and ellipses. My question is : Is this considered non-OO to design using a flowchart. I've tried using Use Case Diagram but the only thing I can put there is two actors on either side with both interacting with a 'Move Piece' oval between them.

If flowcharting is not considered OO, then could someone please explain why.

What would be the best method to design the above.

Thanks In Advance.
Jeanne Boyarsky
author & internet detective

Joined: May 26, 2003
Posts: 32508

I don't consider flow charts to be an OO design artifact. Sequence digarams match better to flow charts than use cases though. Both show the flow of statements and conditional/looping expressions. A use case diagram is a higher level artifact.

[OCA 8 book] [Blog] [JavaRanch FAQ] [How To Ask Questions The Smart Way] [Book Promos]
Other Certs: SCEA Part 1, Part 2 & 3, Core Spring 3, TOGAF part 1 and part 2
Terry Mullett

Joined: Feb 21, 2003
Posts: 26

Only reason I've seen (and sorry, can't remember a source to quote) is that flowcharts are "procedural" while OO concentrates on the responsibilities and collaborations of objects. Seems like a narrow vision, since so many applications automate some sort of process.

I think that sequence and collaboration diagrams are fine for illustrating how a part of a process is achieved by a set of objects, but that's all implemetation-space and you have to get there somehow. Getting there often requires detailing what that process is. You might take a look at activity and maybe state diagrams. In some quarters activity diagrams are also considered non-OO.

But really isn't modeling about exploring, clarifying and communicating ideas? Whatever accomplishes that mission best is what I'd use.

Pradeep bhatt
Ranch Hand

Joined: Feb 27, 2002
Posts: 8927

I don't consider flow charts to be an OO design artifact.

Are Use Cases OO? I dont think so.

Adeel Ansari
Ranch Hand

Joined: Aug 15, 2004
Posts: 2874
Originally posted by Pradeep Bhat:

Are Use Cases OO? I dont think so.

yeah right it depends on thinking. but i think it is more towards OOD than flowcharts.

As Terry described a bit of that "flowcharts are procedural while OO concentrates on the responsibilities and collaborations of objects.".
[ October 12, 2004: Message edited by: adeel ansari ]
Ilja Preuss

Joined: Jul 11, 2001
Posts: 14112

I don�t use flowcharts much any more because I prefer to use UML activity diagrams instead, and in fact activity diagrams are arguably sophisticated flow charts (there�s more to them than this though). Regardless, I it�s important to be aware of flow charts because you will still see them used by experienced IT professionals from time to time.

I tend to agree that it's not important wether a diagram "is OO" (whatever that means). Not every diagram gets directly translated into code, after all...

The soul is dyed the color of its thoughts. Think only on those things that are in line with your principles and can bear the light of day. The content of your character is your choice. Day by day, what you do is who you become. Your integrity is your destiny - it is the light that guides your way. - Heraclitus
I agree. Here's the link:
subject: Regarding OO
It's not a secret anymore!