How to code for Alternate Course AKA Rainy Day Scenary?

Posted by janetsmith on Stack Overflow See other posts from Stack Overflow or by janetsmith
Published on 2009-08-11T12:47:31Z Indexed on 2010/05/08 9:08 UTC
Read the original article Hit count: 270

Alternate course is something when user doesn't do what you expected, e.g. key in wrong password, pressing back button, or database error.

For any programming project, alternate course accounts for more than 50% of a project timeline. It is important. However, most computer books only focus on Basic Course (when everything goes fine).

Basic course is rather simple, compared to Alternate course, because this is normally given by client. Alternate course is what we, as a programmer or Business Analyst needs to take care of.

Java has some built-in mechanism (try-catch) to force us to handle those unexpected behavior. The question is, how to handle them? Any pattern to follow?

Any guideline or industry practice for handling alternate course?

© Stack Overflow or respective owner

Related posts about best-practices

Related posts about industry-standard