{'fraction_non_alphanumeric': 0.018272425249169437, 'fraction_numerical': 0.005813953488372093, 'mean_word_length': 5.409574468085107, '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}}
Teaching a service course in software engineering

The development of stand-alone software engineering curricula has spawned the need for a reevaluation of the survey courses designed to introduce software engineering to the non-software engineer (e.g. computer engineers or computer scientists). The Guidelines for Undergraduate Degree Programs in Software Engineering (SE2004) and the Software Engineering Body of Knowledge (SWEBOK) are two widely accepted guidelines for knowledge areas within software engineering. This paper will examine the recommendations in these guidelines and suggest an appropriate subset of course topic areas and depth of coverage for a software engineering service course. The syllabus for senior-level 4-credit quarter-long service course in software engineering for computer engineers will be presented along with anecdotal evidence of its success as the course is taught at the Milwaukee School of Engineering (MSOE). Recent curriculum changes in computer engineering at MSOE have shifted the software engineering service course from 4-credits in the senior year to 3-credits in the sophomore year and the proposed syllabus for this new course will be presented as well.