aspose file tools*
The moose likes OO, Patterns, UML and Refactoring and the fly likes Defining architecture of presentation tier implementing struts Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of Spring in Action this week in the Spring forum!
JavaRanch » Java Forums » Engineering » OO, Patterns, UML and Refactoring
Bookmark "Defining architecture of presentation tier implementing struts" Watch "Defining architecture of presentation tier implementing struts" New topic
Author

Defining architecture of presentation tier implementing struts

ashishk kumar
Greenhorn

Joined: Jan 29, 2008
Posts: 13
Hi,
This is my first project and they expect me to know everything.... well i should know.
Ok, I am responsible for developing and designing the presentation tier of an application based on Struts 1.3 framework.
I have the use cases in front of me and I have to design the architecture of the presentation tier ONLY.
Ques. What does the architecture consist of - Class diagrams or Sequence Diagrams or any other UML modelling technique?? Or is it like DFD's?

I am totally clueless, any information would be helpful, please reply,
Thanks in Advance,
Ashish
Peer Reynders
Bartender

Joined: Aug 19, 2005
Posts: 2922
    
    5
This may give you some ideas:
Blueprinting a Struts Application by Ted Husted - Sample specification and API for the Struts Example application.
Struts UML Diagrams (PDF) by Jean-Pierre Schnyder

In this case forget about the term "architecture" in this context. You are creating an overall map of how your design satisfies the requirements outlined in the use cases. Model only the "interesting bits" as the trivial aspects will tend to drown out your design. Travel Light. There is no point repeating the same ActionForm, ActionMapping, ActionClass cluster with slightly different class names over and over again.

Keep focused on Class/Responsibility/Collaboration. Focus a diagram on a small number of classes/objects that collaborate to accomplish a non-trivial task.

Class hierarchies are useful where polymorphism is important.
Static class diagrams can show collaboration but Communication and Sequence diagrams are usually better because they also show the division of responsibilities.
Have a look over Introduction to the Diagrams of UML 2.0 to get a sense what each of the diagram types are good for - and then only use them when you have a actual need for them.

Also have a look at this topic.

Originally posted by ashishk kumar:
I have the use cases in front of me and I have to design the architecture of the presentation tier ONLY.


The use cases are supposed to be used to identify the necessary business functionality. It is possible to build the business layer before the presentation layer. To design the presentation layer you should at least have an idea of the interfaces that the business layer exposes.
 
Don't get me started about those stupid light bulbs.
 
subject: Defining architecture of presentation tier implementing struts