|
1 | | -[] |
| 1 | +- abbreviation: compatibility |
| 2 | + description: "Degree to which a product, system or component can exchange information\ |
| 3 | + \ with other products, systems or components, and/or perform its required\ |
| 4 | + \ functions while sharing the same common environment and resources. This\ |
| 5 | + \ characteristic is composed of the following sub-characteristics:\n -Co-existence\ |
| 6 | + \ - Degree to which a product can perform its required functions efficiently\ |
| 7 | + \ while sharing a common environment and resources with other products, without\ |
| 8 | + \ detrimental impact on any other product.\n -Interoperability - Degree\ |
| 9 | + \ to which a system, product or component can exchange information with other\ |
| 10 | + \ products and mutually use the information that has been exchanged." |
| 11 | + identifier: https://w3id.org/everse/i/dimensions/compatibility |
| 12 | + name: Compatibility |
| 13 | + source: |
| 14 | + name: ISO/IEC 25010 standard |
| 15 | + url: https://iso25000.com/index.php/en/iso-25000-standards/iso-25010 |
| 16 | +- abbreviation: fairness |
| 17 | + description: 'FAIRness refers to the degree to which research software adheres |
| 18 | + to the FAIR principles: Findable, Accessible, Interoperable, and Reusable. |
| 19 | + These principles, adapted for research software, aim to enhance the discoverability, |
| 20 | + accessibility, interoperability, and reusability of software, thereby maximizing |
| 21 | + its value and impact in scientific research.' |
| 22 | + identifier: https://w3id.org/everse/i/dimensions/fairness |
| 23 | + name: FAIRness |
| 24 | + source: |
| 25 | + name: Introducing the FAIR Principles for research software |
| 26 | + url: https://www.nature.com/articles/s41597-022-01710-x |
| 27 | +- abbreviation: flexibility |
| 28 | + description: "Degree to which a product can be adapted to changes in its requirements,\ |
| 29 | + \ contexts of use or system environment. This characteristic is composed of\ |
| 30 | + \ the following sub-characteristics:\n - Adaptability - Degree to which\ |
| 31 | + \ a product or system can effectively and efficiently be adapted for or transferred\ |
| 32 | + \ to different hardware, software or other operational or usage environments.\n\ |
| 33 | + \ - Scalability - Degree to which a product can handle growing or shrinking\ |
| 34 | + \ workloads or to adapt its capacity to handle variability.\n - Installability\ |
| 35 | + \ - Degree of effectiveness and efficiency with which a product or system\ |
| 36 | + \ can be successfully installed and/or uninstalled in a specified environment.\n\ |
| 37 | + \ - Replaceability - Degree to which a product can replace another specified\ |
| 38 | + \ software product for the same purpose in the same environment." |
| 39 | + identifier: https://w3id.org/everse/i/dimensions/flexibility |
| 40 | + name: Flexibility |
| 41 | + source: |
| 42 | + name: ISO/IEC 25010 standard |
| 43 | + url: https://iso25000.com/index.php/en/iso-25000-standards/iso-25010 |
| 44 | +- abbreviation: functional_suitability |
| 45 | + created: 03-04-2025 |
| 46 | + description: "This characteristic represents the degree to which a product or\ |
| 47 | + \ system provides functions that meet stated and implied needs when used under\ |
| 48 | + \ specified conditions. This characteristic is composed of the following sub-characteristics:\ |
| 49 | + \ \n Functional completeness - Degree to which the set of functions covers\ |
| 50 | + \ all the specified tasks and intended users' objectives.\n Functional\ |
| 51 | + \ correctness - Degree to which a product or system provides accurate results\ |
| 52 | + \ when used by intended users.\n Functional appropriateness - Degree to\ |
| 53 | + \ which the functions facilitate the accomplishment of specified tasks and\ |
| 54 | + \ objectives." |
| 55 | + identifier: https://w3id.org/everse/i/dimensions/functional_suitability |
| 56 | + name: Functional suitability |
| 57 | + source: |
| 58 | + name: ISO/IEC 25010 standard |
| 59 | + url: https://iso25000.com/index.php/en/iso-25000-standards/iso-25010 |
| 60 | +- abbreviation: interaction_capability |
| 61 | + description: "Degree to which a product or system can be interacted with by specified\ |
| 62 | + \ users to exchange information via the user interface to complete specific\ |
| 63 | + \ tasks in a variety of contexts of use. This characteristic is composed of\ |
| 64 | + \ the following sub-characteristics:\n - Appropriateness recognizability\ |
| 65 | + \ - Degree to which users can recognize whether a product or system is appropriate\ |
| 66 | + \ for their needs.\n - Learnability - Degree to which the functions of\ |
| 67 | + \ a product or system can be learnt to be used by specified users within a\ |
| 68 | + \ specified amount of time.\n - Operability - Degree to which a product\ |
| 69 | + \ or system has attributes that make it easy to operate and control.\n \ |
| 70 | + \ - User error protection. Degree to which a system prevents users against\ |
| 71 | + \ operation errors.\n - User engagement - Degree to which a user interface\ |
| 72 | + \ presents functions and information in an inviting and motivating manner\ |
| 73 | + \ encouraging continued interaction.\n - Inclusivity - Degree to which\ |
| 74 | + \ a product or system can be used by people of various backgrounds (such as\ |
| 75 | + \ people of various ages, abilities, cultures, ethnicities, languages, genders,\ |
| 76 | + \ economic situations, etc.).\n - User assistance - Degree to which a product\ |
| 77 | + \ can be used by people with the widest range of characteristics and capabilities\ |
| 78 | + \ to achieve specified goals in a specified context of use.\n - Self-descriptiveness\ |
| 79 | + \ - Degree to which a product presents appropriate information, where needed\ |
| 80 | + \ by the user, to make its capabilities and use immediately obvious to the\ |
| 81 | + \ user without excessive interactions with a product or other resources (such\ |
| 82 | + \ as user documentation, help desks or other users)." |
| 83 | + identifier: https://w3id.org/everse/i/dimensions/interaction_capability |
| 84 | + name: Interaction Capability |
| 85 | + source: |
| 86 | + name: ISO/IEC 25010 standard |
| 87 | + url: https://iso25000.com/index.php/en/iso-25000-standards/iso-25010 |
| 88 | +- abbreviation: maintainability |
| 89 | + description: "This characteristic represents the degree of effectiveness and efficiency\ |
| 90 | + \ with which a product or system can be modified to improve it, correct it\ |
| 91 | + \ or adapt it to changes in environment, and in requirements.This characteristic\ |
| 92 | + \ is composed of the following sub-characteristics:\n - Modularity - Degree\ |
| 93 | + \ to which a system or computer program is composed of discrete components\ |
| 94 | + \ such that a change to one component has minimal impact on other components.\n\ |
| 95 | + \ - Reusability - Degree to which a product can be used as an asset in\ |
| 96 | + \ more than one system, or in building other assets.\n - Analysability\ |
| 97 | + \ - Degree of effectiveness and efficiency with which it is possible to assess\ |
| 98 | + \ the impact on a product or system of an intended change to one or more of\ |
| 99 | + \ its parts, to diagnose a product for deficiencies or causes of failures,\ |
| 100 | + \ or to identify parts to be modified.\n - Modifiability - Degree to which\ |
| 101 | + \ a product or system can be effectively and efficiently modified without\ |
| 102 | + \ introducing defects or degrading existing product quality.\n - Testability\ |
| 103 | + \ - Degree of effectiveness and efficiency with which test criteria can be\ |
| 104 | + \ established for a system, product or component and tests can be performed\ |
| 105 | + \ to determine whether those criteria have been met." |
| 106 | + identifier: https://w3id.org/everse/i/dimensions/maintainability |
| 107 | + name: Maintainability |
| 108 | + source: |
| 109 | + name: ISO/IEC 25010 standard |
| 110 | + url: https://iso25000.com/index.php/en/iso-25000-standards/iso-25010 |
| 111 | +- abbreviation: performance_efficiency |
| 112 | + description: "This characteristic represents the degree to which a product performs\ |
| 113 | + \ its functions within specified time and throughput parameters and is efficient\ |
| 114 | + \ in the use of resources (such as CPU, memory, storage, network devices,\ |
| 115 | + \ energy, materials...) under specified conditions. This characteristic is\ |
| 116 | + \ composed of the following sub-characteristics:\n -Time behaviour - Degree\ |
| 117 | + \ to which the response time and throughput rates of a product or system,\ |
| 118 | + \ when performing its functions, meet requirements.\n -Resource utilization\ |
| 119 | + \ - Degree to which the amounts and types of resources used by a product or\ |
| 120 | + \ system, when performing its functions, meet requirements.\n - Capacity\ |
| 121 | + \ - Degree to which the maximum limits of a product or system parameter meet\ |
| 122 | + \ requirements." |
| 123 | + identifier: https://w3id.org/everse/i/dimensions/performance_efficiency |
| 124 | + name: Performance Efficiency |
| 125 | + source: |
| 126 | + name: ISO/IEC 25010 standard |
| 127 | + url: https://iso25000.com/index.php/en/iso-25000-standards/iso-25010 |
| 128 | +- abbreviation: reliability |
| 129 | + description: "Degree to which a system, product or component performs specified\ |
| 130 | + \ functions under specified conditions for a specified period of time. This\ |
| 131 | + \ characteristic is composed of the following sub-characteristics:\n -\ |
| 132 | + \ Faultlessness - Degree to which a system, product or component performs\ |
| 133 | + \ specified functions without fault under normal operation.\n - Availability\ |
| 134 | + \ - Degree to which a system, product or component is operational and accessible\ |
| 135 | + \ when required for use.\n - Fault tolerance - Degree to which a system,\ |
| 136 | + \ product or component operates as intended despite the presence of hardware\ |
| 137 | + \ or software faults.\n - Recoverability - Degree to which, in the event\ |
| 138 | + \ of an interruption or a failure, a product or system can recover the data\ |
| 139 | + \ directly affected and re-establish the desired state of the system." |
| 140 | + identifier: https://w3id.org/everse/i/dimensions/reliability |
| 141 | + name: Reliability |
| 142 | + source: |
| 143 | + name: ISO/IEC 25010 standard |
| 144 | + url: https://iso25000.com/index.php/en/iso-25000-standards/iso-25010 |
| 145 | +- abbreviation: safety |
| 146 | + description: "This characteristic represents the degree to which a product under\ |
| 147 | + \ defined conditions to avoid a state in which human life, health, property,\ |
| 148 | + \ or the environment is endangered. This characteristic is composed of the\ |
| 149 | + \ following sub-characteristics:\n - Operational constraint - Degree to\ |
| 150 | + \ which a product or system constrains its operation to within safe parameters\ |
| 151 | + \ or states when encountering operational hazard.\n - Risk identification\ |
| 152 | + \ - Degree to which a product can identify a course of events or operations\ |
| 153 | + \ that can expose life, property or environment to unacceptable risk.\n \ |
| 154 | + \ - Fail safe - Degree to which a product can automatically place itself\ |
| 155 | + \ in a safe operating mode, or to revert to a safe condition in the event\ |
| 156 | + \ of a failure.\n - Hazard warning - Degree to which a product or system\ |
| 157 | + \ provides warnings of unacceptable risks to operations or internal controls\ |
| 158 | + \ so that they can react in sufficient time to sustain safe operations.\n\ |
| 159 | + \ - Safe integration - Degree to which a product can maintain safety during\ |
| 160 | + \ and after integration with one or more components." |
| 161 | + identifier: https://w3id.org/everse/i/dimensions/safety |
| 162 | + name: Safety |
| 163 | + source: |
| 164 | + name: ISO/IEC 25010 standard |
| 165 | + url: https://iso25000.com/index.php/en/iso-25000-standards/iso-25010 |
| 166 | +- abbreviation: security |
| 167 | + description: "Degree to which a product or system defends against attack patterns\ |
| 168 | + \ by malicious actors and protects information and data so that persons or\ |
| 169 | + \ other products or systems have the degree of data access appropriate to\ |
| 170 | + \ their types and levels of authorization. This characteristic is composed\ |
| 171 | + \ of the following sub-characteristics:\n - Confidentiality - Degree to\ |
| 172 | + \ which a product or system ensures that data are accessible only to those\ |
| 173 | + \ authorized to have access.\n - Integrity - Degree to which a system,\ |
| 174 | + \ product or component ensures that the state of its system and data are protected\ |
| 175 | + \ from unauthorized modification or deletion either by malicious action or\ |
| 176 | + \ computer error.\n - Non-repudiation - Degree to which actions or events\ |
| 177 | + \ can be proven to have taken place so that the events or actions cannot be\ |
| 178 | + \ repudiated later.\n - Accountability - Degree to which the actions of\ |
| 179 | + \ an entity can be traced uniquely to the entity.\n - Authenticity - Degree\ |
| 180 | + \ to which the identity of a subject or resource can be proved to be the one\ |
| 181 | + \ claimed.\n - Resistance - Degree to which the product or system sustains\ |
| 182 | + \ operations while under attack from a malicious actor." |
| 183 | + identifier: https://w3id.org/everse/i/dimensions/security |
| 184 | + name: Security |
| 185 | + source: |
| 186 | + name: ISO/IEC 25010 standard |
| 187 | + url: https://iso25000.com/index.php/en/iso-25000-standards/iso-25010 |
| 188 | +- abbreviation: sustainability |
| 189 | + description: The capacity of the software to endure. In other words, sustainability |
| 190 | + means that the software will continue to be available in the future, on new |
| 191 | + platforms, meeting new needs. |
| 192 | + identifier: https://w3id.org/everse/i/dimensions/sustainability |
| 193 | + name: Sustainability |
| 194 | + source: |
| 195 | + name: Defining Software Sustainability |
| 196 | + url: https://danielskatzblog.wordpress.com/2016/09/13/defining-software-sustainability/ |
0 commit comments