Error Handling/Logging Discussed In Requirements or Design Phase?
At what phase of a project should the project team discuss Error Handling/Logging requirements? So determining what errors should be handled by the code in a release and how they should be logged (e.g. format, wording, etc.).
On one hand I'd say this should be discussed during the Requirements phase. Maybe a separate section in the Requirements document to state specific requirements for Error Handling/Logging. But perhaps this topic should be discussed during the Design Phase of a project. Development and/or Test Phase is DEFINITELY too late. So either Requirements or Design (e.g. at design review meetings?). Opinions? This is such an important subject for any project. I'm surprised it's missed so often. What then happens is QA logs a bug or enhancement request saying, "We feel the error message is too ambiguous. Would be tough for support to troubleshoot." Then the developer says, "Well there was no requirement on the wording or format of the error message. You're lucky I even log an error for this case."