A Study on Improving the Embedded Software Process Model - an Example of a Wireless Local Area Network ODM Company
碩士 === 國立清華大學 === 工業工程與工程管理學系 === 97 === 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...
| Main Authors: | , |
|---|---|
| Other Authors: | |
| Format: | Others |
| Language: | zh-TW |
| Published: |
2009
|
| Online Access: | http://ndltd.ncl.edu.tw/handle/42525498102155092190 |
| Summary: | 碩士 === 國立清華大學 === 工業工程與工程管理學系 === 97 === 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.
|
|---|