應用協調理論建立系統軟體測試中問題改善之協作流程

以作者查詢圖書館館藏

、以作者查詢臺灣博碩士

、以作者查詢全國書目

、勘誤回報

、線上人數：58

、訪客IP：18.220.217.228

姓名

唐振強(Chen-Chian Tang) 查詢紙本館藏

畢業系所

資訊管理學系在職專班

論文名稱

應用協調理論建立系統軟體測試中問題改善之協作流程
(Applying Coordination Theory to Establish A Coordinative Process in Managing Issue Improvements That Involve Multiple Parties)

相關論文

★ 專案管理的溝通關鍵路徑探討─以某企業軟體專案為例	★ 運用並探討會議流如何促進敏捷發展過程中團隊溝通與文件化：以T銀行系統開發為例
★ 專案化資訊服務中人力連續派遣決策模式之研究─以高鐵行控資訊設備維護為例	★ 以組織正義觀點介入案件指派決策之研究
★ 應用案例式推理於問題管理系統之研究 -以筆記型電腦產品為例	★ 運用限制理論於多專案開發模式的人力資源配置之探討
★ 應用會議流方法於軟體專案開發之個案研究：以翰昇科技公司為例	★ 多重專案、多期再規劃的軟體開發接案決策模式：以南亞科技資訊部門為例
★ 會議導向敏捷軟體開發及系統設計：以大學畢業專題為例	★ 一種基於物件、屬性導向之變更影響分析方法於差異化產品設計
★ 會議流方法對大學畢業專題的團隊合作品質影響之實驗研究	★ 實施敏捷式發展法於大學部畢業專題之行動研究 – 以中央大學資管系為例
★ 建立一個用來評核自然語言需求品質的線上資訊系統	★ 結合本體論與模糊分析網路程序法於軟體測試之風險與風險關聯辨識
★ 在軟體反向工程中針對UML結構模型圖之線上品質評核系統	★ 以模糊專家系統實作軟體專案調適準則

檔案

[Endnote RIS 格式]

[Bibtex 格式]

[相關文章]

[文章引用]

[完整記錄]

[館藏目錄]

至系統瀏覽論文 ( 永不開放)

摘要(中)

隨著電子科技的日新月異，筆記型電腦也因為技術的演化；繁衍出功能的多樣性以及高度整合性，使得軟硬體與應用程式的開發日趨複雜。BIOS軟體身為電腦開機啟動時，處理器第一個執行的程式，因此，它肩負著重大任務，引導處理器識別所有關聯組件，最後導引至作業系統完成開機作業。然而BIOS系統開發通常需要多方合作，其過程中經常需要釐清作業系統、硬體、軟體以及韌體等多方問題，須經由多方合作協調，過程中難免因為多方協調的溝通不良造成誤解、設計文件標示不明或者需求定義不清，讓溝通不斷的產生甚至發生摩擦造成研發與測試的進度落後。
針對以上多方溝通協調問題，本研究嘗試從多方協調與溝通角度，應用『協調理論』提出以筆記型電腦BIOS系統開發專案為例，系統軟體開發過程中的問題管理活動在涉及多方合作下無法有效解決系統開發問題並及時落實在產品上之解決方案。本研究以個案研究的方式，探討筆記型電腦設計開發中的系統軟體測試之問題管理，檢視台灣辦公室在工作流程中所遭遇的問題，彙整個案公司在進行開發過程中發生的狀況，所面對的流程、人員、問題管理、訊息溝通轉換過程中所發生的問題，建立出一套可持續發展的溝通協調模式，將有助於個案公司的台灣辦公室在系統軟體開發上對於多方合作協調的研發過程之問題管理的改善。

摘要(英)

With the ever-changing technology, the advanced notebook computers generate the diverse and
high integration functions, which makes the software, hardware and application development more
complex . The BIOS system is the first program to be execute d when a computer is turned on. To
finish the computer startup , t he BIOS system is an important role that leads the processor to identify
all of the associated components However, the BIOS system development usually needs to consider
the multilateral cooperation to solve the issue that include the operating system, hardware, software
and firmware; hence there are some problems such as poor communication , unclear design document
and definition in t he discussion. Note that these problems could incur the research and test behind the
schedule
To solve the above
problems , this study attempts the coordination theory (i.e., multilateral
negotiation and communication) to propose the solution entitled A case study of laptop bios system
development ”. The purpose of the solution is to overcome the issue management activities not to be
resolve d efficiently and feedback timely on the product in the system software development process .
The specific company is investigated in this work to explore the issue management associated with
the system software test during the design development of the notebook computers . Therefore, this
study not only inspect s the issues occurred in the work process of Taiwan office and collects the issues
during development in specific company, but also establishes a coordinated model for stable
development to solve the issues in the process , actor , issue management and conversion process of
message communication . This solution can help specific company of Taiwan office to improve the
issue management associated with the system software development in the research process.

關鍵字(中)

★ 問題管理
★ 協調理論
★ 系統軟體測試
★ 筆記型電腦系統軟體開發
★ 多方合作

關鍵字(英)

★ Issue Management
★ Coordination Theory
★ System Software Testing
★ Notebook Computer System Development
★ Multiple Coordination

論文目次

目錄
一、緒論 1
1.1研究背景 1
1.2研究動機 2
1.3研究目的 3
1.4研究範圍 4
1.5研究架構 4
二、文獻探討 5
2.1系統軟體測試 5
2.2問題管理 6
2.3協調理論 11
三、研究方法 15
3.1 個案研究 15
3.2 研究設計 17
3.3 資料收集與分析 18
四、個案分析 20
4.1 個案公司介紹 20
4.2 個案公司對於問題現況描述 22
4.3 協調流程設計 24
五、研究結果 31
5.1關鍵績效指標分析 31
5.2研究訪談 35
5.3研究限制 42
六、結論與未來展望 43
七、參考文獻 44

參考文獻

【中文部分】
1.陳玄玲(2018)，軟體開發技術與軟體專案管理，高立圖書。
2.林建煌, 許美玲, 許棟樑, & 陳大仁. (2012). 整合性優質設計之知識管理系統: 以筆記型電腦產業為例. 管理與系統, 19(1), 169-499.
3.盧正宗、祝道松，2019，「預算支出目標調整之困難度對後續預算執行及預算績效之影響：以策略性溝通作為權變因素」，會計評論，第 69 期：131-171。

【英文部分】
1.Allen, J. H., & Young, L. (2012). Report from the First CERT-RMM Users Group Workshop Series.
2.Ammann, P., & Offutt, J. (2016). Introduction to software testing. Cambridge University Press.
3.Anees, A., & Agrwal, A. (2017). Software process improvement models and their comparison. International Journal of Advanced Research in Computer Science, 8(5).
4.Avdiji, H., & Missonier, S. (2018). A design approach to team coordination. Revue Tranel, 68, 97-106.
5.Bayona-Oré, S., Chamilco, J., & Perez, D. (2019). Applying CMMI best practices to improve processes. MATEC Web of Conferences, (Vol. 292, p. 01065). EDP Sciences.
6.Berntzen, M. (2019). Coordination in Large-Scale Agile Software Development. International Conference on Agile Software Development, (pp. 123-133). Springer, Cham.
7.Canalys, Inc. (2021). Global PC market to grow 8% in 2021 despite worsening component shortages. Retrieved from：
https://canalys-prod-public.s3.eu-west-amazonaws.com/static/press_release/2021/
CanalysWW FCSTPCR2021.pdf
8.Chen, C.-Y., Chen, P.-C., & Lu, Y.-E. (2013). The coordination processes and dynamics within the inter-organizational context of contract-based outsourced engineering projects. Journal of Engineering and Technology Management, 30(2), 113-135.
9.Chase, W. H. (1984). Issue management. Issue Action Publications.
10.Ciervo, J., Shen, S. C., Stallcup, K., Thomas, A., Farnum, M. A., Lobanov, V. S., & Agrafiotis, D. K. (2019). A new risk and issue management system to improve productivity, quality, and compliance in clinical trials. JAMIA open, 2(2), 216-221.
11.Crowston, K., Rubleske, J., & Howison, J. (2015). Coordination theory: A ten-year retrospective. In Human-computer interaction and management information systems: Foundations (pp. 134-152). Routledge.
12.DeSanctis, G., & Jackson, B. M. (1994). Coordination of information technology management: Team based structures and computer based communication systems. Journal of Management information systems, 10(4), 85-110.
13.Ecar, M., da Silva, J. P. S., Amorim, N., Rodrigues, E. M., Basso, F., & Soldá, T. G. (2020, October). Software process improvement diagnostic: A snowballing systematic literature review. In 2020 XLVI Latin American Computing Conference (CLEI) (pp. 156-164). IEEE.
14.Farooq, S. U., & Quadri, S. (2013). Empirical evaluation of software testing techniques–need, issues and mitigation. Software engineering: an international Journal, 3(3), 41-51.
15.Faraj, S., & Sproull, L. (2000). Coordinating expertise in software development teams. Management science, 46(12), 1554-1568.
16.FCCL,Inc.(2022). Corporate About. Retrieved from：
https://www.fujitsu.com/jp/group/fccl/en/about/
17.Fraser, G., & Rojas, J. M. (2019). Software testing. In Handbook of Software Engineering (pp. 123-192). Springer, Cham.
18.Herbsleb, J. D., & Moitra, D. (2001). Global software development. IEEE software, 18(2),
16-20.
19.IDC, Inc. (2021). Personal Computing Devices Market Share. Retrieved from：
https://www.idc.com/promo/pcdforecast
20.ISTQB, Npo. (2018). Certified Tester Foundation Level Syllabus. Retrived from：
https://www.istqb.org/downloads/send/2-foundation-level-documents/281-istqb-ctfl-syllabus-2018-v3-1.html
21.Jamal, M. A. (2021). Issue Management in Arab Professional Company in the Kingdom of Saudi Arabia. iKSP Journal of Innovative Writings, 2(1), 33-41.
22.Kensing, F., Blomberg, J., 1998. Participatory design：Issues and concerns. Computer Supported Cooperative Work 7 (3–4), 167–185.
23.Kerzner, H. (2017). Project management case studies. John Wiley & Sons.
24.Kudaravalli, S., Faraj, S., & Johnson, S. L. (2017). A Configural Approach to Coordinating Expertise in Software Development Teams. MIS quarterly, 41(1).
25.Lechler, T. (2010, July). Project value mindset of project managers. In PMI® research conference: Defining the future of Project Management, Washington, DC.
26.Malone, T. W., & Crowston, K. (1990). What is coordination theory and how can it help design cooperative work systems? Proceedings of the 1990 ACM conference on Computer-supported cooperative work, systems?. In Proceedings of the 1990 ACM conference on Computer-supported cooperative work (pp. 357-370).
27.Malone, T. W., & Crowston, K. (1994). The interdisciplinary study of coordination. ACM Computing Surveys (CSUR), 26(1), 87-119.
28.Masood, S., Khan, S. A., & Hassan, A. (2021). Simulating Synchronization Issues on a Multiprocessor Embedded System for Testing. 2021 IEEE International Conference on Information Communication and Software Engineering (ICICSE), (pp. 299-302). IEEE.
29.Mobtahej, P. (2020). Psychology of Change Management in Development Process within Software Industry. Computational Research Progress in Applied Science & Engineering, 6(4), 294-300.
30.Mossalam, A. (2018). Projects’ issue management. HBRC journal, 14(3), 400-407.
31.Oliveira, G. H. M., Albuquerque, R. F., & Albuquerque, A. B. (2019, August). A comprehensive study on knowledge management applied to embedded system testing processes. In 2019 IEEE International Conference on Computational Science and Engineering (CSE) and IEEE International Conference on Embedded and Ubiquitous Computing (EUC) (pp. 410-418). IEEE.
32.Omoronyia, I., Ferguson, J., Roper, M., & Wood, M. (2010). A review of awareness in distributed collaborative software engineering. Software: Practice and Experience, 40(12), 1107-1133.
33.Ortt, R., Bücker, C., & Klein, S. (2016). Handbook on Networks in Innovation and Crisis management; Theory and Practice in a Dynamic and Disruptive Environment.
34.Patnaik, S., & Pandey, S. C. (2019). Case study research. In Methodological issues in management research: Advances, challenges, and the way ahead. Emerald Publishing Limited.
35.Pawlak, M., & Poniszewska-Marańda, A. (2020). Software Testing Management Process for Agile Approach Projects. In Data-Centric Business and Applications (pp. 63-84). Springer, Cham.
36.Piney, K. (2012). Integrated project risk and issue management. Project Management Institute.
37.Petersen, K., & Wohlin, C. (2010). The effect of moving from a plan-driven to an incremental software development approach with agile practices. Empirical Software Engineering, 15(6), 654-693.
38.Petersen, K., Roos, P., Nyström, S., & Runeson, P. (2014). Early identification of bottlenecks in very large scale system of systems software development. Journal of software: Evolution and Process, 26(12), 1150-1171.
39.Raatikainen, M., Motger, Q., Lüders, C. M., Franch, X., Myllyaho, L., Kettunen, E., Marco, J., Tiihonen, J., Halonen, M., & Männistö, T. (2021). Improved dependency management for issue trackers in large collaborative projects. arXiv preprint arXiv:2102.08485.
40.Sablis, A., Smite, D., & Moe, N. (2021). Team‐external coordination in large‐scale software development projects. Journal of software: Evolution and Process, 33(3), e2297.
41.Seidel, V. P., & O’Mahony, S. (2014). Managing the repertoire: Stories, metaphors, prototypes, and concept coherence in product innovation. Organization Science, 25(3), 691-712.
42.Sharp, H., Robinson, H., & Petre, M. (2009). The role of physical artefacts in agile software development: Two complementary perspectives. Interacting with computers, 21(1-2), 108-116.
43.Siegelaub, J. M. (2007). Six (yes six!) constraints: an enhanced model for project control. In PMI® Global Congress.
44.Sinha, S., Goyal, N. K., & Mall, R. (2021). Reliability and availability prediction of embedded systems based on environment modeling and simulation. Simulation Modelling Practice and Theory, 108, 102246.
45.Sobri, W., Fauzi, S., Nasir, M., Ahmad, R., & Suali, A. (2017). Coordination issues and its impact on project performance: A systematic literature review. Journal of Telecommunication, Electronic and Computer Engineering (JTEC), 9(3-3), 33-37.
46.Speth, S., Becker, S., & Breitenbücher, U. (2021, May). Cross-Component Issue Metamodel and Modelling Language. In CLOSER (pp. 304-311).
47.Strode, D. E., Huff, S. L., Hope, B., & Link, S. (2012). Coordination in co-located agile software development projects. Journal of Systems and Software, 85(6), 1222-1238.
48.Thota, M. K., Shajin, F. H., & Rajesh, P. (2020). Survey on software defect prediction techniques. International Journal of Applied Science and Engineering, 17(4), 331-344.
49.Zaitsev, A., Gal, U., & Tan, B. (2020). Coordination artifacts in agile software development. Information and Organization, 30(2), 100288.
50.Yin, R. K. (2018). Case Study Rsearch and Applications. Sage.

指導教授

陳仲儼

審核日期

2022-6-24

推文