在全球化趨勢之下，企業所面臨的環境變化快速，而其生存與致勝之關鍵在於提昇競爭優勢，其競爭優勢主要來自於將具有創新力的產品和服務導入市場，因此，開發成功的新產品在現今市場中扮演著極其重要的角色，不但可以為企業帶來更多收益和貢獻，更是一種創新成果的展現。過去研究顯示，在實務上許多開發的新產品，由於沒有重視顧客需求，而無法為企業帶來良好的產品績效或導致產品開發失敗。因此，本研究探討需求管理實務作法對於新產品開發績效之影響。
研究中以問卷發放的方式取得資料，前測主要參考國內外文獻與專家學者之意見，使問卷修訂更加完善，於正研究中鎖定之新產品開發專案，依據經濟部產業的分類為主，透過對實際負責執行專案的成員，以紙本和網路問卷調查之方式進行資料收集，共計有效樣本146位受測者，並由Amos以結構方程模式(SEM)進行資料分析與研究。
經分析後，發現在新產品開發過程中，顧客需求管理是一個重要的因素，其中「需求管理實務作法」對「需求穩定性」具有顯著影響，而顧客「需求穩定性」會同時影響「人際衝突」、「專案績效」與「市場績效」，此外，研究發現「人際衝突」對「專案績效」具有負向影響，人際衝突愈高專案績效愈低，且在研究也提出了管理意涵與後續研究之建議。

Under the trend of globalization, the enterprises are facing rapid environmental change and the key to survival and success is to enhance competitive advantage. The innovative products and services are mainly edge. Moreover, the research also suggests that new product development (NPD) usually pays little attention to customer requirements in practices, then lead to NPD project failed. Thus, we try to study the effect of requirements management practices on new product development project performance.
    In pretest, Data collected from literature and specialist suggestion that for revised questionnaires. In total, there are 146 samples in this research; all data were used in structure equation modeling (SEM). With respect to a comprehensive view of customer requirements management, implications and future research directions are identified.
    The results showed that customer requirements is the key success factor in NPD and found requirements management practices was significant impact with requirement stable. The findings also revealed that requirements stable significant directly impact interpersonal conflict, project performance and market performance. Furthermore, the study provides evidence that interpersonal conflict negatively affect project performance.

目錄...............................................................................................................................I
表目錄...........................................................................................................................II
圖目錄..........................................................................................................................III
第一章 緒論 ............................................................................................................... 1
第一節 研究背景 ................................................................................................. 1
第二節 研究動機 ................................................................................................. 2
第三節 研究目的 ................................................................................................. 4
第四節 研究範圍 ................................................................................................. 5
第五節 研究流程 ................................................................................................. 5
第二章 文獻探討 ....................................................................................................... 7
第一節 需求管理實務作法 ................................................................................. 7
第二節 需求穩定性 ........................................................................................... 14
第三節 人際衝突 ............................................................................................... 16
第四節 需求多樣性 ........................................................................................... 20
第五節 專案績效 ............................................................................................... 22
第六節 市場績效 ............................................................................................... 24
第七節 各變數關係與假設推論 ....................................................................... 26
第三章 研究方法與設計 ......................................................................................... 30
第一節 研究架構 ............................................................................................... 30
第二節 研究假設 ............................................................................................... 31
第三節 問卷設計與變數衡量 ........................................................................... 32
第四節 研究對象 ............................................................................................... 38
第五節 資料分析方法 ....................................................................................... 38
第四章 資料分析與討論 ......................................................................................... 41
第一節 敘述性資料分析 ................................................................................... 41
第二節 效度分析與信度分析 ........................................................................... 45
第三節 相關性分性 ........................................................................................... 50
第四節 驗證性因素分析 ................................................................................... 51
第五節 結構模型分析 ....................................................................................... 53
第五章 結論與建議....................................................................................................62
第一節 研究結論 ............................................................................................... 62
第二節 管理意涵 ............................................................................................... 63
第三節 研究建議 ............................................................................................... 64
第四節 研究限制 ............................................................................................... 65
參考文獻 ..................................................................................................................... 66
一、中文部份 ..................................................................................................... 66
二、英文部份 ..................................................................................................... 67
附錄問卷


表目錄
表2-1 需求類型 ......................................................................................................... 8
表2-2 軟體需求水平類型 ....................................................................................... 10
表2-3 需求品質與穩定性之屬性規範 ................................................................... 15
表2-4 專案管理績效衡量指標 ............................................................................... 23
表2-5 市場績效指標 ............................................................................................... 26
表3-1 需求管理實務作法之問項表 ....................................................................... 33
表3-2 需求品質與穩定性之問項表 ....................................................................... 34
表3-3 人際衝突與需求多樣性之問項表 ............................................................... 35
表3-4 新產品發展績效之問項表 ........................................................................... 37
表3-5 專家學者對前測問卷之建議........................................................................39
表4-1 產業類別次數分配表....................................................................................41
表4-2 參與團體數次數分配表................................................................................42
表4-3 專案持續時間次數分配表............................................................................42
表4-4 團隊人數次數分配表....................................................................................43
表4-5 年齡次數分配表............................................................................................43
表4-6 學歷次數分配表............................................................................................44
表4-7 職稱次數分配表............................................................................................44
表4-8 工作年資次數分配表....................................................................................45
表4-9 Bartlett球形檢定與KMO檢定結果........................................................... 46
表4-10 需求管理實務作法構面之因素分析表........................................................47
表4-11 需求穩定性之因素分析表............................................................................48
表4-12 專案績效之因素分析表................................................................................48
表4-13 信度分析結果表............................................................................................49
表4-14 構面相關分析表............................................................................................51
表4-15 絕對適配量測指標........................................................................................52
表4-16 相對適配量測指標........................................................................................52
表4-17 簡約適配量測指標........................................................................................52
表4-18 初始理論模型配適度評鑑表........................................................................53
表4-19 修正後整體理論模式配適度評鑑表............................................................57
表4-20 收歛效度分析結果表....................................................................................58
表4-21 區別效度分析結果表....................................................................................59
表4-22 路徑係數........................................................................................................59
表4-23 假說檢驗........................................................................................................61


圖目錄
圖1-1 顧客需求管理流程圖 ....................................................................................... 2
圖1-2 研究流程圖 ....................................................................................................... 6
圖2-1 線性需求工程模型流程圖 ............................................................................... 9
圖2-3 產品發展團隊人際衝突架構 ......................................................................... 18
圖2-2 人際衝突管理模式 ......................................................................................... 19
圖2-4 需求不確定對剩餘績效風險與專案績效之影響 ......................................... 21
圖2-5 專案管理績效評估模型(客製化EFQM模型) ............................................. 24
圖2-6 市場結構行為績效模型 ................................................................................. 25
圖3-1 本研究架構 ..................................................................................................... 30
圖3-2 架構-假設圖 .................................................................................................... 31
圖4-1 初始理論模型..................................................................................................54
圖4-2 修正後整體理論模型 ..................................................................................... 56

一、中文部份
1. 許光華、何文榮（1998）。「專案管理─理論與實務」，華泰文化事業公司。
2. 邱俊仁(2005)。專案管理應用於新產品開發之研究。國立交通大學管學院碩士
班碩士論文。
3. 胡淑珍、莊青樹、蘇溢祥、陳維政(2008):手提CD音響外觀設計專案。專案管
理學刊，1(1)，34-54。
4. 洪世章、蔡碧凰(2006)。企業興業與成長:比較個案研究。中山管理評論，
14(1)，79-117。
5. 徐永宜譯、Scoot A Shane 著(2005)。科技創業聖經。台北市:台灣培生教育
出版股份有限公司。
6. 蕭文龍(2007)。多變量分析最佳入門實用書-SPSS+LISREAL(SEM)。碁峰資
訊。
67
二、英文部份
1. Abraham, R.(1998),―Emotional dissonance in organizations:antecedents, consequences, and moderators‖, Genetic, Social, and General Psychology Monographs 124 (2), 229–246.
2. Amason, A.C.(1996),―Distinguishing the Effects of Functional and Dysfunctional Conflict on Strategic Decision Making: Resolving a Paradox for Top Management Teams‖, Academy of Management Journal, 39 (1),123-148.
3. Anderson, J.C. and Gerbing, B.W.(1988),―Structural Equation Modling in Practice:
A Review and Recommended Two-Step Approach,‖ Psychological Bulletin,
vol.103, 411-423.
4. Argote, L.(1982),―Input Uncertainty and Organizational Coordination in Hospital
Emergency Unit‖, Administrative Science Quarterly, 27: 420-434.
5. Aurum, A. and Wohlin, C. (2003),―The fundamental nature of requirements
engineering activities as decision making process‖, Journal on Information and
Software Technology, 45(14): 945-954.
6. Aurum, A. and Wohlin, C. (2006),― Engineering and managing software
requirements‖ISSN:0947-3602.
7. Barki, H. and Hartwick J. (2001),―Interpersonal Conflict and Its Management in
Information System Development‖, MIS Quarterly, 25 (2), pp. 195-228.
8. Barki, H. and Hartwick, J.(1994),―User Participation, Conflict, and Conflict
Resolution： The Mediating Roles of Influence‖, Information Systems Research,
Vol 5, Iss 4; pp. 422-438.
9. Bast, T., Scherg, M., Berg, P.(1999),― Multiple source analysis of interictal spikes:
goals, requirements, and clinical value‖, J. Clin. Neurophysiol, 16(3):214–224,
May 1999.
10.Bentler, P.M.(1990),― Comparative fit indexes in structural models‖, Psychological
Bulletin, 107(2), 238-246.
68
11.Berkeley, D., de Hoog, R., Humphreys, P. (1990),― Software Development Project
Management‖, Ellis Horwood Books in Information Technology.
12.Berkly, B. T. and Saylor, J. H. (1994),― Customer-Driver Project Management‖,
New York: McGraw-Hill.
13.Belassi, W., Tukel, O.(1996),― A new framework for determining critical
success/failure factors in projects‖, International Journal Project Management.14
(3),141–151.
14.Berry, D.M. and Lawrence, B.(1998),― Requirements engineering‖, IEEE Software
25(2): 26-29.
15.Boehm, B.W., Grunbacher, P., Brigges, R.O.,(2001),― Developing groupware for
requirements negotiation: lessons learned‖, IEEE, Software, May/June,pp. 46-55.
16.Boulding, W., Staelin, R., Ehret, M., & Johnston, W. J. (2005). A customer
relationship management roadmap: what is known, potential pitfalls, & where to
go. J Mark, 69(4), 155–166.
17.BSC’04 (2004),―The challenges of complex IT projects. The report of a working
group from the Royal academy of engineering and the British computer society‖,
ISBN 1-903496-15-2. Access on 20th October 2004.
http://www.bcs.org/BCS/News/ Positions And Responses/ Positions/
complexity.htm.
18.Bubenko, J., Rolland, C., Loucopoulos, P., DeAutonellis, V.(1994), ―Facilitating
Fuzzy to formal Requirements Engineering‖ Proc. IEEE International Conference
RE pp: 154-7.
19.Bryde, J.D. (2003),―Modelling Project Management Performance‖, International
Journal of Quality& Reliability Management 20(2): 229-254.
20.Campbell,A.J. and R.G. Cooper (1999),―Do Customer Partnerships Improve New
Product Success Rates?‖Industrial Marketing Management 28(5):507-519.
21.Capers, J.(1994),―Revitalizing Software project Management‖ American
Programmer, Vol 6 (7) pp 3-12 ,June.
69
22.Carlshamre, P. (2001),― A Usability Perspective on Requirements Engineering‖,
From Methodology to Product Development. Ph.D. Dissertation No. 726,
Department of Computer and Information Science, Linköpings University.
23.Carnegie Mellon University Software Engineering Institute. (2002),― Capability
Maturity Model Integration‖, Version 1.1,CMU/SEI-2002-TR-001.
24.Cerpa,N., Bardeen, M., Kitchenham, B.,Verner, J.(2010),―Evaluating logistic
regression models to estimate software project outcomes‖, Information and
Software Technology 52 (2010) 934–944.
25.Chatman, J., Flynn, F.(2001),― The influence of demographic composition on the
emergence and consequences of cooperative norms in groups‖, Academy of
Management Journal 44, 956–974.
26.Cleland,D.I. and King, W.R.(1983),―System Analysis and Project Management‖,
New York: McGraw-Hill.
27.Cooper, R.G. (1996),―Overhauling the New Product Process‖, Industrial Marketing
Management 25.465-482.
28.Daft, R.L. and Macintosh, N.B. (1981),―A Tentative Exploration into the amount
and equivocality of information processing in organizational work units‖,
Administrative Science Quarterly, 26 ,207-224.
29.Davis, G.B.(1982),―Strategies for information requirements determination", IBM
Systems Journal, 21(1), 4-30.
30.Deshpande, R., Farley, J. U., Webster, Jr. F. E. (1993),― Corporate culture,
customer orientation, and innovativeness in Japanese firms: A Quadrad Analysis‖,
Journal of Marketing, 56: 69-83.
31.De Waal, A.A. and Counet, H. (2009),― Lessons learned from performance
management systems implementations‖, International journal of productivity and
performance management. Vol 58 (4) 367-390.
70
32.Dess, G.G. and Beard, D.W.(1984),― Dimensions of organizational task
environments‖, Administrative Science Quarterly 29, 52–73.
33.Edwards, J., Coutts I., McLeod, S. (2000),― Support for system evolution through
separating business and technology issues in a banking system‖, In: Proceedings
of international conference on software Maintenance, 11-14 October, pp. 271-276.
34.Emst, H and Krieger, K.(2010),―Customer relationship management and company
performance—the mediating role of new product performance‖, journal of the
Academy of Marketing Science, 16 March 2010.
35.Farris, J., Groesbeck, R.L., Van Aken, E.M., Letens, G.(2006), ―Evaluating the
relative performance of engineering design projects: a case study using data
envelopment analysis‖, IEEE Trans. Eng. Manage. 53 (3),471–482.
36.Fazlollahi, B., Tanniru, M.R.(1991),― Selecting a requirement determination
methodology — contingency model approach revisited‖, Information
Management 21, 291–303.
37.Frambach, R. T., Prabhu, J., Verhallen, T. M. M.( 2003),― The influence of business
strategy on new product activity: The role of market orientation‖, International
Journal of Research in Marketing, 20: 377-388.
38.Fujimoto,T. (1989),―Organizations for Effective Product Development: The Case
of the Global Automobile Industry‖, (Boston, MA, Harvard Graduate School of
Business Administration, Unpublished Doctoral Thesis.
39.Gefen, D. and Keil, M.(1998),―The Impact of Developer Responsiveness on
Perceptions of Usefulness And Ease of Use: An Extension of the Technology
Acceptance Model‖, The DATA BASE for Advances in Information Systems, 29,
2, 35-49
40.Gima, K. A. (1995), ―An Exploratory Analysis of The Impact of Market
Orientation on New Product Performance-- A Contingency Approach,‖ Journal of
Product Innovation Management, 12, 275-93.(PD15)
71
41.Gorschek, T., Svahnberg, M., Borg, A., Loconsole, A., Sandahl, K., (2007),― A
controlled empirical evaluation of a requirements abstraction model‖, Information
and Software Technology 49, 790–805.
42.Gorschek, T. and Davis, A. (2008）, ―Requirements Engineering: In Search of the
Dependent Variables‖, Information and Software Technology. 50, 1-2.
43.Greenley, G. E. and Foxall, G. R. (1998),― External moderation of associations
among stakeholder orientations and company performance‖, International Journal
of Research in Marketing, 15: 51-69.
44.Hair, J. F., Anderson, R. E., Tatham, R. L., Black, W. C.(1998), ―Multivariate Data
Analysis‖, 5th Ed., Prentice Hall, Englewood Cliffs, NJ.
45.Hatch, M.J.(1997),― Organization Theory: Modern, Symbolic, and Postmodern
Perspective‖, Oxford University Press, London, UK.
46.Haumer, P., Pohl, K., Weidenhaupt, K.(1998), ―Requirements Elicitation and
Validation with Real World Scenes", IEEE Transactions on Software Engineering: Special Issue on Scenario Management, Vol. 24, No. 12, December 1998.
47.Hauser, J.D. and Clausing, D.(1998),― The House of Quality‖, Harvard Business
Review, 66(3),pp.63-73.
48.Harrison, F., Lock, D.( 2004),― Advanced Project Management a Structured
Approach‖, Gower Publishing, Ltd.p.34.
49.Heerkens, G. R. (2001),―Project Management‖, McGraw-Hill.
50.IEEE-STD 610.12(1990),― Standard Glossary of Software Engineering
Terminology‖, Institute of Electrical and Electronics Engineers.
51.IEEE Std 830(1993),―Recommended Practice for Software Requirements
Specifications‖, December 2.
72
52.Jarvenpaa, S. L., Tractinsky, J., & Vitale, M. (2000),― Consumer trust in an internet
store. Information Technology and Management‖, 1(1&2),45-71.
53.Jiang, J.J., Klein, G., Wu, S.P.J., Liang, T.P.(2009),― The relation of requirements
uncertainty and stakeholder perception gaps to project management performance‖,
The Journal of Systems and Software 82, 801–808
54.Jiao, J. and Chen, C.H.(2006),―Customer Requirement Management in Product
Development: A Review of Research Issues‖.
55.Jones, Capers (1994),―Revitalizing Software project Management‖,American
Programmer, Vol 6 (7) pp 3-12 ,June.
56.Joreskog, K. G. (1993), ―Testing structural equation models. In K. A. Bollen & J.
S. Long (Eds.), Testing structural equation models (pp. 294-316) Newbury‖, CA:
Sage.
57.Kauppinen, M., Vartiainen, M., Kontio, J., Kujala, S., Sulonen, R.
(2004),― Implementing Requirements Engineering Processes throughout
Organizations: Success Factors and Challenges‖, Information and Software
Technology, 46 (14), 937-953. © 2004 Elsevier Science. By permission.
58.Kennerley, M. and Neely, A.(2003),― Measuring performance in a changing
business environment‖, International Journal of Operations & Production
Management, 23(2): 213-229.
59.Kerzner, H.(2004),―Advanced Project Management: Best Practices on
Implementation‖, John Wiley & Sons.
60.Kitchenham, B. and Pfleeger, S. L.(1996), ― Software Quality: The Elusive Target‖,
IEEE Software, Vol. 13, No. 1, January 1996, pp. 12-21.
61.Kloppenberg, T. and Opfer, W.A.(2002),― The Current State of Project
Management Research: Trends, Interpretations and Predictions‖, Project Management Journal,33(2),5-19.
73
62.Kotonya, G., Sommerville, I. (1998),― Requirements engineering – processes and
techniques‖, ISBN 0471972.
63.Lehmann, D.R. and Winer, R.S.(2002),― Product Management‖, Third edition
McGraw-Hill, Boston.
64.Lewis, J.P. (2006),― Fundamentals of Project Management‖, Third Editio. New
York: AMACOM.
65.Lewis, J.P. (2007),― Mastering Project Management‖, 2nd Ed. New York:
McGraw-Hill.
66.Liang, T. P. , Liu, C. C. , Lin, T. M., Lin, B. (2007), ―Effect of team diversity on
software project performance‖, Industrial Management & Data Systems,Vol.107,
No.5, pp.636-653.
67.Li, J., Hou, L., Qin, Z., Wang, Q., Chen, G.(2008),―An Empirically–Based Process
to Improve the Practice of Requirement Review‖.
68.Linder, J.C. (2006), ―Does innovation drive profitable growth? New metrics for a
complete picture‖, Journal of Business Strategy, 27(5):38-44.
69.Li,T. and Calantone, R. J.(1998),―The Impact of Market Knowledge Competence
on New Product Advantage: Conceptualization and Empirical Examination‖,
Journal of Marketing, Vol.62, October, 13-29.
70.Liu,Y.C.J., Chen,H.G., Chen,C.C., Sheu,T.S.(2010),―Relationships among
interpersonal conflict, requirements uncertainty, and software project
performance‖, International Journal of Project Management, accepted (SSCI)
71.Lu youjie (2005),―New construction economics‖, China Water Power Press, Apr.
72.Macaulay L.A.(1996),― Requirements engineering‖, Springer-Verlag, New York,
London.
73.Madhavji, N.H., Holtje, D., Hong, W., Bruckhaus, T.(1994),― Elicit: a method for
eliciting process models‖, In: Proceedings of CAS conference, Toronto, Canada,
31 October–3 November, pp.11-122.
74
74.Martin, N.L., Pearson, J.M., Furumo, K.( 2007),― Is project management: size,
practices and the project management office‖, Journal of Computer Information
Systems 47, 52–60.
75.Maylor, H.( 2001),― Beyond the Gantt chart: Project management moving
on‖, International Journal ofProject Management, 19(1): 92-100.
76.McKay, A., de Pennington, A., Baxter, J. (2001),― Requirements management: a
representation scheme for product Computer-Aided Design‖,33(7):511-520.
77.Might, R.J. and Fischer, W.A.(1985),― The role of structural factors in
determining project management success‖, IEEE Trans. Eng. Manage.32 (2),
71–77.
78.Moynihan, T.( 2000),― Coping with requirement-uncertainty: the theories-ofaction
of experienced IS/software project managers‖, The Journal of Systems and
Software 53, 99–109.
79.Neely, A. (1999), ―The performance measurement revolution: why now and what
next?‖, International Journal of Operation & Production Management, Vol. 19,
No. 2, pp. 205-228.
80.Neely, A., Gregory, M., Platts, K.( 2005),― Performance measurement system
design: a literature review and research agenda‖, International Journal of
Operation & Production Management, 25 (12), 1228–1263.
81.Nidumolu, S.R.(1995),―The effect of coordination and uncertainty on software
project performance: Residual Performance Risks as an Intervening Variable‖,
Information Systems Research, September , pp.191-219.
82.Nidumolu, S.R.( 1996),― Standardization, requirements uncertainty
and software project performance‖, Information Management 31,
135–150.
83.Nobeoka, K. and Cusumano, M.A. (1992),―Strategy, structure and performance in
product development : Observations from the auto industry‖, Research Policy, 21:
265-293.
75
84.Pohl, K. (1993) ―The Three Dimensions of Requirements Engineering‖,
CAiSE, Paris.
85.Pouloudi, A. and Whitley, E.A (1997),― Stakeholder identification in inter-
organizational systems: Gaining insights for drug use management systems‖,
European journal of information systems, 6: 1-14
86.Project Management Institute(PMI),(2008),― Making project Management
indispensable for business results‖.
87.Project Management Institute(PMI),( 2004),― A Guide to the Project Management
Body of Knowledge‖, ANSI/PMI 99-001-2004, 3rd Newton Square,PA.
88.Putnam, L. L.and Poole, M. S. (1987),― Conflict and negotiation‖, In F.M.Jablin,
L. L. Putnam, K. H. Robert, and L. W. Porter (Eds.), Handbook of Organizational
Communication: An Interdisciplinary Perspective (pp. 549-599). CA: Sage:
Newbury Park.
89.Qureshi, T. M., Warraich, A. S., Hijazi, S. T. (2009),―Significance of project
management performance assessment (PMPA) model‖,International Journal of
Project Management, Vol.27, pp. 378–388.
90.Rafla, T., Robillard, P.N., Desmarais, M.(2007),― A method to elicit architecturally
sensitive usability requirements: its integration into a software development
process‖, Software Quality Journal 15, 117–133.
91.Rahim, M. A.and Bonoma, T. V. (1979), Managing Organizational Conflict: A
Model for Diagnosis and Intervention. Psychological Reports, 44: 1323-1344.
92.Rahim, M. A. (1983),― Rahim organizational conflict inventories‖, Palo Alto,
Calif.: Consulting Psychologist Press.
93.Regnell, B., Beremark, P., Eklundh, O. (1998),― A Market-Driven Requirements
Engineering Process – Results from an Industrial Process Improvement
Programme‖, Requirements Engineering, 3, 121–129.
76
94.Richard Y. Wang and Vada C. Storey,(1998),―Modeling quality requirements in
conceptual database design‖.
95.Robey, D., Smith, L.A., Vijayasarathy, L.R.(1993),― Perceptions of conflict and
success in information system development projects‖, Journal of Management
Information System 10, 123–139.
96.Robey, D.L., Farrow, D., Franz, C.R.(1989),―Group Process and Conflict in
System Development‖, Management Science, 35 (10), 1172-1191.
97.Salo, A. and Käkölä, T. K. (2002),―Groupware Support for Requirements
Management in New Product Development‖.
98.Sawyer, P., Sommerville, I., Viller, S.(1999),―Capturing the Benefits of
Requirements Engineering‖, IEEE Software, 16 (2),pp 78 - 85
99.Scott, W.R.( 2003),― Organizations: Rational, Natural, and Open Systems‖,
Prentice-Hall, Upper Saddle River, NJ.
100.Sethi, R., Smith, D. C.,Park, C. W.(2001),― Cross-functional product
development teams, creativity, and the innovativeness of new consumer
products‖, Journal of Marketing, 38: 73-85.
101.Shepherd, W. G. (1985),― The Economics of Industrial Organization‖,
Englewood Cliffs, NJ, Prentice-Hall, Inc.
102.Sherman, J.D., Souder, W.E., Berkowitz, D. (2005), ―New Product Development
Performance and the Interaction of Cross-Functional Integration and Knowledge
Management‖, Journal of Product Innovation Management, 22 (5), 399–411.
103.Smits, M. and Janssen, R. (2008), ―Impact of Electronic Auctions on Health Care
Markets‖, Electronic Markets 18(1): 19-29.
104.Smits, M.T. and Weigand, H. (2010),― Identifying market performance indicators
that can be influenced by electronic intermediaries‖, In A. Trish, M. Turpin, and
J.P. van Deventer (Eds.) Proceedings of the 18th European Conference on
Information Systems (ECIS '10), Pretoria: University of Pretoria. Further
information.
77
105.Stokes, D.A.(1991),― Requirements Analysis‖, Computer Weekly Software
Engineer’s Reference Book, 1991, pp. 16/3-16/21.
106.Sommerville, I.(2006),―Software Engineering‖, 8th edition. Addison Wesley.
107.Song, X. M., Thieme, R. J., Xie, J. (1998),― The Impact of Cross- Functional
Joint Involvement Across Product Development Stages: An Exploratory Study‖,
Journal of Product Innovation Management, 15(4),289- 303.
108.Teory, T.K.(1990),―Database Modeling and Design: The Entity-Relationship
Approach‖, San Mateo, CA: Morgan Kaufman Publisher.
109.The Standish Report (2004), http://www.standishgroup.com/chronicles/index.php.
110.Thomas, B.; Michael,S. and Patrick, B.(1999),― Multiple Source Analysis of
Interictal Spikes: Goals, Requirements, and Clinical Value‖, Journal of Clinical
Neurophysiology, May 1999 - Volume 16 - Issue 3 - pp 214-224.
111.Thomke, S. and Von Hippel, E.(2002), ― Customer as Innovators: A New way to
Create Value‖, Harvard Business Review, 80(4),74-81.
112.Ulwick, A.W. (2002), ― Turn customer input into innovation‖, Harvard Business
Review, January, 91–97.
113.Urban, G. and Star, S. (1991),― Advanced marketing strategy: Phenomena,
analysis, decisions‖, New Jersey: Prentice-Hall.
114.Wall, J.A. Jr. and Callister, R.R.(1995),―Conflict and Its Management‖, Journal of
Management, 21 (3), 1995, 515-558.
115.Wang, J. and Lin,Y.T.(2003),― Fuzzy multicriteria group decision making
approach to select configuration items for software development‖, Fuzzy Sets
and Systems 134 (3) 343–363.
116.Wang, R. and Storey, V. C.(1994),―Modeling Quality Requirements in
Conceptual Database Design‖, TDQM-94-02, May.
78
117.Wei zhiming,( 2002),―Evolution and new frontiers of industrial organization
theory in the 20th century‖, Social Sciences Abroad, May.
118.Wilson, W.M., Rosenberg, L.H., Hyatt, L.E. (1997),― Automated analysis of
requirement specifications‖, Proceedings of the 19th International Conference on
Software Engineering, Boston, MA, pp. 161-171.
119.Wortzel, R.(1979), ― New Life Style Determinants of Women’s Food Shopping
Behavior‖, Journal of Marketing, Volume 43,P29-P29.
120.Wysocki, R. K. and McGary, R.(2003),―Effective Project Management:
Traditional, Adaptive, Extreme‖,(3rd edition) Wiley | ISBN 0471432210.
121.Zaltman,G.and Burger, P. C. (1975),―Marketing Research: Fundamentals &
Dynamics‖, Hinsdale, IL: Dryden Press.
122.Zhang, G., Lu, J. (2003),―An integrated group decision-making method
dealing with fuzzy preference for alternatives and individual judgments for
selection criteria‖, Group Decision and Negotiation, Vol. 12, No. 6, pp. 501-515.
123.Zhang, Q. and Doll, W. J. (2001), ― The fuzzy front end and success of new
product development: A casual model. European Journal of Innovation
Management‖, 4(2), 95-112.