Software Maintenance Questions and Answers

Q: Which is not a factor influencing system release strategy ?

Verification is not one of the factors.Sommerville lists factors that influence the system release strategy: the technical quality of the system, platform changes, Lehman's fifth law (the incremental change in each release is roughly constant), competition, marketing requirements and customer change proposals.Verification is part of development and testing, done for every release, rather than a factor deciding when or what to release.

Q: Reverse engineering differs fundamentally from reengineering because reverse engineering

Reverse engineering generates higher-level abstractions from existing lower-level artifacts.In the standard definitions of Chikofsky and Cross, reverse engineering analyses an existing system to identify its components and relationships and to create representations at a higher level of abstraction, such as recovering a design or data model from code. It is a process of examination only; the system is not changed. Reengineering goes further: it alters the system to rebuild it in a new form, usually by reverse engineering followed by restructuring and forward engineering.Option A describes restructuring, option B describes forward engineering, and option D describes reengineering or maintenance. All three change or produce code, which reverse engineering does not do.

Q: In the context of software engineering, what is "refactoring" ?

Refactoring is modifying code to improve performance or readability without changing its functionality.Refactoring restructures existing code, for example renaming, extracting methods or removing duplication, to make it cleaner and easier to maintain, while its external behaviour stays the same. Tests are run before and after to confirm nothing changed.Adding or removing features changes the functionality, and rewriting the entire software is a rewrite, not a refactoring.

Q: Which of the following is a type of software maintenance ?

The answer is All of the above.Software maintenance is usually classified into corrective maintenance (fixing faults found after delivery), adaptive maintenance (changing the software to work in a new environment, such as a new operating system), perfective maintenance (improving performance or adding requested features) and preventive maintenance.All three named in the options are recognised types, so no single one is the complete answer.

Q: Which maintenance type involves modifying software to improve performance or maintainability without changing functionality ?

This is perfective maintenance.Perfective maintenance improves software that already works correctly: making it faster, easier to maintain or easier to use, and adding refinements, without being forced by a fault or a change in environment.Corrective maintenance fixes faults found in use. Adaptive maintenance changes the software to suit a new environment, such as a new operating system or new regulations. Preventive maintenance restructures software to head off future problems; it is the near miss here, but the key follows the standard definition, which places improving performance and maintainability under perfective maintenance.

Q: Which type of software maintenance involves fixing bugs discovered after deployment ?

Fixing bugs found after deployment is corrective maintenance.Corrective maintenance diagnoses and repairs faults that users report once the software is in use: errors in logic, coding or design that testing missed.Adaptive maintenance changes the software to fit a new environment, perfective maintenance improves performance or adds refinements, and preventive maintenance restructures the software to stop problems appearing later. None of these is about correcting faults already found.

Which is not a factor influencing system release strategy ?

A.Technical quality of the system
B.Platform changes
C.Lehman's fifth law
D.Verification

Exam Year(s)

MH SET - 2024, SET Exam - 2024,

Answer: D

Verification is not one of the factors.

Sommerville lists factors that influence the system release strategy: the technical quality of the system, platform changes, Lehman's fifth law (the incremental change in each release is roughly constant), competition, marketing requirements and customer change proposals.

Verification is part of development and testing, done for every release, rather than a factor deciding when or what to release.

Discuss in Forum

Reverse engineering differs fundamentally from reengineering because reverse engineering

A.Modifies the internal design while preserving external functionality
B.Converts conceptual designs into operational code
C.Generates higher-level abstractions from existing lower-level artifacts
D.Replaces obsolete modules with optimized versions

Exam Year(s)

Tripura Public Service Commission - 2026,

Answer: C

Reverse engineering generates higher-level abstractions from existing lower-level artifacts.

In the standard definitions of Chikofsky and Cross, reverse engineering analyses an existing system to identify its components and relationships and to create representations at a higher level of abstraction, such as recovering a design or data model from code. It is a process of examination only; the system is not changed. Reengineering goes further: it alters the system to rebuild it in a new form, usually by reverse engineering followed by restructuring and forward engineering.

Option A describes restructuring, option B describes forward engineering, and option D describes reengineering or maintenance. All three change or produce code, which reverse engineering does not do.

Discuss in Forum

In the context of software engineering, what is "refactoring" ?

A.Adding new features to the software
B.Removing unnecessary features from the software
C.Modifying code to improve performance or readability without changing its functionality
D.Rewriting the entire software

Exam Year(s)

Tripura Public Service Commission - 2025,

Answer: C

Refactoring is modifying code to improve performance or readability without changing its functionality.

Refactoring restructures existing code, for example renaming, extracting methods or removing duplication, to make it cleaner and easier to maintain, while its external behaviour stays the same. Tests are run before and after to confirm nothing changed.

Adding or removing features changes the functionality, and rewriting the entire software is a rewrite, not a refactoring.

Discuss in Forum

Which of the following is a type of software maintenance ?

A.Corrective maintenance
B.Adaptive maintenance
C.Perfective maintenance
D.All of the above

Exam Year(s)

Tripura Public Service Commission - 2025,

Answer: D

The answer is All of the above.

Software maintenance is usually classified into corrective maintenance (fixing faults found after delivery), adaptive maintenance (changing the software to work in a new environment, such as a new operating system), perfective maintenance (improving performance or adding requested features) and preventive maintenance.

All three named in the options are recognised types, so no single one is the complete answer.

Discuss in Forum

Which maintenance type involves modifying software to improve performance or maintainability without changing functionality ?

A.Corrective maintenance
B.Adaptive maintenance
C.Perfective maintenance
D.Preventive maintenance

Exam Year(s)

Tripura Public Service Commission - 2026,

Answer: C

This is perfective maintenance.

Perfective maintenance improves software that already works correctly: making it faster, easier to maintain or easier to use, and adding refinements, without being forced by a fault or a change in environment.

Corrective maintenance fixes faults found in use. Adaptive maintenance changes the software to suit a new environment, such as a new operating system or new regulations. Preventive maintenance restructures software to head off future problems; it is the near miss here, but the key follows the standard definition, which places improving performance and maintainability under perfective maintenance.

Discuss in Forum

Which type of software maintenance involves fixing bugs discovered after deployment ?

A.Adaptive
B.Perfective
C.Corrective
D.Preventive

Exam Year(s)

Tripura Public Service Commission - 2026,

Answer: C

Fixing bugs found after deployment is corrective maintenance.

Corrective maintenance diagnoses and repairs faults that users report once the software is in use: errors in logic, coding or design that testing missed.

Adaptive maintenance changes the software to fit a new environment, perfective maintenance improves performance or adds refinements, and preventive maintenance restructures the software to stop problems appearing later. None of these is about correcting faults already found.

Discuss in Forum

Loading…

Topics

Other Subjects

Tags: Software Maintenance Questions and Answers || Software Maintenance MCQ Questions and Answers || Software Maintenance GK Questions and Answers || Software Maintenance GK MCQ Questions || Software Maintenance Multiple Choice Questions and Answers || Software Maintenance GK || GK on Software Maintenance || Software Engineering Questions and Answers || Software Engineering MCQ Questions and Answers || Software Engineering GK Questions and Answers || GK on Software Engineering

Software Maintenance Questions and Answers

Topics

Other Subjects

About Us

Stay informed about all important Dates & Notifications