目前資訊系統之建置多為求速成而以採購所謂解決方案的套裝系統或元件拼裝為主，雖然此舉帶來軟體再用效益使建置成本降低但由於實施過程抽象化不足使得欲讓系統適應用戶環境時客製化困難且各套裝系統詞彙標準不一也造成資料整合時語意混淆，導致空有外殼讓系統與組織扞格不入而無法帶來實質效益。本研究所提之系統發展方法即是為解決上述情況以本體論為概念描述基礎分從靜態資料觀點、動態流程觀點及資訊技術觀點出發進而彙整發展具彈性與再用性之資訊系統。 本研究過程是植基於設計科學的系統發展研究方法論，將資訊系統開發流程分為五個階段，並根據設計科學的定義，驗證研究結果的四項產出：構件、模型、方法與實例，希從學術的嚴謹面提昇產出結果的品質。並藉著探討分析運用本研究之發展方法建置出的個案，其所得到之結果足以供後繼者建置或改善知識管理相關系統做參考。 / In these few decades, many organizations pursued of e-Solutions by selecting so-call off-the-shelf packages or mixed 3rd party components to promote the reusing value and reduce the cost of implementation. However, there is no single solution suitable for all types of organization and customized or hybrid system must be inevitable to face the consistency problem. We believe the proper abstraction and ontological commitment can help in these situations. From this point of view, we propose the information system development methodology which is aiming to implement the flexible and reusable ontology driven information system from the view of static domain data, dynamic workflow and abstract technology. In this study, we conduct the system development research methodology based on design science. In order to easily note, we divide the research process into five stages. According to the criteria of design science, we will examine the research results: constructs, models, methods and instantiations for consolidating the quality of research outputs. Besides, we will show the cases which are implemented by proposed methodology for further study and suggestion of improving present system development issues.

在重視集體智慧、重視服務、且需要因應環境快速變遷的年代，傳統的系統開發方法論雖然有其不可磨滅的價值，但已經顯露出其不足之處。為了順應時代的潮流，方法論必須指引企業去聆聽大眾的心聲，以期確保系統提供優質的服務，方法論也必須指引資訊人員運用有異於以往的手法與步驟，與其他部門和大眾共同合作，來持續不斷地維護系統，使得系統得以注入新的生命力而不斷演進。 為了提出一套不斷吸納使用者的新需求來規劃系統演進的功能需求分析方法論，本研究以哲學詮釋學為基礎，並佐以軟體工程相關文獻，將持續吸納新需求來促進系統演進的抽象概念，化為具體可執行的步驟。本需求分析方法論是針對使用者提議的需求進行初步分析與確認，可分為兩個主要部分：需求形成流程、與衝突處理流程。需求形成流程是分析使用者所提出之功能性需求的主要方式，其中包含了提出新需求、分析新需求在商業活動與科技層次的影響、估計新需求的成本效益來決定是否實作、排序實作的優先權、並且了解新功能的釋出時間的期望。而衝突解決流程是為了解決各方人馬的歧見所造成的爭端，衝突解決的方式包含了自行協商、第三方中間人介入協調、以及高層決策小組的裁決。 為了讓企業外界的大眾提議新需求，本研究發展了一套以部落格為基礎的新需求提議工具，讓網友可在部落格上提出自己對新功能的想法。此外，為了協助企業判斷新需求是否會觸發衝突解決流程，本研究根據哲學詮釋學，將使用案例（Use cases）加以延伸修改，提出一套後設模型，並輔以知識本體，據此來提出一套規則，讓本工具能自動偵測新需求與系統既有設計之間是否有所抵觸，而規則亦可進一步應用在新需求間的衝突上。 為了初步瞭解本研究所提之方法論與工具的優缺點，本研究與中時電子報和民視購物網合作，來試用此方法論與工具。透過試用之後的訪談得知，本方法論與工具有其價值，而也獲得了不少寶貴的試用意見。最後，本研究根據試用的諸多意見，對方法論與工具的改善上，提出了具體的改良作法與方向。 / Nowadays, companies have to respect collective knowledge and improve service quality for adapt their rapidly changing environment. Traditional systems development methodologies may be still valuable but have shortcomings. To accommodate customer-driven trend, new methodologies must guide enterprises to listen to customers for ensuring high-quality system services. New methodologies also have to guide developers to carry out cross-department and customer-centered collaboration in new ways for maintaining systems cyclically. This research proposes a user requirements analysis methodology according on philosophical hermeneutics and software engineering literature. The proposed methodology includes requirements formation and conflict resolution. Requirements formation process involves new user requirement proposition, commercial and technical impact analysis, cost benefit estimation, coding prioritization, and new version release scheduling. Conflict resolution process involves negotiation, mediation, and arbitration. Besides the proposed methodology, this research also develops a blog-based tool for collecting user requirements on Internet. This research extends and modifies use cases diagram and use philosophical hermeneutics as a foundation to propose a meta-model. This research also proposes a set of rules for conflict detection. Base on the proposed meta-model, ontologies, and the proposed rules, the blog-based tool can automatically detect conflicts between new requirements and existing design. These proposed rules also can apply to detect conflicts among new requirements. An online newspaper company and an online shopping mall try to use this methodology and the blog-based tool. In the interviews, they confirm this methodology’s and tool’s values and give several suggestions for improving the methodology and the tool. Finally, this research discusses the improvements and future research directions according to these suggestions.

90年代的後期，敏捷式系統發展方法開始被倡導。相對於傳統的系統發展方法，敏捷式系統發展方法著重於回饋機制而非事前的計畫、以人為中心而非以流程為中心。這樣的方法希望能助於提高組織對回應市場、客戶的效率，進而提高效益。目前在商場中使用此方法做為開發工具的企業仍是少數，本研究希望透過探討敏捷式系統發展方法論的使用時機來進行教學，進而得知系統開發人員對於接受敏捷式系統發展方法的關鍵因素，並藉此了解該如何在企業中導入此方法。本研究發現除了使用此方法的能力會影響影響使用意圖之外，在內在因素方面也包含了公司結構與團隊因素，外部因素則包含了顧客與成功案例因素，這些都是接受敏捷式系統發展方法的關鍵因素。本研究希望根據以上的分析結果，提出敏捷式系統發展方法導入之建議，提供組織做為參考用。 / Awareness of agile system development methodologies (SDM) has grown among information systems development community in recent years. Many of their advocates consider the agile and the plan-driven SDMs polar opposites. Indeed there are circumstances where agile SDMs are more suitable than plan-driven SDMs. Yet, there have been few studies on understanding developers’ adoption intention. This paper takes an initial attempt to gauge new generation of software developers’ intention to select agile SDMs. To many of these developers, agile SDMs are relatively new if not unheard of, in order to assess their intention to choose such category of methodologies, this research first introduced the methodologies to a group of 21 IS-major graduate students and discussed how and when to use agile SDMs. Then a survey was conducted, which was comprised of two parts of questions: agile SDM self-efficacy and intention to use. PLS analysis results showed that agile SDM self-efficacy influence the intention to use through performance outcome expectation, personal outcome expectation, and affect. Although the relationship between self-efficacy and anxiety was not confirmed, anxiety does affect intention to use. The fact that direct relationships between all four emotive variables and the intention to use are established implies that in order to encourage the use of agile SDMs, the focus should be emotive variables, and that self efficacy may be just one of various ways to promote the favorable emotional states. In addition, these participates were invited to a three-round Delphi test and analytic hierarchy process to retrieved their concerns about accepting or rejecting agile SDMs. Ten key factors were extracted and categorized. Adding up the pros and cons, team dimension is the most important dimension, which explains individual first concerns about how the collaboration when using agile SDMs. Other than team dimension, customer, corporate structure, project, success cases and methodology dimensions were consistent with the literatures. Thus our study provides a critical understanding of the factors that affect new generation of software developers’ intention to select agile SDM.