软件工程课后习题答案Word文档下载推荐.docx

1、 （2） the way people communicate （cell phones）; （3） methods of warfare （cyberweapons）; （4） the diagnosis of diseases （MRIs and related computer-based diagnostic devices）, and （5） the manner in which people acquire and enjoy media （music, DVDs, etc.）.1.6） The Law of Conservation of Familiarity: As the

2、 system evolves the users engineers, developers all those associated must have the complete knowledge of the content and behavior to achieve satisfactory results. Increase in growth may diminish that knowledge （mastery）; hence the average increase in growth remains invariant as the system evolves.1.

3、7） Many modern applications change frequently before they are presented to the end user and then after the first versions have been used. A few ways to build software to stop deterioration due to change would be: Make sure that software is designed so that changes in one part of a program do not cre

4、ate side-effects in another part of the program. Make sure that software is designed so that it does not depend on external devices or systems that are likely to change with time. Make sure test cases and results are archived and available so that the software can be retested when changes are made.

5、Make sure you spend time understanding what the customer wants.1.8） The two broadest categories encompass risks associated with economic loss and risks to the well being of people. It might be a good idea to select five risks （culled from the sources noted） and present them to the class. Look for hu

6、morous as well as serious risks.1.9） The same approach to software engineering can be applied for each of the six categories, but it must be adapted to accommodate the special requirements of each category. 1.10） There are literally dozens of real life circumstances to choose from. For example, soft

7、ware errors that have caused major telephone networks to fail, failures in avionics that have contributed to plane crashes, computer viruses （e.g., Michelangelo） that have caused significant economic losses and attacks on major e-commerce sites.1.11） The Law of Declining Quality: The quality of syst

8、ems will decline unless they are maintained by various procedures to adapt to the environmental changes. This concept is similar to the “deterioration” discussed in Problem 1-5.1.12） The Law of Conservation of Organizational Stability: The average effective global activity rate is invariant over the

9、 lifetime of a product.Chapter 22.1）Pattern: CommunicationIntent: To establish a collaborative relationship with the customer in an effort to define project scope, business requirements and other project constraints.” Type: Stage patternInitial context: （1） Appropriate stakeholders have been identif

10、ied and are willing to participate in communication （2） Stakeholders agree that a problem exists and that software may provide a solution Problem: Requirements must be elicited from stakeholders and organized in a way that can be used by software engineers. All stakeholders must collaborate to defin

11、e requirements and to identify those areas where requirements are uncertain.Solution: Each stakeholder must develop a description of the functions, features, information and behavior that are exhibited by the software. To accomplish this, a structured, facilitated meeting is conducted. For more deta

12、ils, see Sections 7.3, 7.4 and 7.5.Resulting Context: When this pattern has been successfully completed, basic information required for the development of an analysis model has been acquired and documented in some manner. Use-cases （user scenarios） have been developed, along with basic descriptions

13、of system function and behavior and the data objects that are to be manipulated and/or produced/Related Patterns: Conducted a meeting; requirement gathering; developing use-cases; building a mini-spec; negotiating requirements, prioritization. Known Uses/Examples: Communication is mandatory at the b

14、eginning of every software project; is recommended throughout the software project; and is mandatory once the deployment activity is underway.2.2） Process assessment examines the software process used by an organization to determine whether it is effective in achieving software engineering goals. The assessment characterizes the current practice within an organizational unit in terms of the capability of the selected processes. The SPICE （ISO/IEC15504） standar