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 approach

 
guy katz
Greenhorn
Posts: 13
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
hi all;
i am trying to determine which approach would generally serve better
for designing component diagrams:
1. CADEs approach where several use cases are combined into one
component diagram (according to package)
2. have a single component diagram for each use case
are both good options?
what criteria should i consider when deciding on an option?
thanks
 
Bill Morrison
Greenhorn
Posts: 25
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Guy,
As you've discovered, the SCEA Study Guide by Cade and Roberts doesn't attempt to teach you the design methodology that addresses your question. There are several very good books on UML and the methodology, including The Unified Software Development Process by the three amigos.
I have also found that Developing Enterprise Java Applications with J2EE and UML by Ahmed and Umrysh, and Building J2EE Applications with the Rational Unified Process by Eeles, Houston, on Kozaczynski helpful in understanding the current UML/J2EE mainstream.
Regards,
Bill
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic