• Post Reply Bookmark Topic Watch Topic
  • New Topic

Part 2: Business Requirements  RSS feed

 
Dan Huskins
Greenhorn
Posts: 15
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Can someone give me an idea as to how intricate our EJBs, DAOs, and various business-related objects need to be for the assignment?

I have read quite a bit about the J2EE patterns and approaches, and I believe I understand how to solve most of the requirements at a conceptual level using these approaches. However, the more I scrutinize the Business Domain Model, the more slippery it becomes.

For example, I have perused real flight systems, such as Delta and American Airlines, and found that flight numbers correlate only with a time of day (not a particular date) and only on certain days of the week, and can be associated with different types of equipment which in turn have different flight times and arrival times. This fact alone, not to mention others, creates a rather complicated set of data when you attempt to map, say, an entity bean to real data representing times, distances, etc. It creates an intricate and complicated interaction of EJBs, etc that doesn't create the sort of simple mapping i was hoping for (such as a Flight has just a destination and an arrival on a particular date and time).

Is this level of detail required?
 
Dhiren Joshi
Ranch Hand
Posts: 463
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Dan,
Keep it simple with the least complications.
If there are options and u need to make assumptions keep it simple and straight. U may add twists and turns if you want to make it interesting though

HTH
Dhiren
 
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!