{'fraction_non_alphanumeric': 0.015651438240270727, 'fraction_numerical': 0.0, 'mean_word_length': 6.188449848024316, '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}}
Patterns for identification of trust concerns and specification of trustworthiness requirements

Software systems enable performing today's complex business processes. Considering trustworthiness requirements in accordance to trust concerns of the end-users during the development of software systems is a critical issue. Particularly challenging are the cross-disciplinary factors that affect trust of the end-users. Furthermore, expertise in domain and requirements analysis are also required. The problem is even more complex considering current advances in technologies like cloud computing, because of the high distribution, huge amounts of data flows, and a large number of involved participants. It is essential for building a trustworthy software system to elicit and analyze trustworthiness requirements. Documenting these trustworthiness requirements along the other requirements that can achieve the construction of a trustworthy system requires eliciting and documenting the trustworthiness-related domain knowledge. Using goal and business process models, gained domain knowledge can be refined into functional or non-functional requirements for software development which contribute to the trustworthiness of the system under development. Our pattern-based approach helps to systematically refine and document the functional as well as non-functional requirements that satisfy the identified trustworthiness goals. In this paper, we develop patterns to aid the documentation of trustworthiness requirements. The provided patterns are used during the requirement engineering phase to support the requirements engineer in documenting trustworthiness requirements by using linguistic templates. Using our patterns, end-users are also supported in expressing their requirements (trust concern identification pattern) and understanding which problems exist and how the problems are addressed (trustworthiness requirement pattern). These patterns yield insights into the relevant trustworthiness requirements that address the corresponding trust concerns. The application of the introduced patterns helps the requirements engineer during the trustworthiness requirement documentation in an unambiguous, understandable, traceable and verifiable way. We illustrate the patterns by applying it on an application example from an ambient assisted living domain.