• 沒有找到結果。

本研究基於哲學詮釋學,以重視集體智慧為主要精神,並佐以軟體工程的相 關研究,來設計一套適合系統演化與不斷維護的需求分析方法論,並且搭配本方 法而發展了一套以部落格為基礎的工具,來協助企業針對分散於各地的使用者來 進行需求的收集,並且應用了設模型與知識本體,來設計了自動衝突偵測的智慧 型系統,來提醒企業在選擇去吸納大眾的意見時,新需求是否與既有設計有所衝 突,進而促使企業對於這種抵觸的狀況來進行進一步的思考與討論。

本研究除了提出方法論與部落格工具之外,也實際由經營網路報紙與購物網 站的企業來進行試用,在經過訪問後,得到了對本方法與工具的初步肯定,但也 獲取了不少重要的實務建議。本研究也依據這些實務建議來對方法論與工具當初 思慮不週之處,來提出改善的方向。相信本研究提出的方法論、工具、以及試用 後訪談,已經適當地回應了本研究最初想引導企業進行新需求初步分析、傾聽網 友需求、以及偵測需求與既有設計衝突的研究問題

本研究的貢獻,可從理論貢獻和實務貢獻兩方面來看。在理論貢獻方面,(1)

相較於以往過度重視全新系統的發展,本研究提出了一套適用於既有系統功能不 斷維護與演化,而且具體可行的需求分析方法論,(2)提出了一套功能需求的後 設模型,並指出功能需求所涉及的多種知識本體類型,並且,(3)提出一套偵測 新需求與既有設計之間衝突的規則。而本研究的實務貢獻,包含了(1)本研究 所提出的方法論,在經過業界企業的試用後,初步被認為是可應用於網站需求分 析,對需求管理的實務工作有所幫助,(2)本研究亦提出了一套以部落格為基礎 的需求擷取工具,有助於企業來蒐集網站的功能需求,(3)部落格具備自動衝突 偵測機制,來幫助企業判斷新需求是否可直接吸納來改善系統功能,抑或是新需 求與現有設計有所衝突,而需要觸發衝突解決流程。

在後續研究方面,可針對方法論與部落格工具兩方面進行改良。例如,可對

於簡易而成本低的新功能需求設計一個快捷簡化的方法,將新需求支持度評分的 功能加入部落格工具中,改善工具的友善性,以及解析需求的文字補充內的自然 語言,來協助利害相關者更容易地建立需求模型。此外,在解決了衝突後,是否 能容許在系統設計中多個分歧目標同時並存,並且制定其目標的優先順序,亦是 相當有趣的問題。再者,可進一步將需求的衝突偵測與應用在不同領域中,例如 數位內容的需求或對商品的需求。而方法論的效果和效益方面,雖然根據軟體工 程以往的經驗與研究文獻中所示,是較為難以驗證的,但如有機會,也可不斷陸 續關切其實務上的效果與效益。也上述這些研究議題,都值得未來繼續投入與努 力。

參考文獻

中文部分:

1. 余千智(主編),民 91,電子商務總論,台北市:智勝。

2. 潘建一,民 88,劇本引導式需求工程發展方法,國立中央大學資訊工程研 究所博士論文,未出版,中壢市。

3. 薛念林,民 88,目標導向之軟體需求工程發展方法,國立中央大學資訊工 程研究所博士論文,未出版,中壢市。

4. 唐日新,民 92,社群導向系統的使用者需求擷取之研究,國立政治大學資 訊管理研究所博士論文,未出版,台北市。

5. 方念萱、蘇彥豪,網路傳播中的對話與對峙—以女性主義連線版的言說為 例。資訊科技與社會轉型研討會,中央研究院社會學研究所籌備處,民 85 年12 月。

英文部分:

1. Abran, A., Moore, J. W. , Bourque, P., and Dupuis, R. Guide to the Software Engineering Body of Knowledge (SWEBOK). Los Alamitos, CA: IEEE Computer Society Press, 2004.

2. Andrade, J., Ares, J., García, R., Pazos, J., Rodríguez, S., and Silva, A. “A Methodological Framework for Viewpoint-Oriented Conceptual Modeling,”

IEEE Transactions on Software Engineering, 30(5) 2004, pp: 282-294.

3. April A., Hayes J. H., Abran, A., and Dumke, R. “Software Maintenance Maturity Model (SMmm): the software maintenance process model,” Journal of Software Maintenance and Evolution, 17(3) 2005, pp: 197-223.

4. Austin, J. L. How to Do Things with Words. Cambridge, Mass: Harvard University Press, 1962.

5. Avison, E., and Fitzgerald, G. “Where now for development methodologies?”

Communications of the ACM, 46 (1) 2003, pp: 79-82.

6. Banker, R. D., Datar S. M., and Kemerer C. F. “A model to evaluate variables impacting the productivity of software maintenance project,” Management Science, 37 (1) 1991, pp: 1-18.

7. Basili, V. R. “Viewing software maintenance as reuse-oriented software development,” IEEE Software, 7(1) 1990, pp: 19-25.

8. Basili, V., Briand, L., Condon, S., Kim, Y., Melo, W. L., and Valett, J. D.

Understanding and predicting the process of software maintenance releases. The International Conference on Software Engineering, Berlin, Germany, March 1996.

9. Berthon, P., Pitt, L., Ewing, M., and Carr, C. L. “Potential research space in MIS:

A framework for envisioning and evaluating research replication, extension, and generation,” Information Systems Research, 13(4) 2002, pp: 416-427.

10. Bieber, M., and Isakowitz, T. “Designing hypermedia applications,”

Communications of the ACM, 38(8) 1995, pp: 26-29.

11. Bieber, M. P., and Kimbrough, S. O. “On generalizing the concept of hypertext,”

MIS Quarterly, 16(1) 1992, pp: 77-93.

12. Bulkeley, W. M. “Marketers scan blogs for brand insights,” The Wall Street Journal, 2005, June 23, pp. B1.

13. Chalmers, M. “Hermeneutics, information and representation,” European Journal of Information Systems, 13(3) 2004, pp: 210-220.

14. Chandrasekaran, B., Josephson, J. R., and Benjamins, V. R. “What are ontologies, and why do we need them?” IEEE Intelligent Systems, 14(1) 1999, pp: 20-25.

15. Chapin, N., Hale, J. E., Khan, K. Md., Ramil, J. F., and Tan, W. G. “Types of software evolution and software maintenance,” Journal of Software Maintenance

and Evolution, 13(1) 2001, pp: 3-30.

16. Daft, R. L., and Lengel, R. H. “Organizational information requirements, media richness and structural design,” Management Science, 32(5) 1986, pp: 554-571.

17. Dart, S., Christie, A. M., and Brown, A. W. A case study in software maintenance (CMU/SEI-93-TR-8). Pittsburgh PA: Carnegie Mellon University, Software Engineering Institute, 1993.

18. Denning, P. J. “Accomplishment,” Communications of the ACM, 46 (7) 2003, pp:

19-23.

19. Dietz, J. L. G. “DEMO: Towards a discipline of organization engineering,”

European Journal of Operational Research, 128(2) 2001, pp: 351-363.

20. Flores, F., Graves, M., Hartfield, B., and Winograd, T. “Computer systems and the design of organizational interaction,” ACM Transactions on Office Information Systems, 6 (2) 1998, pp: 153-172.

21. Gadamer, H. Truth and method (2nd ed.) J. Weinsheimer & D. Marshall, Trans.

New York: Crossroad, 1989.

22. George, J. M., and Jones, G. R. Understanding and managing organizational behavior. Reading, Mass.: Addison-Wesley, 1999.

23. Gervasi, V. and Zowghi, D. “Reasoning about inconsistencies in natural language requirements,” ACM Transactions on Software Engineering and Methodology, 14(3) 2005, pp: 277-330.

24. Ginige, A. Web Engineering: Managing the complexity of web systems development. The 14th international conference on Software engineering and knowledge engineering, Ischia, Italy, July 2002.

25. Gruber, T. “Toward principles for the design of ontologies used for knowledge sharing,” International Journal Human-Computer Studies, 43(5-6) 1993, pp:

907-928.

26. Guariono, N., & Giaretta, P. “Ontologies and Knowledge Base: Towards a Terminological Clarification,” N. J. I. Mars (Ed.), Towards Very Large Knowledge Base: knowledge building and knowledge sharing (1995, pp: 25-32), Amsterdam: IOS Press.

27. Habermas, J. Communication and the Evolution of Society, Boston: Beacon Press, 1979.

28. Heidegger, M. Being and Time, J. Macquarrie & E. Robinson, Trans. New York:

Harper & Row, 1962.

29. Hill, C.J., and Motes, W. “Professional versus generic retail services: new insights,” Journal of Services Marketing, 9(2) 1995, pp: 22-35.

30. Hirschheim R., and Klein H. K. “Realizing emancipatory principles in Information Systems Development: The case for ETHICS,” MIS Quarterly, 18(1) 1994, pp: 83-109.

31. Hirschheim R., Klein, H. K., and Lyytinen K. Information System Development and data modeling. Cambridge: Cambridge University Press, 1995.

32. Hollingshead, A. B., McGrath, J. E., and O’Connor, K. M. “Group task performance and communication technology: A longitudinal study of computer mediated versus face-to-face work groups,” Small Group Research, 24(3) 1993, pp: 307-333.

33. Hooper, J. W. and Hisa P., “Scenario-based prototyping for requirements identification,” ACM SIGSOFT Software Engineering Notes, 7(5) 1982, pp.

88-93.

34. IEEE. IEEE standard glossary of software engineering terminology (IEEE Std 610.12-1990, Software Engineering) New York, NY: Institute of Electrical and Electronics Engineer, 1990.

35. IEEE. IEEE Standard for software maintenance (IEEE Standard 1219) New York,

NY: Institute of Electrical and Electronics Engineers, 1998.

36. Isakowitz, T., Bieber, M., and Vitali, F. “Web Information Systems,”

Communications of the ACM, 41(7) 1998, pp: 78-80.

37. Jacobson, I. Object-oriented software engineering Mass., Addison Wesley Longman, 1992.

38. Kaiya, H. and Saeki, M. “Using domain ontology as domain knowledge for requirements elicitation,” The 14th IEEE International Requirement Engineering Conference, 2006, Minneapolis, Minnesota.

39. Kajko-Mattsson, M. “Problem management maturity within corrective maintenance,” Journal of Software Maintenance and Evolution, 14(3) 2002, pp:

197-227.

40. Kajko-Mattsson, M., and Bosu, M. Eliciting an Enhancive Maintenance Model in Three Organisations in Ghana. The 5th IEEE/ACIS International Conference on Computer and Information Science and 1st IEEE/ACIS International Workshop on Component-Based Software Engineering, Software Architecture and Reuse, 2006, Honolulu, Hawaii.

41. Kendall, J., and Kendall, K. “Metaphors and methodologies: Living beyond the systems machine,” MIS Quarterly, 17(2) 1993, pp: 149-171.

42. Kim, S. “Participative management and job satisfaction: Lessons for management leadership,” Public Administration Review, 62(2) 2002, pp:

231-241.

43. Kimbrough, S. O., and Moore, S. A. “On automated message processing in electronic commerce and work support systems: speech act theory and expressive felicity,” ACM Transactions on Information Systems, 15(4) 1997, pp:

321-367.

44. Kinicki, A. and Williams, B. K. Management: a practical introduction, 2nd ed.

New York: McGraw-Hill, 2006.

45. Kishore, R., Sharman, R., & Ramesh, R. “Computational ontologies and information systems: I. foundations,” Communications of Association for Information Systems, 14(8) 2004a, pp: 158-183.

46. Kishore, R., Sharman, R., & Ramesh, R. “Computational ontologies and information systems: II. formal specification,” Communications of Association for Information Systems, 14(8) 2004b, pp: 184-205.

47. Lacity, M. C., & Janson, M. A. “Understanding qualitative data: A framework of text analysis methods,” Journal of Management Information Systems, 11(2) 1994, pp: 137-155.

48. Lancioni, R. “The reporting relationship of customer service: where does it belong in an industrial company,” Industrial Marketing Management, 24(1) 1995, pp: 19-26.

49. Lee, A. S. “Electronic mail as a medium for rich communication: An empirical investigation using hermeneutic interpretation,” MIS Quarterly, 18(2) 1994, pp:

143-157.

50. Lee, J. and Xue, N. “Analyzing User Requirements by Use Cases: A Goal-Driven Approach,” IEEE Software, 16(4) 1999, pp: 92-101.

51. Lindahl, C., and Blount, E. “Weblogs: simplifying Web publishing. IEEE Computer,” 36 (11) 2003, pp: 114-116.

52. Lucas, R. W. Customer Service: Skills and Concepts for Business. Chicago:

Irwin Mirror Press, 1996.

53. Lucas, F. J., Molina, F., Toval, A., de Castro, M. V., Cáceres, P., and Marcos, E.

Precise WIS Development. The 6th International Conference on Web Engineering, Palo Alto, CA, July 2006.

54. McQuail, D. and Windahl, S. Communication models: for the study of mass

communications. London; New York: Longman, 1993.

55. Mingers, J. “Combining IS research methods: Towards a pluralist methodology,”

Information Systems Research, 12(3) 2001, pp: 240-259.

56. Moor, A. D., and Efimova, L. An argumentation analysis of Weblog conversations. The 9th International Working Conference on the Language-Action Perspective on Communication Modeling, New Brunswick, New Jersey, June 2004.

57. Moran, D. Introduction to phenomenology. London; New York: Routledge, 2000.

58. Myers, M. D. “Dialectical hermeneutics: A theoretical framework for the implementation of information systems,” Information Systems Journal, 5(1) 1994, pp: 51-70.

59. Nissen, H. W., Jeusfeld, M. A., Jarke, M., Zemanek, G. V., and Huber, H.

“Managing multiple requirements perspectives with Metamodels,” IEEE Software, 13(2) 1996, pp: 37-48.

60. Pahl, C. “Adaptive development and maintenance of user-centric software systems,” Information and Software Technology, 46(14) 2004, pp: 973-986.

61. Polo, M., Piattini, M., and Ruiz, F. “Using a qualitative research method for building a software maintenance methodology,” Software - Practice and Experience, 32(13) 2002, pp: 1239-1260.

62. Pouloudi, A. “Stakeholder analysis as a front-end to knowledge elicitation,” AI &

Society, 11(1-2) 1997, pp: 122-137.

63. Robinson, W. N., Pawlowski, S. D., and Volkov, V. “Requirements interaction management,” ACM Computing Surveys, 35(2) 2003, pp: 132-190.

64. Rosenbloom, A. “The Blogosphere,” Communications of the ACM, 47(12) 2004, pp: 31-33.

65. Rumbaugh, J. “Getting started: using use cases to capture requirements,” Journal

of Object-Oriented Programming, 7(5), pp: 8-12.

66. Sarker, S., and Lee A. S. “Does the use of computer-based BPC tools contribute to redesign effectiveness? Insights from a hermeneutic study,” IEEE Transactions on Engineering Management, 53(1), pp: 130-145.

67. Severin, W. J. Communication theories: origins, methods, uses. New York:

Addison Wesley Longman, 2001.

68. Sommerville, I. “Integrated requirements engineering: a tutorial,” IEEE Software, 22(1), pp: 16-23.

69. El Sawy, O. A., and Bowles, G. “Redesigning the customer support process for the electronic economy: insights from Storage Dimensions,” MIS Quarterly, 21(4) 1997, pp: 467-483.

70. Searle, J. R., and Vanderveken, D. Foundations of Illocutionary Logic.

Cambridge: Press Syndicate of the University of Cambridge, 1985.

71. Shannon, C. & Weaver, W. The mathematical theory of communication. Urbana:

University of Illinois Press, 1949.

72. Sinha, V., Sengupta, B., and Chandra, S. “Enabling Collaboration in Distributed Requirements Management,” IEEE Software, 23(5) 2006, pp: 52-61.

73. Smith, B. Ontology and information systems. Buffalo, NY: SUNY at Buffalo, 2003.

74. Sterne, J. Customer Service on the Internet: Building Relationships, Increasing Loyalty, and Staying Competitive. New York: John Wiley & Sons, 2000.

75. Swanson EB. The dimensions of maintenance. The 2nd International Conference on Software Engineering, San Francisco, CA, March 1976.

76. Tepper, M. “The rise of social software,” ACM NetWorker, 7(3) 2003, pp: 19-23.

77. Thayer, R. H., and Dorfman, M. “Software engineering glossary: software maintenance,” IEEE Software, 22(4) 2005, pp: 103.

78. Trauth, E. M., and Jessup, L. M. “Understanding computer-mediated discussions:

Positivist and interpretive analyses of group support system use,” MIS Quarterly, 24(1) 2000, pp: 43-79.

79. Treese, W. “Open systems for collaboration,” ACM NetWorker, 8(1) 2004, pp.

13-16.

80. Väyrynen, T. “A shared understanding: Gadamer and international conflict resolution,” Journal of Peace Research, 42(3) 2005, pp: 347-355.

81. Vidgen, R. “Constructing a web information system development methodology,”

Information Systems Journal, 12(3) 2002, pp: 247-261.

82. Wagner, J. A. III. “Participation's effects on performance and satisfaction: A reconsideration of research evidence,” Academy of Management, 19(2) 1994, pp:

312-330.

83. Weigand, H. “Two decades of the Language-Action Perspective,”

Communications of the ACM, 49(5) 2006, pp: 65-70.

84. West, D. “Hermeneutic Computer Science,” Communications of the ACM, 40(4) 1997, pp: 115-116.

85. Winograd, T. “A Language/Action Perspective on the design of cooperative work,” Human-Computer Interaction, 3(1) 1987, pp: 3-30.

86. Young, Jr., and Terrence, E. “Blogs: is the new online culture a fad or the future?” Knowledge Quest, 31(5) 2003, pp: 50-51.