Requirements validation and verification in Software Engineering - Mini Project: Build & Apply

Requirements Validation and Verification

📖 Scenario: You are part of a software development team working on a new mobile app. Before coding starts, your team needs to ensure the project requirements are clear, complete, and correct. This helps avoid costly mistakes later.

🎯 Goal: Build a simple checklist to understand and apply the concepts of requirements validation and verification in software engineering.

📋 What You'll Learn

Create a list of initial requirements with exact given entries

Add a variable to track the number of requirements verified

Use a loop to check each requirement for validation and verification status

Add a final summary statement about the verification process

💡 Why This Matters

🌍 Real World

In software projects, validating and verifying requirements early helps avoid misunderstandings and costly errors during development.

💼 Career

Understanding requirements validation and verification is essential for roles like business analysts, software testers, and project managers.

1

Create the initial requirements list

Create a list called requirements with these exact entries: 'User login functionality', 'Data encryption', 'Responsive design', 'Offline mode', and 'Push notifications'.

Software Engineering

# Create the list called requirements with the specified entries
# Your code here

Hint

Use square brackets to create a list and include all five exact strings separated by commas.

2

Add a verification counter

Create a variable called verified_count and set it to 0 to track how many requirements have been verified.

Software Engineering

requirements = ['User login functionality', 'Data encryption', 'Responsive design', 'Offline mode', 'Push notifications']
# Create verified_count variable and set it to 0
# Your code here

Hint

Just assign 0 to the variable named verified_count.

3

Check each requirement for validation and verification

Use a for loop with variable req to iterate over requirements. Inside the loop, use an if statement to check if req is not empty (simulating validation). If valid, increase verified_count by 1 (simulating verification).

Software Engineering

requirements = ['User login functionality', 'Data encryption', 'Responsive design', 'Offline mode', 'Push notifications']
verified_count = 0
# Use a for loop to check each requirement and update verified_count
# Your code here

Hint

Loop through each requirement and check if it is not an empty string. If so, add 1 to verified_count.

4

Add a final summary statement

Create a variable called summary and set it to the string 'Total verified requirements: ' concatenated with the string version of verified_count.

Software Engineering

requirements = ['User login functionality', 'Data encryption', 'Responsive design', 'Offline mode', 'Push notifications']
verified_count = 0
for req in requirements:
    if req != '':
        verified_count += 1
# Create summary string with total verified requirements
# Your code here

Hint

Use string concatenation and convert verified_count to string with str().

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