New Semester
Started
Get
50% OFF
Study Help!
--h --m --s
Claim Now
Question Answers
Textbooks
Find textbooks, questions and answers
Oops, something went wrong!
Change your search query and then try again
S
Books
FREE
Study Help
Expert Questions
Accounting
General Management
Mathematics
Finance
Organizational Behaviour
Law
Physics
Operating System
Management Leadership
Sociology
Programming
Marketing
Database
Computer Network
Economics
Textbooks Solutions
Accounting
Managerial Accounting
Management Leadership
Cost Accounting
Statistics
Business Law
Corporate Finance
Finance
Economics
Auditing
Tutors
Online Tutors
Find a Tutor
Hire a Tutor
Become a Tutor
AI Tutor
AI Study Planner
NEW
Sell Books
Search
Search
Sign In
Register
study help
computer science
introduction to software engineering
Software Engineering A Practitioner's Approach 7th Edition Roger Pressman - Solutions
Testing and debugging are different activities, but debugging must be accommodated in any testing strategy?
Testing is conducted by the developer of the software and (for large projects)an independent test group.
Different testing techniques are appropriate for different software engineering approaches and at different points in time.
Testing begins at the component level and works “outward” toward the integration of the entire computer-based system.
To perform effective testing, you should conduct effective technical reviews(Chapter 15). By doing this, many errors will be eliminated before testing commences.
16.11. Acquire a copy of ISO 9001:2000 and ISO 9000-3. Prepare a presentation that discusses three ISO 9001 requirements and how they apply in a software context.
16.10. Consider two safety-critical systems that are controlled by computer. List at least three hazards for each that can be directly linked to software failures.
16.9. The MTBF concept for software is open to criticism. Explain why?
16.8. Besides counting errors and defects, are there other countable characteristics of software that imply quality? What are they and can they be measured directly?
16.7. You have been given the responsibility for improving the quality of software across your organization. What is the first thing that you should do? What’s next?
16.6. Why is there often tension between a software engineering group and an independent software quality assurance group? Is this healthy?
16.5. Can a program be correct and still not exhibit good quality? Explain.
16.4. Can a program be correct and still not be reliable? Explain.
16.3. Quality and reliability are related concepts but are fundamentally different in a number of ways. Discuss the differences.
16.2. Is it possible to assess the quality of software if the customer keeps changing what it is supposed to do?
16.1. Some people say that “variation control is the heart of quality control.” Since every program that is created is different from every other program, what are the variations that we look for and how do we control them?
4. Once the vital few causes have been identified, move to correct the problems that have caused the errors and defects.
3. Using the Pareto principle (80 percent of the defects can be traced to 20 percent of all possible causes), isolate the 20 percent (the vital few).
2. An attempt is made to trace each error and defect to its underlying cause(e.g., nonconformance to specifications, design error, violation of standards, poor communication with the customer).
1. Information about software errors and defects is collected and categorized.
15.10. Considering all of the review guidelines presented in Section 15.6.3, which do you think is most important and why?
15.9. A formal technical review is effective only if everyone has prepared in advance. How do you recognize a review participant who has not prepared? What do you do if you’re the review leader?
15.8. Can you think of a few instances in which a desk check might create problems rather than provide benefits?
15.7. Which of the reference model characteristics do you think has the strongest bearing on review formality? Explain why.
15.6. Describe the meaning of Figure 15.4 in your own words.
15.5. Reconsider the situation described in Problems 15.3 and 15.4. If each of the errors released to the field costs $4,800 to find and correct and each error found in review costs $240 to find and correct, how much money is saved by conducting reviews?
15.4. Reconsider the situation described in Problem 15.3, but now assume that requirements, design, and code reviews are conducted and are 60 percent effective in uncovering all errors at that step. How many errors will be released to the field?
15.3. Assume that 10 errors have been introduced in the requirements model and that each error will be amplified by a factor of 2:1 into design and an addition 20 design errors are introduced and then amplified 1.5:1 into code where an additional 30 errors are introduced. Assume further that all
15.2. Why can’t we just wait until testing to find and correct all software errors?
15.1. Explain the difference between an error and a defect.
9. Conduct meaningful training for all reviewers. To be effective all review participants should receive some formal training. The training should stress both process-related issues and the human psychological side of reviews. Freedman and Weinberg [Fre90] estimate a one-month learning curve for
8. Allocate resources and schedule time for FTRs. For reviews to be effective, they should be scheduled as tasks during the software process. In addition, time should be scheduled for the inevitable modifications that will occur as the result of an FTR.
7. Develop a checklist for each product that is likely to be reviewed. A checklist helps the review leader to structure the FTR meeting and helps each reviewer to focus on important issues. Checklists should be developed for analysis, design, code, and even testing work products.
6. Limit the number of participants and insist upon advance preparation. Two heads are better than one, but 14 are not necessarily better than 4. Keep the number of people involved to the necessary minimum. However, all review team members must prepare in advance. Written comments should be
5. Take written notes. It is sometimes a good idea for the recorder to make notes on a wall board, so that wording and priorities can be assessed by other reviewers as information is recorded. Alternatively, notes may be entered directly into a notebook computer.
4. Enunciate problem areas, but don’t attempt to solve every problem noted. A review is not a problem-solving session. The solution of a problem can often be accomplished by the producer alone or with the help of only one other individual. Problem solving should be postponed until after the
3. Limit debate and rebuttal. When an issue is raised by a reviewer, there may not be universal agreement on its impact. Rather than spending time debating the question, the issue should be recorded for further discussion off-line.
2. Set an agenda and maintain it. One of the key maladies of meetings of all types is drift. An FTR must be kept on track and on schedule. The review leader is chartered with the responsibility for maintaining the meeting schedule and should not be afraid to nudge people when drift sets in.
1. Review the product, not the producer. An FTR involves people and egos. Conducted properly, the FTR should leave all participants with a warm feeling of accomplishment. Conducted improperly, the FTR can take on the aura of an inquisition. Errors should be pointed out gently; the tone of the
3. What were the findings and conclusions?
2. Who reviewed it?
1. What was reviewed?
The duration of the review meeting should be less than two hours.
Advance preparation should occur but should require no more than two hours of work for each person.
Between three and five people (typically) should be involved in the review.
Are all navigation choices clearly labeled?
Are all navigation options or functions represented at the same level of abstraction?
Are color and placement, typeface, and size used effectively?
Does the presentation need to be scrolled?
Is the layout designed using standard conventions? Left to right? Top to bottom?
Major errors found, Errmajor—the number of errors found that can be categorized as major (requiring more than some prespecified effort to correct)
Minor errors found, Errminor—the number of errors found that can be categorized as minor (requiring less than some prespecified effort to correct)
Work product size, WPS—a measure of the size of the work product that has been reviewed (e.g., the number of UML models, or the number of document pages, or the number of lines of code)
Rework effort, Er—the effort (in person-hours) that is dedicated to the correction of those errors uncovered during the review
Assessment effort, Ea—the effort (in person-hours) that is expended during the actual review
Preparation effort, Ep—the effort (in person-hours) required to review a work product prior to the actual review meeting
14.12. Explain why it is that many of us continue to live by Meskimen’s law. What is it about the software business that causes this?
14.11. Are quality and security the same thing? Explain.
14.10. Do a Web search and find three other examples of “risks” to the public that can be directly traced to poor software quality. Consider beginning your search at http://catless.ncl.ac.uk/risks.
14.9. Considering each of the four aspects of the cost of quality, which do you think is the most expensive and why?
14.8. What is “good enough” software? Name a specific company and specific products that you believe were developed using the good enough philosophy.
14.7. Describe the software quality dilemma in your own words.
14.6. Using the subattributes noted for the ISO 9126 quality factor “maintainability” in Section 14.2.3, develop a set of questions that explore whether or not these attributes are present.Follow the example shown in Section 14.2.4.
14.5. McCall’s quality factors were developed during the 1970s. Almost every aspect of computing has changed dramatically since the time that they were developed, and yet, McCall’s factors continue to apply to modern software. Can you draw any conclusions based on this fact?
14.4. Add two additional questions to each of Garvin’s quality dimensions presented in Section 14.2.1.
14.3. Using the definition of software quality proposed in Section 14.2, do you think it’s possible to create a useful product that provides measurable value without using an effective process? Explain your answer.
14.2. Garvin [Gar84] describes five different views of quality. Provide an example of each using one or more well-known electronic products with which you are familiar.
14.1. Describe how you would assess the quality of a university before applying to it. What factors would be important? Which would be critical?
Costs associated with the collection of quality metrics that allow an organization to assess the modes of failure?
Cost that occurs when rework inadvertently generates side effects that must be mitigated
Cost required to perform rework (repair) to correct an error
Does the interface provide a macro capability that enables a user to identify a sequence of common operations with a single action or command?
Can the interface be customized to the specific needs of a user?
Does the interface provide useful diagnosis and guidance when an error condition (associated with software functionality) is uncovered?
Will the interface recognize common cognitive or manipulative mistakes and explicitly guide the user back on the right track?
Will the software recognize the error if data at or just outside prescribed boundaries is input? More importantly, will the software continue to operate without failure or degradation?
Have hierarchical operations been organized in a way that minimizes the depth to which a user must navigate to get something done?
Are output data or content presented so that it is understood immediately?
Can a sequence of operations (or data input) be performed with an economy of motion?
Does the interface layout and style allow a user to locate operations and information efficiently?
Do aesthetics aid in understanding and usage?
Does the interface follow the three golden rules? (Chapter 11)
Is input specified to economize key strokes or mouse clicks?
Does the interface use a recognizable metaphor?
Are interface operations easy to locate and initiate?
Is the interface layout conducive to easy understanding?
What measures and metrics can be used to assess the quality of requirements and design models, source code, and test cases?
How can we manage and control changes that always occur as software is built?
Are there realistic methods that will ensure that software is correct?
What methods are used to design effective test cases?
What strategies are applicable for software testing?
What is software quality assurance?
How do we review quality and how are effective reviews conducted?
What are the generic characteristics of high-quality software?
13.13. Write a brief paper on a hypermedia design method other than OOHDM.
13.12. Define two or three NSUs for the SafeHomeAssured.com WebApp. Describe each in some detail.
13.11. What is the difference between navigation syntax and navigation semantics?
13.10. Do a bit of additional research on the MVC architecture and decide whether it would be an appropriate WebApp architecture for the “learning engine” discussed in Problem 13.4.
13.9. Use UML to develop three or four design representations for content objects that would be encountered as the “learning engine” described in Problem 13.4 is designed.
13.8. Reconsidering the FutureLearning “learning engine” described in Problem 13.4, select a content architecture that would be appropriate for the WebApp. Discuss why you made the choice.
Showing 800 - 900
of 1534
First
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
Step by Step Answers
Get 50% OFF
Claim Now
