{'fraction_non_alphanumeric': 0.01579778830963665, 'fraction_numerical': 0.0, 'mean_word_length': 6.869565217391305, 'pattern_counts': {'":': 0, '<': 0, '<?xml version=': 0, '>': 0, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
Qualitative Software Reliability Requirements: Concept, Classification and Practical Elicitation Methods

Software reliability requirements are specified at the software requirement phase to describe software reliability considerations, which are the key to ensuring software reliability, therefore gaining increasing importance. Qualitative software reliability requirements, as an essential part of software reliability requirements, reflect the idea that software reliability should be designed into software products at an early stage. However, from current engineering practices, the concept of qualitative software reliability requirements remains unclear, and qualitative software reliability requirements elicitation is still inadequate. To solve the issues above, this paper puts forward the definition of qualitative software reliability requirements, classification of qualitative software reliability requirements, and a practical qualitative software reliability requirements elicitation strategy as well as methods, which are used to support guidance of qualitative software reliability requirements elicitation process. A case study of a small unmanned aerial vehicle (UAV) demonstrates the effectiveness and practicability of the proposed approaches.