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

Spliting 1 component diagram into n

 
Aurelio Calegari
Ranch Hand
Posts: 55
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hello,

Sun asks for 1 component diagram. If I do so it will become confusing and complex. Is it ok to split that into many component diagrams in order to show different "views" perspectives of the sysyem?

Thanks in advance.
 
Ricardo Ferreira
Ranch Hand
Posts: 156
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi Aurelio,

There is no problem with this, actually, this is the most appropriate design for the assignment.

Like the real world, you should design a generic component diagram to demonstrate the overall architecture, and realize these architecture for each use case view of your solution.

This means that, if you have 6 use cases from your requirements, you should design 6 component diagrams; each one meeting the general designed architecture.

The same tip applies to the class diagram, because clarity in architecture design is a good point for a better understanding.

I have done my assignment with those ideas, and I could be approved, so you can easly ensure those tips without doubts.

Best Regards,
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic