嵌入式軟體開發的障礙在於規格修改氾濫造成追蹤困難、開發時間掌控不易、軟體版本混亂、軟體缺陷數在開發階段一直無法收斂而造成專案的失敗。導入軟體流程可使整個開發過程得到有效的控制。軟體流程並非一成不變，它會隨著企業內部、市場需求及客戶的特性而改變。原有的標準流程需做適當的裁製以符合實際的需要。
本研究以系統分析的方式，藉由分析嵌入式無線區域網路軟體的特性，對此類軟體流程加以探討，提出「調適型子系統與原型開發流程模式(Adaptive Subsystem and Prototyping Development Process Model; ASPDPM)」：以漸增模式由小到大、逐步擴增系統，以提升軟體系統在開發階段的穩定度；以螺旋形模式的方法改善產品開發初期規格未能確定的難題，並搭配原型快速開發模式的技巧協助客戶迅速熟悉新產品；最後再以敏捷式軟體開發的精神裁製出一個合適的軟體流程模式，其中包含軟體版本控管方式、快速測試及有效的回饋系統。調適型子系統與原型開發流程模式可確保在軟體系統開發時專注於成功關鍵流程的活動，進一步提升軟體的品質，同時也可以作為其他嵌入式軟體開發業者在進行軟體流程改善的參考。

A major hindrance to the embedded software development is the frequent modifications of the product specifications. These modifications may lead to the difficulties of specifications tracking, schedule control, and the confusion of the software versions. The consequence may eventually be the failure of the designated projects. Adopting the software process model can have an effective control over the frequent modifications in the development cycle. However, the effectiveness of the process model may depend on the market demands and the customer’s requests. The process needs to be tailored to meet the actual needs.
This study used the systems analysis approach to study the software processes for the embedded wireless local area network (LAN) software. Using a wireless LAN ODM company as an example, an Adaptive Subsystem and Prototyping Development Process Model (ASPDPM) had been developed and evaluated. This model utilized 1) an incremental model to bring up the quality of the system by enhancing the software stability during development phase; 2) the spiral model to tackle the uncertainty of the product specifications at the early stage; the rapid prototyping model which will provide the techniques for helping the customer quickly understanding the new product; and 3) the agile software development to tailor a suitable software process model. The ASPDPM was shown to ensure that the software development could focus on the key activities and further improve the quality of software. It could also be used as a reference for other embedded software development companies on improving their software processes.

中文部份：
[1] 林信惠，黃明祥 (2002)，軟體專案管理研究架構及趨勢，資訊管理研究學報，第四卷第一期。
[2] 林信惠、黃明祥、王文良 (2005)，軟體專案管理，智勝文化事業有限公司。
[3] 產業情報研究所(Market Intelligence & Consulting Institute, MIC) (2008)，2008年第一季台灣SOHO Router產業產銷暨重要趨勢分析。

英文部份：
[1] Aaen, I. (2003), Software Process Improvement: Blueprints versus Recipes, IEEE Software 20 (5) 86-89.
[2] Abrahamsson, P., Salo, O., Ronkainen, J., and Warsta, J. (2002), Agile Software Development Methods: Review and Analysis, VTT Technical Research Center of Finland, VTT Publications 478.
[3] Ahern, D. M., Clouse, A., and Turner, R. (2004), CMMI Distilled，賴志迢、莊雅喻、熊傳明、王紀先、黃彥荏、徐銓基譯(2004)，「CMMI Distilled中文版」，台灣培生教育出版。
[4] Bally, L., Brittan, J., and Wagner, K.H. (1977), A Prototype Approach to Information System Design and Development, Journal of Information and Management, Volume 1, pp. 21-26.
[5] Beck, K. (1999), Embracing Change with Extreme Programming, IEEE Computer, Volume 32, Issue 10, pp.70-77.
[6] Bennington, H. D. (1956), Production of large computer programs, in Proc. ONR Symp. Advanced Programming Methods for Digital Computers, pp.15-27.
[7] Boehm, B. W. and Bose, P. (1994), A Collaborative Spiral Software Process Model Based on Theory W, Third International Conference on the Software Process.
[8] Boehm, B. W. (1981), Software Engineering Economics, Englewood Cliffs, N. J.: Prentice-Hall, pp.83-94;470-472.
[9] Boehm, B. W. (1988), A Spiral Model of Software Development and Enhancement. IEEE Computer.
[10] Boehm, B. W. and Hoh In (1996), Identifying Quality-Requirements Conflicts, IEEE Software, Vol. 13, No. 2, pp.25-35.
[11] Boehm, B., Egyed, A., Kwan, J., Port, D., Shah, A., and Madachy, R. (1998), Using the WinWin Spiral Model: A Case Study, IEEE Computer, pp.33-44.
[12] Boehm, B. and Egyed, A. (1999), Optimizing Software Product Integrity through Life-Cycle Process Integration, Journal for Computer Standards and Interfaces.
[13] Boehm, B. (2002), Get Ready for Agile Methods, with Care, IEEE Computer 35 (1) 64-69.
[14] Brooks, Jr., F. P. (1975, 1995), The Mythical Man-Month: Essays on Software Engineering，錢一一譯(2004)，「人月神話：軟體專案管理之道」，經濟新潮社。
[15] CMMI Product Team (2002a), Capability Maturity Model Integration, Version 1.1, CMMI-SW/SE/IPPD/SS, Staged Representation CMU/SEI-2002-TR-011.
[16] CMMI Product Team (2002b), Capability Maturity Model Integration, Version 1.1, CMMI-SW/SE/IPPD/SS, Continuous Representation CMU/SEI-2002-TR-012.
[17] CMMI Product Team (2006), CMMI for Development, Version 1.2, CMU/SEI-2006-TR-008 ESC-TR-2006-008
[18] Cockburn, A. (2000), Selecting a Project’s Methodology, IEEE Software 17 (4) 64-71.
[19] Cockburn, A. (2002), Agile Software Development, Addison-Wesley.
[20] Cox, B. J. (1987), Object Oriented Programming: An Evolutionary Approach, Productivity Products International, Addison-Wesley Publishing Company.
[21] Forsberg, K., Mooz, H., and Cotterman, H. (2000), Visualizing Project Management: A Model for Business and Technical Success, John Wiley & Sons.
[22] Gibson, J. E., Scherer, W. T., and Gibson W. F. (2007), How to Do Systems Analysis, John Wiley & Sons, Inc..
[23] Hawrysh, S. and Ruprecht, J. (2000), Light Methodologies: It’s Like Déjà Vu All Over Again, Cutter IT Journal, 13:4-12.
[24] Highsmith, J. and Cockburn, A. (2001), Agile Software Development: The Business of Innovation, Computer 34, 120–122.
[25] Highsmith, J. (2002), What is agile software development? Crosstalk. The Journal of Defense Software Engineering, 4–9.
[26] Humphrey, W. S. and Kellner, M. I. (1989), Software Process Modeling: Principles of Entity Process Models. ICSE 1989:331-342
[27] Jacobson, I., Booch, G., and Rumbaugh, J. (1999), The Unified Software Development Process, Addison-Wesley Professional.
[28] Jalote, P. (2002), Project Management in Practice Processes for Executing Software Projects at Infosys，甄敏、文德蘭、張小萍、李幸秋、陳俊龍、王行一、廖莉芬、陳信宏、黃元巨、應鳴雄、游松文譯 (2004)，「軟體專案管理最佳實務」，維科圖書有限公司。
[29] Jones, C. (1996), Patterns of Software Systems Failure and Success, International Thomson Computer Press.
[30] Kettunen, P. and Laanti, M. (2004), How to Steer an Embedded Software Project: Tactics for Selecting the Software Process Model, Information and Software Technology, December, pp. 587-608.
[31] Lewin, M. D. (2002), Better Software Project management: A Primer for Success, John Wiley & Sons, Inc..
[32] McConnell, S. (1996), Rapid Development: Taming Wild Software Schedules, Microsoft Press.
[33] Mills, H. D. (1971), Top down programming in large system, Prentice Hall.
[34] Mills, H. D. (1971), Chief Programmer Teams: Principles and Procedures, IBM Corporation, Report No. FSC 71-5108.
[35] Miller, G. G. (2001), The Characteristics of Agile Software Processes. The 39th International Conference of Object-Oriented Languages and Systems (TOOLS 39).
[36] Nanus, B. and Farr L. (1964), Some Cost Contributors to Large-scale Programs, AFIPS Proc. SJCC, 25, pp.239-248.
[37] Paulk, M. C., Curtis, B., Chrissis, M., and Weber, C. (1993), Capability Maturity Model for Software, Version 1.1., Technical Report, CMU/SEI-93-TR-024.
[38] Paulk, M. C., Weber, C., Garcia, S., Chrissis, M., and Bush, M. (1993), Key Practices of the Capability Maturity Model , Version 1.1., Technical Report, CMU/SEI-93-TR-025.
[39] Pedreira, O., Piattini, M., Luaces M. R., and Brisaboa, N. R. (2007), A Systematic Review of Software Process Tailoring, ACM SIGSOFT Software Engineering Notes, Volume 32 Number 3.
[40] Peters, J. F. and Pedrycz, W. (2000), Software Engineering: An Engineering Approach，曾祥信、潘得龍譯 (2004)，「軟體工程」，學貫行銷股份有限公司。
[41] Pfleeger, S. L. (1991), Software Engineering: the Production of Quality Software, Macmillan Publishing Company.
[42] Phan, D. D., Vogel, D. R., and Nunamaker, Jr, J. F. (1995), Empirical Studies in Software Development Projects: Field Survey and OS/400 Study, Information & Management, 28, pp.271-280.
[43] Royce, W. W. (1970), Managing the Development of Large Scale Software Systems, Proceedings of IEEE WESCON, Los Angeles CA: IEEE Computer Society Press, pp.1-9.
[44] Royce, W. (1998), Software Project Management: A Unified Framework, Addison-Wesley.
[45] Rubin, H. (1993), Software Process Maturity: Measuring its Impact on Productivity and Quality, In Proceedings of the International Conference on Software Engineering, pp. 468-476.
[46] Shtub, A. F., Bard, J. F., and Globerson, S. (1994), Project Management: Engineering, Technology and Implementation, Prentice-Hall, Inc..
[47] Sorensen, R. (1995), A Comparison of Software Development Methodologies, CrossTalk 8 (1), The Journal of Defense Software Engineering.
[48] Ulrich, K. T. and Eppinger, S. D. (2003), Product Design and Development, McGraw-Hill.
[49] Weinwurm, G. F. (1974), Estimation of resources for Computer Programming Projects, M. S. thesis, Universirt of North Carolina, Chapel Hill.
[50] Weinberg, M. G.. (1992), Quality Software Management, Volume 1: Systems Thinking, Dorset House Publishing Co., Inc..
[51] Williams, A. and Cockburn, A. (2003), Agile Software Development: It’s about Feedback and Change, IEEE Computer 36 (6) pp.39-43.
[52] Wolverton, R. W. (1974), The Cost of Developing Large-Scale Software, IEEE Transactions On Computers, VOL. C-23, NO. 6, pp.615-636.
[53] Yourdon, E. (1982), Managing the System Life Cycle, Yourdon Press.
[54] Yabuuchi, Y., Kocaoglu, D., and Watada, J. (2006), Analysis of Project Management in Software Development, Technology Management for the Global Future, PICMET Voulme 6, pp2809-2814.

網路部份：
[1] Agile Modeling，”Agile Modeling Throughout the XP Lifecycle”, 2008年12月22日取自網頁http://www.agilemodeling.com/essays/agileModelingXPLifecycle.htm
[2] Norlund, R. (2005)，「將Rational Unified Process與管理成功的規劃集成在一起」，IBM DeveloperWorks，2008年12月22日取自網頁http://www.ibm.com/developerworks/cn/rational/rationaledge/content/aug05/norlund/#IDAOLK1
[3] 中華民國招商網新聞與活動 (2005)，「第三季台灣多項電子產品蟬聯全球第一」，2005年11月9日，取自網頁http://investintaiwan.gov.tw/zh-tw/news/200511/2005110901.html