https://training-course-material.com/index.php?action=history&feed=atom&title=Enterprise_Architecture_AnalysisEnterprise Architecture Analysis - Revision history2026-05-12T23:21:52ZRevision history for this page on the wikiMediaWiki 1.45.1https://training-course-material.com/index.php?title=Enterprise_Architecture_Analysis&diff=29094&oldid=prevAhnboyoung at 17:48, 7 February 20162016-02-07T17:48:02Z<p></p>
<p><b>New page</b></p><div>{{Cat|Enterprise Architecture|70}}<br />
<br />
<slideshow style="nobleprog" headingmark="。" incmark="…" scaled="false" font="Trebuchet MS" ><br />
;title: Enterprise Architecture Analysis<br />
;author: Bernard Szlachta (bs@NobleProg.co.uk)<br />
</slideshow><br />
<br />
=Enterprise Architecture Analysis。=<br />
* We create models in order to support the decision-making process<br />
* Changes in the enterprise architecture should be consulted with the model<br />
* Alternative designs should be <br />
<br />
== Analysis Techniques。 ==<br />
* What to analyse?<br />
** Functional<br />
** Quantitative<br />
* How to analyse?<br />
** Simulation<br />
** Analytical<br />
<br />
== Functional Analysis。 ==<br />
* Validates weather the architecture works<br />
* Validates architecture after change (is it going to work?)<br />
* What is the impact of the change in terms of functional correctness<br />
<br />
== Quantitative Analysis。 ==<br />
* Answers quantitative questions questions like:<br />
** "'''how quick''' the response will come"<br />
** "'''how cheap''' it will be to make a change"<br />
** "'''how much''' is it going to cost" <br />
* Performance is a major concern with today realities<br />
<br />
== Simulation 。==<br />
* Shows dynamic behaviour of the model<br />
* Can check both Functional as well as non-functional aspects of the architecture e.g.<br />
** Is the message going to be received by an appropriate system?<br />
** How many messages can we send per second with the current setup?<br />
<br />
<br />
== Analytical Analysis。 ==<br />
* Provides non-statistical answers (i.e. result is reproducible)<br />
<br />
<br />
==Model Value Destruction。==<br />
by David Bridgeland and Ron Zahavi, Business Modeling: A Practical Guide to Realizing Business Value<br />
* Not every model should be built. <br />
* Sometimes the costs of creating and using a model are greater than the benefits that are gained from its use ('''''model value destruction''''').<br />
* Creating/using a model always takes time: <br />
** time interacting with the subject matter experts, <br />
** time spent constructing the model with modeling tools, and making the model simpler<br />
** time spent finding and fixing problems with the model, <br />
** and time spent verifying a model with subject matter experts. <br />
** time spent analyzing the model for business implications, <br />
** time spent explaining the model to others, <br />
** time spent maintaining the model when things change, and so on.<br />
<br />
The decision about whether to create a model is ultimately an economic decision: Are we going to deliver more value using this model than we will spend creating/using/maintaining it?<br />
<br />
<br />
==Model Value Analysis。==<br />
* For small models, that can be built in an hour or four, we typically make a quick informal analysis (Do we expect to realize enough benefits to offset the time and trouble of creating the model?)<br />
* '''Simple and useful model has value.'''<br />
* More formal analysis - '''model value analysis''' - a summary of the expected costs and the expected benefits, and a comparison of the two.<br />
:[[File:ClipCapIt-140901-155631.PNG]]<br />
* '''Spend 1% of the total anticipated modeling time on the model value analysis, to decide whether the other 99% makes economic sense.'''</div>Ahnboyoung