李彤《软件工程》教学课件ch7.pptVIP

Ethnography and prototyping 报告会 Scope of ethnography Requirements that are derived from the way that people actually work rather than the way in which process definitions suggest that they ought to work. Requirements that are derived from cooperation and awareness (知道) of other people’s activities. 7.3 Requirements validation Concerned with demonstrating that the requirements define the system that the customer really wants. Requirements error costs are high so validation is very important Fixing a requirements error after delivery may cost up to 100 times the cost of fixing an implementation error. Requirements checking Validity. Does the system provide the functions which best support the customer’s needs? Consistency. Are there any requirements conflicts? Completeness. Are all functions required by the customer included? Realism. Can the requirements be implemented given available budget and technology Verifiability. Can the requirements be checked? Requirements validation techniques Requirements reviews Systematic manual analysis of the requirements. Prototyping Using an executable model of the system to check requirements. Covered in Chapter 17. Test-case generation Developing tests for requirements to check testability. Requirements reviews Regular reviews should be held while the requirements definition is being formulated. Both client and contractor staff should be involved in reviews. Reviews may be formal (with completed documents) or informal. Good communications between developers, customers and users can resolve problems at an early stage. Review checks Verifiability. Is the requirement realistically testable? Comprehensibility. Is the requirement properly understood? Traceability. Is the origin of the requirement clearly stated? Adaptability. Can the requirement be changed without a large impact on other requirements? 7.4 Requirements management Requirements management is the process of managing changing requirements during the requirements engineerin