Bookmark Topic Watch Topic
  • New Topic

Big Smokes Standard/Petite/Flavored use Object diagram to explain?  RSS feed

Igor Katkov
Posts: 6
  • Mark post as helpful
  • send pies
  • Report post to moderator

I'm working on Big Smokes assignment. Business Domain Model (BDM) lists Standard/Petite/Flavored cigars as entities. I feel that when it comes down to class diagram and persistence Standard/Petite/Flavored is just a category.
I've done excessive study online of cigar selling stores, all cigar have pretty much same attributes regardless whether they are flavored or petite.
Also, I've seen that in real life there are much more categories than just these 3. So it's likely that as soon as BigSmoles online store goes into UAT phase it would become a must-have feature. Therefore I feel that I need to design something that would be extensible enough to allow that.

I've read somewhere that my class diagram *must* depict all entities from the BDM. If I go with "categories" I would not have classes like
FlavoredCigar <<@entity>>
StandardCigar <<@entity>>
PetitteCigar <<@entity>>
but rather
Cigar <<@entity>> with all the attributes.

Question: How do I make sure that I've shown that these three important categories are supported by my design?
One solution that came to my mind - is to provide Object diagram along with my Class diagram and that on that Object diagram show these Categories

I've read "Position on real assignment" I don't feel like my post reveal any solution details.
Andrew Monkhouse
author and jackaroo
Marshal Commander
Posts: 12150
C++ Firefox Browser IntelliJ IDE Java Mac Oracle
  • Mark post as helpful
  • send pies
  • Report post to moderator
But how do you expect anyone to answer this without revealing solution details?

Topic closed.
It is sorta covered in the JavaRanch Style Guide.
    Bookmark Topic Watch Topic
  • New Topic
Boost this thread!