{'fraction_non_alphanumeric': 0.024096385542168676, 'fraction_numerical': 0.002126151665485471, 'mean_word_length': 5.303571428571429, '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}}
REAL-TIME CONTROL SYSTEMS: A "ONE DOCUMENT" OBJECT ORIENTED DEVELOPMENT PROCESS

The Object Oriented community is converging towards a unified development process driven by Use Cases[1], where the Unified Modelling Language (UML)[3] has become the standard analysis and design language. Control systems for scientific experiments are typically designed and developed in parallel by many different groups and user requirements evolve with time. It is therefore necessary to adapt the process to these constraints. Our experience shows that: • Use Cases are an effective way of capturing requirements and are well accepted by the customer as a base for discussion. • Use Cases are also a good base for modular and integration testing and for requirements tracing. • All project’s documentation must be for the whole team "one document", easily accessible online for consultation and update. Hypertext navigability provides road maps through the document and prevents information redundancy and obsolescence. The Web can be a good solution, but also case tools can provide the same functionality. • The process must be able to produce the standard paper deliverables, defined in IEEE[5] or similar Project Management Plans. A wide collaboration between organisations in the definition of a unified development process for such control systems can provide significant timesaving in the projects and must be pursued.