----- Original Message ----- > From: "Paul Graydon" <[email protected]>
> A few quick thoughts, and a few useful resources. I comment from possibly a much lower place on the food chain. Assume (*cough*) that you're going to, sooner or later, have someone supporting it who *isn't* one of your developers. To save everyone's time during the 3am phone call to a sleepy developer, prepare means of testing subsections with absolute certainty. You've got a web front end with embedded java and other clever things that talks from the user's browser to a server that then talks to a master server (i.e. master/slave) and on and on and on. Give your support folks a "Test all lamps" button that, will prove all the pieces work. The support person can say with a high degree of reliability, that the problem lies within a subsystem block. One of my customers did it so that if you went to his usual URL but specified a particular port, (from a specific set of addresses) you got back the results of his running a subsystem test. You'd see something like: 101: Browser supported. 102: OS Support. 103: Java version check. 201: Server response time within boundaries. 301: Master/Slave communcations available. 302: Certificate check. 401: Database server online. 402: Database authentication working. 501: LDAP server response failed. etc. etc. etc.... By his doing this, anyone could quickly narrow down where the problem lies (and it never seemed to be the same twice) and attack the problem using clear methods. If you expect early in the process that you'll have to support your product, you'll make better decisions. Just my nickel's worth of experience. Thanks for everyone's time. _______________________________________________ Tech mailing list [email protected] https://lists.lopsa.org/cgi-bin/mailman/listinfo/tech This list provided by the League of Professional System Administrators http://lopsa.org/
