Nalla Senthilnathan

Ranch Hand
+ Follow
since Jul 13, 2003
Cows and Likes
Total received
In last 30 days
Total given
Total received
Received in last 30 days
Total given
Given in last 30 days
Forums and Threads
Scavenger Hunt
expand Ranch Hand Scavenger Hunt
expand Greenhorn Scavenger Hunt

Recent posts by Nalla Senthilnathan

Originally posted by Keith Shacks:

Is there any document out there on the web somewhere which applies RUP to a J2EE project . There is lot of theory materials available but I am not able to find any good RUP by example sort of stuff which explains all the different iterations and all the artifacts to be included with each iteration , how rational tools like rose take use case and generate code out of the use case model itself.

Can someone send me URL to the above mentioned stuff if available.

Thanks a lot folks !!


Try this:

This article discusses applying RUP to a .Net project but many of the RUP concepts are equally applicable for a corresponding J2EE project.

[ November 07, 2004: Message edited by: Nalla Senthilnathan ]

Originally posted by Raj Joe:
Can anyone direct me to some really good resources on the web ,which talks about OOAD Vs Modular Appraoch

Try this:


Originally posted by jucua kwok:

Could somebody give me a real world example of well documented
system development methodology? It's nice if it's based on OOADP...


Try this:


Originally posted by Miguel Flecha:
I got it. thanks a lot!!!


You have come across a non-trivial problem situation with Struts. See whether the discussions on this page helps:

Good luck,
17 years ago

Originally posted by Saritha ventrapragada:
I have following queries on class diagram.

1. while designing classes, do we show only business classes in class diagram or can we show DB, VO, facade classes along and their association with business classes?

Do we show all classes along with struts, facade, EJB, VO and DB in class diagram?.

You can get some hints using the BluePrints document:

Here is what I see from the above document. Class diagrams can be presented in two types: "framework class diagram" (Fig. 17) and "structure class diagram" (Fig 20). Based on this, I would include Struts actions, session facades and DAOs in the first one and include all the VOs in the second one.

Hope that helps,

Originally posted by HS Thomas:

But currently you'd get more support (in tools and skills) for the source than for the models.
[ April 23, 2004: Message edited by: HS Thomas ]

Here is my attempt at creating platform-independent models:
Let me know what you think.

Originally posted by patrick jiang:
I put subsystem instead of detail components, so that the component diagram is very small.

Subsystems by themselves may not be sufficient to represent the whole system. I think adding components inside each subsystem with J2EE stereotypes like:
might represent the system more convincingly.

Originally posted by Patrick Nolan:

The Domain layer is used across all layers and contains data and business logic/behavior.
Any thoughts?
Patrick J. Nolan, Jr.

Figure 15. in this doc seem to support your argument.

Originally posted by Priya Patel:

2) Do sequence diagrams begin after Class Diagrams (Since you have to list Classes at the top ?) or do you begin with sequence diagrams (and thus deducing what classes you require for your class diagram ??)

I have found ( ) that identifying components first makes the process of identifying classes much effortless. Using the clases and the event flows one can get sequence diagrams.
[ February 01, 2004: Message edited by: Nalla Senthilnathan ]

Originally posted by sam joe:
Hi, guys, I just confused with the following relations,
In component or deployment diagram,
Can a component contain other components?
Can a component contain packages?
Can a package contain components?

Try this

Originally posted by Leonardo Penha:
I am currently designing my component diagram, and I feel the ServiceLocator component is cluttering it. Every EJB dependency relationship has to use the service locator to lookup the bean. In my case I have 3 Session Facades plus a few other Entity Beans. If every EJB dependency needs a service locator then I have too many lines crossing each other in the diagram.
I was thinking about providing just one example of an EJB lookup via service locator in a separate component diagram and saying in my assumptions document that every EJB dependency relationship in the main component diagram uses the service locator.Would anyone think this is acceptable?

The component diagram (Figure 3) in this BluePrints example does show ServiceLocator:

Originally posted by Paolo Giannini-South Africa:
I can’t seem to find any material of a detailed example to follow or learn in a step by step process/sequence.

Try this:
[ December 09, 2003: Message edited by: Nalla Senthilnathan ]

Originally posted by Ilja Preuss:

How does that fit into the usage of the terms as a result instead of an activity? ("Let's discuss the systems architecture." or "The system has a brittle design.")

Hi Ilja,
Here is my interpretation of the usage of the terms:
"Let's discuss the systems architecture." - you are discussing about the set of components involved in the system, their dependencies and their deployment issues.
"The system has a brittle design." - the implementing classes are poorly designed (disregarding patterns and other oo principles).

Originally posted by Anil Vupputuri:
Difference between System Design & System Architecture?

Here is my 2c:
System architecture transforms requirements into components.
System design transforms components into classes.
I agree with Stefan Sorman. For example in the Petstore example
we can write the Business Use Case as:
customer -> ( purchase pets ) << include >> ( process order )
and system use case as:
OrderProcessingSystem -> ( process order )

[ December 04, 2003: Message edited by: Nalla Senthilnathan ]