--Should I try to explain some design decisions using Assumptions? Or should I only put it as notes in my diagram?
--I need to show a call using AJAX from one my JSP pages, but how do I indicate that in the class diagram. Should I mention it in Assumptions instead?
--Currently, for authentication, I am making a authenticate call from my Intercepting filter to a AuthHelper class which then calls LDAP to authenticate. Do you think it is a --good idea to call LDAP directly from a Filter, or is it a better pattern to delegate this to a business service.
--What is the best place to show components like Load Balancers. Do we have to show it in both deployment and component diagrams?
SCJP, SCWCD, SCEA
Rajiv Shr wrote:Thanks Arpit. One more question -
Is it ok to call out specific hardware and application server you are using. Eg: I want to use F5 Big IP for load balancing and Websphere application server as my web/app server. Further, I am using IBM QREP for replication of data between data centers which have IBM DB2 databases.
If I use IBM, will that offend Sun examiners ?
Is it ok to call out specific hardware and application server you are using. Eg: I want to use F5 Big IP for load balancing and Websphere application server as my web/app server. Further, I am using IBM QREP for replication of data between data centers which have IBM DB2 databases.
Can I separate out the common steps of search and getDetails in a separate sequence diagram and then put a note before all other sequence diagrams. Will I loose marks for breaking down the sequence diagram this way?
Beyond the basics
I've covered the basics of the sequence diagram, which should allow you to model most of the interactions that will take place in a common system. The following section will cover more advanced notation elements that can be used in a sequence diagram.
Referencing another sequence diagram
When doing sequence diagrams, developers love to reuse existing sequence diagrams in their diagram's sequences. [Note: It is possible to reuse a sequence diagram of any type (e.g., programming or business). I just find that developers like to functionally break down their diagrams more.] Starting in UML 2, the "Interaction Occurrence" element was introduced. The addition of interaction occurrences is arguably the most important innovation in UML 2 interactions modeling. Interaction occurrences add the ability to compose primitive sequence diagrams into complex sequence diagrams. With these you can combine (reuse) the simpler sequences to produce more complex sequences. This means that you can abstract out a complete, and possibly complex, sequence as a single conceptual unit.
An interaction occurrence element is drawn using a frame. The text "ref" is placed inside the frame's namebox, and the name of the sequence diagram being referenced is placed inside the frame's content area along with any parameters to the sequence diagram. The notation of the referenced sequence diagram's name follows the pattern of:
SCJP, SCWCD, SCEA
--Currently, for authentication, I am making a authenticate call from my Intercepting filter to a AuthHelper class which then calls LDAP to authenticate. Do you think it is a --good idea to call LDAP directly from a Filter, or is it a better pattern to delegate this to a business service.
[OCP 21 book] | [OCP 17 book] | [OCP 11 book] | [OCA 8 book] [OCP 8 book] [Practice tests book] [Blog] [JavaRanch FAQ] [How To Ask Questions] [Book Promos]
Other Certs: SCEA Part 1, Part 2 & 3, Core Spring 3, TOGAF part 1 and part 2
catch it before it slithers away! Oh wait, it's a tiny ad:
Gift giving made easy with the permaculture playing cards
https://coderanch.com/t/777758/Gift-giving-easy-permaculture-playing
|