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
=+5.12. Using the process pattern template presented in Chapter 3, develop a process pattern for any one of the Scrum patterns presented in Section 5.5.1.
=+5.11. Describe the XP concepts of refactoring and pair programming in your own words.
=+5.10. What is a spike solution in XP?
=+5.9. Write an XP user story that describes the "favorite places" or "favorites" feature avail-able on most Web browsers.
=+Do you think this implies that geographical separation is something to avoid? Can you think of ways to overcome this problem?
=+5.8. Most agile process models recommend face-to-face communication. Yet today, mem-bers of a software team and their customers may be geographically separated from one another.
=+5.7. Why do requirements change so much? After all, don't people know what they want?
=+sented an overview of these process models only, so it may not be possible to determine whether a principle has been addressed by one or more of the models, unless you do addi-tional research
=+5.6. Select one agility principle noted in Section 5.3.1 and try to determine whether each of the process models presented in this chapter exhibits the principle. [Note: We have pre-
=+5.5. Try to come up with one more "agility principle" that would help a software engineering team become even more maneuverable.
=+ Build a table that maps the generic activities into the activities defined for each agile process.
=+5.4. Could each of the agile processes be described using the generic framework activities noted in Chapter 3?
=+Is it possible to complete a project in just one iteration and still be agile? Explain your answers.
=+discussed in this chapter iterative?
=+5.3. Why does an iterative process make it easier to manage change? Is every agile process
=+5.2. Describe agility (for software projects) in your own words.
=+5.1. Reread the "Manifesto for Agile Software Development" at the beginning of this chap-ter. Can you think of a situation in which one or more of the four "values" could get a soft-ware team into
=+ What do you plan to accomplish by the next team meeting?
=+ What obstacles are you encountering?
=+What did you do since the last team meeting?
=+4.11. Are the Unified Process and UML the same thing? Explain your answer.
=+4.10. It is possible to prove that a software component and even an entire program is correct. So why doesn't everyone do this?
=+4.9. Provide three examples of software projects that would be amenable to the component-based model. Be specific.
=+4.8. What are the advantages and disadvantages of developing software in which quality is"good enough "? That is, what happens when we emphasize development speed over prod-uct quality?
=+resent in your own words, and then indicate how they come into play within the concurrent process model.
=+4.7. The concurrent process model defines a set of "states. " Describe what these states rep-
=+4.6. Is it possible to combine process models? I so, provide an example.
=+4.5. As you move outward along the spiral process flow, what can you say about the software that is being developed or maintained?
=+4.4. Provide three examples of software projects that would be amenable to the incremen-tal model. Be specific.
=+4.3. What process adaptations are required if the prototype will evolve into a delivery sys-tem or product?
=+4.2. Provide three examples of software projects that would be amenable to the prototyping model. Be specific.
=+4.1. Provide three examples of software projects that would be amenable to the waterfall model. Be specific.
=+conflicting requirements. Develop a process pattern (this would be a stage pattern) using the template presented in Section 3.4 that addresses this problem and suggest an effective approach to it.
=+3.4. A common problem during communication occurs when you encounter two stakehold-ers who have conflicting ideas about what the software should be. That is, you have mutually
=+3.3. Try to develop a set of actions for the communication activity. Select one action and define a task set for it.
=+Can you identify types of problems that might be applicable to each of the generic flows described?
=+3.2. Discuss the differences among the various process flows described in Section 3.1.
=+4 The SEI's CMMI [CMM07] describes the characteristics of a software process and the criteria for a successful process in voluminous detail.
=+3.1. In the introduction to this chapter Baetjer notes: "The process provides interaction be-tween users and designers, between users and evolving tools, and between designers and evolving tools
To understand the notion of software engineering and why it is important
To appreciate the technical (engineering), managerial, and psychological aspects of software engineering
To understand the similarities and differences between software engineering and other engineering disciplines
To know the major phases in a software development project
To appreciate ethical dimensions in software engineering
To be aware of the time frame and extent to which new developments impact software engineering practice
Define the term software engineering.
What are the essential characteristics of software engineering?
What are the major phases in a software development project?
What is the difference between verification and validation?
Define four kinds of maintenance activity.
Why is the documentation of a software project important?
Explain the 40--20--40 rule of thumb in software engineering.
What is the difference between software development and software maintenance?
~ Do you think the linear model of software development is appropriate? In which cases do you think an agile approach is more appropriate? You may wish to reconsider this issue after having read the
~ Discuss the major differences between software engineering and some other engineering discipline, such as bridge design or house building. Would you consider state-of-the-art software engineering
Quality and productivity are major issues in software engineering. It is often advocated that automated tools (CASE tools) will dramatically improve both quality and productivity. Study a
~ Medical doctors have their Hippocratic oath. Could a similar ethical commitment by software engineers be instrumental in increasing the quality of software systems?
Suppose you are involved in an office automation project in the printing industry. The system to be developed is meant to support the work of journal editors. The management objective for this
~ Discuss the difference between requirements-based software development and market-driven software development (Sawyer, 2001).
~ Discuss the impact of globalisation on software development.
Study both the technical and user documentation of a system at your disposal. Are you satisfied with them? Discuss their possible shortcomings and give remedies to improve their quality.
Take a piece of software you wrote more than a year ago. Is it documented adequately? Does it have a user manual? Is the design rationale reflected in the technical documentation? Can you build an
Try to gather quantitative data from your organization that reveals how much effort is spent on various kinds of maintenance activity. Are these data available at all? If so, is the pattern like
A 1999 Computer Society survey lists the following candidate fundamental principles of software engineering:A. Apply and use quantitative measurements in decision-making.B. Build with and for
What is software testing?(a) It is the process of demonstrating that errors are not present.(b) It is the process of establishing confidence that a program does what it is supposed to do.(c) It is
Why should testing be done?(a) To ensure the correctness of a program(b) To find errors in a program(c) To establish the reliability of a program(d) To certify the effectiveness of a program
Which phase consumes maximum effort to fix an error?(a) Requirements analysis and specifications(b) Design phase(c) Coding phase(d) Feasibility study phase
Which objective is most difficult to achieve?(a) Execute every statement of a program at least once(b) Execute every branch statement of a program at least once(c) Execute every path of a program at
Software errors during coding are known as:(a) Bugs(b) Defects(c) Failures(d) Mistakes
The cost of fixing an error is:(a) More in requirements analysis and specification phase than coding phase(b) More in coding phase than requirements analysis and specification phase(c) Same in all
Beta testing is done by:(a) Developers(b) Testers(c) Potential customers(d) Requirements writers
Alpha testing is carried out at the:(a) Developer’s site in a controlled environment(b) Developer’s site in a free environment(c) Customer’s site in a controlled environment(d) Customer’s
The purpose of acceptance testing is:(a) To perform testing from the business perspective(b) To find faults in the software(c) To test the software with associated hardware(d) To perform feasibility
Acceptance testing is done by:(a) Developers(b) Customers(c) Testers(d) All of the above
Program is:(a) Subset of software(b) Superset of software(c) Set of software(d) Union of software
Which is not an infrastructure software?(a) Compiler(b) Operating system(c) Testing tools(d) Result Management Software
Software should have:(a) Program + operating system + compiler(b) Set of programs + operating system(c) Programs + documentation + operating procedures(d) None of the above
Concepts of software testing are applicable to:(a) Procedural programming languages(b) Object oriented programming languages(c) ‘C’, ‘C++’ and Java programming languages(d) All of the above
CASE Tool is:(a) Computer Aided Software Engineering Tool(b) Component Aided Software Engineering Tool(c) Constructive Aided Software Engineering Tool(d) Complete Analysis Software Enterprise Tool
One fault may lead to:(a) One failure(b) Many failures(c) No failure(d) All of the above
Test suite of a program is a:(a) Set of test cases(b) Set of inputs with pre-conditions(c) Set of outputs with post-conditions(d) Set of testing strategies
Alpha and Beta testing techniques are related to:(a) Unit testing(b) Integration testing(c) System testing(d) Testing by Customer
Testing a software is primarily focused on:(a) Verification activities only(b) Validation activities only(c) Verification and validation activities(d) None of the above
Testing a software with real data in real environment is known as:(a) Alpha testing(b) Beta testing(c) System testing(d) Integration testing
Verification activities are:(a) Performed manually(b) Related to reviewing the documents and source code(c) Known as static testing(d) All of the above
Validation activities are:(a) Dynamic activities and require program execution(b) Related to inspecting the source code(c) Related to static testing(d) Related to source code design and documentation
When the output of a program is different from the expected output, it is known as:(a) A fault(b) An error(c) A failure(d) A mistake
Software testing activities should be started:(a) After the completion of source code(b) After the completion of design phase(c) As early as possible in the software development life cycle(d) After
Software testing activities are important in:(a) Every phase of the software development life cycle(b) The last few phases of the software development life cycle(c) The software requirements and
The focus of acceptance testing is:(a) To find faults(b) To ensure correctness of software(c) To test integration related issues(d) To test from the user’s perspective
A reliable software is one which is:(a) Liked by its users(b) Delivered on time and with budget(c) Unlikely to cause failures(d) Very easy to use
When to stop testing and release the software to customers should be decided on the basis of:(a) Market conditions(b) Budget and availability of resources(c) Test metrics(d) Capabilities of the
What are the good software testing practices?(a) Involve testing persons as early as possible in the software development life cycle(b) Apply effective verification techniques(c) Enforce inspections
What is a test case?(a) Input(s), expected output(s), pre-condition(s) and post-condition(s)(b) Steps of execution(c) A list of activities which can be tested(d) None of the above
You cannot control what you cannot :(a) Define(b) Measure(c) Improve(d) Change
What is the major benefit of verifications in the early phases of the software development life cycle?(a) It identifies changes in the SRS (b) It reduces defect multiplication (c) It allows
Behavioural specifications are required for:(a) Modelling(b) Verification(c) Validation(d) Testing
Which, in general, is the least expected skill of a testing person?(a) Diplomatic(b) Reliable(c) Having good attention to detail(d) Good developer
Debugging of a program is(a) The process of executing the program(b) The process of identifying a fault and removing it from the program(c) The process of experiencing a failure(d) The process of
All validation activities come under the category of:(a) Dynamic testing(b) Static testing(c) Source code design(d) None of the above
Showing 2600 - 2700
of 3313
First
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34