{'fraction_non_alphanumeric': 0.03916768665850673, 'fraction_numerical': 0.02447980416156671, 'mean_word_length': 5.390625, '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}}
An object-oriented tool for tracing requirements

It is widely agreed that tracing requirements is essential in developing large systems. Tracing helps in verifying system features against requirements, in identifying error sources, and most significantly, in managing change, which is pervasive and continuous in software development. We describe a tool called TOOR (Traceability of Object Oriented Requirements) that is based on principles from hyperprogramming (J. Goguen, 1990) and hyperrequirements (J. Goguen and Luqi, 1995), and is motivated by the considerations about context and information discussed by J. Goguen (1996), and about the importance of the social discussed by J. Goguen (1994). TOOR uses the sophisticated module system of FOOPS (J. Goguen, 1987) for flexibility, reuse and object orientation.