Get Even More Visitors To Your Blog, Upgrade To A Business Listing >>

Quality in Software Quality Engineering

Hello my name is Junaid, in this article I am going to share my knowledge about quality in software quality engineering. Basically there is know any definition of quality in software quality engineering currently.

You will found many authors which have their own definition of quality. I am going to share a generic definition of quality in software quality engineer.


Conformance to explicit stated functional and performance requirement, explicit document development standard and implicit characteristic that are expected of all professionally develop software.

In simple words the quality is the name of measurements like the functional and nonfunctional etc.

Quality Problems in Software Quality Engineering

There are two kind of views in every business field 10 is of customer and second view is a Developer. We can also state that the one who made the product and the one who will create that product.

The major problem in every business domain is all about the communication I mean by the someone want to convey the message but the message cannot be conveyed successfully order thoughts of user and developer did not match every time, that’s why there are lot of problems occur during the development phase.

Basically there are two major problems which will occurred during the software quality engineering process.

1Customer Quality Requirement

Sometime customer demanding the quality, and quality near to the customer is all about the graphics and the user interface. Because customer is not aware with a technical knowledge that’s why the most important thing to customer is just the output of the product. In all of these customer did not know what is the mean of quality that’s why customer because he just result.

When will follow the customer, the product doesn’t get expected sales, short words the product get failed. Because just follow the customer focus on the graphical user interface of the product not the other factors of the product.

Engineering thoughts, the need of the customer is always efficiency and reliability.

Efficiency in this sense, that what is the peak level uses of the final develop product.

Reliability in this sense, that the final develop product is how much user friendly and platform friendly, in short words that can every person use this product.

2Developer Quality Requirements

When every developer start working on any product or on project, the main thing to focused is just the reusability of the product and maintainability of the product. Which are the biggest problem of every developer.

Reusability in this sense, that how much percentage of the code can be reused in the whole project. In short words that developer try their best to make the project code short as possible. Because as much the court with increased the chance of error is also increased.

So to develop the Optimus product they always try to keep the code short and reuse the block of code again and again to build the same functionality instead to write different code for the same functionality.

Maintainability in this sense, that how much product is maintainable in the future aspect. Sometime the user will change the developer for any reason so it’s the duty of the developer to make the product maintainable so that the new developer can understand what old developer have done in the past.

So to developed the maintainability in the product developer have to face many problems, sometime developer have to neglect some of the requirement of client to just make the product maintainable.

5 Quality View

Harvard professor David Garvin, in his book Managing Quality, summarized five principal approaches to defining quality: transcendent, product based, user based, manufacturing based, and value based. Let’s discuss each one of them:

1 Transcendental View of Quality: Those who hold transcendental view would say, “I can’t define it, but I know when I see it.”

Advertisers are fond of promoting products in these terms. “Where shoping is a pleasure” (supermarket), “We love to fly and it shows” (airline), and “It means beautiful eyes” (cosmetics) are example.

2 Product-Based View: Product based definitions are different. Quality is viewed as quantifiable and measurable characteristics or attributes. For example durability or reliability can be measured (e.g. mean time between failure, fit and finish), and the engineer can design to that benchmark. Quality is determined objectively. Although this approach has many benefits, it has limitations as well. Where quality is based on individual taste or preference, the benchmark for measurement may be misleading.

3 User-Based View: User based definitions are based on the idea that quality is an individual matter, and products that best satisfy their preferences (i.e. perceived quality) are those with the highest quality. This is a rational approach but leads to two problems. First, consumer preferences vary widely, and it is difficult to aggregate these preferences into products with wide appeal. This leads to the choice between a niche strategy or a market aggregation approach which tries to identify those product attributes that meet the needs of the largest number of consumers.

4 Manufacturing-Based View: Manufacturing-based definitions are concerned primarily with engineering and manufacturing practices and use the universal definition of “conformance to requirements.” Requirements, or specifications, are established design, and any deviation implies a reduction in quality. The concept applies to services as well as products. Excellence in quality is not necessarily in the eye of the beholder but rather in the standards set by the organization.

This approach has serious weaknesses. The consumer’s perception of quality is equated with conformance and hence is internally focused. Emphasis on reliability in design and manufacturing tends to address cost reduction as the objective, and cost reduction is perceived in a limited way–invest in design and manufacturing improvement until these incremental costs equal the costs of non-quality such as rework or scrap.

5 Value-Based View: Value-based quality is defined in terms of costs and prices as well as a number of other attributes. Thus, the consumer’s purchase decision is based on quality (however it is defined) at the acceptable price.

The post Quality in Software Quality Engineering appeared first on Junaid Shahid | P-Blogger.

This post first appeared on Junaid Shahid | P-Blogger, please read the originial post: here

Share the post

Quality in Software Quality Engineering


Subscribe to Junaid Shahid | P-blogger

Get updates delivered right to your inbox!

Thank you for your subscription