Please use this identifier to cite or link to this item: http://dspace.mediu.edu.my:8181/xmlui/handle/1721.1/3811
Full metadata record
DC FieldValueLanguage
dc.creatorOtto, Kevin-
dc.date2003-12-10T18:58:35Z-
dc.date2003-12-10T18:58:35Z-
dc.date2000-
dc.date.accessioned2013-10-09T02:32:41Z-
dc.date.available2013-10-09T02:32:41Z-
dc.date.issued2013-10-09-
dc.identifierhttp://hdl.handle.net/1721.1/3811-
dc.identifier.urihttp://koha.mediu.edu.my:8181/xmlui/handle/1721-
dc.descriptionThis paper presents an approach to determine the proper number of levels required on independent product architectural attributes, given their ability to generate added revenue through more direct targeting to smaller segments, and given the added costs of doing so. This is done in as simple and readily implementable manner as possible, making use only of conjoint data and cost estimates. From this, the order in which to consider added breakouts across the different attributes are prioritized. From this, for any minimum level of profit worth considering, a set of attribute levels to offer on each architectural attribute can be selected. Then, for any selected set of attribute levels to offer, the most effective product family using those levels is determined from the permutations.-
dc.descriptionCenter for Innovation in Product Development-
dc.format63441 bytes-
dc.formatapplication/pdf-
dc.languageen_US-
dc.subjectplatform architectures-
dc.subjectproduct families-
dc.subjectcommon product architecture-
dc.subjectportfolio architecture-
dc.subjectmodularity-
dc.subjectproduct platform-
dc.titleArchitecting Option Content-
dc.typeWorking Paper-
Appears in Collections:MIT Items

Files in This Item:
There are no files associated with this item.


Items in DSpace are protected by copyright, with all rights reserved, unless otherwise indicated.