{'fraction_non_alphanumeric': 0.016835016835016835, 'fraction_numerical': 0.0, 'mean_word_length': 5.01010101010101, '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}}
Rambience: Restaurant Management Design for Stakeholder Dynamics

Why do people go to restaurants? And, why do people go to restaurants again? These were fundamental questions that had to be answered in order to be able to even start thinking about how to build a Restaurant Management Software/System called Rambience. This paper focuses on the process a software company had to follow in order to plan, design and finally create a booking and restaurant management software. Moreover, the paper examines the outcome of this project and the conclusions that were reached once it was concluded.