{'fraction_non_alphanumeric': 0.014891179839633447, 'fraction_numerical': 0.0, 'mean_word_length': 5.522388059701493, '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}}
Formalizing EARS – First Impressions

The Easy Approach to Requirements Specification (EARS) has been designed primarily as a set of templates to assist requirements engineers in writing software requirements that are clear and understandable. Its target are thus requirements engineers, software architects and developers. Due to the minimalistic nature of the English sentences that make up an EARS specification, it is reasonable to expect that automated tasks can be performed on EARS specification, among which verification and code synthesis. Given English cannot be directly understood by machines without some degree of ambiguity, EARS requirements can only by automatically processed if they are translated in advance into formal specifications. In this short paper, we explore how a translation from EARS into Linear Temporal Logic can be implemented in practice.