Free Mock Test : Software Engineering : Software Reliability Model, Maintenance and Testing (Test 1)

Question : Software reliability is defined as:

Speed of software

Ability of software to perform without failure for a specified period under specified conditions

Software size

Programming language

Question : Which model assumes the number of faults in software is fixed before testing begins?

Goel-Okumoto Model

Musa-Okumoto Model

Jelinski & Moranda Model

Basic Execution Time Model

Question : The Jelinski & Moranda Model assumes that:

New faults are introduced during debugging.

Faults are removed perfectly.

Failure rate remains constant.

Software reliability decreases after testing.

Question : In the Jelinski & Moranda Model, failure rate:

Increases as faults are removed.

Remains constant.

Decreases as faults are removed.

Depends only on execution time.

Question : The Basic Execution Time Model measures reliability based on:

Calendar time

CPU execution time

Number of programmers

Memory usage

Question : Which software reliability model was proposed by Goel and Okumoto?

Linear Model

Non-Homogeneous Poisson Process (NHPP) Model

Spiral Model

Agile Model

Question : The Goel-Okumoto Model assumes:

Failure intensity remains constant.

Fault detection follows an exponential distribution.

Software size changes continuously.

No failures occur during testing.

Question : Musa-Okumoto Model is also known as:

Linear Reliability Model

Logarithmic Poisson Model

Waterfall Model

Spiral Reliability Model

Question : Which reliability model assumes failure intensity decreases logarithmically?

GO Model

Musa-Okumoto Model

J-M Model

Rayleigh Model

Question : Which reliability model uses execution time instead of calendar time?

Musa Basic Execution Time Model

Waterfall Model

Agile Model

RAD Model

Question : Software maintenance refers to:

Writing new software

Modifying software after delivery

Selling software

Installing software

Question : Which maintenance corrects software defects?

Adaptive

Perfective

Corrective

Preventive

Question : Adaptive maintenance is performed to:

Remove bugs

Improve performance

Adapt software to environmental changes

Reduce software size

Question : Perfective maintenance aims to:

Correct faults

Improve software performance and usability

Remove viruses

Replace hardware

Question : Preventive maintenance is performed to:

Improve future maintainability

Add new modules

Fix user errors

Increase software price

Question : A major cause of maintenance problems is:

Good documentation

Poor documentation

Proper testing

Modular design

Question : Which increases maintenance difficulty?

Modular programming

High code complexity

Proper comments

Coding standards

Question : Frequent requirement changes lead to:

Easier maintenance

Increased maintenance effort

Better testing

Reduced cost

Question : Which factor significantly affects maintenance cost?

Software age

Code quality

Documentation

All of the above

Question : Approximately what percentage of software lifecycle cost is maintenance?

5%

15%

60–80%

100%

Question : Which reduces maintenance cost?

Poor design

Modular design

Duplicate code

No documentation

Question : Software testing aims to:

Prove software is error-free

Find defects

Increase code length

Reduce documentation

Question : Which testing is performed by developers?

Alpha Testing

Unit Testing

Beta Testing

Acceptance Testing

Question : Which testing checks interactions between modules?

Unit Testing

Integration Testing

System Testing

Acceptance Testing

Question : System testing validates:

Individual functions

Entire integrated software

Database only

User documentation

Question : Acceptance testing is mainly performed by:

Developers

Database administrators

Customers/Users

Test automation tools

Question : Which assumption is NOT made in the Jelinski & Moranda Model?

Perfect debugging

Fixed number of faults initially

Failure rate proportional to remaining faults

New faults are introduced after every fix

Question : The Goel-Okumoto Model belongs to which category?

Deterministic Model

Statistical Reliability Growth Model

Agile Model

Structured Model

Question : Which maintenance type improves software without changing its environment?

Adaptive

Corrective

Perfective

Emergency

Question : Which statement about software testing is TRUE?

Testing proves software has no bugs.

Exhaustive testing is possible.

Testing can show the presence of defects, not their absence.

Testing is unnecessary if coding is perfect.

Free Mock Test - Software Engineering : Software Reliability Model, Maintenance and Testing (Test 1)