• Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Class Diagram question

 
muhilan govin
Greenhorn
Posts: 21
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi Ranchers,

As a part of my Dream Car assignment i have created a framework for the web tier. Do i need to show them in my class diagram or component diagram

Thanks in advance.

Regards,
Muhilan
 
Janis Kazakovs
Ranch Hand
Posts: 33
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hello Muhilan,

Assuming you did not use any of the existing J2EE web frameworks and assuming you have based the design of your web framework on some J2EE presentation tier design patterns, as for example, front controller, application controller and have used several command handlers for each view. You could display on your component diagram three components, namely front controller, application controller and command handler. While in your class diagram you could display actual classes that correspond to that or another component. In case of the command handlers your class diagram would display several command handler classes.

Janis
 
muhilan govin
Greenhorn
Posts: 21
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Thanks for the quick reply. How about each of the use cases? i think we can skip the flow through all components of the framework and just show the framework as one component. Is this fine?

Thanks and regards,
Muhilan
 
Janis Kazakovs
Ranch Hand
Posts: 33
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I would not do that. Skipping a component in your sequence diagram would mean that it does not exist in your execution flow. You would have to explain then why it is not present in your sequence diagram, otherwise it will be confusing for the reader. You can, of course, do that. I would rather externalise repeating behaviour in a separate sequence diagram and would reference it in my use case sequence diagram from the interaction use. You can, for example, have a separate sequence diagram that specifies your business logic, and which, in turn, is referenced from another sequence diagram that specifies your presentation logic. Another example, would be a specification of authentication or authorisation behaviours that would be, probably, referenced from all your use case sequence diagram.
 
muhilan govin
Greenhorn
Posts: 21
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Thanks that should be fine even though there would be one additional sequence diagram.

Regards,
Muhilan
 
Maciek Falski
Greenhorn
Posts: 21
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi

I agree, too much details could clutter use case based sequence diagrams. Having seperate diagram for user request handling sounds like very good idea.

Cheers,
Maciek
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic