Unit 1.3: Verification and Validation: Ensuring Software Excellence
Two intertwined concepts stand as sentinels of quality: verification and validation. These two processes play distinct yet complementary roles in the journey to create reliable and high-quality software applications. Verification ensures that the software is built correctly, adhering to specifications, while validation ensures that the right software is built, meeting user needs and expectations.
Verification: Are we building the software correctly?
Verification checks whether the software matches the written requirements and design documents.
Short version: Did we build the system the way we said we would?
A requirement states: "Lock a user's account after 3 failed login attempts."
Verification checks:
- Does the code lock the account after exactly 3 failed attempts?
- Does the database update the account status correctly?
- Do unit tests assert this behavior?
If the implementation matches the spec and tests pass, the feature is verified.
Common verification activities
- Code reviews — developers check each other's code for correctness.
- Walkthroughs — team steps through logic or design together.
- Inspections — formal review of design docs and code.
- Unit testing — test small components (e.g., login function).
Validation: Are we building the right software?
Validation checks whether the software solves the users' real problems and provides a good user experience.
Short version: Did we build the right system for the users?
Even if the account locks after 3 failed attempts (verification passed), users might complain that:
- They accidentally get locked out too easily.
- The password reset flow is confusing.
- The app doesn't explain why they were locked out.
Validation asks whether the behavior makes sense for users and supports their goals. If users are frustrated or unable to use the system effectively, validation fails.
Common validation activities
- User Acceptance Testing (UAT) — end users verify the system works for their needs.
- Beta testing — limited release to real users for feedback.
- Usability testing — observe users completing tasks.
- Customer feedback sessions — collect real-world impressions.
Quick comparison
| Verification | Validation |
|---|---|
| Are we building the product correctly? | Are we building the right product? |
| Checks against requirements & design | Checks against user needs |
| Mostly developers & testers | Involves real users |
| Focus on technical correctness | Focus on usefulness & satisfaction |
| Example: "Does login lock after 3 failures?" | Example: "Is the login experience user-friendly?" |
The V-Model: An Elegant Representation of Verification and Validation
The V-Model, also known as the Validation and Verification Model, presents a visually intuitive representation of the testing process in relation to the development lifecycle. It illustrates the parallelism between the development stages and their corresponding testing phases. Just as development progresses in a linear manner, from requirements to coding and deployment, testing proceeds in a mirrored fashion, ensuring that each development phase is thoroughly validated.
In the V-Model, each development phase is paired with a corresponding testing phase. For instance:
- Requirements gathering is matched with requirements validation.
- System design is linked with system testing, also referred to as end-to-end testing.
- Implementation (coding) coincides with unit testing.
- Integration of components aligns with integration testing.
- Deployment corresponds to acceptance testing.
The V-Model's symmetrical structure underscores the importance of validation at each step, affirming that the software's components and functionalities align with expectations and requirements. This methodology enhances the likelihood of identifying and rectifying defects early in the development process, saving time, effort, and costs.
Source: https://insights.sei.cmu.edu/blog/four-types-of-shift-left-testing/
The Shift-Left Movement and V & V
The shift-left movement in software development has significantly changed the approach to verification and validation (V&V) processes. Shift-left emphasizes the early integration of testing and quality assurance activities in the software development lifecycle, pushing them closer to the beginning of the development process. This shift has several key impacts on V&V:
- Early Detection of Issues: By integrating testing and validation activities at the beginning of the
development process, issues and defects are detected and addressed much earlier. This reduces the likelihood
of critical issues surfacing later in the development cycle, which can be more costly and time-consuming to
fix.
- Reduced Cost of Issue Resolution: Fixing defects early is generally less expensive than fixing them
later in the development process. Shift-left helps minimize the cost of resolving issues, as they are
identified closer to the point of introduction.
- Improved Collaboration: Shift-left encourages closer collaboration between development, testing, and
quality assurance teams. Cross-functional teams work together from the start to establish testing
requirements, testing environments, and quality metrics.
- Continuous Feedback Loops: Continuous integration and continuous delivery (CI/CD) pipelines, which are
central to the shift-left approach, create continuous feedback loops. Teams can quickly test, validate, and
provide feedback on changes, leading to faster iterations and improvement of software quality.
- Test Automation: The shift-left approach emphasizes test automation, allowing for the rapid and
repeatable execution of tests. Automated tests can be integrated into the CI/CD pipeline, enabling faster
feedback on code changes.
- Increased Test Coverage: By starting testing early in the development process, shift-left promotes a
higher level of test coverage. Teams can assess and validate various aspects of the software, such as
functionality, performance, security, and usability, from the beginning.
- Enhanced Risk Management: Shift-left supports proactive risk management by identifying potential issues
and vulnerabilities before they become significant risks. This is particularly important for industries with
strict compliance requirements or high security standards.
- Shorter Time to Market: With faster feedback and early issue detection, software development teams can
release software more quickly, allowing businesses to be more responsive to market demands.
- User-Centric Focus: Shift-left encourages a user-centric approach by involving end users and
stakeholders in the testing and validation process from the outset, leading to software that better meets
user needs and expectations.
- Cultural and Mindset Shift: The shift-left movement is not only a process change but also a cultural
shift in organizations. It promotes a mindset of shared responsibility for software quality among all team
members, not just the testing and QA teams.
Overall, the shift-left movement has transformed V&V practices from being isolated, end-stage activities to being integral components of the entire software development process. This results in higher-quality software, faster delivery, and increased collaboration among cross-functional teams. However, it requires a commitment to cultural change, new tooling, and automation to fully realize the benefits of this approach.
For more information about this important topic check out this blog by Donald Firesmith of Carnegie-Mellon University.
https://insights.sei.cmu.edu/blog/four-types-of-shift-left-testing/
Useful Links: ←Unit 1.2 | Unit 1.4→ | Table of Contents