• 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 Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Ron McLeod
  • Junilu Lacar
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • Jeanne Boyarsky
  • Rob Spoor
  • Bear Bibeault
Saloon Keepers:
  • Tim Moores
  • Tim Holloway
  • Piet Souris
  • Carey Brown
  • Stephan van Hulst
Bartenders:
  • Frits Walraven
  • fred rosenberger
  • salvin francis

Confused about Component Diagrams

 
Greenhorn
Posts: 11
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I am very confused about what to include in the component diagrams. My class/seq diagrams are set but I am unsure as to what exactly a component is... Can someone point me to examples of J2EE component diagrams that I can use as a model for the SCEA one ?
 
Greenhorn
Posts: 23
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
You can read about Component Diagrams in Martin Fowler's UML Distilled book.
 
Dinesh Bhattacharya
Greenhorn
Posts: 11
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Here is how I have designed my component diagrams. I have laid out 5 diagrams
one for each sub-system / package

Flight
Itinierary
Payment
Pricing
Miles
Security

Within each diagram, I represent the individual classes as components.
When I have to reference a class in other diagram, I just refer to the subsystem name and proceed...

Is this the right approach ? Please reply asap, I am going to submit within 24 hrs...
 
Joseph A Alexander
Greenhorn
Posts: 23
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I cannot validate your approach and I should not. Sorry.

Please refer to Case Study in the Cade Roberts SCEA Study guide.

Component diagrams should have only Components (Ex: J2EE components like EJB, JSP, Servlets etc), J2EE/Core Java Patterns (like DAO, Service Delegate etc), Reference to other Subsystems as you have mentioned and should clearly depict the flow between these components.

Hope this helps.
 
Dinesh Bhattacharya
Greenhorn
Posts: 11
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Ok, thanks for the response. my main question was - is it ok to show subsystems in a component diagram and is it ok to dissect the large component
diagram into smaller units for the SCEA exam....

Looks like I'm on on the 1st question
 
Ranch Hand
Posts: 38
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

Originally posted by Dinesh Bhattacharya:
Ok, thanks for the response. my main question was - is it ok to show subsystems in a component diagram and is it ok to dissect the large component
diagram into smaller units for the SCEA exam....

Looks like I'm on on the 1st question


It's ok to show subsystems and dissect large components as long as your diagrams would not appear to be very confusing. You may also put additional explanations in your assumptions documents. Keep your component diagrams clear, concise, yet simple.
 
Ranch Hand
Posts: 224
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
The following link may help
http://www-128.ibm.com/developerworks/rational/library/dec04/bell/
 
reply
    Bookmark Topic Watch Topic
  • New Topic