Software Quality Characteristics

Topics: Forward compatibility, Backward compatibility Pages: 5 (1440 words) Published: April 28, 2013
Software Quality Characteristics
Go through the list and think about your product/features. Add specifics for your context, and transform the list to your own.

Capability. Can the product perform valuable functions?
- Completeness: all important functions wanted by end users are available. - Accuracy: any output or calculation in the product is correct and presented with significant digits. - Efficiency: performs its actions in an efficient manner (without doing what it’s not supposed to do.) - Interoperability: different features interact with each other in the best way. - Concurrency: ability to perform multiple parallel tasks, and run at the same time as other processes. - Data agnosticism: supports all possible data formats, and handles noise. - Extensibility: ability for customers or 3rd parties to add features or change behavior.

Reliability. Can you trust the product in many and difficult situations? - Stability: the product shouldn’t cause crashes, unhandled exceptions or script errors. - Robustness: the product handles foreseen and unforeseen errors gracefully. - Stress handling: how does the system cope when exceeding various limits? - Recoverability: it is possible to recover and continue using the product after a fatal error. - Data Integrity: all types of data remain intact throughout the product. - Safety: the product will not be part of damaging people or possessions. - Disaster Recovery: what if something really, really bad happens? - Trustworthiness: is the product’s behavior consistent, predictable, and trustworthy?

Usability. Is the product easy to use?
- Affordance: product invites to discover possibilities of the product. - Intuitiveness: it is easy to understand and explain what the product can do. - Minimalism: there is nothing redundant about the product’s content or appearance. - Learnability: it is fast and easy to learn how to use the product. - Memorability: once you have learnt how to do something you don’t forget it. - Discoverability: the product’s information and capabilities can be discovered by exploration of the user interface. - Operability: an experienced user can perform common actions very fast. - Interactivity: the product has easy-to-understand states and possibilities of interacting with the application (via GUI or API). - Control: the user should feel in control over the proceedings of the software. - Clarity: is everything stated explicitly and in detail, with a language that can be understood, leaving no room for doubt? - Errors: there are informative error messages, difficult to make mistakes and easy to repair after making them. - Consistency: behavior is the same throughout the product, and there is one look & feel. - Tailorability: default settings and behavior can be specified for flexibility. - Accessibility: the product is possible to use for as many people as possible, and meets applicable accessibility standards. - Documentation: there is a Help that helps, and matches the functionality.

Charisma. Does the product have “it”?
- Uniqueness: the product is distinguishable and has something no one else has. - Satisfaction: how do you feel after using the product? - Professionalism: does the product have the appropriate flair of professionalism and feel fit for purpose? - Attractiveness: are all types of aspects of the product appealing to eyes and other senses? - Curiosity: will users get interested and try out what they can do with the product? - Entrancement: do users get hooked, have fun, in a flow, and fully engaged when using the product? - Hype: should the product use the latest and greatest technologies/ideas? - Expectancy: the product exceeds expectations and meets the needs you didn't know you had. - Attitude: do the product and its information have the right attitude and speak to you with the right language and style? - Directness: are (first) impressions impressive? - Story: are there compelling stories about the product’s inception, construction...
Continue Reading

Please join StudyMode to read the full document

You May Also Find These Documents Helpful

  • Software Maintenance and Change Control Research Paper
  • Software Testing Research Paper
  • Software Metrics Essay
  • Software Process and Project Metrics Essay
  • Software Testing Essay
  • Software Reliability Engineering: A Roadmap Essay
  • Quality Assurance Question Bank Essay
  • Problems in Software Engineering Essay

Become a StudyMode Member

Sign Up - It's Free