Win a copy of The Journey To Enterprise Agility this week in the Agile and Other Processes forum! And see the welcome thread for 20% off.
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Jeanne Boyarsky
  • Liutauras Vilda
  • Campbell Ritchie
  • Tim Cooke
  • Bear Bibeault
Sheriffs:
  • Paul Clapham
  • Junilu Lacar
  • Knute Snortum
Saloon Keepers:
  • Ron McLeod
  • Ganesh Patekar
  • Tim Moores
  • Pete Letkeman
  • Stephan van Hulst
Bartenders:
  • Carey Brown
  • Tim Holloway
  • Joe Ess

Component Diagram  RSS feed

 
Greenhorn
Posts: 2
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi guys.

I'm a little bit confused with what I'll put in my component diagram. I had been read some posts of our "gods" (the ones that passed) and they are not so clear. When they said: "I put all j2ee patterns in the component diagrams" what they realy want to say? they put some classes in there? every patterns is a component? or what?

Did you know what they means?

Thanks a lot.

Joao Emilio
 
Greenhorn
Posts: 9
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Component diagram should have all the components in your design and explain how they together fulfill the system requirements. here is a clue..
Client tier may have Application client components, JSPs..
Web tier may have Framework components
Business Tier may have all your Session and Entity bean components and what design patterns they implement( session facade, composite entity, VLH ..)
 
Joao Emilio
Greenhorn
Posts: 2
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Thanks...
 
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!