Flowchart
SOFTWARE MAP
Flowchart content
Software Quality Model for porduct
McCall Model
Operation
Revision
Revision
ISO 9126 and ISO 25000
Use
Internal
External
Parameters
Functional suitability
Performance efficiency
Compatibility
Usability
Reliability
Security
Maintainability
Portability
Functional completeness
Functional correctness
Functional appropriateness
Time behaviour
Resource utilization
Capacity
Co-existence
Interoperability
Appropriateness
Learnability
Operability
User error protection
User interface aesthetics
Accessibility
Maturity
Availability
Fault tolerance
Recoverability
Confidentiality
Integrity
Non-repudation
Authenticity
Accountability
Modularity
Reusability
Analyzability
Modifiability
Testability
Adaptability
Installability
Replaceability
ISO/IEC 2500n
ISO/IEC 25000
ISO/IEC 25001
ISO/IEC 2501n
ISO/IEC 2502n
ISO/IEC 2503n
ISO/IEC 2504n
ISO/IEC 25010
ISO/IEC 25012
ISO/IEC 25020
ISO/IEC 25021
ISO/IEC 25022
ISO/IEC 25023
ISO/IEC 25024
ISO/IEC 25030
ISO/IEC 25040
ISO/IEC 25041
ISO/IEC 25042
ISO/IEC 25045
quality of the execution of the software
quality of the code of the software
use of the software
Fulfillment of tasks and objectives of user specified
Capacity of the product to provide correct results
Capability to provide a set of functions appropriate for the tasks specified by the user.
Response time under certain conditions
Quantities and types of resources used under certain conditions
Degree parameter of a product comply with the requirements
Product capacity to coexist with other software
Ability of two or more systems to exchange information and to use the information exchanged
capability that allows the user to learn its application
Capacity that allows the user to understand if the software is suitable for their particular needs
capability that allows the user to use it easily
Capacity to protect users to commit errors
Capacity that the user interface can satisfy the interaction of the user
Capability that allows that it can be used by users with disabilities
Capacity to meet the needs of reliability under normal conditions
Capacity to be available and accessible when required
Ability to operate according to provisions against possible failures of hardware or software
Capacity to recover any lost data and restore the system in case of interruption or failure
Ability to protect information against unauthorized access
Capacity to prevent unauthorized modification.
Capacity to demonstrate that actions or events have taken place
Ability to trace clearly the actions of an entity
Ability to demonstrate the identity of a resource
Ability to allows a change in a component to have a minimum impact on other components
Capacity of an asset that can permit that it can be used in more than one software system
Evaluate the impact that can have a change, in the rest of the software, diagnosing deficiencies.
Capability that allows that this be modified effectively and efficiently
ease with which tests may be done to determine if these criteria are meet
Capacity to be adapted effectively, and efficiently, to different hardware environments, software, operational or use
Ability to install or uninstall without problems in a given environment
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.
- Created by
- Juan David Camargo
- Views
- 0
- Rating