{'fraction_non_alphanumeric': 0.011508951406649617, 'fraction_numerical': 0.0, 'mean_word_length': 5.808695652173913, '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}}
The role of the software practitioner in the development of public safety software-intensive systems

Software Engineering is primarily a human process and consideration of human factors in safety-related software systems should always be mindful of the role that software practitioners themselves play in the delivery of those systems. As a Software Engineering Project Manager I have had responsibility for most aspects of the software development lifecycle and for guiding the software practitioners towards a successful outcome. This paper explores some experiences managing the delivery of software into the public safety-related emergency services environment, and the challenges of requirements analysis, design and implementation of software-intensive public safety systems.