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

Cade Sequence Diagrams

 
Edward Peters
Greenhorn
Posts: 8
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hello,
While currently working on the assignment and using the Case Study from the Cade book as an example, I got a few questions:
1. The Case Study does not use the form instance name/class name in the sequence diagrams. Is this common practice or should the diagram show the instance name when the system uses a particular instance?
2. Is it neccesary to show the front end objects, like the JSP's and the front controller in the sequence diagrams? I know in real life I don't, but maybe this is a bad habit I should change.
Basically what I want to know: Is the style used in the Cade diagrams the (only) one accepted by the examiners?
Answers on this topic will be appreciated.
Kind regards,
Edward
 
Bernd Pross
Greenhorn
Posts: 10
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
1. The Case Study does not use the form instance name/class name in the sequence diagrams. Is this common practice or should the diagram show the instance name when the system uses a particular instance?
2. Is it neccesary to show the front end objects, like the JSP's and the front controller in the sequence diagrams? I know in real life I don't, but maybe this is a bad habit I should change.
Basically what I want to know: Is the style used in the Cade diagrams the (only) one accepted by the examiners?
Hi Edward,
1. I don't think you need to show the instance name in a class diagram.
2. For me it's a good idea to show the JSPs in the sequence digrams, so it's clear how the components work togather.
From my point of view Cade is a minimalist somehow, I think his granularity is good enough for passing. Showing more details may not result in more points, but may make it clearer to the assessor to understand your solution (which may result in more points !). So it's up to you how detailed your solution is. My goal was to do the design in a way that someone could do the coding without having to care for any more design decissions.
Hope that helps,
Bernd
 
Juan Rolando Prieur-Reza
Ranch Hand
Posts: 237
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Originally posted by Bernd Pross:
... Case Study does not use the form instance name/class name in the sequence diagrams ...

A sequence diagram in the architectural phase (analysis or design perspective) should not show instances, according to UML. That should be done, if necessary, in an implementation perspective.
... But I can't speak for what the SCEA project really requires on this point.
 
ravi appala
Ranch Hand
Posts: 35
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I think total point of these architecture diagrams is to make a developer or some tech to understand better about the project architecture and how it works. it is always possible that you could go back and forth to give more info, so sequence daigrams could show instances,uml tools also provide that facility to use it if neededd.

thanks,
ravi
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic