This week's book giveaway is in the JDBC forum.
We're giving away four copies of Make it so: Java DB Connections & Transactions and have Marcho Behler on-line!
See this thread for details.
The moose likes Architect Certification (SCEA/OCMJEA) and the fly likes SCEA PART 2 - Business Domain Model Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login

Win a copy of Make it so: Java DB Connections & Transactions this week in the JDBC forum!
JavaRanch » Java Forums » Certification » Architect Certification (SCEA/OCMJEA)
Bookmark "SCEA PART 2 - Business Domain Model" Watch "SCEA PART 2 - Business Domain Model" New topic

SCEA PART 2 - Business Domain Model

Luigi Fugaro

Joined: Apr 05, 2011
Posts: 18

Hi everybody,
I downloaded the assignment a week ago and I came up with a big dilemma!
Should/Could I change the business domain model provided within the assignment, or not?

As the assignment says,
All of these objects and the relationships between them should be addressed in your design and implementation.

It suggests me to respect/follow the given business domain model, but there could be some reason (valid ones) to change it a little!
It does not say that the model must be and remain the given one.

Besides to my reasoning if they are wrong or right,
what should I do?
Actually I have a many-to-many relationship that I would never have in my real-project business domain model!

Did anybody change the given business domain model and pass part 2?

Thanks in advance,

Antoni Mysliborski
Ranch Hand

Joined: May 13, 2011
Posts: 55
From what I have read so far in this forum, unless you have a really serious reason to change BDM (eg. something very important is missing or there's an error in a given model), better don't do it. For sure not for the sake of optimization, simplifying or anything like that. Many people have failed because of this.

And many to many relationship is handled quite well by JPA for example, so I believe you don't need to worry about it.
Georgiana Lungu
Ranch Hand

Joined: May 17, 2010
Posts: 34
I have found this successful story
and since I have the same assignment, I was also very tempted to change it. In the end I found some solution without changing it but I am afraid it might be a bit "forced" as I am basically improvising some relations that can lead me by transitivity to the relation in the BDM. Problem is now that I am thinking which is worse? changing the BDM or putting things in there just to fit the given BDM? did you reach to any conclusion, will you change it?
Luigi Fugaro

Joined: Apr 05, 2011
Posts: 18

Hi Georgiana,
I'm still thinking... I don't know what i s worse, if working on something that I do not really understand or change it a little and start understanding what I'm doing.
Anyway I'll document and justify my changes, if any!
The use cases will remain the same, I'll add more class to the BDM.

I'll let you all know!

Ranganathan Kaliyur Mannar

Joined: Oct 16, 2003
Posts: 1101

I think if you are changing it slightly, you should document it clearly in your assumptions. Of course, big changes wouldn't be good. One thing that can be thought of is, even when changing, try to maintain the original relationship - maybe indirectly...

I agree. Here's the link:
subject: SCEA PART 2 - Business Domain Model
It's not a secret anymore!