KEMBAR78
Software Engineering Course File - 2025 | PDF | Conceptual Model | Unified Modeling Language
0% found this document useful (0 votes)
9 views19 pages

Software Engineering Course File - 2025

The document outlines the course structure and syllabus for the Software Engineering course for B.Tech III year CSE students at Sreenidhi Institute of Science & Technology. It includes course objectives, outcomes, detailed unit topics, and assessment methodologies. The course aims to equip students with knowledge of software engineering principles, lifecycle models, testing techniques, and practical exposure to testing tools.

Uploaded by

Ramu Pasam
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
9 views19 pages

Software Engineering Course File - 2025

The document outlines the course structure and syllabus for the Software Engineering course for B.Tech III year CSE students at Sreenidhi Institute of Science & Technology. It includes course objectives, outcomes, detailed unit topics, and assessment methodologies. The course aims to equip students with knowledge of software engineering principles, lifecycle models, testing techniques, and practical exposure to testing tools.

Uploaded by

Ramu Pasam
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
You are on page 1/ 19

SREENIDHI INSTITUTE OF SCIENCE & TECHNOLOGY

(AN AUTONOMOUS INSTITUTION UNDER JNTUH)


(Approved by AICTE & Aided by World Bank under TEQIP)
Yamnampet, Ghatkesar Mandal, Hyderabad - 501 301.

COURSE FILE
For

SOFTWARE ENGINEERING

For

B. Tech. III year - I Semester


CSE BRANCH

DEPARTMENT
OF
COMPUTER SCIENCE and ENGINEERING
2025
Syllabus for B.Tech (CSE) III YEAR I SEM
COMPUTER SCIENCE and ENGINEERING
SOFTWARE ENGINEERING
Code: 9EC03
Prerequisite: Database management systems
Course Objectives
 To understand the importance of software engineering lifecycle models in the
development of software
 To understand the various design principles in modeling software
 To Test software which adheres to the standard benchmarks
 To undergo Practical exposure on testing tools to meet current market value

Course Outcomes:
After completion of the course, the student should be able to
1. Students can able to identify software process and software engineering practices to
select and justify approaches for a given project and its constraints and distinguish
lifecycles for developing software product.
2. Students know what and how to gather the requirements for a project and able to
prepare requirement document
3. Students understand the importance and principles of Unified Modeling Language, its
building blocks and to relate UML paradigm for problem solving.
4. Students can able to understand what is testing and format for writing test cases for
different applications
5. Students can able to measure a software quality by using different metrics during whole
software development life cycle
6. Students can able to know different testing techniques and their significance

UNIT I
Introduction to Software Engineering: The evolving role of software, Changing Nature of
Software, Characteristics of Software, Software myths.
A Generic view of Process: Software engineering- A layered technology, a Process
framework. The Capability Maturity Model – Integrated (CMM-I)

UNIT II
Software Requirements: Functional and Non-functional Requirements, User Requirements,
System Requirements, the Software Requirements Document.
Requirements engineering process: Feasibility studies, requirements elicitation and analysis,
requirements validation, Requirements management, RTM
Process Models: Software Development Life Cycle, The waterfall model, Incremental
Process models, RAD Model, Unified Process Model, Evolutionary Process models
(Prototype Model, Spiral Model, Concurrent Development Model, V-Model, Agile Model)

UNIT III
Introduction to UML: Importance of Modeling, Principles of Modeling, Conceptual model of
the UML, Architecture, Diagrams: Class Diagrams, Forward and Reverse engineering for
class Diagram. Use case Diagrams, Sequence Diagram,
UNIT IV
Testing: What is Testing, Characteristics of Test Engineers, Software Testing Life Cycle,
Levels of Testing, Testing Approaches, Test Cases: Format for Writing Test Case, Test plan:
Format to prepare Test plan Purpose of testing, Dichotomies, Consequences of bugs

UNIT V
Flow graphs and Path testing: Basics concepts of path testing
Data Flow Testing: Basics of Data Flow Testing Logic Based Testing: Decision Tables
Software Metrics: Software Quality, Metrics for Analysis Model, Metrics for Design Model,
Metrics for source code, Metrics for testing, Metrics for maintenance

UNIT VI
Software Testing Techniques: Black-box Testing, White box testing, Gray box Testing,
Boundary Value Analysis, Regression Testing, Cause Effect graphing, CRUD, Database,
Mutation Testing, Random Testing, Performance testing, Stress Testing, Spike Testing,
Accepting Testing, Alpha and Beta Testing, V& V
Automated Testing Tools: Need for Automated testing tools, Taxonomy of Testing Tools,
Exposure to Software Testing Tools: Selenium, UFT

TEXT BOOKS
1. Software Engineering, A Practitioner‘s Approach- Roger S. Pressman, 6th edition.
McGraw-Hill International Edition. (Unit 1, 2, 5)
2. Grady Booch, James Rumbaung, Ivar Jacobson: The Unified Modeling Language User
Guide, Pearson Education.(Unit 3)
3. Software testing techniques – Boris Beizer, Dreamtech, second edition.(Unit 4,5,6, Refer
Internet)

REFERENCES:
1. Software Testing and continuous Quality Improvement, by William
E.Lewis,Gunasekaran,2nd Edition Auerbach publications (Unit 6,Refer Internet)
2. Software testing tools – by Dr. K.V.K.K Prasad Dreamtech (Unit 4)
3. Software Engineering- Sommerville, 7th edition, Pearson education.
4. Software Engineering- K.K. Agarwal & Yogesh Singh, New Age International Publishers
5. Software Engineering, an Engineering approach- James F. Peters, WitoldPedrycz, John
Wiely.
6. Systems Analysis and Design- Shely Cashman Rosenblatt,Thomson Publications.
7. Software Engineering principles and practice- Waman S Jawadekar, The McGraw-Hill
Companies
8. Meilir Page-Jones: Fundamentals of Object Oriented Design in UML, Pearson Education.
9. Pascal Roques: Modeling Software Systems Using UML2, WILEY-Dreamtech India Pvt.
Ltd.
10. AtulKahate: Object Oriented Analysis & Design, The McGraw-Hill Companies.
11. Mark Priestley: Practical Object-Oriented Design with UML,TATA McGrawHill
12. Craig Larman Appling UML and Patterns: An introduction to Object – Oriented Analysis
and Design and Unified Process, Pearson Education
13. Hans-Erik Eriksson, Magnus Penker, Brian Lyons, David Fado: UML 2 Toolkit,
WILEYDreamtech India Pvt. Ltd
COURSE INFORMATION SHEET

PROGRAMME: B. Tech. (CSE) DEGREE: B.TECH


COURSE: Software Engineering YEAR/SEMESTER: III/ I CREDITS: 2
COURSE CODE: 9EC03 REGULATION: A22 COURSE TYPE: CORE
COURSE AREA/DOMAIN: Software Engineering CONTACT HOURS: 2 hours/Week
CORRESPONDING LAB COURSE CODE (IF ANY): LAB COURSE NAME: Software Engineering lab
9EC63

SYLLABUS:

UNIT DETAILS HOURS


I Introduction to Software Engineering: The evolving role of software,
Changing Nature of Software, Characteristics of Software, Software
myths.
A Generic view of Process: Software engineering- A layered 9
technology, a Process framework. The Capability Maturity Model–
Integrated (CMM-I)

II Software Requirements: Functional and Non-functional Requirements,


User Requirements, System Requirements, the Software Requirements
Document. Requirements engineering process: Feasibility studies,
requirements elicitation and analysis, requirements validation,
Requirements management, RTM 8
Process Models: Software Development Life Cycle, The waterfall
model, Incremental Process models, RAD Model, Unified Process
Model, Evolutionary Process models (Prototype Model, Spiral Model,
Concurrent Development Model, V-Model, Agile Model)
III Introduction to UML: Importance of Modeling, Principles of Modeling,
Conceptual model of the UML, Architecture, 10
Diagrams: Class Diagrams, Forward and Reverse engineering for class
Diagram. Use case Diagrams, Sequence Diagram,
IV Testing: What is Testing, Characteristics of Test Engineers, Software
Testing Life Cycle, Levels of Testing, Testing Approaches, Test Cases: 7
Format for Writing Test Case, Test plan: Format to prepare Test plan
Purpose of testing, Dichotomies, Consequences of bugs
V Flow graphs and Path testing: Basics concepts of path testing
Data Flow Testing: Basics of Data flow Testing Logic Based Testing:
Decision Tables 11
Software Metrics: Software Quality, Metrics for Analysis Model,
Metrics for Design Model, Metrics for source code, Metrics for testing,
Metrics for maintenance
VI Software Testing Techniques: Black-box Testing, White box testing,
Gray box Testing, Boundary value Analysis, Regression Testing, Cause
Effect graphing, CRUD, Database, Mutation Testing, Random Testing,
Performance testing, Stress Testing, Spike Testing, Accepting Testing, 13
Alpha and Beta Testing , V& V
Automated Testing Tools: Need for Automated testing tools,
Taxonomy of Testing Tools, Exposure to Software Testing Tools:
Selenium, UFT
TOTAL HOURS 57
Tutorial Classes 00
Mid Tests 02
Classes for related topics beyond syllabus 05
Remedial Classes/NPTL 00
TOTAL NUMBER OF CLASSES 64
TEXT/REFERENCE BOOKS:
T/R BOOK TITLE/AUTHORS/PUBLICATION

Text Book Software Engineering, A Practitioner‘s Approach- Roger S. Pressman, 6th


edition. McGraw-Hill International Edition.
Text Book Grady Booch, James Rumbaung, Ivar Jacobson: The Unified Modeling
Language User Guide, Pearson Education.
Text Book Software testing techniques – Boris Beizer, Dreamtech, second edition.
Reference Book Software testing tools – by Dr. K.V.K.K Prasad Dreamtech
Reference Book Software Engineering- Sommerville, 7th edition, Pearson education.
Reference Book AtulKahate: Object Oriented Analysis & Design, The McGraw-Hill Companies.

Programme Outcomes:

a. An ability to apply knowledge of basic sciences, mathematics and engineering in the area
of Computer Science.
b. An ability to design, implement and evaluate a software or software / hardware system to
meet the desired needs within realistic constraints such as space and time.
c. An ability to use the techniques, skills, and modern engineering tools such as software
testing tools, data warehousing and mining tools, necessary for practice as a CSE
professional.
d. An ability to analyze and solve open-ended problems using mathematical foundations,
algorithmic principles, and computer science theory in the modeling and design of computer-
based systems in a way that demonstrates comprehension of the tradeoffs involved in design
choices and to arrive at an optimal solution.
e. To understand principles of engineering, entrepreneurship with emphasis on women, and
financial management through relevant management courses to demonstrate knowledge in
the conceptualization and realizing group projects, mini & main projects.
f. An ability to function effectively as individual and as a member or leader in diverse team
in achieving multidisciplinary tasks.
g. Learn to communicate effectively on complex engineering activities through report
writing, experimental work, assignments, seminars, group projects, mini & main projects.
h. To recognize the need for and have the preparation and ability to be a life-long learner
through the courses such as seminars & projects.
i. An ability to identify, formulate and analyze engineering problems.
j. An ability to conduct investigation of complex problems in multidisciplinary areas.
k. An understanding of professional ethics and responsibilities.
l. An engineer should be aware of social, safety, cultural and information security issues
and also responsibilities relevant to professional practice and skills.
m. An ability to understand the impact of environmental protection and sustainable
development.

Programme Educational Objectives:

A. Graduates of the program will have requisite engineering knowledge with abilities for
analysis of the problem and to design, development of solutions and to arrive at an optimal
solution using modern tools which help them to be employable.
B. Ability to work in a team/ lead a team which needs effective communication skills and
knowledge of project management, finance and entrepreneurial abilities.
C. Graduates should have abilities to conduct investigation of complex problems and
attitude for lifelong learning skills which will enable them to pursue advanced studies,
Research and Development.
D: The graduates must be aware of the engineering professional ethics, the impact of
engineering profession on the society and the need for environmental protection and
sustainable development.-
Course Objectives, Course Outcomes

COURSE OBJECTIVES:
1. To understand the importance of software engineering lifecycle models in the
2. development of software
3. To understand the various design principles in modeling a software
4. To Test a software which adheres to the standard benchmarks
5. To undergo Practical exposure on testing tools to meet current market value

COURSE OUTCOMES:

SNO DESCRIPTION PO
MAPPING
1 Students can able to identify software process and software engineering a , b,c,f
practices to select and justify approaches for a given project and its
constraints and distinguish lifecycles for developing software product.
2 Students know what and how to gather the requirements for a project and a,b,c,d
able to prepare requirement document
3 Students understand the importance and principles of Unified Modeling a,b.c d, .i
Language, its building blocks and to relate UML paradigm for problem
solving.
4 Students can able to understand what is testing and format for writing test a,b,c,i,l
cases for different applications
5 Students can able to measure a software quality by using different metrics
during whole software development life cycle
6 Students can able to know different testing techniques and their
significance

TOPICS BEYOND SYLLABUS/ADVANCED TOPICS/DESIGN:


1 Software automation and Testing Guest Lecture
2 Software Testing tools( commercial and open source tools) Class teaching
cum guest
lecture

WEB SOURCE REFERENCES:


S. No. Name of Book / Website
1. http://www.etestinghub.com/
2. http://www.softwaretestingtimes.com/2010/04/software-testing-tutorials-for.html
3. http://www.slideshare.net/ketanmehta4u/software-testing
4. http://www.softwaretestingclass.com/software-testing-tools-list/
5. Effective Methods for Software Testing, 2nd Edition by William E.Perry, Wiley publications.

6. Handbook of Software Quality Assurance, by G.Gordon Schulmeyer,James I.McManus,2nd Edition,


International Thomson Computer Press

DELIVERY/INSTRUCTIONAL METHODOLOGIES:

CHALK & TALK -yes ☐ STUD. ☐ WEB RESOURCES –


ASSIGNMENT- yes yes
LCD/SMART BOARDS - ☐ STUD. SEMINARS - ☐ ADD-ON COURSES –
yes yes yes

ASSESSMENT METHODOLOGIES-DIRECT

☐ ASSIGNMENTS -yes ☐ STUD. SEMINARS - ☐ TESTS/MODEL ☐ UNIV.


yes EXAMS -yes EXAMINATION -yes
☐ STUD. LAB ☐ STUD. VIVA ☐ MINI/MAJOR ☐ CERTIFICATIONS
PRACTICES PROJECTS
☐ ADD-ON COURSES- ☐ OTHERS
yes

ASSESSMENT METHODOLOGIES-INDIRECT

☐ ASSESSMENT OF COURSE OUTCOMES (BY ☐ STUDENT FEEDBACK ON FACULTY


FEEDBACK, ONCE) -yes (TWICE) -yes
☐ ASSESSMENT OF MINI/MAJOR PROJECTS BY ☐ OTHERS
EXT. EXPERTS
Mapping onto PEO & PO
PO’s:
a) An ability to apply knowledge of basic sciences, mathematics and engineering in the area
of Computer Science.
b) An ability to design, implement and evaluate a software or software / hardware system to
meet the desired needs within realistic constraints such as space and time.
c) An ability to use the techniques, skills, and modern engineering tools such as software
testing tools, data warehousing and mining tools, necessary for practice as a CSE
professional.
d) An ability to analyze and solve open-ended problems using mathematical foundations,
algorithmic principles, and computer science theory in the modeling and design of
computer-based systems in a way that demonstrates comprehension of the tradeoffs
involved in design choices and to arrive at an optimal solution.
e) To understand principles of engineering, entrepreneurship with emphasis on women, and
financial management through relevant management courses to demonstrate knowledge
in the conceptualization and realizing group projects, mini & main projects.
f) An ability to function effectively as individual and as a member or leader in diverse team
in achieving multidisciplinary tasks.
g) Learn to communicate effectively on complex engineering activities through report
writing, experimental work, assignments, seminars, group projects, mini & main projects.
h) To recognize the need for and have the preparation and ability to be a life-long learner
through the courses such as seminars & projects.
i) An ability to identify, formulate and analyze engineering problems.
j) An ability to conduct investigation of complex problems in multidisciplinary areas.
k) An understanding of professional ethics and responsibilities.
l) An engineer should be aware of social, safety, cultural and information security issues
and also responsibilities relevant to professional practice and skills.
m) An ability to understand the impact of environmental protection and sustainable
development.

PEO’s:
A. Graduates of the program will have requisite engineering knowledge with abilities for
analysis of the problem and to design, development of solutions and to arrive at an
optimal solution using modern tools which help them to be employable.
B. Ability to work in a team/ lead a team which needs effective communication skills
and knowledge of project management, finance and entrepreneurial abilities.
C. Graduates should have abilities to conduct investigation of complex problems and
attitude for lifelong learning skills which will enable them to pursue advanced
studies, Research and Development.
D. The graduates must be aware of the engineering professional ethics, the impact of
engineering profession on the society and the need for environmental protection and
sustainable development.

Programme Outcomes
PEOs
a b c d e f g h i j k l m
A     
B   
C   
D   
Model Lesson Plan
SOFTWARE ENGINEERING
Lecture Schedule
Unit – I
S.No. No. of Lectures Name of the Topic
Introduction Software Engineering. The
1 1 evolving role of software,
Changing Nature of Software,
2 2 Characteristics of Software,
3 2 Software myths.
A Generic view of Process: Software
4 1 engineering- A layered technology,
5 1 a Process framework
The Capability Maturity Model – Integrated
6 2 (CMM-I)
Unit – II
7 1 Introduction to Software Requirements
Functional and Non-functional
8 1 Requirements,
User Requirements, System Requirements,
9 2 the Software Requirements Document.
introduction to Requirements engineering
10 1 process
Feasibility studies, requirements elicitation
11 1 and analysis,
requirements validation, Requirements
management, RTM
12 1
Process Models: Software Development Life
13 2 Cycle, The waterfall model,
Incremental Process models, RAD Model,
15 2 Unified Process Model,
introduction to Evolutionary Process
16 1 models
Unit –III
17 2 Introduction to UML
Importance of Modeling, Principles of
18 1 Modeling
Conceptual model of the UML,
19 2 Architecture,.
Class Diagrams, Forward and Reverse
20 1 engineering for class Diagram
21 2 Use case Diagrams, Sequence Diagram,

Unit –IV
22 1 Introduction to Testing
What is Testing, Characteristics of Test
23 1 Engineers,
Software Testing Life Cycle, Levels of
24 1 Testing,
25 1 Testing Approaches,
26 1 Test Cases: Format for Writing Test Case,
27 1 Test plan: Format to prepare Test plan
28 1 Purpose of testing, Dichotomies,
29 1 Consequences of bugs
Unit – V
Introduction to Flow graphs and Path
30 1 testing
31 1 Basics concepts of path testing
Data Flow Testing: Basics of Data flow
32 1 Testing
33 1 Logic Based Testing: Decision Tables
Software Metrics: Software Quality, Metrics
34 1 for Analysis Model
Metrics for Design Model, Metrics for
35 2 source code,
Metrics for testing, Metrics for
36 1 maintenance
Unit – VI
introduction to Software Testing
37 1 Techniques
Black-box Testing, White box testing, Gray
38 1 box Testing,
Boundary value Analysis, Regression
39 2 Testing,
40 1 Cause Effect graphing, CRUD, Database,
Mutation Testing , Random Testing,
Performance testing, Stress Testing, Spike
41 2 Testing
Accepting Testing, Alpha and Beta Testing ,
42 1 V& V
Automated Testing Tools: Need for
43 1 Automated testing tools
44 1 Taxonomy of Testing Tools,
Exposure to Software Testing Tools:
45 2 Selenium,UFT
Total Number of classes Required:9+12+8+8+8+12=57
Software Engineering
Unit-1
Quiz Questions
1. Define Software.
2. List Software Characteristics.
3. What is reusability?
4. List Applications of Software.
5. List Management myths.
6. List customer myths.
7. Diagrammatically represent software engineering layers.
8. Define Software Engineering.
9. Write about the maintenance phase.
10. Diagrammatically represent the software process.
11. List the five process maturity levels.

Essay Questions
1. Discuss the evolving role of software.
2. Discuss software characteristics.
3. Discuss software applications.
4. Discuss software myths.
5. What is the software process? What are the process maturity levels?

Software Engineering
Unit-II
Quiz Questions
1. Write Functional Requirements
2. Write Non-functional Requirements
3. Define User Requirements
4. Define System Requirements
5. Define Interface specification
6. Define the Software Requirements Document.
7. Define requirement management.
8. What is software design?
9. Write a note on design and software quality?
10. Write a note on design process.
11. Discuss the various design concepts.
12. Write a note on functional independence.
13. Write a note on Design Heuristics for Effective modularity.
14. Write a note on design documentation.
15. Write a note on Data Design
16. Write a note on Transform mapping.
17. Discuss transaction mapping.

Essay Questions
1. Write a note on feasibility studies
2. Write a note on waterfall model
3. Write a note on Incremental Process models
4. Write a note on Evolutionary Process models.
5. Write a note on structured methods
6. Write a note on requirements elicitation
7. Write a note on requirements validation

Software Engineering
Unit-III
Quiz Questions

1. What is a class and object?


2. What is an attribute and operation?
3. What is encapsulation?
4. How do you identify objects and classes?
5. What is polymorphism?
6. What is the importance of modeling?
7. What are the principles of modeling?
8. What are the basic things in UML?
9. What are the common mechanisms in UML?
10. What are the rules of UML?
11. What are the various kinds of diagrams in UML?
12. Identify the S/W development life cycle using UML?
13. What is generalization relationship?
14. What is realization, extensibility relationship?
15. How do you represent roles of objects in UML?
16. Identify the basic rules in UML.
17. What is the importance of modeling
18. What are the various relationships identified in UML
19. What is the importance of object oriented techniques.
20. Identify the various diagrams in UML.
21. How do you identify the objects in UML?
22. Identify various types of things in UML.
23. Write short notes for Advanced classes
24. Write short notes for Advanced Relationships
25. Define Interfaces
26. Define Types and Roles
27. Define Packages.
28. Define Class
29. Define Object
30. What are the various types of sequencing that can be used in sequence diagram?
31. What is the difference between sequence & collaboration diagrams?
32. What are the various types of interaction diagrams in UML?
33. What is the use of self-in loops in interaction diagrams?
34. What are the various types of messages that can be depicted in collaboration diagrams?
35. Identify the things contained in interaction diagrams?
36. List the various types of sequencing that can be used in sequence diagram?
37. Differentiate between sequence & collaboration diagrams?
38. Identify the various types of interaction diagrams in UML?
39. What is the importance of self-in loops in interaction diagrams?
40. Identify the various types of messages that can be depicted in collaboration diagrams?
41. What are the things contained in a use case diagram?
42. What is an activity diagram?
43. What are the things that are contained in activity diagrams?
44. What is meant by forking and joining?
45. What is the use of swim lanes in activity diagrams?
46. How do you model object flow in activity diagrams?
47. Identify the use of swim lanes in activity diagrams?
48. Trace the object flow model in activity diagrams?

Essay Questions
1. Explain in detail the different kinds of things in UML?
2. Explain in detail Data Abstraction, Information Hiding, Encapsulation and
Polymorphism?
3. Explain in detail the need for modeling?
4. Explain the principles of modeling in detail?
5. Describe the conceptual model for UML?
6. Enumerate the advanced relationships that can be used in UML in detail.
7. Discuss about the advanced classes in UML?
8. Explain the packages and how to integrate classes in a package diagram.
9. Design a class diagram for student information system?
10. Explain terms and concepts of class diagrams
11. Explain Forward and Reverse engineering for class diagram.
12. Explain Forward and Reverse engineering for object diagram.
13. Explain in detail about the various interaction diagrams that can be used to represent
the dynamic aspects of a system.
14. Explain the terms, concepts, difference between sequence and collaboration
diagrams?
15. How do you depict various types of messages in sequence diagrams?
16. How do you model the flow of control in interaction diagrams?
17. Design a use case diagram for online Bookstore example.
18. Describe the activities of an activity diagram using swim lanes forks and joins
Software Engineering
Unit-IV
Quiz Questions
1. Define Testing?
2. Explain the characteristics of Testing?
3. Who are involved in Testing?
4. Define Test Case?
5. What is the Test Plan?
6. Give the Levels of Testing?
7. In Requirement phase, what are the different validation activities to be performed?
8. What is the difference between the Testing and Debugging?
9. In Test phase, what are the different validation activities to be performed?
10. In Program phase, what are the different validation activities to be performed?
11. In Maintenance phase, what are the different validation activities to be performed?
12. Give the IEEE format to prepare the test cases?
13. Define bug?
14. What is the difference between normal SDLC and SDLC Testing?
15. What are the goals of Testing?
16. What are Different phases of Testing?

Essay Questions
1. What is the purpose of testing? List out the various dichotomies and explain.
2. What are the principles of test case design? Explain.
3. What is meant by Software Testing? Discuss clearly the purpose of testing.
4. Discuss in detail various phases in a Tester’s Mental life.
5. Explain the importance of bugs.
6. Write the test plan document for known application.
7. What is test case? Write the test cases to validate the ATM CARD.
8. Discuss in detail how the consequences of bugs are measured?
9. What are the possible consequences of bugs?
10. Explain in details the factors on which the importance of bugs depend
11. Explain Software Testing Life Cycle (STLC)
Software Engineering
Unit-V
Quiz Questions
1. Define Path Testing.
2. What is Statement Coverage?
3. Define Branch Coverage?
4. What is Data flow Testing?
5. What is Decision Tables?
6 Define Predicate and Path Predicate?
7. Define the term Module.
8. What is the accumulated cost for normal SDLC and SDLC testing? Which one is
preferable?

Essay Questions
1. Compare and contrast between control flow graphs and flow charts.
2. Give a detailed note on path testing.
3. Explain applications of paths, path products and regular expressions.
4. What is meant by statement coverage and branch coverage?
5. Discuss the role of decision table in a test case design.
6. Explain in Details about Data flow testing with neat sketch.
7. Explain the expansion of the immaterial cases in the decision table?
8. Compare and contrast between control flow graphs and flow charts.
9. Give a detailed note on path testing.
10. Explain applications of paths, path products and regular expressions.
11. What is meant by statement coverage and branch coverage?
12. Discuss the role of decision table in a test case design.
13. Explain in Details about Data flow testing with neat sketch
14. Explain the expansion of the immaterial cases in the decision table. ?
.
.

Software Engineering
Unit-VI
Quiz Questions
1. What is black box testing?
2. What are the advantages of Black box testing?
3. Black box testing is done by whom?
4. What is white box testing?
5. What is the difference between white box and black box testing?
6. Black box testing also known as?
7. What is gray box testing?
8. What is white box testing?
9. What is Sandwitch testing?
10. What is performance testing?
11. Abbreviate BVA and EP?
12. What is incremental integration testing?
13. What is Regression Testing?
14. What is Alpha and Beta Testing?
15. What is bottom-up integration testing?
16. What is top-down integration testing?
17 Define the term ‘UNIT TESTING’.
18 Define the term ‘COMPONENT TESTING’.
19 Define the term ‘INTEGRATION TESTING’.
20 Define the term ‘SYSTEM TESTING’
21 What is Automation?
22 Advantages of Automation testing?
23. Differences between Manual and Automation testing?
24 What are the different bug tracking tools?
25. What are the different test management tools?

Essay Questions
1. Explain different software testing techniques?
2. Explain the below terms
i) White box testing ii) Black box testing iii) Gray box testing
3. Explain Cause Effect Graphing with suitable example?
4. What is integration testing? And explain the different types of integration testing?
5. Abbreviate CRUD and Explain?
6. Give the brief note for the following
a) Alpha Testing b) Beta Testing c) Stress Testing d) Spike Testing
7. What is Regression Testing? And explain different Regression Testing Tools used to perform
Regression Testing?
8. Explain the Different Categories of Testing Tools available in Market?
9. Explain the Methodology to Evaluate Automated Testing Tools?
10. Majority of testing is done manually why? What is the difference between manual testing
and Automation testing?

You might also like