• Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Regarding OO

 
Greedy thomas
Ranch Hand
Posts: 37
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
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
Marshal
Posts: 34860
369
Eclipse IDE Java VI Editor
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
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.
 
Terry Mullett
Greenhorn
Posts: 26
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
flowcharts?

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.

Cheers,
Terry
SCEA,SCWCD,SCBCD,SCJP
 
Pradeep bhatt
Ranch Hand
Posts: 8933
Firefox Browser Java Spring
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I don't consider flow charts to be an OO design artifact.


Are Use Cases OO? I dont think so.
 
Adeel Ansari
Ranch Hand
Posts: 2874
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
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
author
Sheriff
Posts: 14112
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
From http://www.agilemodeling.com/artifacts/flowChart.htm


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...
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic