Page 2 of 2

Posted: Mon May 08, 2006 10:10 pm
by alvinphp
Hockey wrote:You're missing the point...I needed some tool and representation of how my tables were related, if at all...
I do miss the point sometimes. Sorry about that.

Posted: Mon May 08, 2006 10:16 pm
by alex.barylski
Fare enough, but you implied that I was in the wrong (in wanting to use UML post planning) by saying:
A little off subject, buuuut the point of UML is not to document everything after the tables are built
However, post-documentation should not be your only documentation. Arborint said it best about the current trend in project planning where it is not about huge document plans, but small agile ones which are very specific to the milestone you are working on.
I've been programming for a long time dude...I'm well aware of what works and what doesn't...

Cheers :)

Posted: Tue May 09, 2006 2:07 am
by timvw
alvinphp wrote: <off-topic->
So, are you saying that sometimes it is better to do all your documentation after coding and no planning should be done? Do you just jump into coding and then fix as problems arise?
</off-topic->
I think you're smart enough to know that is not what i said.

I did say that the use of UML as a modelling all depends on *your* own needs (Eg: Instead of a UML class diagram i prefer to model my database with ERD.)

Posted: Tue May 09, 2006 2:09 am
by alvinphp
Hockey wrote:I've been programming for a long time dude...I'm well aware of what works and what doesn't...
Then you are much more of an advanced programmer then me as I have been doing this for a long time myself and I am still learning what works and what does not. My apologies for trying to help. Just disregard everything I said.

Posted: Tue May 09, 2006 2:17 am
by alvinphp
timvw wrote:I think you're smart enough to know that is not what i said.

I did say that the use of UML as a modelling all depends on *your* own needs (Eg: Instead of a UML class diagram i prefer to model my database with ERD.)
I apologize for my misunderstanding.