Software quality
Download as PPT, PDF0 likes345 views
The document discusses definitions of software quality and defines key attributes of software quality according to ISO 9126 standards. It defines functionality, reliability, usability, efficiency, maintainability, and portability as key quality attributes and further breaks down each attribute into sub-attributes that define important aspects of quality.
Software quality
- 1. Software quality Tricode Professional Services www.tricode.nl 14-07-2008 Sander van Beek
- 3. “ Degree to which a set of inherent characteristic fulfils requirements ” - ISO 9000
- 4. “ Degree to which a set of inherent characteristic fulfils requirements ” - ISO 9000
- 5. “ Uniformity around a target value ” - Six Sigma
- 6. “ Fitness for use ” - Joseph M. Juran
- 7. “ Products and services that meet or exceed customers ’ expectations ” - Noriaki Kano et al.
- 8. “ The result of care ” - Robert Pirsig
- 9. What isn’t quality? Price Effort Production process (as long as the process is not the product)
- 11. Functionality Efficiency Maintainability Usability Portability Reliability (extended) ISO 9126
- 12. Functionality A set of attributes that bear on the existence of a set of functions and their specified properties. The functions are those that satisfy stated or implied needs.
- 13. Functionality Suitability Accuracy Interoperability Compliance Security Traceabilty
- 14. Functionality: suitability Attribute that bears on the presence and appropriateness of a set of functions for specified tasks.
- 15. Functionality: accuracy Attributes that bear on the provision of right or agreed results or effects.
- 16. Functionality: interoperability Attributes that bear on its ability to interact with specified systems.
- 17. Functionality: compliance Attributes that make the software adhere to application related standards, conventions or regulations in laws and similar prescriptions.
- 18. Functionality: security Attributes that bear on its ability to prevent unauthorised access, whether accidental or deliberate, to programs and data.
- 19. Functionality: traceability Attributes that bear on the effort needed to verify correctness of data processing on required points.
- 20. Reliability A set of attributes that bear on the capability to maintain its level of performance under stated conditions for a stated period.
- 21. Reliability Maturity Fault tolerance Recoverability Availability Degradability
- 22. Reliability: maturity Attributes that bear on the frequency of failure by faults in the software.
- 23. Reliability: fault tolerance Attributes that bear on its ability to maintain a specified level of performance in cases of software faults or of infringement of its specified interface.
- 24. Reliability: recoverability Attributes that bear on the capability to re-establish its level of performance and recover the data directly affected in case of a failure and on the time and effort needed for it.
- 25. Reliability: availability Attributes that bear on the amount of time the product is available to the user at the time it is needed.
- 26. Reliability: degradability Attributes that bear on the effort needed to re-establish the essential functionality after a breakdown.
- 27. Usability A set of attributes that bear on the effort needed for use, and on the individual assessment of such use, by a stated or implied set of users.
- 28. Usability Understandability Learnability Operability Explicitness Customisability Attractivity Clarity Helpfulness User-friendliness
- 29. Usability: understandability Attributes that bear on the users' effort for recognising the logical concept and its applicability.
- 30. Usability: learnability Attributes that bear on the users' effort for learning its application (for example, control, input, output).
- 31. Usability: operability Attributes that bear on the users' effort for operation and operation control.
- 32. Usability: explicitness Attributes that bear on the clarity of the software product with regard to its status (progression bars, etc.).
- 33. Usability: customisability Attributes that enable the software to be customised by the user to reduce the effort required for use and increase satisfaction with the software.
- 34. Usability: attractivity Attributes that bear on the satisfaction of latent user desires and preferences, through services, behaviour and presentation beyond actual demand.
- 35. Usability: clarity Attributes that bear on the clarity of making the user aware of the functions it can perform.
- 36. Usability: helpfulness Attributes that bear on the availability of instructions for the user on how to interact with it.
- 37. Usability: user-friendliness Attributes that bear on the users' satisfaction.
- 38. Efficiency A set of attributes that bear on the relationship between the level of performance of the software and the amount of resources used, under stated conditions.
- 39. Efficiency Time behaviour Resource behaviour
- 40. Efficiency: time behaviour Attributes that bear on response and processing times and on throughput rates in performing its function.
- 41. Efficiency: resource behaviour Attributes that bear on the amount of resources used and the duration of such use in performing its function.
- 42. Maintainability A set of attributes that bear on the effort needed to make specified modifications.
- 43. Maintainability Analysability Changeability Stability Testability Manageability Reuseability
- 44. Maintainability: analysability Attributes that bear on the effort needed for diagnosis of deficiencies or causes of failures, or for identification of parts to be modified.
- 45. Maintainability: changeability Attributes that bear on the effort needed for modification, fault removal or for environmental change.
- 46. Maintainability: stability Attributes that bear on the risk of unexpected effect of modifications.
- 47. Maintainability: testability Attributes that bear on the effort needed for validating the modified software.
- 48. Maintainability: manageability Attributes that bear on the effort needed to (re)establish its running status.
- 49. Maintainability: reusability Attributes that bear on its potential for complete or partial reuse in another softwareproduct.
- 50. Portability A set of attributes that bear on the ability of software to be transferred from one environment to another.
- 51. Portability Adaptability Installability Conformance Replaceability
- 52. Portability: adaptability Attributes that bear on the opportunity for its adaptation to different specified environments without applying other actions or means than those provided for this purpose for the software in question.
- 53. Portability: installability Attributes that bear on the effort needed to install the software in a specified environment.
- 54. Portability: conformance Attributes that make the software adhere to standards or conventions relating to portability.
- 55. Portability: replaceability Attributes that bear on the opportunity and effort of using it in the place of specified other software in the environment of that software.
Editor's Notes
- #13: Oohashi junction in Shinjuki (Japan)
- #15: Building a shed for office space or a skyscraper for storing your garden utensils
- #16: When the house is build, and you enter it, do you always end up in the hallway? Or sometimes in the kitchen? Or in the neighbours’ home?
- #17: Does your home connect to the street? To the sewer system? Does it sit against that of your neighbours? But also should it be equiped to handle 110V, 220V and 380V?
- #18: Is your building build according to building regulations? Do you have a permit to build it there?
- #19: Did you install a security alarm? A fence? Iron bars before the windows?
- #20: Are you able to track every one in the building?
- #23: How often does your building colapse?
- #24: Is the building earthquake resistant? And is it still usable after I drove into it with a car?
- #25: Is your furnitue unharmed when the house colapses? Does everyone survive?
- #26: Can you always use the building? Or are the bricks used by another building?
- #27: How easy is it to rebuild a part of the building after it broke down?
- #30: Do you need to get to the kitchen via the attic? And back through the basement?
- #31: How easy is it to use the building? Or do you still have rooms nobody knew of?
- #32: Does your building have a 36 digit combination lock that has to be changed every day? Is the furniture randomly placed every day? Do you have to travel through 20 rooms before you reach the living room?
- #33: Is it clear that the door is locked? Or unopened?
- #34: How easy is it to redecorate?
- #35: Did your building come with a butler? And a doorman? And electric doors? Can everything be operated with a remote control? Do you have an escalator?
- #36: Is it a door? Or a window? No it is the kitchen!
- #37: Did you get directions how to get to your home? A floorplan? A helpful message beneath your doorbel that states “Ring here if you want to enter”.
- #38: Are you satisfied with your buiding?
- #45: Is it hard to find where that leakage came from?
- #46: How easy can you relocate your home? Can you easily extend or fix it?
- #47: Does your house colapse after you put up that painting on the wall?
- #48: Do you have a similar house for testing purposes?
- #49: Do you need to clean your home every hour? Keeps the plaster falling of?
- #50: Could you reuse your kitchen in another home?
- #53: Is your house resistent to anual flooding? Can it cope with both summer and winter?
- #54: How easy can you put down your pre-build home?
- #55: Is it possible for the local contractor to build your house?
- #56: Can you replace your kitchen? Change the electric system? Or the fridge? Or a light bulb?