This week's book giveaway is in the Agile and other Processes forum. We're giving away four copies of The Mikado Method and have Ola Ellnestam and Daniel Brolund on-line! See this thread for details.
Do we need to explicitly show and explain how SuD manages logging and exception handling? Chapter 9 of cade's book just displays a package in the class diagram with some text on it. Is this sufficient?
That is fine. For logging, I didn't mention it at all. For exception handling, I only mentioned issues with business meaning. And even then, I didn't put them in the sequence diagram unless they were a common business flow.
Jeanne Boyarsky wrote:That is fine. For logging, I didn't mention it at all. For exception handling, I only mentioned issues with business meaning. And even then, I didn't put them in the sequence diagram unless they were a common business flow.
Thanks Jeanne. So this means we need to show business exceptions in class and sequence diagrams if they are a part common business flow
Correct. What happens if the database goes down is likely to not be a business flow.
Kumar Amit
Ranch Hand
Joined: Aug 13, 2001
Posts: 103
posted
0
IF the external system is down and the request times out OR may be returns some other exception, should it be converted into a business exception and returned to web tier?
In the real world, absolutely. In this design we aren't going document everything that might happen. I didn't include much exception handling in my submission.
0
