教程需求分析re requirements-problem_第1頁
教程需求分析re requirements-problem_第2頁
教程需求分析re requirements-problem_第3頁
教程需求分析re requirements-problem_第4頁
教程需求分析re requirements-problem_第5頁
免費預覽已結束,剩余9頁可下載查看

下載本文檔

版權說明:本文檔由用戶提供并上傳,收益歸屬內容提供方,若內容存在侵權,請進行舉報或認領

文檔簡介

1、Chapter 1:The Requirements ProblemObjectivesTo define the goal of software developmentTo describe the root causes of software project success and failureTo illustrate the high cost of requirements errorsThe Goal of Software DevelopmentTo develop quality software on time and on budget that meets cust

2、omers real needs. A Look at the Data A study by the Standish Group 1994 reported:In the United States, $250 billion spent each year on IT application development of approximately 175,000 projects. 31% of projects will be canceled before they ever get completed. 52.7% of projects will cost 189% of th

3、eir original estimates.The Root Causes of Project Success and Failure The Standish Group survey also asked respondents to identify the most significant factors that contributed to projects that were rated “Success”“Challenged” (late and did not meet expectations)“Impaired” (canceled)Factors that Cau

4、sed Projects to be “ChallengedThe 1994 Standish Group study noted the three most commonly cited factors that caused projects to be challenged:Lack of user input: 13 percent of all projects plete requirements and specifications: 12 percent of all projectsChanging requirements and specifications: 12 p

5、ercent of all projectsIt appears that at least a third of development projects run into trouble for reasons that are directly related to requirements gathering, requirements documentation, and requirements management. Factors that Caused Projects to be “SuccessAccording to the Standish study, the th

6、ree most important success factors wereUser involvement: 16 percent of all successful projectsExecutive management support: 14 percent of all successful projectsClear statement of requirements: 12 percent of all successful projectsLargest Software Development Problems by Category The two largest pro

7、blems, appearing in about half the responses, wereRequirements specificationsManaging customer requirementsSurvey conducted by European Software Process Improvement Training Initiative (ESPITI) 1995, 3,800 responsesThe High Cost of Requirements Errors The High Cost of Requirements Errors (Contd)The

8、errors discovered during the design of a development project could fall into one of two categories: Errors that occurred when the development staff created a technical design from a correct set of requirements, or Errors that should have been detected as requirements errors somewhat earlier in the p

9、rocess but that somehow leaked into the design phase of the project. Its the second category of errors that turn out to be particularly expensive, for two reasons (see the next slide).The High Cost of Requirements Errors (Contd)By the time the requirements-oriented error is discovered, the developme

10、nt group will have invested time and effort in building a design from those erroneous requirements. As a result, the design will probably have to be thrown away or reworked.The true nature of the error may be disguised; everyone assumes that theyre looking for design errors during the testing or ins

11、pection activities that take place during this phase, and considerable time and effort may be wasted until someone says, Wait a minute! This isnt a design mistake after all; weve got the wrong requirements.The High Cost of Requirements Errors (Contd)In order to repair a defect, we are likely to expe

12、rience costs in some or all of the following areas:Re-specification.Redesign.Recoding.Retesting.Change orders.Corrective actionundoing whatever damage may have been done. Scrap code and design that are based on incorrect requirements.Recall of defective versions of softwareWarranty costs.Product lia

13、bilityif the customer sues for damages caused by the defective software.Service costs for a company representative to visit a customers field location to reinstall the new software.Improved Project PerformanceThe Standish Groups CHAOS studies show improvements in IT projects in the past decade.*The Standish Group, “Latest Standish Group CHAOS Report Shows Project Success Rates Have Improved by 50%” (March 25, 2003).Key pointsThe goal of software development is to develop quality software on time and on budget that meets customers real needs.Project success depends on effective r

溫馨提示

  • 1. 本站所有資源如無特殊說明,都需要本地電腦安裝OFFICE2007和PDF閱讀器。圖紙軟件為CAD,CAXA,PROE,UG,SolidWorks等.壓縮文件請下載最新的WinRAR軟件解壓。
  • 2. 本站的文檔不包含任何第三方提供的附件圖紙等,如果需要附件,請聯系上傳者。文件的所有權益歸上傳用戶所有。
  • 3. 本站RAR壓縮包中若帶圖紙,網頁內容里面會有圖紙預覽,若沒有圖紙預覽就沒有圖紙。
  • 4. 未經權益所有人同意不得將文件中的內容挪作商業或盈利用途。
  • 5. 人人文庫網僅提供信息存儲空間,僅對用戶上傳內容的表現方式做保護處理,對用戶上傳分享的文檔內容本身不做任何修改或編輯,并不能對任何下載內容負責。
  • 6. 下載文件中如有侵權或不適當內容,請與我們聯系,我們立即糾正。
  • 7. 本站不保證下載資源的準確性、安全性和完整性, 同時也不承擔用戶因使用這些下載資源對自己和他人造成任何形式的傷害或損失。

評論

0/150

提交評論