1 |
Requirements Management of Software Development in CMMI / 以CMMI為基礎提升軟體開發需求管理蘇毓婷, Su, Yu-Ting Unknown Date (has links)
在軟體開發的過程中,有效的需求管理能促成高品質的軟體及管理。在CMMI中與需求管理有關的議題包括需求發展(Requirements Development)流程領域-屬於CMMI成熟度第三級,提供一些目標、執行方法(practices)和相關資訊作為指引,協助開發團隊發展顧客需求和產品需求。另一個相關議題-需求管理(Requirements Management) 流程領域,屬於CMMI成熟度第二級,可用於幫助需求管理的規劃與控制,建立追蹤機制,以及評估改變衝擊。
本篇論文以達成CMMI中需求發展和需求管理流程領域目標為前提,利用概念形成(Concept Formulation)和系統展示(System Representation)研究方法,並調適RUP中的需求工作流程(workflow),最後發展出一個整合的需求管理架構-稱為IREQM(Integrated Requirements Management),用於處理需求面的問題。本研究亦根據IREQM架構進行實作,發展出一套可協助軟體需求發展與管理的支援系統。最後,我們利用自我評鑑表,評估IREQM及依據IREQM實作的雛型系統與CMMI目標和執行方法相符的程度。 / Effective requirements management can help the software development process to ensure a high-quality software development and management process. In CMMI, the process area RD (Requirements Development) provides a set of goals, practices, and related features to develop customer and product requirements, and the process area REQM (Requirements Management) is to help establishing and appraising the quality of requirements management. Both issues are covered by the generic requirement management concerns.
This study is conducted by the Concept Formulation and System Representation method to develop a systematic process to deal with the requirements issues in the software development process, in order to meet the RD and REQM goals in CMMI. The study proposes an integrated requirement management framework, called IREQM, tailored from the requirements workflow in RUP. A CMMI support system, to implement IREQM is established to facilitate the REQM and RD activities during the software development process. Finally, a self-appraisal checklist is used to evaluate the compliance of the IREQM framework and its implementation to the CMMI model.
|
2 |
系統功能演化之需求分析方法論 / Requirements Analysis Methodology for System Functional Evolution劉季綸, Liu, Chi-Lun Unknown Date (has links)
在重視集體智慧、重視服務、且需要因應環境快速變遷的年代,傳統的系統開發方法論雖然有其不可磨滅的價值,但已經顯露出其不足之處。為了順應時代的潮流,方法論必須指引企業去聆聽大眾的心聲,以期確保系統提供優質的服務,方法論也必須指引資訊人員運用有異於以往的手法與步驟,與其他部門和大眾共同合作,來持續不斷地維護系統,使得系統得以注入新的生命力而不斷演進。
為了提出一套不斷吸納使用者的新需求來規劃系統演進的功能需求分析方法論,本研究以哲學詮釋學為基礎,並佐以軟體工程相關文獻,將持續吸納新需求來促進系統演進的抽象概念,化為具體可執行的步驟。本需求分析方法論是針對使用者提議的需求進行初步分析與確認,可分為兩個主要部分:需求形成流程、與衝突處理流程。需求形成流程是分析使用者所提出之功能性需求的主要方式,其中包含了提出新需求、分析新需求在商業活動與科技層次的影響、估計新需求的成本效益來決定是否實作、排序實作的優先權、並且了解新功能的釋出時間的期望。而衝突解決流程是為了解決各方人馬的歧見所造成的爭端,衝突解決的方式包含了自行協商、第三方中間人介入協調、以及高層決策小組的裁決。
為了讓企業外界的大眾提議新需求,本研究發展了一套以部落格為基礎的新需求提議工具,讓網友可在部落格上提出自己對新功能的想法。此外,為了協助企業判斷新需求是否會觸發衝突解決流程,本研究根據哲學詮釋學,將使用案例(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.
|
Page generated in 0.0319 seconds