Win a copy of The Little Book of Impediments (e-book only) this week in the Agile and Other Processes forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Audit, Logging, Exception handling - SCEA Part II

 
Arpit Kumar Jain
Ranch Hand
Posts: 41
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi All,
I have one question. As we all know that Audit/History of Customer operations, Logging in the application and Exception handling are in integral part of any enterprise application.

My questions are:-
1) If i include all these in my design, especially in the class diagram and sequence diagrams, i fear that diagrams will be cluttered with these accessories classes, neither they are part of stated requirements nor a part of any of the business process of my application. So do these features need to be shown in design.

2) If these need to be shown in design diagram, then can these hierarchies can be depicted separately and not in core class diagram.
 
Ranganathan Kaliyur Mannar
Bartender
Posts: 1103
10
Java Netbeans IDE Ubuntu
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
For every use case specified, you need to have one sequence diagram. If the Audit/History is not specified in the assignment, then it should NOT be in the sequence diagrams at all. Same would be the case with Class Diagrams. From an exam point of view, we should be to the point. Also, the more unnecessary information you give, chances of mistakes also go high. So, I would resist this.
In the real world though, If you are accustomed with the company/client and you know Audit Histroy is a default requirement, you would have it then...
 
Arpit Kumar Jain
Ranch Hand
Posts: 41
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Thanks Ranganathan for your reply.
Can you please share your thoughts on "Exception handling" also, as it is also not mentioned in the requirements?

Thanks
Arpit Jain
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic