CODE NO: 6863/CDE
FACULTY OF INFORMATICS
M.C.A.III YEAR (CDE) (MAIN) EXAMINATION, AUGUST/SEPTEMBER 2010
SOFTWARE QUALITY AND TESTING
TIME: 3 Hours] [max.marks:80
Note: Answer one question from each unit. All questions carry equal marks.
UNIT-I
1. (a) What is software quality? Give brief explanation. 3
(b) How can “Defect density metrics’ be used as a product quality metric? 5
(c) Explain how “Run charts’ are useful quality tools in software development. 8
(or)
2. (a) Explain how ‘customer satisfaction metric’ is useful for measuring the product quality. 4
(b) With an example explain the phase-based defect removal model. 7
(c) What is understood by ‘Quality Planning’? 5
UNIT-II
3. (a) Explain the criteria for evaluation of models- Reliability growth models. 8
(b) Discuss the PTR submodel for tracking of development quality. 8
(OR)
4. (a) Explain the steps to model software reliability. 8
(b)Explain how the Rayleigh model provides directions for development quality improvement. 8
UNIT-III
5.(a). What are ‘system bugs’ and ‘Integration Bugs’? 4
(b) What is ‘Path sensitizing’? Explain. 4
(c) Explain the ‘Transaction-Flow testing techniques’. 8
(or)
6. (a). What bugs are specific to requirements, features and functionality of the software to be developed? 5
(b) Explain the concepts of testing multi-entry or multi-exit routines 5
(c) Give the definitions, usage and implementation of transaction flows. 6
UNIT-IV
7.(a). Explain some strategies for Data-flow testing 6
(b) What are Domain Bugs and how can they be tested? 5
(c) What do linguistic metrics measure ? 5
(or)
8.(a). Explain the components of the data flow model 6
(b) Explain about nice domains and ugly domains. 5
(c) What are the requirements which a useful metric should satisfy ? 5
UNIT-V
9.(a). Explain how KV Charts can be used in logic-based testing. 10
(b) What are the three phases into which testing can be divided ? Explain them.. 6
(or)
10.(a). Explain the procedure for state testing with limitations and extensions. 6
(b) Explain the tools that can be used in testing. 10
No comments:
Post a Comment