Software Engineering 9th Edition Ian Sommerville - Solutions

Discover comprehensive solutions to the "Software Engineering 9th Edition" by Ian Sommerville with our exclusive online resources. Access the answers key and detailed solutions pdf for each chapter, offering step-by-step answers to all solved problems. Enhance your understanding with the instructor manual, featuring a complete test bank and questions and answers tailored for in-depth learning. Whether you're a student or instructor, our textbook solutions empower you with chapter solutions and a solution manual for effective learning. Enjoy the convenience of a free download to explore these invaluable resources.

The capability maturity model is used by many companies as an incentive to implement new practices. Tha t is, organizations set goals and reward behavior to help them move up from level 1 toward level 5.Wha t kinds of measurable goals can be set for each of the key process a reas? How can these
The people ma turity model assumes that cohesive teams produce better products.Describe how you might test this hypothesis in a fonnal evaluation. How would you measure team cohesion? What crite ria would you use to determine when a product is "better"?
How can we quantitatively assess the maintenance process?
How can we use that assessment to improve the maintenance process?
How do we quantitatively evaluate the effectiveness of any process improveme!llts?
Suppose you are tracking the fau lt density in a series of similar products, so that you can monitor the effectiveness of the new inspection process you introduced. Over time, you find that the fault density decreases. Explain how you might determine whether the falling fault density is the result
Abdel-Hamid's systems dynamics model takes into account the changes in project understanding as the project progresses. What are the pros and cons of capturing assumptions about these changes? How can we test our assumptions, so that we have more confidence in the results of the model?
Explain how systems dynamics might be used to examine the trade-offs between adequate computer security and acceptable system performance.
What are the dangers in assuming that the SEL experience with cleanroom applies to your organization?
Suppose your organization is considering rapid prototyping on its next project. Gordon and Bieman (1995) have catalogued the lessons learned about rapid prototyping from reports in the literature, and the results a re not always clear. How would you design a process to introduce rapid prototyping,
The president of your company has learned about ISO 9000 and insists that the company become certified. She wants quantitative evidence that ISO 9000 has improved the company's processes and products. How would you measure the effect of ISO 9CXXJ certification?
Should software engineers be licensed or certified the way many other professional engineers are? Can a software engineer's performance be evaluated in an objective, quantitative way? How do licensing issues relate to the issues introduced in this chapter?
3: What patterns and tactics can you discern in the portions of the architecture shown in Figures 13.4, 13.5 and 13.7?
2: The Web did not have performance as one of its early quality goals, which is unusual for a successful system. Why do you think the system was successful anyway? What, if anything, does this say about the future of computing?
1: We have identified a number of qualities that made the WWW successful: interoperability, portability, remote access, extensibility, and scalability. Which of these do you think contributed most substantially to the Web's success? If any of these qualities had been sacrificed, would the Web still
2: Determination of costs and benefits is fraught with uncertainty. What sources of uncertainty do you typically have to deal with and how would you go about characterizing, measuring, and minimizing them?
1: One of the novel aspects of the CBAM is the creation of utility-response curves. Consider the curve styles shown in Figure 12.2. What are the circumstances under which you can imagine each of those curves elicited from the stakeholders? What situations does each of these curves represent?
1: Think of an important software system in your organization. Could you present the business drivers or discuss the architecture using the template given in this chapter? If not, what information is missing? Could you sketch a utility tree for the system?
4: Chapter 6 described a code template used to provide a consistent approach to high availability across the ISSS air traffic control system. Suppose you wanted to confirm that developers and maintainers had remained faithful to this template over the lifetime of the system. Describe the
3: For each use of reconstruction mentioned in Section 10.1, specify the architectural views you would want to reconstruct.
2: Suppose you believed that the architecture for a system followed a shared repository style. What information would you want to extract from the source code to confirm or refute this hypothesis?
1: Suppose you believed that the architecture for a system was layered. What information would you want to extract from the source code to confirm or refute this hypothesis?
Explain the Graphical representation of elements and relationships
What documentation would you need to do performance analysis?
You are a new hire to a project. Lay out a sequence of documentation you would like to have to acquaint you with your new position.
What views from this chapter are pertinent to a system you are currently working on? What views have you documented? Why is there a difference?
How does the use of a skeletal system restrict the designer? How is this beneficial and how is it detrimental?
The data and control flow constraints on subsystem controllers and controller children are very stringent. As a designer and implementor, do you think you would welcome these constraints or find them too restrictive?
The strong relationship between the structure of the system being simulated and the structure of the simulating software is one of the things that makes the Structural Modeling pattern so flexible with respect to mirroring the modeled system in the event of change, extension, or contraction.
How does ADD compare to an ad hoc approach to design in terms of the outputs and the time and resources required to run the method? When would ADD be appropriate and when would ad hoc design be appropriate?
What other techniques can you think of for creating an initial version of a software or system architecture. How do these techniques address functional, business, and quality attribute requirements?
ADD provides one method for "chunking" requirements. Architectural drivers are satisfied and other requirements have to be satisfied in the context of the design developed for the drivers. What other chunking methods are there for a decomposition design strategy? Why can't all requirements be
Architectures beget the teams that build the modules that compose the architectures. The architectural structure usually reflected in the teams is modular decomposition. What would be the advantages and disadvantages of basing teams around components of some of the other common architectural
Construct quality attribute scenarios, as described in Chapter 4, for as many of the requirements given in Section 6.2 as you can. Where necessary information is missing, propose reasonable substitutions
How many architectural patterns can you recognize in the architecture for ISSS?
High availability was a main impetus behind the architecture presented in this chapter. How were other quality attributes, such as performance, affected by this requirement? How might the architecture change if this requirement were removed?
Usability is not always given due consideration in architecture design, making usability system goals often difficult to achieve because they are treated as an afterthought. Think of a system where you are familiar with the architecture and try to enumerate the usability tactics, if any, it has
Given the set of tactics you chose in question 1, what tradeoffs with other quality attributes might you expect from using them (such as security, availability, and modifiability)?
As in question 3 from Chapter 4, consider a widely used Web site, such as Amazon or eBay. What tactics would you need to consider when choosing the architectural patterns or architectural strategies for meeting the performance requirements you enumerated in that question?
Suppose that monitors were added to ensure that correct values were being stored in the Data Banker and computed by the Function Drivers. If the monitors detected a disparity between the stored or computed values and what they computed as the correct values, they would signal an error. Show how
Chapter 7 will discuss using the architecture as a basis for incremental development: starting small and growing the system but having a working subset at all times. Propose the smallest subset of the A-7E software that still does something (correctly, in accordance with requirements) observable by
Suppose that a version of the A-7E software were to be developed for installation on a flight trainer version of the aircraft. This aircraft would carry no weapons, but it would teach pilots how to navigate using the onboard avionics. What structures of the architecture would have to change, and
26.10. Do you think that process improvement programs, which involve measuring the work of people in the process and introducing changes into that process, can be inherently dehumanizing? What resistance to a process improvement program might arise and why?
26.9. What are the advantages and disadvantages of using a process maturity model that focuses on goals to be achieved, rather than good practices to be introduced?
26.8. Under what circumstances would you recommend the use of the staged representation of the CMMI?
26.7. Give two advantages and two disadvantages of the approach to process assessment and improvement that is embodied in the process improvement frameworks such as the CMMI.
26.6. Design a process for assessing and prioritizing process change proposals. Document this process as a process model showing the roles involved in this process. You should use UML activity diagrams or BPMN to describe the process.
26.5. Describe three types of software process metric that may be collected as part of a process improvement process. Give one example of each type of metric.
26.4. Assume that the goal of process improvement in an organization is to increase the number of reusable components that are produced during development. Suggest three questions in the GQM paradigm that this might lead to.
26.3. Suggest three specialized software tools that might be developed to support a process improvement program in an organization.
26.2. Under what circumstances is product quality likely to be determined by the quality of the development team? Give examples of the types of software product that are particularly dependent on individual talent and ability.
26.1. What are the important differences between the agile approach and the process maturity approach to software process improvement?
have been introduced to the ideas of process capability and process maturity, and the general form of the SEI’s CMMI model for process improvement.
know how the Goal-Question-Metric approach may be used to guide process measurement;
understand the principles of software process improvement and the cyclic process improvement process;
understand the rationale for software process improvement as a means of improving both product quality and the efficiency and effectiveness of software processes;
25.10. Describe five factors that should be taken into account by engineers during the process of building a release of a large software system.
25.9. A common problem with system building occurs when physical file names are incorporated in system code and the file structure implied in these names differs from that of the target machine. Write a set of programmer’s guidelines that helps avoid this and any other systembuilding problems
25.8. With reference to system building, explain why you may sometimes have to maintain obsolete computers on which large software systems were developed.
25.7. Describe the difficulties that may arise when building a system from its components. What particular problems might occur when a system is built on a host computer for some target machine?
25.6. Software is increasingly being developed by teams where the team members are working at different locations. Suggest features in a version management system that may be required to support this distributed software development.
25.5. Imagine a situation where two developers are simultaneously modifying three different software components. What difficulties might arise when they try to merge the changes that they have made?
25.4. Explain why it is essential that every version of a component should be uniquely identified.Comment on the problems of using a version identification scheme that is simply based on version numbers.
25.3. Describe six essential features that should be included in a tool to support change management processes.
25.2. What are the benefits of using a change request form as the central document in the change management process?
25.1. Suggest five possible problems that could arise if a company does not develop effective configuration management policies and processes.
understand the differences between a system version and a system release, and know the stages in the release management process.
know the essential functionality that must be provided by a version management system, and the relationships between version management and system building;
understand the processes and procedures involved in software change management;
24.10. A colleague who is a very good programmer produces software with a low number of defects but consistently ignores organizational quality standards. How should her managers react to this behavior?
24.9. Explain why it is difficult to validate the relationships between internal product attributes, such as cyclomatic complexity and external attributes, such as maintainability.
24.8. Explain why design metrics are, by themselves, an inadequate method of predicting design quality.
24.7. Explain why program inspections are an effective technique for discovering errors in a program. What types of error are unlikely to be discovered through inspections?
24.6. Assume you work for an organization that develops database products for individuals and small businesses. This organization is interested in quantifying its software development.Write a report suggesting appropriate metrics and suggest how these can be collected.
24.5. Briefly describe possible standards that might be used for:• The use of control constructs in C, C#, or Java;• Reports which might be submitted for a term project in a university;• The process of making and approving program changes (see Chapter 26);• The process of purchasing and
24.4. Design an electronic form that may be used to record review comments and which could be used to electronically mail comments to reviewers.
24.3. Discuss the assessment of software quality according to the quality attributes shown in Figure 24.2. You should consider each attribute in turn and explain how it might be assessed.
24.2. Explain how standards may be used to capture organizational wisdom about effective methods of software development. Suggest four types of knowledge that might be captured in organizational standards.
24.1. Explain why a high-quality software process should lead to high-quality software products.Discuss possible problems with this system of quality management.
understand how measurement may be helpful in assessing some software quality attributes and the current limitations of software measurement.
understand how reviews and inspections are used as a mechanism for software quality assurance;
be aware of the importance of standards in the quality management process and know how standards are used in quality assurance;
understand that software quality is affected by the software development process used;
have been introduced to the quality management process and know why quality planning is important;
23.10. Is it ethical for a company to quote a low price for a software contract knowing that the requirements are ambiguous and that they can charge a high price for subsequent changes requested by the customer?
23.9. Some very large software projects involve writing millions of lines of code. Explain why the effort estimation models, such as COCOMO, might not work well when applied to very large systems.
23.8. A software manager is in charge of the development of a safety-critical software system, which is designed to control a radiotherapy machine to treat patients suffering from cancer. This system is embedded in the machine and must run on a special-purpose processor with a fixed amount of
23.7. The XP planning game is based around the notion of planning to implement the stories that represent the system requirements. Explain the potential problems with this approach when software has high performance or dependability requirements.
23.6. Figure 23.14 shows the task durations for software project activities. Assume that a serious, unanticipated setback occurs and instead of taking 10 days, task T5 takes 40 days. Draw up new bar charts showing how the project might be reorganized.
23.5. Figure 23.14 sets out a number of tasks, their durations, and their dependencies. Draw a bar chart showing the project schedule.
23.4. Cost estimates are inherently risky, irrespective of the estimation technique used. Suggest four ways in which the risk in a cost estimate can be reduced.
23.3. Briefly explain the purpose of each of the sections in a software project plan.
23.2. Explain why the process of project planning is iterative and why a plan must be continually reviewed during a software project.
23.1. Under what circumstances might a company justifiably charge a much higher price for a software system than the software cost estimate plus a reasonable profit margin?
understand how the COCOMO II model can be used for algorithmic cost estimation.
have been introduced to the ‘planning game’, which is used to support project planning in extreme programming;
understand what is involved in project scheduling and the use of bar charts to present a project schedule;
know what sections should be included in a project plan that is created within a plan-driven development process;
understand the fundamentals of software costing and reasons why the price of the software may not be directly related to its development cost;
22.10. As a programmer, you are offered promotion to a project management position but you feel that you can make a more effective contribution in a technical rather than a managerial role.Discuss whether you should accept the promotion.

Showing 1400 - 1500 of 3990

First
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
Last

Software Engineering 9th Edition Ian Sommerville - Solutions

Step by Step Answers