Win a copy of The Little Book of Impediments (e-book only) this week in the Agile and Other Processes forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Can we ignore implementation?

 
D. Rose
Ranch Hand
Posts: 215
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi,

I am sure that actually implementing getting the flight list for journey would implement complicated algorithms (with graph theory and finding connectivity and all) and as an architect we should not be bothered much about implementation details but would not our design choices affect implementation? Then how can we ignore implementation details?
[ August 09, 2004: Message edited by: D. Rose ]
 
Ajith Kallambella
Sheriff
Posts: 5782
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hint : Design by contract.

For processing components in your system, try defining their contracts(aka interfaces) first. Define arguments, return types, pre-conditions and post-conditions. This should be sufficient to describe what the method does without worrying about how it is done.
 
D. Rose
Ranch Hand
Posts: 215
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi,

I meant from point of view of classes and their relationships especially flight-segment etc. DB design would mostly map to classes and so it will have effect on algorithm performance in turn.
 
Anil Vupputuri
Ranch Hand
Posts: 527
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Cool link on DBC,

Java World
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic