• Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

part 2 assignment clarification

 
ananthakrishnan ramachandran
Ranch Hand
Posts: 52
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi,

Is it required to show the user login (authentication and authorization)and exception handling scenarios in the diagrams.If so, which diagram can be used to depict the same?


thanks and regards
R.Anantharishnan
 
Rajan Choudhary
Ranch Hand
Posts: 196
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
It depends upon the solution you are proposing. If it's database centric then your client (JSP), web(Managed Bean), business(UserManagement), integration (JPA) and EIS (Database) all will have components to be shown in class (userDetails, SLB, JPA entity), component (JSP, bean, ejb), deployment (DB box) and sequence diagrams (complete flow from login.jsp to db table)
If it's LDAP centric then obviously flow and all entities will be different.
 
Yegor Bugayenko
Ranch Hand
Posts: 80
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Keep in mind that diagrams are not used "to depict" something, but to explain certain architectural decisions made in the system. Don't draw pictures, explain concepts. If you're explaining authentication/authorization mechanisms of your application - depict necessary components/classes. Almost every UML diagram type may help you here.
 
Sharma Ashutosh
Bartender
Posts: 346
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
It depends what is in scope and what is out of scope.
If the use cases are not talking about it-don't draw sequence diagram for it but make sure your big picture diagrams-Component diagram as well as System context diagram should be having them.

In Big Smokes Cigar shop-i assumed that Authentication and Authorization modules are already there and it's out of scope for my SuD.
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic