Information Technology > QUESTIONS & ANSWERS > THE QUALITY ASSURANCE AND TESTING STRATEGIES (All)

THE QUALITY ASSURANCE AND TESTING STRATEGIES

Document Content and Description Below

THE QUALITY ASSURANCE AND TESTING STRATEGIES Tutorial #3 QUESTION 1 Can a program be correct and still not be reliable? Explain. Q1-ANSWER It is possible that a program is correct, but it is no ... t reliable. A program is correct if it behaves according to its stated functional specifications. If a program is correct, it does not ensure the non-occurrence of a failure. Thus, if the consequence of a software error is not serious, incorrect software may be reliable. Q2 Can a program be correct and still not exhibit good quality? Explain. Q3 Why is there often tension between a software engineering group and an independent software quality assurance group? Is this healthy? Q4 You have been given the responsibility for improving the quality of software across your organization. What is the first thing that you should do? What’s next? Q4-ANSWER Q5 Besides counting errors and defects, are there other countable characteristics of software that imply quality? What are they and can they be measured directly? Q6 State ONE quality metric that can be used for measuring: Security, Safety, Maintainability & Learnability. Endpoint incidents :Endpoint incidents are how many devices have been infected by a virus in a given period of time. Mean time to repair (MTTR):Mean time to repair in this context measures the time from the security breach discovery to when a working remedy is deployed. PART 2: SOFTWARE TESTING STRATEGIES Using your own words, describe the difference between verification and validation. Do both make use of test-case design methods and testing strategies? Verification Validation 1. Verification is a static practice of verifying documents, design, code and program. 2. It does not involve executing the code. 3. It is human based checking of documents and files. . 4. Verification uses methods like inspections, reviews, walkthroughs, and Desk-checking etc. 5. Verification is to check whether the software conforms to specifications. |. 6. It can catch errors that validation cannot catch. It is low level exercise. 7. Target is requirements specification, application and software architecture, high level, complete design, and database design etc. | 8. Verification is done by QA team to ensure that the software is as per the specifications in the SRS document. 9. It generally comes first-done before validation. 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? Is unit testing possible or even desirable in all circumstances? Provide examples to justify your answer. Who should perform the validation test—the software developer or the software user? Justify your answer. Develop a complete test strategy for the SafeHome system discussed earlier in this book. Document it in a Test Specification. [Show More]

Last updated: 3 years ago

Preview 1 out of 31 pages

Buy Now

Instant download

We Accept: