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
4. Instrument participants’ interaction with the WebApp while testing is conducted.
3. Select participants who will conduct the tests.
2. Design tests that will enable each goal to be evaluated.
1. Define a set of usability testing categories and identify goals for each.
Test to determine whether the WebApp can recall shopping cart contents at some future date (assuming that no purchase was made).
Test to determine the persistence of shopping cart contents (this should be specified as part of customer requirements).
Is every node reachable from the site map? Are node names meaningful to end users?
If a node within an NSU is reached from some external source, is it possible to process to the next node on the navigation path? Is it possible to return to the previous node on the navigation path?
Does the user understand his location within the content architecture as the NSU is executed?
If the system does fail, how long will it take to come back online?
What values of N, T, and D force the server environment to fail? How does failure manifest itself? Are automated notifications sent to technical support staff at the server site?
Is data integrity affected as capacity is exceeded?
Are transactions lost as capacity is exceeded?
Does the server queue resource requests and empty the queue once capacity demands diminish?
Does server software generate “server not available” messages? More generally, are users aware that they cannot reach the server?
Does the system degrade “gently,” or does the server shut down as capacity is exceeded?
If proxy servers are used, have differences in their configuration been addressed with on-site testing?
Have system administrator errors been examined for their effect on WebApp operations?
Do server-side WebApp scripts execute properly?
Is the WebApp properly integrated with database software? Is the WebApp sensitive to different versions of database software?
Has the WebApp been tested with the distributed server configuration11(if one exists) that has been chosen?
Do system security measures (e.g., firewalls or encryption) allow the WebApp to execute and service users without interference or performance degradation?
Are system files, directories, and related system data created correctly when the WebApp is operational?
Is the WebApp fully compatible with the server OS?
Test to determine whether a purchase empties the cart of its contents.
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.
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.
How is the information to be delivered?
What is the format of the information?
25.1. Describe the difference between process and project metrics in your own words.
Is every navigation node (defined for an NSU) reachable within the context of the navigation paths defined for the NSU?
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?
Are high-priority changes implemented in a timely manner?
9. Review the scoping document or collection of use cases with all concerned.
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.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.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.
Don’t use metrics to appraise individuals.
Work with practitioners and teams to set clear goals and metrics that will be used to achieve them.
Is our response time for fixing bugs acceptable based on customer need?
How large is the change request backlog?
Is our change control process (Chapter 22) followed?
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.
Never use metrics to threaten individuals or teams.
Metrics data that indicate a problem area should not be considered“negative.” These data are merely an indicator for process improvement.
Don’t obsess on a single metric to the exclusion of other important metrics.
Time (hours or days) elapsed from the time a request is made until evaluation is complete, tqueue.
Effort (person-hours) to perform the evaluation, Weval.
Time (hours or days) elapsed from completion of evaluation to assignment of change order to personnel, teval.
17.10. As a class project, develop a Debugging Guide for your installation. The guide should provide language and system-oriented hints that have been learned through the school of hard knocks! Begin with an outline of topics that will be reviewed by the class and your instructor.Publish the guide
17.9. Develop a complete test strategy for the SafeHome system discussed earlier in this book.Document it in a Test Specification.
17.8. Who should perform the validation test—the software developer or the software user?Justify your answer.
17.7. Is unit testing possible or even desirable in all circumstances? Provide examples to justify your answer.
17.6. How can project scheduling affect integration testing?
17.5. The concept of “antibugging” (Section 17.2.1) is an extremely effective way to provide built-in debugging assistance when an error is uncovered:a. Develop a set of guidelines for antibugging.b. Discuss advantages of using the technique.c. Discuss disadvantages.
17.4. Why is a highly coupled module difficult to unit test?
17.3. Is it always possible to develop a strategy for testing software that uses the sequence of testing steps described in Section 17.1.3? What possible complications might arise for embedded systems?
17.2. List some problems that might be associated with the creation of an independent test group. Are an ITG and an SQA group made up of the same people?
17.1. Using your own words, describe the difference between verification and validation.Do both make use of test-case design methods and testing strategies?
5. Regression testing (discussed later in this section) may be conducted to ensure that new errors have not been introduced.
4. On completion of each set of tests, another stub is replaced with the real component.
3. Tests are conducted as each component is integrated.
2. Depending on the integration approach selected (i.e., depth or breadth first), subordinate stubs are replaced one at a time with actual components.
1. The main control module is used as a test driver and stubs are substituted for all components directly subordinate to the main control module.
Showing 700 - 800
of 1534
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
Last
Step by Step Answers
Get 50% OFF
Claim Now
