• Post Reply 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 Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Classifying which objects as Composition and Aggregation.

 
Ranch Hand
Posts: 69
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I am faced with a design decision while making an asset tracking system. The Classification of class below is included in the first use case and the first iteration.
Use case - where the system gives the basic information about the following Asset and allows creating new asset.
1)The domain vocabulary consists of Asset, AssetClass, AssetSubclass, Vendor, Location, Employee,MainAsset, ComponentAsset (Indicated weather it is a main part or the component part).
AssetClass – Tangible , Intangible , Financial asset etc.
AssetSubclass – Car, Stock, Machinery. etc
2)Should the Assetclass and AssetSubClass inherit the Asset class or should it be part of the asset information (again the AssetClass is Compulsory).
3)This sort or abstraction problem is also present in MainAsset and ComponentAsset classes.
What could be the proper classification and decomposition of the above use case?
 
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.
reply
    Bookmark Topic Watch Topic
  • New Topic