Software Engineering A Practitioner's Approach 7th Edition Roger Pressman - Solutions

Discover comprehensive resources for "Software Engineering: A Practitioner's Approach, 7th Edition" by Roger Pressman, now available online. Access the complete answers key and solutions manual to enhance your understanding. Our solutions PDF offers step-by-step answers to solved problems and questions and answers from the textbook, providing clarity and insight. Whether you're searching for chapter solutions or utilizing the test bank, our instructor manual is designed to assist students and educators alike. Enjoy the convenience of a free download and explore the textbook's content with confidence.

Are examples accurate?
Is the description of each interaction sequence accurate?
Does the documentation accurately describe how to accomplish each mode of use?
4. If internal program data structures have prescribed boundaries (e.g., a table has a defined limit of 100 entries), be certain to design a test case to exercise the data structure at its boundary?
3. Apply guidelines 1 and 2 to output conditions. For example, assume that a temperature versus pressure table is required as output from an engineering analysis program. Test cases should be designed to create an output report that produces the maximum (and minimum) allowable number of table
2. If an input condition specifies a number of values, test cases should be developed that exercise the minimum and maximum numbers. Values just above and below minimum and maximum are also tested.
3. If an input condition specifies a member of a set, one valid and one invalid equivalence class are defined.
2. If an input condition requires a specific value, one valid and two invalid equivalence classes are defined.
1. If an input condition specifies a range, one valid and two invalid equivalence classes are defined.
What effect will specific combinations of data have on system operation?
What data rates and data volume can the system tolerate?
How are the boundaries of a data class isolated?
Is the system particularly sensitive to certain input values?
What classes of input will make good test cases?
How are system behavior and performance tested?
How is functional validity tested?
4. Continue until all loops have been tested.
3. Work outward, conducting tests for the next loop, but keeping all other outer loops at minimum values and other nested loops to “typical” values.
2. Conduct simple loop tests for the innermost loop while holding the outer loops at their minimum iteration parameter (e.g., loop counter) values. Add other tests for out-of-range or excluded values.
1. Start at the innermost loop. Set all other loops to minimum values.
The resources required during traversal of a link.?
The memory required during traversal of a link
The processing time expended during traversal of a link
The probability that a link (edge) will be execute.
25.13. A software team delivers a software increment to end users. The users uncover eight defects during the first month of use. Prior to delivery, the software team found 242 errors during formal technical reviews and all testing tasks. What is the overall DRE for the project after one month’s
25.12. At the conclusion of a project, it has been determined that 30 errors were found during the modeling activity and 12 errors were found during the construction activity that were traceable to errors that were not discovered in the modeling activity. What is the DRE for the modeling activity?
25.11. A WebApp and its support environment have not been fully fortified against attack. Web engineers estimate that the likelihood of repelling an attack is only 30 percent. The system does not contain sensitive or controversial information, so the threat probability is 25 percent. What is the
25.10. A Web engineering team has built an e-commerce WebApp that contains 145 individual pages. Of these pages, 65 are dynamic; that is, they are internally generated based on enduser input. What is the customization index for this application?
25.9. The software used to control a photocopier requires 32,000 lines of C and 4,200 lines of Smalltalk. Estimate the number of function points for the software inside the copier.
25.8. Using the table presented in Section 25.2.3, make an argument against the use of assembler language based on the functionality delivered per statement of code. Again referring to the table, discuss why C++ would present a better alternative than C.
25.7. Compute the function point value for a project with the following information domain characteristics:Number of user inputs: 32 Number of user outputs: 60 Number of user inquiries: 24 Number of files: 8 Number of external interfaces: 2 Assume that all complexity adjustment values are average.
25.6. Present an argument against lines of code as a measure for software productivity. Will your case hold up when dozens or hundreds of projects are considered?
25.5. Team A found 342 errors during the software engineering process prior to release. Team B found 184 errors. What additional measures would have to be made for projects A and B to determine which of the teams eliminated errors more efficiently? What metrics would you propose to help in making
25.4. Grady suggests an etiquette for software metrics. Can you add three more rules to those noted in Section 25.1.1?
25.3. What is an indirect measure, and why are such measures common in software metrics work?
25.2. Why should some software metrics be kept “private”? Provide examples of three metrics that should be private. Provide examples of three metrics that should be public?
25.1. Describe the difference between process and project metrics in your own words.
What is the format of the information?
How is the information to be delivered?
Who requires ongoing metrics information?
8. Define appropriate feedback mechanisms.
7. Establish a metrics database.The relative sophistication of the database is established.Use of related tools (e.g., an SCM repository, Chapter 26) is explored.Existing database products are evaluated.
6. Acquire appropriate tools to assist in collection and assessment.
How are data stored?
When are data collected and recorded?
Who is responsible for collecting the data?
Can tools be used to collect the data?
What is the source of the measurements?
4. Identify the measures and metrics to be collected and computed.
3. Identify metrics required to achieve goals.Questions to be answered are defined; for example, How many errors found in one framework activity can be traced to the preceding framework activity?Create measures and metrics that will help answer these questions.
2. Define the goals to be achieved by establishing a metrics program Examples: improve accuracy of estimation, improve product quality.
1. Understand the existing software process.Framework activities (Chapter 2) are identified.Input information for each activity is described.Tasks associated with each activity are defined.Quality assurance functions are noted.Work products that are produced are listed.
Are high-priority changes implemented in a timely manner?
Is our change control process (Chapter 22) followed?
Is our response time for fixing bugs acceptable based on customer need?
How large is the change request backlog?
Do customer change requests contain the information we require to adequately evaluate the change and then implement it in a timely manner?
Defects uncovered after change is released to the customer base, Dchange.1. Identify your business goals.2. Identify what you want to know or learn.3. Identify your subgoals.4. Identify the entities and attributes related to your subgoals.5. Formalize your measurement goals.6. Identify quantifiable
Errors uncovered during work to make change, Echange.
Time required (hours or days) to make the change, tchange.
Effort (person-hours) required to make the change, Wchange.
Time (hours or days) elapsed from completion of evaluation to assignment of change order to personnel, teval.
Effort (person-hours) to perform the evaluation, Weval.
Time (hours or days) elapsed from the time a request is made until evaluation is complete, tqueue.
Don’t obsess on a single metric to the exclusion of other important metrics.
Metrics data that indicate a problem area should not be considered“negative.” These data are merely an indicator for process improvement.
Never use metrics to threaten individuals or teams.
Work with practitioners and teams to set clear goals and metrics that will be used to achieve them.
Don’t use metrics to appraise individuals.
Provide regular feedback to the individuals and teams who collect measures and metrics.
Use common sense and organizational sensitivity when interpreting metrics data.
24.11. Do a first-level functional decomposition of the page layout function discussed briefly in Section 24.3.2.
24.10. You have been asked to develop a small application that analyzes each course offered by a university and reports the average grade obtained in the course (for a given term). Write a statement of scope that bounds this problem.
24.9. You have been appointed a software project manager for a company that services the genetic engineering world. Your job is to manage the development of a new software product that will accelerate the pace of gene typing. The work is R&D oriented, but the goal is to produce a product within the
24.8. You have been appointed a project manager for a major software products company.Your job is to manage the development of the next-generation version of its widely used wordprocessing software. Because competition is intense, tight deadlines have been established and announced. What team
24.7. You have been appointed a project manager for a small software products company. Your job is to build a breakthrough product that combines virtual reality hardware with state-of-theart software. Because competition for the home entertainment market is intense, there is significant pressure to
24.6. You have been appointed a project manager within an information systems organization.Your job is to build an application that is quite similar to others your team has built, although this one is larger and more complex. Requirements have been thoroughly documented by the customer. What team
24.5. Review a copy of Weinberg’s book [Wei86], and write a two- or three-page summary of the issues that should be considered in applying the MOI model.
24.4. The decisions made by senior management can have a significant impact on the effectiveness of a software engineering team. Provide five examples to illustrate that this is true.
24.3. Describe three real-life situations in which the customer and the end user are the same.Describe three situations in which they are different.
24.2. The Software Engineering Institute’s People Capability Maturity Model (People-CMM)takes an organized look at “key practice areas” that cultivate good software people. Your instructor will assign you one KPA for analysis and summary.
24.1. Based on information contained in this chapter and your own experience, develop “ten commandments” for empowering software engineers. That is, make a list of 10 guidelines that will lead to software people who work to their full potential.
10. Modify the scoping document or use cases as required.
9. Review the scoping document or collection of use cases with all concerned.
8. Assemble the mini-specs into a scoping document.
7. Review each mini-spec or use case for correctness, consistency, and lack of ambiguity.
6. Jointly develop mini-specs that reflect data, functional, and behavioral features of the software. Alternatively, develop use cases that describe the software from the user’s point of view.
5. Conduct the meeting.
4. Prepare a “working document” and an agenda for the formal meeting.
3. Conduct research to specify the proposed solution and existing approaches.
2. Plan and schedule a formal, facilitated meeting with all stakeholders.
1. Review the customer request.
5. Modify the statement of scope as required.
4. Review the statement of scope with all concerned.
3. Jointly develop a statement of scope.
2. Meet with stakeholders to address clarification issues.
1. Develop list of clarification issues.
Mavericks may have to be excluded from the team, if team cohesiveness is to be maintained.
The distribution of skills must be appropriate to the problem.
Team members must have trust in one another.

Showing 1 - 100 of 1534

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
Last

Software Engineering A Practitioner's Approach 7th Edition Roger Pressman - Solutions

Step by Step Answers