軟體開發的流程是一項知識密集的活動，更是軟體開發組織的重要資產。除了最後所交付的軟體產品是重要的產品知識外，專案開發過程中的產出─例如專案計畫、需求規格書、測試報告等，皆為開發此軟體產品過程中重要的知識結晶。然而軟體產品知識只是一種工作結果，它們的產生是一個協同過程─其需要不同的人在不同的時間透過漸進或循環的溝通方式來共同合作產生。因此，團隊溝通過程所產生的資訊或知識之間的相依關係可以做為產品知識發展的脈絡。此外，在協同過程中團隊的溝通通常為專案運行中重要的議題。本研究嘗試建立並開發出以議題流程為導向的產品知識脈絡系統應用於軟體協同開發環境，並以Web-based的方式呈現系統。輔助專案團隊保存在協同開發過程中經專案議題溝通逐步產生的產品知識脈絡，並供成員進行後續產品維護或成為新類似專案的參考。

The process of software development is knowledge-intensive, and is a critical asset of software development organizations. Beside the final software development product, the artifacts (e.g. project plans, requirement specification, and testing reports, etc.) created during the process of software development are also important product knowledge. However, the development of explicit product knowledge requires different people to participate and communicate in different times for getting different information and implicit knowledge. Therefore, the relations between the knowledge which are generated by team communication and participation become the contexture in the development of product knowledge. Besides, the communications in team’s collaborative processes usually that take place via project agendas. This research proposes a concept of agenda-oriented contextual flow of agenda to model the development of product knowledge in collaborative software development. To implement the concept, this research develops a web-based system. This system assists project team in preserving contextual flow of product knowledge from collaborative processes, and provides team members a guideline to maintain the product or create a new similarity project.

[1] AddFlow官網：http://www.lassalle.com/
[2] Ajmal, M., Helo, P., Kekäle, T. (2010). Critical factors for knowledge management in project business. Journal of Knowledge Management, 14(1), 156 – 168.
[3] Alam, O., Adams, B., Hassan, A.E. (2012). Preserving knowledge in software projects. The Journal of Systems and Software, 85, 2318– 2330.
[4] Alavi, M., Leidner, D.E. (2001). Review: Knowledge Management and Knowledge Management Systems: Conceptual Foundations and Research Issues. MIS Quarterly, 25(1), 107 – 136.
[5] Antunes, P., Ho, T., Carriço, L. (1999). A GDSS Agenda Builder for Inexperienced Facilitators. Proceedings of the 10th EuroGDSS workshop.
[6] Barker, A. (2007). How to Manage Meetings (2nd Edition). Kogan.
[7] Bergmann, R. (2002). Knowledge Management: Foundations, Development Methodology, and Internet-based Applications. Springer: Germany.
[8] Chen, C.Y., Chao, K.H., Chen, P.C. (2007). A Preliminary study of meeting flow management for software project development: the prototype (MfPMIS). Industrial Engineering and Engineering Management (pp. 1009-1013), IEEE.
[9] Chen, C.Y., Chen, P.C., Tsai, W.L. (2008). Organizing project-based group communication events: A macro perspective. Industrial Engineering and Engineering Management (pp. 1798 - 1803), IEEE.
 
[10] Chen, C.Y. (2009). A Meetings Flow Approach for Conducting Student Final-Year Projects. Journal of Computing Science in Colleges, 24(6), 28 - 34.
[11] Chen, C.Y. (2011). Managing projects from a client perspective: the concept of the meetings-flow approach. International Journal of Project Management, 29(6), 671 - 696.
[12] Cronbach, L.J. (1951). Coefficient alpha and the internal structure of tests. Psychometrika, 16(3), 297 - 334.
[13] Dickinson, T.L., McIntyre, R.M. (1997). A conceptual framework of teamwork measurement, in: M.T. Brannick, E. Salas, C. Prince (Eds.), Team Performance Assessment and Measurement: Theory, Methods, and Applications, Psychology Press, NJ, Pages 19 - 43
[14] Dingsøyr, T. (2002). Knowledge Management in Medium-Sized Software Consulting Companies. Empirical Software Engineering, 7(4), 383 - 386.
[15] DOD. (1998). Department of Defense Handbook Work Breakdown Structure. USA.
[16] Ebert, C., Man, J.D. (2008). Effectively Utilizing Project, Product and Process Knowledge. Information and Software Technology, 50(6), 579 - 594.
[17] Fuggetta, A. (2000). Software Process: A Roadmap. Proceedings of the Conference on The Future of Software Engineering (pp. 25 - 34).
[18] Gallupe, B. (2001). Knowledge management systems: surveying the landscape. International Journal of Management Review, 3(1), 61 - 77.
 
[19] Garcia, A.C.B., Kunz, J., Fischer, M. (2005). Voting on the agenda: the key to social efficient meetings. International Journal of Project Management, 23, 17 - 24
[20] Zhuge, H. (2002). A Knowledge Flow Model for Peer-to-Peer Team Knowledge Sharing and Management. Expert Systems with Applications, 23(1), 23 - 30.
[21] Hoegl, M., Gemuenden, H.G. (2001). Teamwork quality and the success of innovative projects: A theoretical concept and empirical evidence. Organization Science, 12(4), 435 - 449.
[22] Humphrey, W.S. (2000). The team software process. Technical Report, CMU/SEI-2000-TR-023.
[23] IBM (1997). Project Management Fundamentals Handbook.
[24] Jabar, M.A., Ahmadi, R., Shafazand, M.Y., Ghani, A.A.A., Sidi, F., Hasan, S. (2013). An Automated Method for Requirement Determination and Structuring Based on 5W1H Elements. 2013 IEEE 4th Control and System Graduate Research Colloquium.
[25] Johnson-Laird (1983). Mental Models, Cambridge: Cambridge University Press.
[26] Jung, J., Choi, I., Song, M. (2007). An integration architecture for knowledge management systems and business process management systems. Computers in Industry, 58, 21 - 34.
[27] Jurison, J. (1999, September). Software Project Management: The manager’s view. Communications of AIS, 2(17).
[28] Katzenbach, R., Smith, K. (1993). The Discipline of Teams. Harvard Business Review.
[29] Khalefa, M.S., Jabar, M.A., Abdullah, R.H., Abdullah, S., Amidi, A. (2014). Overview of knowledge flow in a software development process. Information Technology and Multimedia (ICIMU), 2014 International Conference on (pp.151 – 156).
[30] Kraut, R.E., Streeter, L.A. (1995). Coordination in software development. Communications of the ACM, 38(3), 69 - 81.
[31] Kruchten, P. (2000). The Rational Unified Process: An Introduction, 2nd Edition. Addison Wesley.
[32] Lai, C.H., Liu, D.-R. (2009). Integrating knowledge flow mining and collaborative filtering to support document recommendation. Journal of Systems and Software, 82(12), 2023 - 2037.
[33] Levesque1, L.L, Wilson1, J.M., Wholey, D.R. (2001). Cognitive divergence and shared mental models in software development project teams. Journal of Organizational Behavior, 22(2), 135 - 144.
[34] Lin, Y.C., Lee, H.Y. (2012). Developing project communities of practice-based knowledge management system in construction. Automation in Construction, 22, 422 - 432.
[35] Liu, D.R., Lin, C.W., Chen, H.F. (2013). Discovering role-based virtual knowledge flows for organizational knowledge support. Decision Support Systems, 55(1), 12 - 30.
[36] Luo, X., Hu, Q., Xu, W., Yu, Z. (2008). Discovery of textual knowledge flow based on the management of knowledge maps. Concurrency and Computation: Practice and Experience, 20 (15), 1791 - 1806.
[37] Maclachlan, L. (1996). Making Project Management for You. London: Library Association.
[38] Malhotra, Y. (2000). Knowledge Management and Virtual Organizations. Idea Group Publishing, Hershey, PA.
[39] Moe, N.B., Dingsøyr, T., Dybå, T. (2010). A Teamwork Model for Understanding An Agile Team: A Case Study of A Scrum Project. Information and Software Technology, 52(5), 480 - 491.
[40] Ngai, E.W.T., Chan, E.W.C. (2005). Evaluation of knowledge management tools using AHP. Expert Systems with Applications, 29, 889 - 899.
[41] Niederman, F., Volkema, R. (1996). Influence of Agenda Creation and Use on Meeting Activities and Outcomes: Report on Initial Results. Proceedings of the 1996 conference on ACM Sigcpr / Sigmis Conference (pp. 192-205).
[42] Nonaka, I. (1994). A Dynamic Theory of Organizational Knowledge Creation. Organization science, 5(1), 14 - 37.
[43] Ouertani, M.Z., Baïna, S., Gzara, L., Morel, G. (2011). Traceability and Management of Dispersed Product Knowledge during Design and Manufacturing. Computer-Aided Design, 43(5), 546 - 562.
[44] PMI (2004). A Guide to the Project Management Body of Knowledge, 3rd ed., (PMBOK Guides.)
[45] Polanyi, M. (1966). The Logic of Tacit Inference. The Royal Institute of Philosophy, 41(155), 1 - 18.
[46] Rodríguez, O.M., Martínez, A.I., Favela, J., Vizcaíno, A., Piattini, A. (2004). Understanding and supporting knowledge flows in a community of software developers. 10th Collaboration Researchers International Working Group (CRIWG) Conference, San Carlos, Costa Rica (pp. 52 - 66).
[47] Salisbury, M.W. (2003). Putting theory into practice to build knowledge management systems. Journal of knowledge management, 7(2), 128 - 141.
[48] Schmidt, R.F. (2013). Software Engineering: Architecture-Driven Software Development. MA: Morgan Kaufmann, an imprint of Elsevier.
[49] Sieli, E.M. (1991). Managing a project as a process. AT&T Technical Journal, 70(2), 33-39.
[50] Stapel, K., Schneider, K. (2012). Managing knowledge on communication and information flow in global software projects. Expert Systems - Special Issue on Knowledge Engineering in Global Software Engineering, in press.
[51] Tilley, R., Müller, H.A., Orgun, M.A. (1992). Documenting Software Systems with Views. In Proceedings of the 10th International Conference on Systems Documentation (SIGDOC '92)(pp. 211-219), Canada.
[52] Tsui, E. (2003). Tracking the role and evolution of commercial knowledge management software. In C. W. Holsapple (Ed.), Handbook on knowledge management 2: Knowledge directions (pp. 5–28). New York: Springer.
[53] Udeaja, C.E., Kamara, J.M., Carrillo, P.M., Anumba, C.J., Bouchlaghem, N., Tan, H.C. (2008). A web-based prototype for live capture and reuse of construction project knowledge. Automation in Construction, 17, 839–851.
[54] Wysocki, R.K., Beck, R.J., Crance, D.B. (1995). Effective, Project Management: How to Plan, Manage, and Deliver Projects on Time and within Budget. NY: John Wieley & Sons.
[55] Xu, P., Ramesh, B. (2003). A Tool for the Capture and Use of Process Knowledge in Process Tailoring. Proceedings of the 36th Hawaii International Conference on System Sciences.
[56] Yoo, K., Suh, E., and Kim, K.-Y. (2007). Knowledge Flow-Based Business Process Redesign: Applying a Knowledge Map to Redesign a Business Process, Journal of Knowledge Management, 11(3), 104 - 125.
[57] Yoshioka, T., Herman, G., Yates, J., Orlikowski, W. (2001). Genre taxonomy: A knowledge repository of communicative actions. ACM Transactions on Information Systems (TOIS), 19(4), 431 - 456.
[58] Zack, M. (1999). Managing codified knowledge. Sloan Management Review, 40(4), 45 - 58.
[59] Zhang, X., Li, M. (2005). Workflow-based Knowledge Flow Modeling and Control. Journal of Software, 16(2), 184 - 193.
[60] Zhuge, Hi. (2001). Knowledge flow management for distributed team software development. Knowledge-Based Systems, 15(8), 465 - 471.