CS Free MCQ Bank

[ Option B ]

The FURPS (Functionality, Usability, Reliability, Performance, Supportability) Model, developed by Hewlett-Packard (HP), is a well-known framework used to classify software quality attributes.

[ Option A ]

The ISO 9001 provides guidelines for quality management systems applicable to software and other industries.

[ Option C ]

Software Quality Assurance (SQA) is a broad activity that ensures the software meets the required quality standards. It is not limited to just testing but covers the entire software development process.
Verification ensures that the software is being built correctly according to specifications and design documents ("Are we building the product right?"). It focuses on the process of development.
Validation ensures that the final product meets the user's needs and requirements ("Are we building the right product?"). It focuses on the product itself.

[ Option C ]

Direct Measure are the values we can observe or record directly. For example, how many people worked on a project (effort), how much money was spent (cost), or the number of lines of code written. They do not need extra calculation.

Indirect Measure are values we derive or calculate from direct measures. For example, productivity (lines of code per person-month), efficiency (output vs. input), or defect density (defects per thousand lines of code). These cannot be measured directly but are obtained through formulas or analysis of direct measures.

[ Option C ]

In software engineering and system design, Reliability is an important quality attribute. It refers to the ability of a system to perform its intended function without failure for a specified period of time, under given conditions.

[ Option D ]

In systems theory, entropy refers to the natural tendency of a system to move toward disorder or breakdown.
Positive Entropy : System moves toward disorder, decay, or breakdown.
Negative Entropy : System receives inputs of energy or resources that help it stay healthy, organized, and functioning.

[ Option D ]

In software engineering, Risk Management is the process of identifying and controlling risks that may affect a software project. The stages occur in a logical order.

Correct Order: Risk Identification → Risk Analysis → Risk Planning → Risk Monitoring.

[ Option A ]

Software Compatibility refers to the ability of new software or systems to work with existing programs without modification. It ensures that older applications can still run properly even after upgrades or changes.
Basically, this helps in:

• Avoiding rewriting old programs.
• Maintaining continuity in system usage.
• Reducing cost and effort.

[ Option C ]

Adaptive Maintenance primarily focuses on modifying the system to remain usable in a changed or changing environment, such as new operating systems, hardware, or regulations. 
It is not mainly concerned with accommodating new or changed user requirements that aspect is typically covered under Perfective Maintenance.

[ Option C ]

Perfective Maintenance enhances performance or adds new features based on user requests.

[ Option D ]

In software engineering, availability tells us how much time a system remains operational and usable. It depends on two important factors:

• MTBF (Mean Time Between Failures): Average time the system works without failure.
• MTTR (Mean Time To Repair): Time taken to fix the system after failure.

A system is considered highly available if it fails less often (High MTBF) and is repaired quickly (Low MTTR). The formula used is:
Availability = MTBF / (MTBF + MTTR) * 100
Given:

• MTBF = 25 Days
• MTTR = 6 hours = 6 / 24 = 0.25 Days

Availability = 25 / (25 + 0.25) * 100
Availability = 25 / 25.25 * 100
Availability = 0.990099 * 100
Availability = 99.009%

[ Option B ]

QA ensures quality is built into every stage of software development, not just during testing.

[ Option D ]

Software Complexity refers to the degree of difficulty in understanding, developing, testing, and maintaining a software system. A highly complex system usually has more lines of code, intricate logic, higher development effort, and is harder to manage. Measuring complexity helps in estimating cost, time, and resources needed for software projects.

Lines of Code (LOC): Counts the total number of lines in the source code. More lines usually mean more complexity, but it does not reflect code quality or logic.
Man-Years: Shows the total human effort (time and people) needed to build the software. Bigger and more complex projects require more man-years.
Function Points (FP): Measures the software based on the functionality it provides to users (inputs, outputs, files). Independent of programming language, it gives a better view of user-side complexity.
Cyclomatic Complexity: Measures how many independent paths exist in the program’s flow (like branches, loops, conditions). Higher values mean the program is harder to test and maintain.

[ Option C ]

The Capability Maturity Model (CMM) defines 5 levels of process maturity in software development. These levels describe how well an organization’s processes are defined and managed.

[ Option B ]

The bathtub curve in hardware reliability is a graph that shows how the failure rate of a component changes over time. It is called a “bathtub” because its shape has three distinct parts that look like a bathtub when drawn.

Three Phases of Bathtub Curve:

E.g.:
A new electronic device:

• Initially may fail (Burn-in).
• Then works fine for years (Useful life).
• Eventually wears out (Wear-out).