• Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Class Diagram - Sequence Diagram - Patterns

 
David Brossard
Ranch Hand
Posts: 109
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi guys,

I'm well into my design of the FBN system now and feeling more & more in doubt w/ regards to what Sun expects. I've been reading up different posts here (thanks to all for contributing) but still I've some doubts.

It seems to me (both based on my hunches & what I read) that the class diagram should be technology agnostic. It's an extension of the BDM. It could possibly show patterns depending on its extensiveness.

In my case, the class diagram is merely an extension of the BDM with at most 15 classes. From reading it, you cannot tell whether I intend to use patterns and it doesn't show what would eventually be in the web tier (e.g. servlets & JSPs). In other words it's very much a model class diagram. It's technology-agnostic. Is this acceptable?

I've read that some of you did further class diagrams to explain for instance how the web tier will work (illustrating MVC for instance or another view strategy).

For instance, one could draw a class diagram of the TA's SWING application (I give out SWING as an example - it's not the only option). That class diagram would clearly show the use of patterns.

I do realize that my main class diagram could be 'stereotyped' and the stereotypes would therefore show the patterns in play (e.g. a business delegate...)

W/ regards to the sequence diagrams, I would be tempted to do them based on my core class diagram but if I do so, I'm going to be missing out on a lot of classes. So do the sequence diagrams delve into more detail? Should they be J2EE-specific? What are your thoughts?

Cheers,
David.
 
Ronald Wouters
Ranch Hand
Posts: 190
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
W/ regards to the sequence diagrams, I would be tempted to do them based on my core class diagram


Usually I do things the other way around. I start with the dynamics of the system, walking thru a given use case scenario. The messages that are exchanged between the objects naturally lead the methods and parameters (that need to be) defined in the class diagram. When thinking thru the dynamics I usually tend to think of what patterns are applicable/appropriate for the given use case a lot sooner also. Just my five cents...
 
Marcel Dullaart
Ranch Hand
Posts: 55
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi David,

I know the feeling.
I am somewhat in a similar situation although I did start creating the sequence diagrams first deriving the classes and methods from there, making them out on the fly.
I do think that all UML models should be in sync, meaning showing the same level of detail.
So you can't for instance leave out the classes that make up a pattern in class diagrams, while incorporating in sequence diagrams.
I think that you can simplify the diagrams by using a stereotype. That way you don't have to model every detail of the source code.

Anyway I wish you success on your assignment, please keep sharing your experiences I will do the same on my blog, if I get around to blogging about it.

Marcel.
[ January 28, 2008: Message edited by: Marcel Dullaart ]
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic