Abstract
This paper highlights a growing problem as software systems become more and more tightly coupled and complex, that of poor diagnostic capability. Diagnosis has never been particularly sophisticated in software systems, often being an ad hoc process in which programmers receive no training. As a result, significant numbers of failures in modern systems cannot be diagnosed in the sense of being uniquely related to one or more faults and as such they continue to fail. As a result, modern software systems are unique amongst modern engineering systems is being characterised by repetitive and frequently avoidable failure. This paper discusses the strongly related issues of repetitive failure, feedback and diagnosis in a generally light-hearted way but makes a plea for diagnosis to be an essential feature of systems design. All engineering systems fail and this knowledge should be part of the software design process such that inevitable failures can be quickly related to the contributing fault or faults and the system corrected to avoid future re-occurrence.
Sign-in/Register to access full text options 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callDisclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
