1,269 reputation
312
bio website
location
age 30
visits member for 2 years, 8 months
seen Jun 5 '13 at 14:10

Dec
17
comment Review my class hierarchy
Your classes would be User, Book, Magazine, Inventory, Author and Publisher. You can't have fewer than this even if it's an example. Else, just have a Book, Inventory and User class, add a category and map your enumerations to the book class as variables rather than properties. Authors and Publishers are part of book so they just can't be treated as properties.
Dec
17
comment Review my class hierarchy
Separate classes are preferable.
Dec
17
revised Review my class hierarchy
added a link
Dec
17
answered Review my class hierarchy
Dec
17
comment Orthogonal design for product pricing and production planning with a NoSQL database
Thanks for the suggestion (and thanks to Satyajit too). You are spot on with your RDBMS comment. What I need is a freely extensible model that could be developed as a stand-alone product. Also need to know the general pricing/cost software in market (I just can't see lot of full-fledged software for pricing/cost estimation. Most of them comes bundled with ERP or a spreadsheet is used. Kindly correct my perception if it's wrong). Not starting any flame wars, if Product P has attributes [A(1-4),B(1-6),C(1-5)], you have 120 possible combinations. Star schema may be the solution but I prefer JSON.
Dec
17
awarded  Editor
Dec
17
revised Orthogonal design for product pricing and production planning with a NoSQL database
missing detail regarding JSON added
Dec
17
awarded  Student
Dec
17
asked Orthogonal design for product pricing and production planning with a NoSQL database