Win a copy of The Little Book of Impediments (e-book only) this week in the Agile and Other Processes forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Component diagram level of detail

 
Alexander Petrov
Greenhorn
Posts: 27
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi, I am a bit confused about the level of detail I should place in the component diagram. I have created the following scenario. I have a timer service which is communicating with EJB that holds the business logic this EJB communicates with a External web service which returns a DTO that through Mapper is converted to Entity that later is stored by a repository class.

Is it too much if I put everything in the component diagram this would say the DTO to be part of the diagram plus the Entity that will be generated plus the repository class.

Is it better if I remove the mapper and the repository. And leave just the timer service the EJB with the business logic and the Webservice consumer. Is the repository and the mapper too much for the component diagram ? I think that by including them the whole algorithm is much more visible.

I am kind of not completely sure how much details is ok for the component diagram
 
K. Tsang
Bartender
Posts: 3583
16
Android Java
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
First off, the component diagram is a high(er) level view of the class diagram.

Components, according to the assignment, are "key" objects like controllers, DAO, entities, etc.
In another words, if you can group the classes accordingly to a package-like "component" then that thing is in your component diagram.

If I recall correctly, the component diagram has the same points as the class diagram, so being detail is better.
The 2 ends of the extreme can be a) way too simple: "just packages" (aka similar to package diagram) and the other end b) each class is a component itself.

Hope this helps.
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic