Software Engineering Chapter 22 Questions and Answers

Document Content and Description Below

Software Engineering Chapter 22 :Exercises Explain why the intangibility of software systems poses special problems for .22.1 .software project management Software cannot be seen or touched. Software ... project managers cannot see progress by looking at the artefact that is being .constructed 22.2. Explain how company size and software size are factors that affect software project management. Company size Small companies can operate with informal management and team communications and do not need formal .policies and management structures .They have less management overhead than larger organizations In larger organizations, management hierarchies, formal reporting .and budgeting, and approval processes must be followed Software size Small systems can be developed by a small team, which can get together in the same room to discuss progress and .other management issues Large systems usually need multiple development teams that may .be geographically distributed and in different companies The project manager has to coordinate the activities of these teams .and arrange for them to communicate with each other Small companies can operate with informal management and team communications and do not need formal policies and management structures. They have less management overhead than larger organizations. In larger organizations, management hierarchies, formal reporting and budgeting, and approval processes must be followed. Small systems can be developed by a small team, which can get together in the same room to discuss progress and other management issues.  Large systems usually need multiple development teams that may be geographically distributed and in different companies. The project manager has to coordinate the activities of these teams and arrange for them to communicate with each other. 22.3. Using reported instances of project problems in the literature, list management difficulties and errors that occurred in these failed programming projects. (I suggest that you start with The Mythical Man Month, as suggested in Further Reading.) The software may be delivered late, cost more than originally .estimated, or fail to meet the expectations of customers 22.4. In addition to the risks shown in Figure 22.1, identify at least six other possible risks that could arise in software projects. The business gets bought out by a competit [Show More]

Last updated: 1 year ago

Preview 1 out of 5 pages