Requirements validation and verification in Software Engineering - Time & Space Complexity

Time Complexity: Requirements validation and verification

O(n)

Understanding Time Complexity

When checking software requirements, it is important to understand how the time needed to validate and verify them grows as the number of requirements increases.

We want to know how the effort changes when we have more requirements to check.

Scenario Under Consideration

Analyze the time complexity of the following process for validating and verifying requirements.

for each requirement in requirements_list:
    check if requirement is clear and complete
    for each related document in related_documents:
        verify requirement matches document
    record validation and verification results

This code checks each requirement for clarity and completeness, then verifies it against related documents.

Identify Repeating Operations

• Primary operation: Looping through each requirement and then through related documents for verification.
• How many times: Outer loop runs once per requirement; inner loop runs once per related document for each requirement.

How Execution Grows With Input

As the number of requirements grows, the total checks increase because each requirement needs validation and verification against documents.

Input Size (n requirements)	Approx. Operations
10	About 10 times the number of related documents
100	About 100 times the number of related documents
1000	About 1000 times the number of related documents

Pattern observation: The total work grows roughly in direct proportion to the number of requirements.

Final Time Complexity

Time Complexity: O(n)

This means the time to validate and verify grows linearly with the number of requirements.

Common Mistake

[X] Wrong: "Validation and verification time stays the same no matter how many requirements there are."

[OK] Correct: Each requirement needs individual checking, so more requirements mean more work and more time.

Interview Connect

Understanding how validation and verification scale helps you explain testing and quality assurance processes clearly and confidently.

Self-Check

"What if each requirement needed to be checked against every other requirement for consistency? How would the time complexity change?"

Practice

1. What is the main question that requirements validation tries to answer?

easy

A. Is the code free of bugs?

B. Are we building the right product?

C. Are we building the product right?

D. Is the software delivered on time?

Solution

1. Step 1: Understand the definition of validation

   Validation checks if the product meets the user's real needs and expectations.

2. Step 2: Match the question to validation

   Validation asks if we are building the right product, ensuring it solves the correct problem.

3. Final Answer:

   Are we building the right product? -> Option B

4. Quick Check:

   Validation = Are we building the right product? [OK]

Hint: Validation checks the product's purpose, not the process [OK]

Common Mistakes:

• Confusing validation with verification
• Thinking validation checks code correctness
• Mixing up product quality with delivery timing

2. Which of the following best describes verification in software engineering?

easy

A. Checking if the software meets user needs

B. Testing the software with real users

C. Ensuring the software is built according to specifications

D. Planning the software development schedule

Solution

1. Step 1: Define verification

   Verification ensures the product is built correctly according to the design and requirements.

2. Step 2: Identify the matching option

   Ensuring the software is built according to specifications states ensuring the software is built according to specifications, which matches verification.

3. Final Answer:

   Ensuring the software is built according to specifications -> Option C

4. Quick Check:

   Verification = Built according to specs [OK]

Hint: Verification checks the process, not user needs [OK]

Common Mistakes:

• Confusing verification with validation
• Thinking verification involves user feedback
• Assuming verification is about project planning

3. Consider this scenario: A team tests if the software matches the design documents but ignores if the design meets user needs. Which activity are they performing?

medium

A. Project management

B. Requirements validation

C. User acceptance testing

D. Requirements verification

Solution

1. Step 1: Analyze the activity described

   The team checks if software matches design documents, focusing on correctness to specs.

2. Step 2: Match activity to concept

   This is verification, which ensures the product is built right, not necessarily the right product.

3. Final Answer:

   Requirements verification -> Option D

4. Quick Check:

   Checking against design = Verification [OK]

Hint: Verification checks specs, validation checks user needs [OK]

Common Mistakes:

• Confusing verification with validation
• Assuming user acceptance testing is verification
• Mixing project management with testing activities

4. A software team wrote requirements but forgot to check if they reflect user needs. What is the main problem here?

medium

A. Validation was skipped

B. Verification was skipped

C. Testing was incomplete

D. Design was incorrect

Solution

1. Step 1: Identify what was missed

   The team did not check if requirements reflect user needs, which is validation.

2. Step 2: Understand the impact

   Skipping validation risks building the wrong product, even if specs are correct.

3. Final Answer:

   Validation was skipped -> Option A

4. Quick Check:

   Missing user needs check = Validation skipped [OK]

Hint: Validation ensures user needs are met, not just specs [OK]

Common Mistakes:

• Confusing verification with validation
• Assuming testing covers validation
• Blaming design instead of requirements process

5. A project uses automated tools to check if code matches requirements and holds regular user reviews to confirm needs. What does this combination ensure?

hard

A. Both validation and verification are done

B. Only validation is done

C. Neither validation nor verification is done

D. Only verification is done

Solution

1. Step 1: Identify automated checks role

   Automated tools checking code against requirements perform verification.

2. Step 2: Identify user reviews role

   User reviews confirm if needs are met, which is validation.

3. Step 3: Combine both activities

   Doing both ensures the product is built right and is the right product.

4. Final Answer:

   Both validation and verification are done -> Option A

5. Quick Check:

   Automation + user reviews = Validation + Verification [OK]

Hint: Verification checks specs; validation checks user needs together [OK]

Common Mistakes:

• Thinking automated checks cover validation
• Assuming user reviews replace verification
• Believing one activity is enough alone