软件需求-中职.pptVIP

Requirements Engineering Du Yugen ygdu@sei.ecnu.edu.cn Objectives After completing this unit, you should be able to know: Requirements Engineering Requirements Engineering Tasks Requirements Management Traceability Tables Initiating Requirements Engineering Process Eliciting Requirements Elicitation Work Products Developing Use-Cases Analysis Model Negotiating Requirements Requirement Review (Validation) Requirements Engineering需求工程 Inception—Establish a basic understanding of the problem and the nature of the solution. Elicitation—Draw out the requirements from stakeholders. Elaboration—Create an analysis model that represents information, functional, and behavioral aspects of the requirements. Negotiation—Agree on a deliverable system that is realistic for developers and customers. Specification—Describe the requirements formally or informally. Validation—Review the requirement specification for errors, ambiguities, omissions, and conflicts. Requirements management—Manage changing requirements. Inception先启阶段 Ask “context-free” questions Who is behind the request for this work? Who will use the solution (product/system)? What will be the economic benefits? How would you characterize “good” output from the system? What problems does this solution address? What environment will the product be used in? Are you the right person to answer these questions? Are these question relevant? Can anyone else provide additional information? Should I be asking you anything else? Getting Requirements Right “The hardest single part of building a software system is deciding what to build. No part of the work so cripples the resulting system if done wrong. No other part is more difficult to rectify later.” —Fred Brooks “The seeds of major software disasters are usually sown within the first three months of commencing the software project.” —Capers Jones “We spend a lot of time—the majority of project effort—not implementing or testing, but trying to decide what to