GoConqr has a new look! Let us know what you think.

Flowchart

SOFTWARE MAP

Juan David Camargo Spanish

Flowchart content

  1. Software Quality Model for porduct

  2. McCall Model

  3. Operation

  4. Revision

  5. Revision

  6. ISO 9126 and ISO 25000

  7. Use

  8. Internal

  9. External

  10. Parameters

  11. Functional suitability

  12. Performance efficiency

  13. Compatibility

  14. Usability

  15. Reliability

  16. Security

  17. Maintainability

  18. Portability

  19. Functional completeness

  20. Functional correctness

  21. Functional appropriateness

  22. Time behaviour

  23. Resource utilization

  24. Capacity

  25. Co-existence

  26. Interoperability

  27. Appropriateness

  28. Learnability

  29. Operability

  30. User error protection

  31. User interface aesthetics

  32. Accessibility

  33. Maturity

  34. Availability

  35. Fault tolerance

  36. Recoverability

  37. Confidentiality

  38. Integrity

  39. Non-repudation

  40. Authenticity

  41. Accountability

  42. Modularity

  43. Reusability

  44. Analyzability

  45. Modifiability

  46. Testability

  47. Adaptability

  48. Installability

  49. Replaceability

  50. ISO/IEC 2500n

  51. ISO/IEC 25000

  52. ISO/IEC 25001

  53. ISO/IEC 2501n

  54. ISO/IEC 2502n

  55. ISO/IEC 2503n

  56. ISO/IEC 2504n

  57. ISO/IEC 25010

  58. ISO/IEC 25012

  59. ISO/IEC 25020

  60. ISO/IEC 25021

  61. ISO/IEC 25022

  62. ISO/IEC 25023

  63. ISO/IEC 25024

  64. ISO/IEC 25030

  65. ISO/IEC 25040

  66. ISO/IEC 25041

  67. ISO/IEC 25042

  68. ISO/IEC 25045

  69. quality of the execution of the software

  70. quality of the code of the software

  71. use of the software

  72. Fulfillment of tasks and objectives of user specified

  73. Capacity of the product to provide correct results

  74. Capability to provide a set of functions appropriate for the tasks specified by the user.

  75. Response time under certain conditions

  76. Quantities and types of resources used under certain conditions

  77. Degree parameter of a product comply with the requirements

  78. Product capacity to coexist with other software

  79. Ability of two or more systems to exchange information and to use the information exchanged

  80. capability that allows the user to learn its application

  81. Capacity that allows the user to understand if the software is suitable for their particular needs

  82. capability that allows the user to use it easily

  83. Capacity to protect users to commit errors

  84. Capacity that the user interface can satisfy the interaction of the user

  85. Capability that allows that it can be used by users with disabilities

  86. Capacity to meet the needs of reliability under normal conditions

  87. Capacity to be available and accessible when required

  88. Ability to operate according to provisions against possible failures of hardware or software

  89. Capacity to recover any lost data and restore the system in case of interruption or failure

  90. Ability to protect information against unauthorized access

  91. Capacity to prevent unauthorized modification.

  92. Capacity to demonstrate that actions or events have taken place

  93. Ability to trace clearly the actions of an entity

  94. Ability to demonstrate the identity of a resource

  95. Ability to allows a change in a component to have a minimum impact on other components

  96. Capacity of an asset that can permit that it can be used in more than one software system

  97. Evaluate the impact that can have a change, in the rest of the software, diagnosing deficiencies.

  98. Capability that allows that this be modified effectively and efficiently

  99. ease with which tests may be done to determine if these criteria are meet

  100. Capacity to be adapted effectively, and efficiently, to different hardware environments, software, operational or use

  101. Ability to install or uninstall without problems in a given environment

  102. Capacity of a product so that this can be used instead of other product software determined

Information

Description
Flowchart on SOFTWARE MAP, created by Juan David Camargo on 19/04/2020.
Views
0
Rating

Feedback

What is it about?

What do you think of the new look?

How do you like it?