Requirements validation and verification in Software Engineering - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is requirements validation in software engineering?

Requirements validation is the process of checking if the requirements meet the needs and expectations of the stakeholders. It ensures the right product is being built.

beginner

What does requirements verification mean?

Requirements verification is the process of confirming that the requirements are correctly specified, consistent, and complete according to standards and documentation.

beginner

Name one common technique used for requirements validation.

One common technique is reviews, where stakeholders and team members examine the requirements to find errors or misunderstandings.

intermediate

Why is it important to perform both validation and verification on requirements?

Validation ensures the product will meet user needs, while verification ensures the requirements are correctly and clearly defined. Both prevent costly mistakes later.

beginner

Give an example of a question asked during requirements validation.

An example question is: "Does this requirement reflect what the user really wants?" This helps confirm the requirement's relevance.

What is the main goal of requirements validation?

A To write test cases

B To check code correctness

C To ensure requirements meet user needs

D To deploy the software

Validation focuses on confirming that requirements satisfy the user's needs and expectations.

Which activity is part of requirements verification?

A Checking for requirement consistency

B Interviewing users for needs

C Running software tests

D Collecting feedback after release

Verification involves checking that requirements are consistent, complete, and correctly documented.

Which technique is commonly used in requirements validation?

A Code compilation

B System deployment

C Unit testing

D Requirement reviews

Requirement reviews involve stakeholders examining requirements to find errors or misunderstandings.

Why is requirements verification important?

A To confirm requirements are clear and correct

B To check user satisfaction

C To design the user interface

D To write user manuals

Verification ensures requirements are well-defined, consistent, and free of errors.

Which question would you ask during requirements validation?

A "Are the requirements consistent with each other?"

B "Do the requirements meet user needs?"

C "Are the requirements feasible to implement?"

D "Are the requirements written in code?"

Validation focuses on confirming that requirements meet the actual needs of users.

Explain the difference between requirements validation and verification.

Think about 'Are we building the right product?' vs 'Are the requirements written correctly?'

Describe why both validation and verification are important in the requirements process.

Consider the risks of missing user needs or having unclear requirements.

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