Design Forum - little OO, XP design (lack there of)

Articles |
News |
Weblogs |
Books |
Forums

Artima Forums | Articles | Weblogs | Java Answers | News

Sponsored Link •

Design Forum
little OO, XP design (lack there of)

1 reply on 1 page. Most recent reply: Nov 6, 2003 12:06 AM by javafan13

Welcome Guest
Sign In

Back to Topic List

Reply to this Topic

Search Forum

Threaded View


Previous Topic		Next Topic

Flat View: This topic has 1 reply on 1 page

John Keenan

Posts: 1
Nickname: keenan
Registered: Oct, 2003

little OO, XP design (lack there of)

Posted: Oct 31, 2003 3:52 PM

just a simple OO question: I have a bunch objects. They have parent/child relationships. Could be say up to 10 levels deep. Each child is a different "object-type". The question is, in displaying a parent/child tree of the relationships should the "tree-object" pull the object attributes directly from the DB or should the objects be "loaded" and the tree-object pull the attributes from the object itself. Note, the tree needs to show more than just a "name-attribute".....

The 2nd topic is on Extreme Programming. While I "think" I understand the concept, I cannot find where the "over-all-design" takes place. I see discussions about releasing to users every 2-3 weeks. I see no reference where you "design the automobile". How does one deliver new applications or even major changes without doing up front design to show where you would like to end up? Or are people just coding with "hair-on-fire"? Yes I know about the "pair-coding", but what if what one pair is coding has to "communicate" or work with another "pair's" ? Would you not want to discuss that up front? As if you wait until the 2nd pair realizes they need something from the 1st pair then there may be rework for the 1st pair.

Or just as bad, if both pairs start down their coding paths. They both need to implement something very similar... but they do not know each pair needs the same capability.. Guess what duplicate knowledge (in code form).

javafan13

Posts: 4
Nickname: javafan13
Registered: Jun, 2003

Re: little OO, XP design (lack there of)

Posted: Nov 6, 2003 12:06 AM

You have a too complicated tree to take its attributes directly from the database, which shouldn't be done anyway, for the sake of the good old model-view (well, not so old:-))
Let specialized objects become fully constructed, loaded and consistent, then take their needed attributes for the tree-view.
Concerning 2nd topic, don't know much about xp, or even if I do I did not work in an xp-driven environment. This being said, I do not see any serious development without a centralized scheme whose parts are to be implemented, in pairs or not.

Flat View: This topic has 1 reply on 1 page

Previous Topic

Next Topic


	Web Artima.com