| Author |
low level design
|
ankur rathi
Ranch Hand
Joined: Oct 11, 2004
Posts: 3829
|
|
Do you do low/class level design for your developer? Or leave it up to the developer to decide class names and method names and just let them know what kind of functionality you want?
How do you do low (class) level design? Say, you have identified classes, methods inside those and their interaction. But how do you draw the diagram? Do you use any tool to draw graphics?
Thanks. 
|
 |
Stan James
(instanceof Sidekick)
Ranch Hand
Joined: Jan 29, 2003
Posts: 8791
|
|
|
See the reply in your other thread. I worked on one team where a quick hallway conversation or a short meeting around a whiteboard did the job. Very rarely I wrote up real design docs when things got too complex for me to remember easily. I'm now on a team that believes medium level static and sequence diagrams are appropriate almost all the time.
|
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
|
|
Gabriel Claramunt
Ranch Hand
Joined: May 26, 2007
Posts: 375
|
|
I'm a big fan of modeling (it works well for me, I guess I'm a "visual" thinker), but there's always some level of detail that's better to left out from the models, because is easier to do with code.
Method names usually are not critical, so as long as you describe the intention/responsibility is ok. Class names usually are more important to keep/decide (specially the ones that represent domain concepts) so is better to have them.
What diagrams do you want to draw?
I usually use UML tools (StarUML is a good free one) because is easier to change than drawing on a whiteboard. A nice side effect is that you can get the skeleton classes from a diagram.
|
Gabriel
Software Surgeon
|
|
Ilja Preuss
author
Sheriff
Joined: Jul 11, 2001
Posts: 14112
|
|
Originally posted by ankur rathi:
Do you do low/class level design for your developer?
If I'm understanding correctly that you are doing design that others will implement, I'd assume that the best way to find out what they need to do it effectively would be to ask them...
Can you tell us more about your situation?
The information on http://www.agilemodeling.com/ might be interesting to you...
|
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
|
|
ankur rathi
Ranch Hand
Joined: Oct 11, 2004
Posts: 3829
|
|
Thanks All and sorry Ilja for not following it up promptly. Situation is like *I* only have to decide what documents should be required and *I* only have to create them.
Asking developers is a good idea.
[ September 10, 2007: Message edited by: ankur rathi ]
|
|
 |
|
|
subject: low level design
|
|
|
0
