有效需求分析

內(nèi)容概要

本書(shū)從管理和技術(shù)兩個(gè)角度，以案例方式闡述了軟件項(xiàng)目中與需求分析相關(guān)的各種問(wèn)題，力圖讓讀者能夠?qū)π枨蠓治龅目蚣荏w系和過(guò)程形成較為清晰的認(rèn)識(shí)，在實(shí)踐中準(zhǔn)確了解客戶(hù)的業(yè)務(wù)需求，正確調(diào)配各種資源，更加準(zhǔn)確地把握項(xiàng)目的方向，保證整個(gè)項(xiàng)目的成功。    本書(shū)內(nèi)容豐富翔實(shí)，實(shí)用性強(qiáng)，適合作為高等學(xué)校本科生和研究生的軟件工程類(lèi)教材，同時(shí)也可供軟件企業(yè)對(duì)開(kāi)發(fā)和項(xiàng)目管理人員進(jìn)行培訓(xùn)使用。

書(shū)籍目錄

List of Figures xiForeword xvPreface xviiAcknowledgments xxiiiPART I BACKGROUD   CHAPTER 1 INTRODUCTION     The State of the Industry Today     The Need to Use Effective Requirements Practices     The Requiements Process      What Is a Process?      What Is the Requirements Process?    Benefits of a Process Approach    Pitfalls of Using a Process Approach    About This Book      Roles      Key Terms      A Requirements Taxonomy      Systems and Software Engineers      Intended Audience      Reconnemded Mind-set for Readers of This Book      The"Team,"the "Project,"and the "Project Manager"      Footnotes in This Book      Key References and Suggested Readings    Upcoming Topics    Summary    Key References and Suggested ReadingsPART II RECOMMENDED REQUIREMENTS PRACTICES   CHAPTEFR 2 COMMIT TO THE APPROACH    What Do We Mean by Commitment?    How Can Commitment Be Attainde and Maintained?    Recommendations to Assist in Evolving the Partnering Approach      Involve Managers with Authority in the Partnering Workshop      Develop a Requirements Plan      Utilize a Set of Mechahisms,Methods ,Techniques,and Tools      Work Toward a Quality Culture    Summary    Key References and Suggested Readings  CHAPTER 3 ESTABLISH AND UTILIZE A JOINT TEAM RESPONSIBLE FOR THE REQUIREMENTS    What Is a"Joint Team"    What Doea the Joint Team Do?    How Is the Joint Team Created?    Who Should Be on the Joint Team?    How Often Should the Joint Team Meet?    What Metrics Need to Be Created and Tracked?    Calculating Return on Investment (ROI)from Uding Effective Requirements Practices    Customer and Supplier Roles    Summary    Key References and Suggested Readings  CHAPTER 4 DEFINE THE REAL CUSTOMER NEEDS    Recommendations to Facilitate Getting to the Real Requirements      Invest More in the Requirements Process      Train PMs to Pay More Attention to the Requirements Process      Identify a Project Champion      Define the Project Vision and Scope      Identify a Requirements Engineer and Utilize Domain Experts to Perform        Requirements Engineerng Tasks      Train Developers Not to Make Requirements Decisions and Not to Gold Plate      Utilize a Variety of Techniques to Elicit to Elicit Customer and User Requirements and Expectations        Use Cases      Train Requirements Engineers to Write Good Requirements         The Impact of Requirements Errors        The Importance of Requirements to Program Costs        What Is a Good Requirement?      Document the Rationale for Each Requirement      Utilize Methods and Automated  Tools to Analyze,Prioritize,and Track Requirements      Collect Requirements from Multiple Viewpoints      Consider the Use of Formal Methods When Appropriate    Pitfalls    Summary    Key REFERENCES AND suggested Readings  ……PART III WHAT TO DO NEXT EpilogueList of AcronymsGlossaryCreditsBibliographyAuthor IndexSubject Index

圖書(shū)封面

圖書(shū)標(biāo)簽Tags

無(wú)

評(píng)論、評(píng)分、閱讀與下載

---

    有效需求分析 PDF格式下載

---