All Matches
Solution Library
Expert Answer
Textbooks
Search Textbook questions, tutors and Books
Oops, something went wrong!
Change your search query and then try again
Toggle navigation
FREE Trial
S
Books
FREE
Tutors
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
Ask a Question
AI Study Help
New
Search
Search
Sign In
Register
study help
business
software testing and quality assurance
Questions and Answers of
Software Testing And Quality Assurance
=+What concepts and principles guide software engineering practice?
=+What is requirements engineering and what are the under-lying concepts that lead to good requirements analysis?
=+How is the requirements model created and what are its elements?
=+What are the elements of a good design?
=+How does architectural design establish a framework for
=+all other design actions and what models are used?
=+How do we design high-quality software components?
=+What concepts, models, and methods are applied as a user interface is designed?
=+What is pattern-based design?
=+What specialized strategiesand methods are used to design WebApps?
=+What specialized strategiesand methods are used to design mobile apps?
=+7.1. Since a focus on quality demands resources and time, is it possible to be agile and still maintain a quality focus?
=+7.2. Of the eight core principles that guide process (discussed in Section 7.2.1), which do you believe is most important?
=+7.3. Describe the concept of separation of concerns in your own words.
=+7.4. An important communication principle states, "Prepare before you communicate."
=+How should this preparation manifest itself in the early work thavt you do?
=+What work prod-ucts might result as a consequence of early preparation?
=+7.5. Do some research on "facilitation" for the communication activity (use the references provided or others) and prepare a set of guidelines that focus solely on facilitation.
=+7.6. How does agile communication differ from traditional software engineering communi-cation? How is it similar?
=+7.7. Why is it necessary to "move on"?
=+7.8. Do some research on "negotiation" for the communication activity and prepare a set of guidelines that focus solely on negotiation.
=+7.9. Describe what granularity means in the context of a project schedule.
=+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
Showing 1600 - 1700
of 3313
First
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
Last