Know and understand the need for validation as well as verification

15 Proofing

What is Proofing?

Proofing is the process of checking your work to make sure it meets the required standards. Think of it like checking a recipe before you cook – you want to be sure all the ingredients are correct and the instructions are clear. In ICT, proofing ensures that software, data, or documentation is accurate, reliable, and ready for use. 🚀

Validation vs Verification

Both validation and verification are types of proofing, but they answer different questions:

  • Verification (V): “Did we build the product right?” – checking that the implementation matches the design or specification. Think of it as building a Lego set exactly as the instruction booklet says. $V$
  • Validation (E): “Did we build the right product?” – checking that the final product meets user needs and real-world requirements. It’s like testing the Lego set to see if it works for the game you want to play. $E$

Why Do We Need Proofing?

Proofing is essential because:

  1. It detects errors early, saving time and money.
  2. It ensures quality and reliability of software and data.
  3. It protects users from bugs, security risks, and misinformation.
  4. It improves confidence for developers, stakeholders, and end‑users.

Proofing Techniques

Here are common techniques used in ICT to prove that a system is correct:

  • Unit Testing – checking individual pieces of code.
  • Integration Testing – ensuring components work together.
  • System Testing – testing the complete system in a real environment.
  • Acceptance Testing – confirming the system meets user requirements.
  • Code Review – peers examine each other's code for mistakes.
  • Static Analysis – tools scan code for potential errors without running it.

Proofing in Practice: A Web Form Example

Imagine you’re building a contact form for a website. Here’s how you would apply validation and verification:

Step What to Check Tools / Methods
1. Design Define required fields and data types. Specification document.
2. Verification Check that the form code matches the spec. Code review, unit tests.
3. Validation Test that the form works for real users. User acceptance testing, usability testing.
4. Deployment Deploy to live server. Continuous integration pipeline.

Analogy: The Construction Site

- Verification is like the architect’s blueprint review – making sure every wall, door, and window is placed correctly.
- Validation is like the final walk‑through with the homeowner – checking that the house feels right, the doors open smoothly, and the kitchen meets the family’s needs. 🏗️

Key Takeaways

  1. Proofing is the safety net that keeps ICT projects on track.
  2. Verification checks processes and specifications; validation checks user needs and real-world performance.
  3. Use a mix of automated tools and human judgment for best results.
  4. Remember: “Build it right” and “Build the right thing” are both essential.”

Revision

Log in to practice.

4 views 0 suggestions