Skip to content

Commit 2e04270

Browse files
Automated update of RSQKit data files
1 parent 8dfed2a commit 2e04270

File tree

1 file changed

+11
-347
lines changed

1 file changed

+11
-347
lines changed

_data/quality_dimensions.yml

Lines changed: 11 additions & 347 deletions
Original file line numberDiff line numberDiff line change
@@ -34,7 +34,8 @@
3434
source:
3535
name: Introducing the FAIR Principles for research software
3636
url: https://www.nature.com/articles/s41597-022-01710-x
37-
- abbreviation: flexibility
37+
- &id001
38+
abbreviation: flexibility
3839
description: 'Degree to which a product can be adapted to changes in its requirements,
3940
contexts of use or system environment. This characteristic is composed of
4041
the following sub-characteristics:
@@ -72,349 +73,12 @@
7273
source:
7374
name: ISO/IEC 25010 standard
7475
url: https://iso25000.com/index.php/en/iso-25000-standards/iso-25010
75-
- abbreviation: functional_suitability
76-
created: 03-04-2025
77-
description: 'This characteristic represents the degree to which a product or
78-
system provides functions that meet stated and implied needs when used under
79-
specified conditions. This characteristic is composed of the following sub-characteristics:
80-
81-
82-
**Functional completeness**
83-
84-
85-
Degree to which the set of functions covers all the specified tasks and intended
86-
users'' objectives.
87-
88-
89-
**Functional correctness**
90-
91-
92-
Degree to which a product or system provides accurate results when used by
93-
intended users.
94-
95-
96-
**Functional appropriateness**
97-
98-
99-
Degree to which the functions facilitate the accomplishment of specified tasks
100-
and objectives.'
101-
identifier: https://w3id.org/everse/i/dimensions/functional_suitability
102-
name: Functional suitability
103-
source:
104-
name: ISO/IEC 25010 standard
105-
url: https://iso25000.com/index.php/en/iso-25000-standards/iso-25010
106-
- abbreviation: interaction_capability
107-
description: 'Degree to which a product or system can be interacted with by specified
108-
users to exchange information via the user interface to complete specific
109-
tasks in a variety of contexts of use. This characteristic is composed of
110-
the following sub-characteristics:
111-
112-
113-
**Appropriateness recognizability**
114-
115-
116-
Degree to which users can recognize whether a product or system is appropriate
117-
for their needs.
118-
119-
120-
**Learnability**
121-
122-
123-
Degree to which the functions of a product or system can be learnt to be used
124-
by specified users within a specified amount of time.
125-
126-
127-
**Operability**
128-
129-
130-
Degree to which a product or system has attributes that make it easy to operate
131-
and control.
132-
133-
134-
**User error protection**
135-
136-
137-
Degree to which a system prevents users against operation errors.
138-
139-
140-
**User engagement**
141-
142-
143-
Degree to which a user interface presents functions and information in an
144-
inviting and motivating manner encouraging continued interaction.
145-
146-
147-
**Inclusivity**
148-
149-
150-
Degree to which a product or system can be used by people of various backgrounds
151-
(such as people of various ages, abilities, cultures, ethnicities, languages,
152-
genders, economic situations, etc.).
153-
154-
155-
**User assistance**
156-
157-
158-
Degree to which a product can be used by people with the widest range of characteristics
159-
and capabilities to achieve specified goals in a specified context of use.
160-
161-
162-
**Self-descriptiveness**
163-
164-
165-
Degree to which a product presents appropriate information, where needed by
166-
the user, to make its capabilities and use immediately obvious to the user
167-
without excessive interactions with a product or other resources (such as
168-
user documentation, help desks or other users).'
169-
identifier: https://w3id.org/everse/i/dimensions/interaction_capability
170-
name: Interaction Capability
171-
source:
172-
name: ISO/IEC 25010 standard
173-
url: https://iso25000.com/index.php/en/iso-25000-standards/iso-25010
174-
- abbreviation: maintainability
175-
description: 'This characteristic represents the degree of effectiveness and efficiency
176-
with which a product or system can be modified to improve it, correct it or
177-
adapt it to changes in environment, and in requirements. This characteristic
178-
is composed of the following sub-characteristics:
179-
180-
181-
**Modularity**
182-
183-
184-
Degree to which a system or computer program is composed of discrete components
185-
such that a change to one component has minimal impact on other components.
186-
187-
188-
**Reusability**
189-
190-
191-
Degree to which a product can be used as an asset in more than one system,
192-
or in building other assets.
193-
194-
195-
**Analysability**
196-
197-
198-
Degree of effectiveness and efficiency with which it is possible to assess
199-
the impact on a product or system of an intended change to one or more of
200-
its parts, to diagnose a product for deficiencies or causes of failures, or
201-
to identify parts to be modified.
202-
203-
204-
**Modifiability**
205-
206-
207-
Degree to which a product or system can be effectively and efficiently modified
208-
without introducing defects or degrading existing product quality.
209-
210-
211-
**Testability**
212-
213-
214-
Degree of effectiveness and efficiency with which test criteria can be established
215-
for a system, product or component and tests can be performed to determine
216-
whether those criteria have been met.'
217-
identifier: https://w3id.org/everse/i/dimensions/maintainability
218-
name: Maintainability
219-
source:
220-
name: ISO/IEC 25010 standard
221-
url: https://iso25000.com/index.php/en/iso-25000-standards/iso-25010
222-
- abbreviation: open_source_software
223-
description: Open source software is software with source code that anyone can
224-
inspect, modify, and enhance. Research software can be published with or without
225-
open access to the source code. Open access to source code aligns better with
226-
academic research purposes than closed source software; open source software
227-
aligns with the FAIR4RS principles. It allows other researchers to directly
228-
verify the methods used to produce the results published in papers. It also
229-
makes reproducibility much easier. In addition to these research-driven reasons,
230-
publishing research software as open source software can help with long term
231-
maintenance in a cost-effective way, since interested developers can easily
232-
contribute new functionality or fix bugs. Moreover, by integrating with the
233-
greater open source ecosystem, researchers can leverage tools and support
234-
communities already available. As such, for most academic communities with
235-
limited resources, it is also a good choice from a software engineering perspective
236-
identifier: https://w3id.org/everse/i/dimensions/open_source_software
237-
name: Open Source Software
238-
source:
239-
- identifier: https://doi.org/10.5281/zenodo.14204478
240-
name: EVERSE Reference Framework
241-
url: https://doi.org/10.5281/zenodo.14204478
242-
- name: What is Open Source?
243-
url: https://opensource.com/resources/what-open-source
244-
- abbreviation: performance_efficiency
245-
description: 'This characteristic represents the degree to which a product performs
246-
its functions within specified time and throughput parameters and is efficient
247-
in the use of resources (such as CPU, memory, storage, network devices, energy,
248-
materials...) under specified conditions. This characteristic is composed
249-
of the following sub-characteristics:
250-
251-
252-
**Time behaviour**
253-
254-
255-
Degree to which the response time and throughput rates of a product or system,
256-
when performing its functions, meet requirements.
257-
258-
259-
**Resource utilization**
260-
261-
262-
Degree to which the amounts and types of resources used by a product or system,
263-
when performing its functions, meet requirements.
264-
265-
266-
**Capacity**
267-
268-
269-
Degree to which the maximum limits of a product or system parameter meet requirements.'
270-
identifier: https://w3id.org/everse/i/dimensions/performance_efficiency
271-
name: Performance Efficiency
272-
source:
273-
name: ISO/IEC 25010 standard
274-
url: https://iso25000.com/index.php/en/iso-25000-standards/iso-25010
275-
- abbreviation: reliability
276-
description: 'Degree to which a system, product or component performs specified
277-
functions under specified conditions for a specified period of time. This
278-
characteristic is composed of the following sub-characteristics:
279-
280-
281-
**Faultlessness**
282-
283-
284-
Degree to which a system, product or component performs specified functions
285-
without fault under normal operation.
286-
287-
288-
**Availability**
289-
290-
291-
Degree to which a system, product or component is operational and accessible
292-
when required for use.
293-
294-
295-
**Fault tolerance**
296-
297-
298-
Degree to which a system, product or component operates as intended despite
299-
the presence of hardware or software faults.
300-
301-
302-
**Recoverability**
303-
304-
305-
Degree to which, in the event of an interruption or a failure, a product or
306-
system can recover the data directly affected and re-establish the desired
307-
state of the system.'
308-
identifier: https://w3id.org/everse/i/dimensions/reliability
309-
name: Reliability
310-
source:
311-
name: ISO/IEC 25010 standard
312-
url: https://iso25000.com/index.php/en/iso-25000-standards/iso-25010
313-
- abbreviation: safety
314-
description: 'This characteristic represents the degree to which a product under
315-
defined conditions avoids a state in which human life, health, property, or
316-
the environment is endangered. This characteristic is composed of the following
317-
sub-characteristics:
318-
319-
320-
**Operational constraint**
321-
322-
323-
Degree to which a product or system constrains its operation to within safe
324-
parameters or states when encountering operational hazard.
325-
326-
327-
**Risk identification**
328-
329-
330-
Degree to which a product can identify a course of events or operations that
331-
can expose life, property or environment to unacceptable risk.
332-
333-
334-
**Fail safe**
335-
336-
337-
Degree to which a product can automatically place itself in a safe operating
338-
mode, or to revert to a safe condition in the event of a failure.
339-
340-
341-
**Hazard warning**
342-
343-
344-
Degree to which a product or system provides warnings of unacceptable risks
345-
to operations or internal controls so that they can react in sufficient time
346-
to sustain safe operations.
347-
348-
349-
**Safe integration**
350-
351-
352-
Degree to which a product can maintain safety during and after integration
353-
with one or more components.'
354-
identifier: https://w3id.org/everse/i/dimensions/safety
355-
name: Safety
356-
source:
357-
name: ISO/IEC 25010 standard
358-
url: https://iso25000.com/index.php/en/iso-25000-standards/iso-25010
359-
- abbreviation: security
360-
description: 'Degree to which a product or system defends against attack patterns
361-
by malicious actors and protects information and data so that persons or other
362-
products or systems have the degree of data access appropriate to their types
363-
and levels of authorization. This characteristic is composed of the following
364-
sub-characteristics:
365-
366-
367-
**Confidentiality**
368-
369-
370-
Degree to which a product or system ensures that data are accessible only
371-
to those authorized to have access.
372-
373-
374-
**Integrity**
375-
376-
377-
Degree to which a system, product or component ensures that the state of its
378-
system and data are protected from unauthorized modification or deletion either
379-
by malicious action or computer error.
380-
381-
382-
**Non-repudiation**
383-
384-
385-
Degree to which actions or events can be proven to have taken place so that
386-
the events or actions cannot be repudiated later.
387-
388-
389-
**Accountability**
390-
391-
392-
Degree to which the actions of an entity can be traced uniquely to the entity.
393-
394-
395-
**Authenticity**
396-
397-
398-
Degree to which the identity of a subject or resource can be proved to be
399-
the one claimed.
400-
401-
402-
**Resistance**
403-
404-
405-
Degree to which the product or system sustains operations while under attack
406-
from a malicious actor.'
407-
identifier: https://w3id.org/everse/i/dimensions/security
408-
name: Security
409-
source:
410-
name: ISO/IEC 25010 standard
411-
url: https://iso25000.com/index.php/en/iso-25000-standards/iso-25010
412-
- abbreviation: sustainability
413-
description: The capacity of the software to endure. In other words, sustainability
414-
means that the software will continue to be available in the future, on new
415-
platforms, meeting new needs.
416-
identifier: https://w3id.org/everse/i/dimensions/sustainability
417-
name: Sustainability
418-
source:
419-
name: Defining Software Sustainability
420-
url: https://danielskatzblog.wordpress.com/2016/09/13/defining-software-sustainability/
76+
- *id001
77+
- *id001
78+
- *id001
79+
- *id001
80+
- *id001
81+
- *id001
82+
- *id001
83+
- *id001
84+
- *id001

0 commit comments

Comments
 (0)