• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Interfaces and Java Client
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Interfaces and Java Client


  • Subject: Re: Interfaces and Java Client
  • From: Paul Lynch <email@hidden>
  • Date: Fri, 28 Apr 2006 16:02:52 +0100


On 28 Apr 2006, at 06:03, David Avendasora wrote:

I am using inheritance in the model as well as interfaces but the problem isn't the inheritance! I'm having a hard time explaining the structure of my application so I've done my first-ever UML Class Diagram to try to explain it better. I've attached it - hopefully it makes it.

I don't think I'm doing anything crazy. I think it is pretty standard OO stuff (straight out of Head First Design Patterns). Can anyone tell me a better structure?

Looks to my like a classic MRP model, a little over-refined. The interfaces are an implementation details, and are really a red herring. Choosing the database schema is as much to do with performance as anything else. I think the first time I had to implement one of these was pre-relational, and I was fortunate enough to be able to use Total instead of IMS (extra detail added for the veterans among us).


The design you displayed could be implemented in a zillion different ways, and that's even ignoring the interfaces decisions. EOModeler is going to want to have relationships defined using entities, rather than interfaces, because EOF needs to be able to instantiate instances of the related objects, which I think is fair enough.

In the absence of any information to the contrary, I'd probably use a Part and a BoM table. I notice that the interfaces in some cases are identical in the UML (which is an over-refinement hint). I'd probably use a type field in Part to distinguish between your three subparts, and make them separate entities. The BoM table doesn't need to be separated. Relationships live in your Part entity/class, and ignore the ones you don't want. Depending on your industry, it's not unknown for "Intermediate" parts to suddenly become raw materials or finished goods at times; this will also affect your design.

Paul
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


References: 
 >Re: Interfaces and Java Client (From: David Avendasora <email@hidden>)
 >Re: Interfaces and Java Client (From: Paul Lynch <email@hidden>)
 >Re: Interfaces and Java Client (From: Chuck Hill <email@hidden>)
 >Re: Interfaces and Java Client (From: Ken Anderson <email@hidden>)
 >Re: Interfaces and Java Client (From: David Avendasora <email@hidden>)

  • Prev by Date: MYSQL Error on new install
  • Next by Date: Re: Scheduled WOApps not scheduled, Barbarian Solution
  • Previous by thread: Re: Interfaces and Java Client
  • Next by thread: Re: Interfaces and Java Client
  • Index(es):
    • Date
    • Thread