Win a copy of Spark in Action this week in the Open Source Projects forum!
    Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
  • Campbell Ritchie
  • Bear Bibeault
  • Ron McLeod
  • Jeanne Boyarsky
  • Paul Clapham
  • Tim Cooke
  • Liutauras Vilda
  • Junilu Lacar
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • fred rosenberger
  • salvin francis
  • Piet Souris
  • Frits Walraven
  • Carey Brown

The requirement has a confliction?

Posts: 16
  • Mark post as helpful
  • send pies
  • Report post to moderator
In the dream car project,
Business Domain Model shows
One Request can have mutiple PurchaseOrder and Mutiple parts components.
But in Use Case Basic Flow,
One Request can have one part category and quantity of it, can have one PurchaseOrder based on winning bid.

Which assiciation relationship shold be followed in the class diagram?

I do not know if this question break the discussion policy.
Ranch Hand
Posts: 109
  • Mark post as helpful
  • send pies
  • Report post to moderator
I think the examiners want "You the architect" to decide which of these two is the better choice and be able to justify that choice in your design decisions. Discussing the pros and cons of these two designs could be considered a violation of the Oracle policy because then we would be discussing the actual solution.
Yeah, but does being a ninja come with a dental plan? And what about this tiny ad?
Building a Better World in your Backyard by Paul Wheaton and Shawn Klassen-Koop
    Bookmark Topic Watch Topic
  • New Topic