CODE VERIFICATION

I really don’t now anything about code verification and validation this is way beyond my expertise, but I do know that actual code are valued as a work of literature. Which is something I learned in my Entrepreneurship class, yup weird.

click image for source

Anyway here are the definitions and some characteristics that both conditions talk about.

Software Validation

Validation: Are we building/coding the right product/software? 

So we can see that validation is the process of checking whether the software product is up to the mark or in other words product has the right specifications from our customers.

Or in some The process of evaluating software during or at the end of the development process to determine whether it satisfies specified business requirements.

It’s objective is to ensure that the product actually meets the user’s needs and that the specifications were correct in the first place.

Activities involved in validation:

  1. Black box testing
  2. White box testing
  3. Unit testing
  4. Integration testing

I understand that here is where you make sure that you are doing the right product, if it is what your customer wants, independently if the code is pretty and so more.

If you want to learn more click the button!

Software Verification

Verification: Are we building/coding the product/software right? 

Is the process of checking that a software achieves its goal without any bugs. The last part the part of ANY BUGS is the most important, that is the main difference between verification and validation.

Here is were you ensure that you are doing the right code without any bugs.

To ensure that the product is being built according to the requirements and design specifications. In other words, to ensure that work products meet their specified requirements without any errors.

Activities involved in verification:

  1. Inspections
  2. Reviews
  3. Walkthroughs
  4. Desk-checking

If you want to learn more click the button!

International Standards

The software quality standards are part of the software engineering, use of standards and methodologies for the design, programming, testing and analysis of the software developed, in order to offer greater reliability, maintainability in accordance with the requirements, with This increases productivity and control in software quality, part of quality management are set to improve its effectiveness and efficiency.

I believe that the standards even if they tell you how to do your product it also gives value to it, if you have the exactly same code twice but one of them has the standard then it has more value than the other, but this is just my opinion.

ISO 12207 Software Life Cycle Models.

Standard for the life cycle processes of the organization’s software.

The standard indicates a series of processes from the collection of requirements to the completion of the software.

ISO / IEC 9126 The ISO / IEC 9126 of 1991

Is the standard to evaluate software products, this standard indicates the quality characteristics and the guidelines for its use, the quality characteristics and their associated metrics, can be useful as well as for evaluate the product as to define the requirements of quality and other uses.


ISO / IEC 14598 standard The ISO / IEC 14598

Standard is currently used as a methodological basis for the evaluation of the software product. In its different stages, it establishes a framework to evaluate the quality of software products by providing, in addition, metrics and requirements for their evaluation processes.

If you want to learn more click the button!

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s