Showing posts with label software Quality Assurance. Show all posts
Showing posts with label software Quality Assurance. Show all posts

Sunday, June 2, 2019

Types of Verification

As we know that Verification is basically reviewing any application without running it.
So we can do verification in two ways. Namely, Walkthroughs & Inspection.

Broadly speaking Walkthroughs are informal way of verification wherein we ask our colleague or we can our self verify the documentation & coding.

On the other hand, Inspection is a Formal & Official way of Verifying. For Example, an organisation may have a separate team for carrying out inspection by  verifying design documents for every project.Every project needs to go through this process and if there is any mistake in design document then the project will get non conformance list and for proceeding further every project needs to go through this.






Share:

Wednesday, May 29, 2019

Prioritization of Tests


Prioritization of Tests :

Why do we need to Prioritize ?

  1.  Time constraints
  2.  Resource Constraints
  3.  We need to get the best done in the time available
  4. How do we Prioritize?
  5. Identification of the Most Important Tests first(MITs)

Basis of Prioritization of Tests:

  1.  Business complexity.
  2.  Severity of potential failure
  3.  Visibility of failure
  4.  Likelihood of error
  5.  User requirements and priorities
  6.  Technical complexity and complexity
  7.  Contractual requirements / Compliance requirement

Share:

Tuesday, May 28, 2019

What is Quality Management, Quality Control & Quality Assurance ?




Quality Management: Responsible choosing the correct process to ensure that the product is ‘fit for purpose’.


  • A predictable degree of uniformity and dependability at low cost and
  • suited to the market (Dr. Edward Deming).
  • Degree to which a set of inherit character tics fulfills the requirements
  • (ISO-9000)
  • Meeting the customer requirements first time and every time which is fit
  • for use to its intended functions with reasonable cost and within in time.
  • Quality must be measurable and should predictable.
  • Quality must be well defined and should be quantified
  • Quality objective should be achievable and traceable.
  • Quality is Value , Value = Utility (Fit for Purpose) + Warranty (Fit for Use)
  • Utility = What customer wants / Warranty = How it is delivered.
  • ISO9126 – Quality Standard ( The standard is divided into four parts : Quality model , Internal metrics, External metrics , Quality in use metrics)


Quality Control : “ is the activity performed to ensue that a Product is ‘fit for Purpose’ “.

1. Concentrates on specific products.
2. Defect – detection and correction oriented.
3. Usually done after the product is built.
4. This is usually a line function.
5. Examples : Software testing at various levels.

Quality Assurance: “is the activity performed to test the process is being followed”
1. Concentrates on the process of producing the products
2. Defect – prevention oriented
3. Usually done throughout the life cycle.
4. This is usually a staff function.
5. Examples : Reviews and Audits
Share:

Monday, May 20, 2019

What are Quality Assurance and Quality Control in Software Testing?




Quality Assurance in software involves activities related to the process of building a software.This approach used to prevent the defect in the process of developing software and application.


Quality Control in software is a product oriented approach towards building a software product. It requires the execution of the code or program in order to find the bugs in the software or an application.
Share:

Email Subscription

Enter your email address:

Delivered by FeedBurner

Follow my blog

Total Pageviews

Contact Form

Name

Email *

Message *

Translate