Win a copy of Spark in Action this week in the Open Source Projects forum!

Arnold Reuser

Ranch Hand
+ Follow
since Nov 20, 2003
Cows and Likes
Cows
Total received
0
In last 30 days
0
Total given
0
Likes
Total received
6
Received in last 30 days
0
Total given
2
Given in last 30 days
0
Forums and Threads
Scavenger Hunt
expand Ranch Hand Scavenger Hunt
expand Greenhorn Scavenger Hunt

Recent posts by Arnold Reuser

Apart from Togaf you could also have a look at DYA.
5 years ago
Enterprise Architecture as a field and Togaf as a methodology is a broad topic. In what context would you like to apply it and what's your role in that context?
Otherwise providing book references doesn't make much sense.
5 years ago
Service to Worker and Dispatcher View represent the two most common presentation usage scenarios, both describing a common combination of a controller and dispatcher with views and helpers. While describing this common structure, they emphasize related but different usage of patterns :
• Dispatcher View is a view-centric architecture. The view components request business processes and thus might have to assume some controller responsibility.
• Service to Worker is a controller-centric architecture. The controller requests business processes.
The main difference therefore is that unlike Service to Worker, Dispatcher View defers business processing until view processing is performed.
Study guide is for individuals wishing to self study for TOGAF 9 Certification and who plan to take the Part 1 and Part 2 examinations.
No additional training is required.
7 years ago
If Togaf Foundation certification is your primary goal. Then invest two months of your time.
Read the study guide from cover to cover and take a few test exams and you will do fine.
7 years ago
Based on Gartner's 2011 Global Enterprise Architecture Survey, 37% of organizations globally name homemade or blended as their primary framework.
With the exception of Togaf, which is the primary framework for 8% of organizations globally, no other branded framework garners more than 6% of organizations
As such Togaf would be a good investment of your time if your interested in studying an Enterprise Architecture framework and your organization doesn't already have a homemade or blended framework.
From a more regional perspective. Togaf is most popular in Brazil, China and India.
7 years ago
To help you out with your deployment diagram issues.
These are the items I've addressed, related a deployment diagram, to clear my SCEA exam with 98%
Hopefully these guidelines will provide some food for thought while your writing your exam.

Give 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.
This is possible because the exam specifies the no. of concurrent users,
the required up time or words to that effect. The size of a typical request can
be reasonably guessed from the estimated maximum size of the web page in the application .
I don't think they hold it against you for naming a specific vendor as far as you are
able to justify the hardware specifications. Note marks are added if hardware configurations are mentioned.

Also address items like :
* Resilience, fail-over, redundancy characteristics can also be planned and designed for.
* Upgrading Applications Without Loss of Availability can be addressed
* 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, describe appropriate RAID / storage configuration*
* Consider virtualization
* Consider and provide other environments (QA, UAT, pre production)
* Continually review the SLAs for this section

Furthemore I've used a deployment diagram to provide a clear view on the layout
of the components on the web - and application servers.
For this purpose you can use the componts as defined in your component diagram.
And a network diagram to provide a layout of the used servers in a datacenter. And last but not least.
I've mentioned how failover and loadbalancing is organized geographically in case a datacenter fails.

Probably not all items are required if you just want to pass your exam.
But it doesn't harm you, to at least consider them, during your exam and at work.
Is your remark related to one of these guidelines?
The guideline was about using several diagrams to separate concerns
I've passed OCMJEA and Pearson Vue has published the score report. The score is 98%
Below I've stated the main guidelines that I've used while crafting my assignment :
* Use multiple class diagrams to address multiple views e.g. domain and technical related issues
* Help the reader of a sequence diagram understand the flow by adding remarks related to what you would like to achieve
* Clarify how each class maps onto a specific component in your component diagram
* Use official benchmarks and configurations, to proof that you've made a decent guesstimate of your DTAP hardware configurations, to support your deployment diagram

A quote from the email to state that one has passed the Oracle Certified Master :
"Passing grades do not receive a score, just the pass. A failing grade will receive section level scoring so that a candidate may isolate the area of failure and resubmit their assignment. Numeric scores are only provided on failures."

Now because there is a major difference between passing with the absolute minimum score and the maximum score.
I would like to know if it is, in any way, possible to acquire the report stating the scores related to the exam?

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.
What you could do is use a deployment diagram as a logical implementation of your deployment approach.
As a guideline of how to implement this approach :

* Logical servers specified in this diagram could actually be zones - virtual operating systems - on the physical servers deployed.
You could use hardware profiles to depict which logical server is part of an actual physical server
* Containers specified in this diagram could actually be virtual machines on the logical server deployed
Your deployment approach can be used as a guideline to specify what kind of artifact ( e.g. ear, war, jar,.. ) is deployed on a specific type of container
As a result multiple JVMs could potentially be used on one logical server.
* Artifacts specified in this diagram could actually be the set of components you've chosen to package together.

Using this approach will provide you :

* Roadmap of how to transform the components specified in the component diagram into artifacts deployed on an actual set of physical servers.
* Clear view on how,from a deployment point of view, you will actually implement the quailty of service required

To answer this question. Your description is about the open closed principle.
Most applicable patterns are template method or strategy pattern.
You can differ between these two based on the answering the following question :
* Are you redefining a step of an algorithm without changing the algorithms structure. A positive answer on this will result in the template method.
* Are you redefining the structure of the algorithm used. A positive answer on this will result in the strategy pattern.