• 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
  • Liutauras Vilda
  • Tim Cooke
  • Jeanne Boyarsky
  • Paul Clapham
Sheriffs:
  • Devaka Cooray
  • Ron McLeod
  • paul wheaton
Saloon Keepers:
  • Tim Moores
  • Piet Souris
  • Tim Holloway
  • Stephan van Hulst
  • Carey Brown
Bartenders:
  • Al Hobbs
  • Frits Walraven
  • Scott Selikoff

class vs component diagram

 
Greenhorn
Posts: 22
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
which classes from the class diagram i dont have to put in component diagram?

do i put interfaces or their implementations in componenet diagram?

which classes that arent on class diagram do i put on component diagram?

what are objects that i put into component diagram? are they classes from class diagram?

is eg security (implemented declarativly in web.xml) a component?

does component ~ class or component ~ package/functionality

which relationship line should connect service with dao on class diagram?

is there any sample solution of sample assignment? or any old assigment from sun?
 
author and cow tipper
Posts: 5006
1
Hibernate Spring Tomcat Server
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
So, I think you might want to start off by defining what a component diagram is. Do a google search and find some sample component diagrams, and find a good definition. Then share with us on this thread what you found out.



http://en.wikipedia.org/wiki/Component_diagram

From the questions you're asking, it seems that you're really struggling with what a component diagram is. Components and classes are very different concepts.

-Cameron McKenzie
 
Kazimierz Trzonek
Greenhorn
Posts: 22
 
Kazimierz Trzonek
Greenhorn
Posts: 22
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
when do we use assembly line, and when normal arrows?

when one component displays an interface, and other uses it - than it's assembly?

but whan use line whith arrow?

shouldn't on below picture be used assebly connections? (picture from http://www.visual-paradigm.com/VPGallery/diagrams/Component.html):



on the picture from wiki assebly is used in internal dependencies of component, and arrows connect to external ports.

are ports equal to interfaces? name port is used in external context and interface in internal?
 
Ranch Hand
Posts: 254
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Read the relevant section of the UML 2.x specification. It makes it quite clear what the various elements are for, the constraints that exist upon them, and the associations and attributes that characterise them
 
If you two don't stop this rough-housing somebody is going to end up crying. Sit down and read this tiny ad:
the value of filler advertising in 2021
https://coderanch.com/t/730886/filler-advertising
reply
    Bookmark Topic Watch Topic
  • New Topic