UGC NET Computer Science Software Engineering Previous Year Questions (PYQs) – Page 3 of 11
A Place for Latest Exam wise Questions, Videos, Previous Year Papers,
Study Stuff for MCA Examinations
Study Stuff for MCA Examinations
Showing 109 questions
Fault base testing technique is
1
2
3
4
Solution
Fault based testing is a testing technique in which artificial faults are introduced into a program.
The purpose is to check whether the test cases are strong enough to detect those faults.
Mutation testing follows this idea.
In mutation testing, small changes are made in the program to create mutants.
If test cases detect these mutants, then the test cases are considered effective.
Now check the options:
Unit testing checks individual modules.
Beta testing is done by real users before final release.
Stress testing checks system behavior under heavy load.
Mutation testing is a fault based testing technique.
The purpose is to check whether the test cases are strong enough to detect those faults.
Mutation testing follows this idea.
In mutation testing, small changes are made in the program to create mutants.
If test cases detect these mutants, then the test cases are considered effective.
Now check the options:
Unit testing checks individual modules.
Beta testing is done by real users before final release.
Stress testing checks system behavior under heavy load.
Mutation testing is a fault based testing technique.
Alpha and Beta testing are forms of
1
2
3
4
Solution
Alpha testing and Beta testing are performed to check whether the software is acceptable to users.
Alpha testing is usually done at the developer side by internal users or testers.
Beta testing is done by real users in the real environment before final release.
Both are used to validate the software from the user's point of view.
Therefore, Alpha and Beta testing are forms of Acceptance Testing.
Now check the options:
White-Box Testing checks internal code structure.
Black-Box Testing checks functionality without seeing internal code.
System Testing checks the complete system.
Acceptance Testing checks whether the software is acceptable for final use.
Alpha testing is usually done at the developer side by internal users or testers.
Beta testing is done by real users in the real environment before final release.
Both are used to validate the software from the user's point of view.
Therefore, Alpha and Beta testing are forms of Acceptance Testing.
Now check the options:
White-Box Testing checks internal code structure.
Black-Box Testing checks functionality without seeing internal code.
System Testing checks the complete system.
Acceptance Testing checks whether the software is acceptable for final use.
For the software quality assurance, which of the followings are correct?
A. Execution of code
B. No execution of code
C. Preventive technique
D. A corrective technique
1
2
3
4
Solution
Software Quality Assurance (SQA):
• Focuses on process improvement
• Works as a preventive technique
• Usually involves reviews, audits and standards
• Does not require execution of code
Thus:
B → True
C → True
A → False
D → False (corrective is more related to debugging/testing)
The process to gather the software requirements from client, analyze and document is known as -
1
2
3
4
Solution
Requirement Engineering is the complete process of handling software requirements.
It includes:
Gathering requirements from the client
Analyzing requirements
Documenting requirements
Validating requirements
The question clearly mentions gathering, analyzing and documenting requirements.
So, this is not only requirement elicitation.
Requirement elicitation is only the activity of collecting requirements.
The complete process is called Requirement Engineering Process.
It includes:
Gathering requirements from the client
Analyzing requirements
Documenting requirements
Validating requirements
The question clearly mentions gathering, analyzing and documenting requirements.
So, this is not only requirement elicitation.
Requirement elicitation is only the activity of collecting requirements.
The complete process is called Requirement Engineering Process.
Given below are two statements:
Statement I: Quality control involves the series of inspections, reviews and tests used throughout the software process, to ensure each work product meets the requirements placed upon it.
Statement II: Quality assurance consists of auditing and reporting functions of management.
In the light of the above statements, choose the correct answer from the options given below:
Statement I: Quality control involves the series of inspections, reviews and tests used throughout the software process, to ensure each work product meets the requirements placed upon it.
Statement II: Quality assurance consists of auditing and reporting functions of management.
In the light of the above statements, choose the correct answer from the options given below:
1
2
3
4
Solution
Statement I is true.
Quality control is related to inspections, reviews and testing of software products.
Its main purpose is to check whether the work product satisfies the given requirements or not.
Statement II is also true.
Quality assurance is a management activity.
It includes auditing and reporting functions to ensure that proper software processes are being followed.
Therefore, both statements are true.
Quality control is related to inspections, reviews and testing of software products.
Its main purpose is to check whether the work product satisfies the given requirements or not.
Statement II is also true.
Quality assurance is a management activity.
It includes auditing and reporting functions to ensure that proper software processes are being followed.
Therefore, both statements are true.
Size and complexity are a part of
1
2
3
4
Solution
Software metrics are used to measure different aspects of software development.
Product metrics are related to the software product itself.
They measure properties such as:
Size of the software
Complexity of the software
Quality of the software
Performance of the software
Here, size and complexity describe the software product.
So, they are part of Product Metrics.
Now check the options:
People Metrics are related to team members.
Project Metrics are related to project cost, schedule and effort.
Process Metrics are related to software development process.
Product Metrics are related to software size, complexity and quality.
Product metrics are related to the software product itself.
They measure properties such as:
Size of the software
Complexity of the software
Quality of the software
Performance of the software
Here, size and complexity describe the software product.
So, they are part of Product Metrics.
Now check the options:
People Metrics are related to team members.
Project Metrics are related to project cost, schedule and effort.
Process Metrics are related to software development process.
Product Metrics are related to software size, complexity and quality.
An observational technique that can be used to understand operational process and help to derive requirement for software to support operational process is known as
1
2
3
4
Solution
Ethnography is an observational technique used to understand real work practices and operational processes.
Arrange the following so that they can be placed in perfect/appropriate order.
A. Planning
B. Construction
C. Modeling
D. Communication
E. Deployment
Choose the correct answer from the options given below:
1
2
3
4
Solution
Software development process:
Communication → Planning → Modeling → Construction → Deployment
Order:
$D \rightarrow A \rightarrow C \rightarrow B \rightarrow E$
Which Metrics are derived by normalizing quality and/or productivity measures by considering the size of the software that has been produced?
1
2
3
4
Solution
Size oriented metrics are derived by considering the size of the software product.
Usually, size is measured in terms of lines of code.
These metrics normalize quality and productivity measures using software size.
For example:
Productivity can be measured as output per line of code.
Quality can be measured as defects per line of code.
Since the question says that quality and/or productivity measures are normalized by considering the size of the software, it refers to Size Oriented Metrics.
Usually, size is measured in terms of lines of code.
These metrics normalize quality and productivity measures using software size.
For example:
Productivity can be measured as output per line of code.
Quality can be measured as defects per line of code.
Since the question says that quality and/or productivity measures are normalized by considering the size of the software, it refers to Size Oriented Metrics.
The model in which the requirements are implemented by its category is
1
2
3
4
Solution
In Iterative Enhancement Model, the complete system is not developed at once.
The requirements are divided into parts or categories.
Then each category of requirements is implemented step by step in different iterations.
After every iteration, the software is improved by adding new features or enhancing existing features.
Waterfall model follows a fixed sequence of phases.
Prototyping model focuses on making a prototype first.
Evolutionary model evolves the software with user feedback.
But implementing requirements category-wise is mainly related to Iterative Enhancement Model.
The requirements are divided into parts or categories.
Then each category of requirements is implemented step by step in different iterations.
After every iteration, the software is improved by adding new features or enhancing existing features.
Waterfall model follows a fixed sequence of phases.
Prototyping model focuses on making a prototype first.
Evolutionary model evolves the software with user feedback.
But implementing requirements category-wise is mainly related to Iterative Enhancement Model.
UGC NET Computer Science
Online Test Series, Information About Examination,
Syllabus, Notification
and More.
View More
UGC NET Computer Science
Online Test Series, Information About Examination,
Syllabus, Notification
and More.
View More
Ask Your Question or Put Your Review.
