University of Madras
Chepauk, Chennai - 600 005
Bachelor of Computer Applications
Chepauk, Chennai - 600 005
Bachelor of Computer Applications
Title of the Paper: Software Testing
Month & Year of Examination: April - 2013
Subject Code: SEE6G
Semester: VI
Year: Third Year
Question Paper Number: 50412
Time: Three hours
Maximum: 75 marks
Month & Year of Examination: April - 2013
Subject Code: SEE6G
Semester: VI
Year: Third Year
Question Paper Number: 50412
Time: Three hours
Maximum: 75 marks
Section – A (10 * 2 = 20 marks)
Answer any TWO questions.
All questions carry equal marks.
Answer any TWO questions.
All questions carry equal marks.
1.Define: Software reliability, Software efficiency.
2.Compare project format with functional format.
3.What is event table?
4.Name any four software cost factors.
5.Give the structure of the problem statement analyzer.
6.Mention the need for HIPO diagrams.
7.Write the concept of stepwise refinement design technique.
8.What is asynchronous message passing?
9.Name any four typeless programming languages.
10. What is recursion? Give an example?
11. Give the purpose of linkage editors and comparators tools in software maintenance.
12.What is configuration management?
2.Compare project format with functional format.
3.What is event table?
4.Name any four software cost factors.
5.Give the structure of the problem statement analyzer.
6.Mention the need for HIPO diagrams.
7.Write the concept of stepwise refinement design technique.
8.What is asynchronous message passing?
9.Name any four typeless programming languages.
10. What is recursion? Give an example?
11. Give the purpose of linkage editors and comparators tools in software maintenance.
12.What is configuration management?
Section – B (5 * 5 = 25 marks)
Answer any FIVE questions.
All questions carry equal marks.
Answer any FIVE questions.
All questions carry equal marks.
13. How are projects categorized based on their size? Explain.
14.Describe the phased life-cycle model.
15.Discuss about algorithmic cost models.
16.List the relational notations used for software requirement specification and explain.
17.What are coupling and cohesion? Discuss.
18.Explain the do's and don'ts of good coding style.
19.Discuss about unit testing and debugging.
14.Describe the phased life-cycle model.
15.Discuss about algorithmic cost models.
16.List the relational notations used for software requirement specification and explain.
17.What are coupling and cohesion? Discuss.
18.Explain the do's and don'ts of good coding style.
19.Discuss about unit testing and debugging.
Section – C (3 * 10 = 30 marks)
Answer any THREE questions.
All questions carry equal marks.
Answer any THREE questions.
All questions carry equal marks.
20.List and explain the factors that influence quality and productivity of software.
21.Describe the format and contents of software requirement specification.
22.Explain the fundamental software design concepts.
23.Discuss the issues related with structured coding techniques.
24.How are walkthroughs and inspections conducted? Explain.
21.Describe the format and contents of software requirement specification.
22.Explain the fundamental software design concepts.
23.Discuss the issues related with structured coding techniques.
24.How are walkthroughs and inspections conducted? Explain.
Subject Name: Software Testing
Month & Year: November & 2011
Subject Code : SAZ6C
Year: Third
Semester: VI
Time : Three Hours
Maximum : 75 marks
SECTION A - (10 * 2 = 20 marks)
Answer any TEN questions.
All questions carry equal marks.
1. Define Software.
2. Give the purpose of testing.
3. Why bug arises?
4. What is meant by a graph?
5. How to prepare the format for the test plan?
6. Define test cases.
7. Mention the types of testing.
8. Why testing is difficult?
9. Give the expansion for SQA.
10.Define path.
11.How error differs from a bug.
12.Give any two importances of decision tables.
SECTION B - (5 * 5 = 25 marks)
Answer any FIVE questions.
All questions carry equal marks.
13. How to maintain the quality in software?
14. Explain the technique of creating design styles.
15. What is meant by path instrumentation?
16. Explain the concept of path testing.
17. Give the importance of domain testing.
18. Explain the concept of structural metrics.
19. How decision tables can be used for logic testing?
SECTION C - (3 * 10 = 30 marks)
Answer any THREE questions.
All questions carry equal marks.
20. What is a bug? Discuss on its types.
21. Discuss on transaction flow testing techniques.
22. How data flow testing strategies can be strengthened?
23. With an example, show how syntax testing is done.
24. Discuss the following:
a. Transition testing
b. State testing
Month & Year: November & 2011
Subject Code : SAZ6C
Year: Third
Semester: VI
Time : Three Hours
Maximum : 75 marks
SECTION A - (10 * 2 = 20 marks)
Answer any TEN questions.
All questions carry equal marks.
1. Define Software.
2. Give the purpose of testing.
3. Why bug arises?
4. What is meant by a graph?
5. How to prepare the format for the test plan?
6. Define test cases.
7. Mention the types of testing.
8. Why testing is difficult?
9. Give the expansion for SQA.
10.Define path.
11.How error differs from a bug.
12.Give any two importances of decision tables.
SECTION B - (5 * 5 = 25 marks)
Answer any FIVE questions.
All questions carry equal marks.
13. How to maintain the quality in software?
14. Explain the technique of creating design styles.
15. What is meant by path instrumentation?
16. Explain the concept of path testing.
17. Give the importance of domain testing.
18. Explain the concept of structural metrics.
19. How decision tables can be used for logic testing?
SECTION C - (3 * 10 = 30 marks)
Answer any THREE questions.
All questions carry equal marks.
20. What is a bug? Discuss on its types.
21. Discuss on transaction flow testing techniques.
22. How data flow testing strategies can be strengthened?
23. With an example, show how syntax testing is done.
24. Discuss the following:
a. Transition testing
b. State testing