QUALITY

 QUALITY. 

Quality is extremely hard to define, and it is simply stated: "Fit for use or purpose." It is all about meeting the needs and expectations of customers with respect to functionality, design, reliability, durability, & price of the product

Quality - Quality is the totality of features and characteristics of a product or service which relate on its ability to satisfy a given need.

Who is responsible for Software quality?

Quality is the responsibility of everyone because no one person can successfully deliver a project by themselves. Usually, in the project world, projects are run by a number of people that are seldom from one organization.

It is imperative that each organization takes appropriate measures to ensure quality is engraved within its culture.

When quality expectations are understood by the project team, and each organization has set up in place a procedure to ensure quality control and assurance measures are taken, the project is more likely to be delivered to better quality and hence more like to be a success.

Key aspects that conclude software quality include,

• Good design – It’s always important to have a good and aesthetic design to please users
• Reliability – Be it any software it should be able to perform the functionality impeccably without issues
• Durability- Durability is a confusing term, In this context, durability means the ability of the software to work without any issue for a long period of time.
• Consistency – Software should be able to perform consistently over platform and devices
• Maintainability – Bugs associated with any software should be able to capture and fix quickly and news tasks and enhancement must be added without any trouble
• Value for money – customer and companies who make this app should feel that the money spent on this app has not gone to waste.
• 
  
  
  

  

  
  
  

  Verification vs Validation: Key Difference

  Verification	Validation
  The verifying process includes checking documents, design, code, and program	It is a dynamic mechanism of testing and validating the actual product
  It does not involve executing the code	It always involves executing the code
  Verification uses methods like reviews, walkthroughs, inspections, and desk- checking, etc.	It uses methods like Black Box Testing, White Box Testing, and non-functional testing
  Whether the software conforms to specification is checked	It checks whether the software meets the requirements and expectations of a customer
  It finds bugs early in the development cycle	It can find bugs that the verification process can not catch
  Target is application and software architecture, specification, complete design, high level, and database design etc.	Target is an actual product
  QA team does verification and make sure that the software is as per the requirement in the SRS document.	With the involvement of testing team validation is executed on software code.
  It comes before validation	It comes after verification

  Example of verification and validation

  • In Software Engineering, consider the following specification

  A clickable button with name Submet

  • Verification would check the design doc and correcting the spelling mistake.
  • Otherwise, the development team will create a button like

  

• • So new specification is

  A clickable button with name Submit

  • Once the code is ready, Validation is done. A Validation test found –

  

  • Owing to Validation testing, the development team will make the submit button clickable