%0 Journal Article %1 Yassine.200811 %A Yassine, Ali A. %A Sreenivas, Ramavarapu S. %A Zhu, Jian %D 2008/1/1/ %J European Journal of Operational Research %K Concurrent Design Overlapping Product development engineering iteration %N 1 %P 311-326 %T Managing the exchange of information in product development %V 184 %X In the present paper, we develop a dynamic programming (DP) model of the product development (PD) process. We conceptualize product development as a sequence of decisions: whether to incorporate a piece of information that just arrived (i.e. became available) or wait longer. We utilize this formulation to analyze different situations that depend on the type, and nature of information that is exchanged: stationary versus dynamic information. We derive optimal decision rules to determine whether (and when) to incorporate for each case. An analysis of the model results in several important findings. First, we must not necessarily incorporate all available information that is related to the design activity. Specifically, once the information collection exceeds certain value, the design team should stop collecting further information. Second, only when past design work accumulates to a certain threshold value should the team include the latest information and perform rework. Large uncertain

@article{Yassine.200811, abstract = {In the present paper, we develop a dynamic programming (DP) model of the product development (PD) process. We conceptualize product development as a sequence of decisions: whether to incorporate a piece of information that just arrived (i.e. became available) or wait longer. We utilize this formulation to analyze different situations that depend on the type, and nature of information that is exchanged: stationary versus dynamic information. We derive optimal decision rules to determine whether (and when) to incorporate for each case. An analysis of the model results in several important findings. First, we must not necessarily incorporate all available information that is related to the design activity. Specifically, once the information collection exceeds certain value, the design team should stop collecting further information. Second, only when past design work accumulates to a certain threshold value should the team include the latest information and perform rework. Large uncertain}, added-at = {2011-01-21T09:59:21.000+0100}, author = {Yassine, Ali A. and Sreenivas, Ramavarapu S. and Zhu, Jian}, biburl = {https://www.bibsonomy.org/bibtex/2e297fe0d6c0a309b10d1f8a6c4476036/comanderkeen}, interhash = {748b0d3ca3d3ba340e97ccb1ce7e1b35}, intrahash = {e297fe0d6c0a309b10d1f8a6c4476036}, issn = {0377-2217}, journal = {European Journal of Operational Research}, keywords = {Concurrent Design Overlapping Product development engineering iteration}, number = 1, pages = {311-326}, timestamp = {2011-01-21T09:59:38.000+0100}, title = {Managing the exchange of information in product development}, volume = 184, year = {2008/1/1/} }