Please note that as of October 24, 2014, the Nokia Developer Wiki will no longer be accepting user contributions, including new entries, edits and comments, as we begin transitioning to our new home, in the Windows Phone Development Wiki. We plan to move over the majority of the existing entries over the next few weeks. Thanks for all your past and future contributions.

How to measure quality?

From Wiki
Jump to: navigation, search
Article Metadata
Created: SannaH (21 Nov 2007)
Last edited: hamishwillee (31 Jul 2012)

Measuring quality is not always straightforward and easy due to the subjective nature of quality. The perceived quality depends on the context and the person assessing the product: a software engineer, product manager, marketing representative, or the end user may all have different expectations for the product. Each of these subjective viewpoints is important and should be considered.

Some aspects of quality can be measured and verified and thus be considered objective. For example, you can define specific and exact requirements for application maximum response times, and amounts of errors or findings in different reviews and testing along the development process. Meeting the project deadlines and milestones can be one metric for assessing the quality, as well as conformance with the requirement specification.

For subjective quality issues, you should be aware of the expectations of the different stakeholders and turn them into product requirements in the requirement specification phase. You can also gather feedback during the project, for example by involving the end users in the development process and allowing them to express their opinions on the product concept and early design drafts.

Reference links

  • More quality related information can be found here
This page was last modified on 31 July 2012, at 05:10.
40 page views in the last 30 days.

Was this page helpful?

Your feedback about this content is important. Let us know what you think.


Thank you!

We appreciate your feedback.