{'fraction_non_alphanumeric': 0.014792899408284023, 'fraction_numerical': 0.0, 'mean_word_length': 5.34375, '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}}
Separation in Theory - Coordination in Practice

The lack of a common language and mutual understanding between the disciplines of systems development/software engineering and HCI does create challenges for both teaching and practice in systems and software development. In this paper we propose, however, not to attempt to ‘bridge the gap’ between the disciplines when teaching information systems development. Using our own teaching as an example, we argue that it would require a considerable effort to reconcile the differences in terminology and approaches to systems development between the two disciplines and that the reasonable way forward is to teach the students how to coordinate in practice, while keeping the theories separate. Coordination of HCI and SE curricula can take place by using a vehicle of tacit knowledge, the software prototype, which enables students to learn through practical experience the richness and usefulness of both approaches. The implications of this position are discussed.