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
business
software testing and quality assurance
Software Engineering A Practitioner's Approach Software Engineering A Practitioner's Approach 8th Edition Roger Pressman - Solutions
=+7.10. Why are models important in software engineering work? Are they always necessary?
=+Are there qualifiers to your answer about necessity?
=+7.11. What three "domains" are considered during requirements modeling?
=+7.12. Try to add one additional principle to those stated for coding in Section 7.3.4.
=+7.13. What is a successful test?
=+7.14. Do you agree or disagree with the following statement: "Since we deliver multi-
=+ple increments to the customer, why should we be concerned about quality in the early increments-we can fix problems in later iterations. " Explain your answer.
=+7.15. Why is feedback important to the software team?
=+Are requirements stated clearly? Can they be misinterpreted?
=+Is the source (e.g ., a person, a regulation, a document) of the requirement identified?
=+Has the final statement of the requirement been examined by or against the original source?
=+Is the requirement bounded in quantitative terms?
=+What other requirements relate to this requirement?
=+Are they clearly noted via a cross-reference matrix or other mechanism?
=+Does the requirement violate any system domain constraints?
=+Is the requirement testable? If so, can we specify tests(sometimes called validation criteria) to exercise the requirement?
=+Is the requirement traceable to any system model that has been created?
=+Is the requirement traceable to overall system/product objectives?
=+Is the specification structured in a way that leads to easy understanding, easy reference, and easy translation into more technical work products?
=+Has an index for the specification been created?
=+Have requirements associated with performance, behavior, and operational characteristics been clearly stated?
=+What requirements appear to be implicit?.
=+Who is behind the request for this work?
=+Who will use the solution?
=+What will be the economic benefit of a successful solution?
=+Is there another source for the solution that you need?
=+. How would you characterize "good" output that would be generated by a successful solution?
=+What problem(s) will this solution address?
=+Can you show me (or describe) the business environment in which the solution will be used?.
=+Will special performance issues or constraints affect the way the solution is approached?
=+. Are you the right person to answer these questions? Are your answers"official"?
=+. Are my questions relevant to the problem that you have?
=+Am I asking too many questions?
=+Can anyone else provide additional information?
=+Should I be asking you anything else?
=+Can we build the system?
=+Will this development process allow us to beat our competitors to market?
=+Do adequate resources exist to build and maintain the proposed system?
=+Will the system performance meet the needs of our customers?.
=+Who is the primary actor, the secondary actor(s)?
=+What are the actor's goals?
=+What preconditions should exist before the story begins?
=+What main tasks or functions are performed by the actor?
=+What exceptions might be considered as the story is described?
=+What variations in the actor's interaction are possible?
=+What system information will the actor acquire, produce, or change?
=+Will the actor have to inform the system about changes in the external environment?
=+What information does the actor desire from the system?
=+Does the actor wish to be informed about unexpected changes?
=+Is each requirement consistent with the overall objectives for the system or product?
=+Have all requirements been specified at the proper level of abstraction?
=+That is, do some requirements provide a level of technical detail that is inappropriate at this stage?
=+Is the requirement really necessary or does it represent an add-on feature
=+that may not be essential to the objective of the system?
=+Is each requirement bounded and unambiguous?
=+Does each requirement have attribution?
=+ That is, is a source (generally, a specific individual) noted for each requirement?
=+Do any requirements conflict with other requirements?
=+Is each requirement achievable in the technical environment that will house the system or product?
=+Is each requirement testable, once implemented?
=+Does the requirements model properly reflect the information, function,
=+and behavior of the system to be built?
=+Has the requirements model been "partitioned" in a way that exposes pro-gressively more detailed information about the system?
=+8.1. Why is it that many software developers don't pay enough attention to requirements engineering?
=+Are there ever circumstances where you can skip it?
=+8.2. You have been given the responsibility to elicit requirements from a customer who tells
=+you he is too busy to meet with you. What should you do?
=+8.3. Discuss some of the problems that occur when requirements must be elicited from three or four different customers.
=+8.4. Why do we say that the requirements model represents a snapshot of a system in time?
=+8.5. Let's assume that you've convinced the customer (you're a very good salesperson) to agree to every demand that you have as a developer. Does that make you a master negoti-ator? Why?
=+8.6. Develop at least three additional "context-free questions" that you might ask a stake-holder during inception.
=+8.7. Develop a requirements-gathering "kit."The kit should include a set of guidelines for
=+conducting a requirements-gathering meeting and materials that can be used to facilitate the creation of lists and any other items that might help in defining requirements.
=+8.8. Your instructor will divide the class into groups of four or six students. Half of the group will play the role of the marketing department and half will take on the role of software en-
=+gineering. Your job is to define requirements for the SafeHome security function described in this chapter. Conduct a requirements-gathering meeting using the guidelines presented in this chapter.
=+8.9. Develop a complete use case for one of the following activities:a. Making a withdrawal at an ATM.
=+b. Using your charge card for a meal at a restaurant.c. Buying a stock using an online brokerage account.
=+d. Searching for books (on a specific topic) using an online bookstore
=+e. An activity specified by your instructor.
=+8.10. What do use case "exceptions" represent?
=+8.11. Write a user story for one of the activities listed in question 8.9.
=+8.12. Consider the use case you created in question 8.9, write a nonfunctional requirement for the application.
=+8.13. Describe what an analysis pattern is in your own words.
=+8.14. Using the template presented in Section 8.5.2, suggest one or more analysis pattern for the following application domains:a. Accounting software.b. E-mail software.c. Internet browsers
=+d. Word-processing software.e. Website creation software.
=+1. An application domain specified by your instructor.
=+8.15. What does win-win mean in the context of negotiation during the requirements engi-neering activity?
=+8.16. What do you think happens when requirement validation uncovers an error? Who is involved in correcting the error?
=+8.17. What five tasks make up a comprehensive requirements monitoring program?
=+Can the actor take some other action at this point?
=+Is it possible that the actor will encounter some error condition at this.
=+point? If so, what might it be?
=+Is it possible that the actor will encounter some other behavior at this point(e.g ., behavior that is invoked by some event outside the actor's control)? If so, what might it be?
=+. Are there cases in which some "validation function" occurs during this use case?
=+ This implies that validation function is invoked and a potential error condition might occur.
=+. Are there cases in which a supporting function (or actor) will fail to re-spond appropriately? For example, a user action awaits a response but the function that is to respond times out..
=+Can poor system performance result in unexpected or improper user ac-tions? For example, a Web-based interface responds too slowly, resulting in a user making multiple selects on a processing button. These selects queue inappropriately and ultimately generate an error condition.
=+1.What mechanisms protect unauthorized use of this capability by employees of SafeHome Products?
=+2.Is security sufficient? Hacking into this feature would represent a major invasion of privacy.
=+3. Will system response via the Internet be accept-able given the bandwidth required for camera views?
Showing 2300 - 2400
of 3990
First
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
Last
Step by Step Answers
Get 50% OFF
Claim Now
