{'fraction_non_alphanumeric': 0.014028056112224449, 'fraction_numerical': 0.001002004008016032, 'mean_word_length': 5.204968944099379, '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}}
Assessing computer science programs: what have we learned

1. SUMMARY How does a department evaluate the effectiveness of its major programs in computer science? In years past it might have been done rather informally by faculty members having a sense of what their students are learning and measuring that against curriculum guidelines developed by national organizations such as ACM and the IEEE Computer Society. Or, maybe faculty members might have made that judgment by the types of jobs their students were obtaining right after they graduate or the number of students who would go on to graduate school in computer science. Nowadays, however, because of both internal and external forces, computer science departments are introducing formal processes. These involve articulating objectives (or goals) and outcomes for their programs and using a variety of instruments to measure success in meeting those objectives and outcomes, all with the idea of using the results to improve the program.