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

deployment diagram - 24 points?

 
Jeanne Boyarsky
author & internet detective
Marshal
Posts: 35279
384
Eclipse IDE Java VI Editor
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
The deployment diagram is worth 24 points. This is more than the sequence diagram. But a sequence diagram is much more involved.

A deployment diagram is basically boxes representing the layers and servers in each layer. (and contingency.) How could it possibly be worth 24 points? I looked at the example in Cade & Sheil. That has more in it than mine, but their architecture is more complicated. Cade & Sheil also say some points are awarded for listing the hardware requirements. I disagree that this is a good idea, but I'll put it in.

This still doesn't seem worth 24 points though. Am I missing something? Or maybe it is the sequence diagram is too low and that's skewing my gut feeling. Compared to the component/class diagram, it seems like a logical amount of points. Or maybe they are including how well your design follows non-functional requirements in the 24 points and not just the diagram?
 
Jomon George
Greenhorn
Posts: 16
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I share same thoughts...
Considering it worth 24 marks, I decided to add more stuff into Deployment Diagram.
 
Anil Chowdary
Ranch Hand
Posts: 43
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I agree with you that from the development point of view, Sequence diagrams are much more important from Deployment diagram. But from the architiecture point of view, the deployment diagram is the one that justifies the scalability, availability requirements mentioned in the problem statement. I think for the very same reason they have awarded more points to Deployment diagrams.
 
deepak adlakha
Ranch Hand
Posts: 325
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Deployment diagram is important, as this tell us where do application component fits in the hardware architecture and how scalability, availability, failover mode are addressed.

Basically its tells us which component is running where and its important part of deliverables and I think that's why its 24 points. Its my personal opinion.
 
Ravi Iyer
Ranch Hand
Posts: 49
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Sheil advises getting to actual hardware specs. I added actual example of what Load balancer could be used (Cisco), what database server (Solaris maybe), what database app (Oracle, DB2 if you are brave :-) )....
I believe the idea is that the candidate should know what kind of software/hardware is available today (I could be wrong - this is just "my understanding").

IMHO - if you are getting into that level of detail, 24 points may be worth

Rgds
 
Jomon George
Greenhorn
Posts: 16
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Thanks a lot for all comments....If we go up to that it worth 24 points.
Cade/Sheil sample is really simple one... just demonstrates load balancing concept.

I think we can also demonstrate/emphasize security aspects in the deployment diagram.

When specifying hardware/software specs, do we need to be specific? , Or can we specify more than one options?

 
Jeanne Boyarsky
author & internet detective
Marshal
Posts: 35279
384
Eclipse IDE Java VI Editor
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Yes, I wound up including the hardware specs. Which just feels wrong because I don't think that belongs in the deployment diagram. But I had to put something in to justify the large number of points!
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic