Ambiguity in Domain model and Use case

Hi Ranchers,

In my assignment it has mentioned that, i need to keep domain model relationships with out any modification into class diagram.
But this domain model cardinality is not in synch with use case description. Could you please comment on this.

Thanks and Regards,
Purna Manepalli.

http://www.coderanch.com/t/601244/java-Architect-SCEA/certification/Domain-Diagram-matching-Cases

Thanks Fernando.

As per your comment:
"You as the architect can change your domain model to reflect a solution designed to solve all use cases. Do not forget to document the reasons.
Remember, the assignament may be missing a lot of information in which you will have to assume in order to develop and deliver your proposed solution. "

Here the issue is, it was clearly mention that all domain classes and their relationships should present in my class diagram.

Please advice me.

Cheers,
Purna Manepalli.

Here the issue is, it was clearly mention that all domain classes and their relationships should present in my class diagram.

For you solve this, you need to think like an architect. Then think: "you as an architect seeing that something is wrong, you implement the wrong solution or correct the inconsistency? This falls under the list of assumptions.
This happened with several candidates, all that changed the domain model were approved for certification.
Regards.

Thanks a lot Fernando.

I am sure, i need to change cardinality at one place in my Domain Model. Then rest all perfect. I was just worried how can i change my DM.

Cheers,
Purna Manepalli.