wood burning stoves 2.0*
The moose likes OO, Patterns, UML and Refactoring and the fly likes whiteboard modeling Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of Android Security Essentials Live Lessons this week in the Android forum!
JavaRanch » Java Forums » Engineering » OO, Patterns, UML and Refactoring
Bookmark "whiteboard modeling" Watch "whiteboard modeling" New topic
Author

whiteboard modeling

Stefan Bell
Ranch Hand

Joined: Aug 26, 2003
Posts: 82
Can somebody explain whiteboard modeling? I believe it is designing on a whiteboard and then taking a digital picture of it? Does this only happen in small shops? Do you then put it in a software tool (Rose, XDE) or is that the model, if so what happens with refactoring and such?

Thanks...
Lasse Koskela
author
Sheriff

Joined: Jan 23, 2002
Posts: 11962
    
    5
Originally posted by Stefan Bell:
Can somebody explain whiteboard modeling? I believe it is designing on a whiteboard and then taking a digital picture of it?

Whiteboard modeling is just that -- modeling on a whiteboard. It might involve taking a digital photograph of the outcome for extended memory or formal documentation purposes, but that's not really part of the modeling itself anymore.


Originally posted by Stefan Bell:
Does this only happen in small shops?

Would you call a 100,000-employee Fortune 500 company "small"? How about another 70,000-employee Fortune 500 company? I'm employed by one and working for the other right now, and we are doing whiteboard modeling every now and then. Then again, we're also doing pen-and-paper modeling and we do use a CASE tool for drawing pretty, perfectly rectangular, colored boxes as well -- every now and then.

Originally posted by Stefan Bell:
Do you then put it in a software tool (Rose, XDE) or is that the model, if so what happens with refactoring and such?

As I said, we do use a CASE tool. However, we only maintain a domain model in electronic form. Drawing full-blown class diagrams (let alone sequence or collaboration diagrams) of each and every class in the system would be overkill and would slow us down significantly. If you're worried that a refactoring would require you to redraw a bunch of class diagrams, you should seriously evaluate whether you're modeling on a too detailed level.


Author of Test Driven (2007) and Effective Unit Testing (2013) [Blog] [HowToAskQuestionsOnJavaRanch]
Stan James
(instanceof Sidekick)
Ranch Hand

Joined: Jan 29, 2003
Posts: 8791
Whiteboarding implies several things ... a group of people collaborating and drawing, informal diagrams that don't use every last decoration in the UML, and transient artifacts. (The digital camera makes them less transient, but still we're not painstakingly entering them into The Official Rose Model for perpetuity.) Whiteboarding is kind of a code word for a focused, short, informal interactive design session. Having a bunch of smart people in a room jumping up and contributing to the drawing is one of the very best parts of my job.

I had almost the same experience putting the findings of a meeting into the Wiki on a projector the other day. Sure beat going back to my desk to write up the minutes and distribute them via Notes. Anybody else make that a regular part of their routine?


A good question is never answered. It is not a bolt to be tightened into place but a seed to be planted and to bear more seed toward the hope of greening the landscape of the idea. John Ciardi
Stefan Bell
Ranch Hand

Joined: Aug 26, 2003
Posts: 82
Originally posted by Lasse Koskela:

As I said, we do use a CASE tool. However, we only maintain a domain model in electronic form. Drawing full-blown class diagrams (let alone sequence or collaboration diagrams) of each and every class in the system would be overkill and would slow us down significantly. If you're worried that a refactoring would require you to redraw a bunch of class diagrams, you should seriously evaluate whether you're modeling on a too detailed level.


We reuse a lot of classes, objects and so forth so the model lets us know if a change is going to occur what the repurcussions may be throughout the application. I am not worried about redrawing diagrams and such, mainly if something changes what all will be affected and by using XDE (soon going to RSA) it gives us an indication.
Scott Ambler
author
Ranch Hand

Joined: Dec 12, 2003
Posts: 608
Check out http://www.agilemodeling.com/essays/whiteboardModeling.htm

I've worked on very large projects, and small projects too, and on every single one of them I've modeled on whiteboards. Yes, I'll also use other modeling tools such as TogetherCC or Argo or ERWin or Popkin's Software Architect but I'll always use whiteboards.

I think you'd be hard pressed to find any organization that doesn't have whiteboards available to their IT staff for doing modeling. I was at OOPSLA last week on an MDA panel and I asked the audience point blank who was using whiteboards for sketching on their projects and it looked as if about 95% of the people raised their hands. Later on another panelist asked if people where using modeling tools, and only about half the people raised their hands. It tells me that a lot of people don't realize that whiteboards are modeling tools, and not only that they're the most common modeling tools. Sketches, IMHO, are models.

Use the right tool for the job.

- Scott


<a href="http://www-306.ibm.com/software/rational/bios/ambler.html" target="_blank" rel="nofollow">Scott W. Ambler</a><br />Practice Leader Agile Development, IBM Rational<br /> <br />Now available: <a href="http://www.ambysoft.com/books/refactoringDatabases.html" target="_blank" rel="nofollow">Refactoring Databases: Evolutionary Database Design</a>
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: whiteboard modeling
 
Similar Threads
Object modelling
Free/Open Source UML Designers
Developing a Chat application in java
Design - Tool
Lightweight UML/Diagramming Tools