Software quality measures how well software is designed (quality of design), and how well the software conforms to that design (quality of conformance). Quality of conformance is concerned with implementation and quality of design measures how valid the design and requirements are in creating a worthwhile product.
Quality starts and ends with documentation, if you have no documentation, then you can have no quality. We write down what is supposed to happen. Then we write down what actually happens. Software that contains few faults is considered by some to have higher quality than software that contains many faults.
Quality software is reasonably bug-free, delivered on time and within budget, meets requirements and/or expectations, and is maintainable. However, quality is a subjective term. It will depend on who the customer is and their overall influence in the scheme of things. Each type of customer will have their own view on quality; the accounting department might define quality in terms of profits while an end-user might define quality as user-friendly and bug-free.
Link to this articule from your own website; just copy/paste this HTML:
Subscribe
