Win a copy of Micro Frontends in Action this week in the Server-Side JavaScript and NodeJS forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Ron McLeod
  • Paul Clapham
  • Bear Bibeault
  • Junilu Lacar
Sheriffs:
  • Jeanne Boyarsky
  • Tim Cooke
  • Henry Wong
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • salvin francis
  • Frits Walraven
Bartenders:
  • Scott Selikoff
  • Piet Souris
  • Carey Brown

Does everyone use Mark's SCEA study book Part 2 style to make Component/Deployment diagram?

 
Ranch Hand
Posts: 46
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I am little worry about whether it does hold enough detail.

For example, in Deployment diagram, because max 200 concurrent users at peak times, I only have 7 node with 2 hardware profiles as total. 1 web app ser and 1 standby, 1 db and 1 standby, 3 external system node...

Is it too "simple" to get enough pass point in Deployment diagram(Minimum Pass/ Points : 17/24) ?

Thanks.
 
Ranch Hand
Posts: 462
Scala jQuery Java
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
mine was virtually identical to Cades and I passed
 
Ranch Hand
Posts: 55
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I think it would be quite ridiculous if we had to add unnecessary hardware just to make the deployment diagram more complicated ;). I bet though it would be a good idea to add some explanation showing why do you believe such configuration is sufficient.
 
Ranch Hand
Posts: 196
  • Likes 1
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
To provide you a bit more detail on the potential points of interest related to your deployment diagram.
Here is a list you could use while sketching your own diagram :

* Provide a decent guesstimate of hardware configuration and explain :
Resources: CPU, memory, network and disk
why I need such RAID here and another there and
why here is to be more memory than there.
* Resilience, fail-over, redundancy characteristics can also be planned and designed for.
* Upgrading Applications Without Loss of Availability
* Consider inter-tier security
* Consider using a firewall
* Describe network protocols used
* Describe network connectivity expected
* Define hardware profiles A, B and C in English text
* For database-centric applications (all!), describe appropriate RAID / storage configuration
* Consider virtualization
* Consider and provide other environments (QA, UAT, pre production)
* Continually review the SLAs for this section

Probably there are far more potential points of interest you can use if you use the search functionality of this forum
My point of view of the deployment diagram provided by the study guide is that they are oversimplified.
Whether they are sufficient to pass is already mentioned in a previous post.
 
Ranch Hand
Posts: 40
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I went through Cade and Sheils case study in the SCEA 2nd edition study guide and also Sheils presentation (scea-part-two-2009-bof.pdf) and tried to cover major aspects in both.
 
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.
reply
    Bookmark Topic Watch Topic
  • New Topic