{'fraction_non_alphanumeric': 0.022199798183652877, 'fraction_numerical': 0.0, 'mean_word_length': 4.8698224852071, '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}}
Applying Formal Specifications in Web Design - A Comparative Study

This paper provides an example (the Piano example) that illustrates parts of the software life cycle processes of specification, refinement and implementation in a Web Service- and Web form application. Part of the software system is specified in Z, data- and operation refined and then implemented into Visual C# .NET. A relational database PianosService.mdf is used, and the system is run on the ASP.NET platform. The main emphasis of the paper is to indicate how the implementation language and technologies used drive the design of the specification, and not the other way around. In other words, how the specification of a component or system might be developed in response to evolving awareness and understanding of context, changing requirements and user experience. The Piano system has been designed, tested and run to check its correct behaviour and the correct specification for the data and data access methods.