NOTE: MY POSTINGS REFLECT MY OWN VIEWS AND DO NOT NECESSARILY REPRESENT THE VIEWS OF MY EMPLOYER, ACCENTURE.
DIFFICULTY LEVEL: BEGINNER to ADVANCED
Assumes having taken the class SSNF and has good intermediate to advanced level of knowledge and/or familiarity with Scripting in ServiceNow.
I thought I would share this as something of importance. I know as ServiceNow software developers we do not build what could be termed necessarily as life-critical-systems (failure of which could cause loss-of-life); that I am aware of, but we do build software that if done poorly could result in loss of money.
For several years now ACM (Association for Computing Machinery) has been tracking Software Risks-to-the-Public via the Software Engineering Special Interest Group (SIGSOFT). I received my copy once-a-month for several years, and it made me a believer. No matter how small the system you work on; always keep in mind risks to the user base, and failure recovery.
The link below is for a cumulative article published as of early last year, by Peter Neumann of SRI International (Stanford U.) in Menlo Park. It is in essence everything from the ACM publications, but also covers hardware problems. Take special notice of the Descriptor Symbols section. Then read on. It is amazing what is listed.
Build it solid. Unit test everything. Be responsible for your code!
Illustrative Risks to the Public
Enjoy!
Steven Bell.
If you find this article helps you, don't forget to log in bookmark it, and mark it as "Helpful"!
Originally published on: 2-29-2016 01:53 PM
I updated the code and brought the article into alignment with my new formatting standard.
