{'fraction_non_alphanumeric': 0.03624733475479744, 'fraction_numerical': 0.016346837242359632, 'mean_word_length': 5.3710407239819, '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}}
Managing a training project for a complex software system

In 1975, the University of Cincinnati Computer Center (UCCC) received the first of a series of contracts from the U.S. Environmental Protection Agency's (EPA) Office of Drinking Water (ODW). The contracts required: (1) detailed design, programming, testing and documentation of a computer software system; (2) a needs assessment and development of training packages based on identified needs; and (3) installation of the computer software and delivery of the training program. The computer system, known as the Model State Information System (MSIS), was designed to meet all annual reporting requirements of the National Interim Primary Drinking Water Regulations (NIPDWR). These regulations expand general mandates of the Safe Drinking Water Act of 1974.
 MSIS characteristics included: 73 program modules; IBM, UNIVAC, and Honeywell versions; structured, top-down, programming; over four feet of systems documentation; 70 input forms; 50 standard reports; and more than 200,000 lines of ANS COBOL source code.
 ODW realized that the complexity of MSIS required intensive user training to achieve good system utilization. The authors, who were responsible for managing all phases of MSIS training, began with a literature search. A review of this literature, and the decisions which resulted in the MSIS training design and delivery, are described