<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/atom10full.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://feeds.feedburner.com/~d/styles/itemcontent.css"?><feed xmlns="http://www.w3.org/2005/Atom" xmlns:openSearch="http://a9.com/-/spec/opensearch/1.1/" xmlns:georss="http://www.georss.org/georss" xmlns:gd="http://schemas.google.com/g/2005" xmlns:thr="http://purl.org/syndication/thread/1.0" xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" gd:etag="W/&quot;C0UGRHo8eip7ImA9WhRVFUk.&quot;"><id>tag:blogger.com,1999:blog-4560463190032436692</id><updated>2012-01-14T12:40:25.472+01:00</updated><category term="business architecture" /><category term="workflow" /><category term="enterprise architecture" /><category term="architect enterprise BPM systems" /><category term="e-gov" /><category term="terminology" /><category term="enterprise patterns" /><category term="service" /><category term="SOA" /><category term="BPMS" /><category term="book about BPM SOA EA" /><category term="practical process patterns" /><category term="PMO" /><category term="e-Tunisia" /><category term="SAP" /><category term="process orchestration" /><category term="From vendor-centric BPM to customer-centric BPM" /><category term="PI" /><category term="EPN" /><category term="EA" /><category term="NetWeaver" /><category term="enterprise business perfomance" /><category term="PLM" /><category term="ACM" /><category term="SDLC" /><category term="BA" /><category term="process" /><category term="outside-in" /><category term="example" /><category term="OMG" /><category term="KPI" /><category term="BPM reference model" /><category term="IT strategy" /><category term="BPM" /><category term="flexibily" /><category term="cloud" /><category term="ERM" /><category term="PMI" /><category term="SLA" /><category term="ITIL" /><category term="case management" /><category term="e-Tunisie" /><category term="BPMN" /><category term="architect" /><category term="process choreography" /><category term="Intalio" /><category term="architecture" /><category term="automation" /><category term="virtualisation" /><category term="BPM standards" /><category term="data" /><category term="CMMI" /><category term="modelling procedure" /><title>Improving Enterprise Business Process Management Systems</title><subtitle type="html">This blog complements the support web site for my book "Improving enterprise business process management systems" about BPM, SOA and EA, which has just been published (see www.improving-BPM-systems.com/book ).</subtitle><link rel="http://schemas.google.com/g/2005#feed" type="application/atom+xml" href="http://improving-bpm-systems.blogspot.com/feeds/posts/default" /><link rel="alternate" type="text/html" href="http://improving-bpm-systems.blogspot.com/" /><link rel="next" type="application/atom+xml" href="http://www.blogger.com/feeds/4560463190032436692/posts/default?start-index=26&amp;max-results=25&amp;redirect=false&amp;v=2" /><author><name>Alexander Samarin</name><uri>https://profiles.google.com/112810118258856486156</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh5.googleusercontent.com/-rb1Di6vctuI/AAAAAAAAAAI/AAAAAAAAAQM/-5VNACIpAaQ/s512-c/photo.jpg" /></author><generator version="7.00" uri="http://www.blogger.com">Blogger</generator><openSearch:totalResults>176</openSearch:totalResults><openSearch:startIndex>1</openSearch:startIndex><openSearch:itemsPerPage>25</openSearch:itemsPerPage><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" type="application/atom+xml" href="http://feeds.feedburner.com/ImprovingEnterpriseBusinessProcessManagementSystems" /><feedburner:info uri="improvingenterprisebusinessprocessmanagementsystems" /><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com/" /><feedburner:emailServiceId>ImprovingEnterpriseBusinessProcessManagementSystems</feedburner:emailServiceId><feedburner:feedburnerHostname>http://feedburner.google.com</feedburner:feedburnerHostname><entry gd:etag="W/&quot;C0UGRHozfCp7ImA9WhRVFUk.&quot;"><id>tag:blogger.com,1999:blog-4560463190032436692.post-3659266580176154611</id><published>2012-01-14T12:40:00.000+01:00</published><updated>2012-01-14T12:40:25.484+01:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2012-01-14T12:40:25.484+01:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="ITIL" /><category scheme="http://www.blogger.com/atom/ns#" term="EA" /><category scheme="http://www.blogger.com/atom/ns#" term="PMO" /><category scheme="http://www.blogger.com/atom/ns#" term="enterprise patterns" /><title>Enterprise pattern: SITO, extended</title><link rel="replies" type="application/atom+xml" href="http://improving-bpm-systems.blogspot.com/feeds/3659266580176154611/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=4560463190032436692&amp;postID=3659266580176154611" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/4560463190032436692/posts/default/3659266580176154611?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/4560463190032436692/posts/default/3659266580176154611?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/ImprovingEnterpriseBusinessProcessManagementSystems/~3/8I_zag4iueQ/enterprise-pattern-sito-extended.html" title="Enterprise pattern: SITO, extended" /><author><name>Alexander Samarin</name><uri>https://profiles.google.com/112810118258856486156</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh5.googleusercontent.com/-rb1Di6vctuI/AAAAAAAAAAI/AAAAAAAAAQM/-5VNACIpAaQ/s512-c/photo.jpg" /></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://3.bp.blogspot.com/-fEt_klyRVU8/TxFd4kNADSI/AAAAAAAAAh0/YNUxnx10-m0/s72-c/C12.PNG" height="72" width="72" /><thr:total>0</thr:total><georss:featurename>Gammarth, Tunisia</georss:featurename><georss:point>36.91284278707261 10.311012268066406</georss:point><georss:box>36.88745028707261 10.271530268066407 36.938235287072615 10.350494268066406</georss:box><content type="html">
Comments to SITO enterprise pattern (see the updated version of it at http://improving-bpm-systems.blogspot.com/2011/10/enterprise-pattern-structuring-it.html ) were that it is too classic. Sure, structuring is the first step to establish the balance between functions and projects. 





Next step is how to preserve, enrich and re-use the technical/business knowledge and experience gained in 
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/8Ruh3y5aFX9ZEdixpp4kp4_HFZM/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/8Ruh3y5aFX9ZEdixpp4kp4_HFZM/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/8Ruh3y5aFX9ZEdixpp4kp4_HFZM/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/8Ruh3y5aFX9ZEdixpp4kp4_HFZM/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/ImprovingEnterpriseBusinessProcessManagementSystems/~4/8I_zag4iueQ" height="1" width="1"/&gt;</content><feedburner:origLink>http://improving-bpm-systems.blogspot.com/2012/01/enterprise-pattern-sito-extended.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DkQNSHszfyp7ImA9WhRWGUg.&quot;"><id>tag:blogger.com,1999:blog-4560463190032436692.post-847817467021665501</id><published>2012-01-06T09:32:00.001+01:00</published><updated>2012-01-07T17:39:59.587+01:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2012-01-07T17:39:59.587+01:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="virtualisation" /><category scheme="http://www.blogger.com/atom/ns#" term="enterprise patterns" /><title>Enterprise anti-pattern: Silo-Oriented Virtualisation Anarchy (SOVA)</title><link rel="replies" type="application/atom+xml" href="http://improving-bpm-systems.blogspot.com/feeds/847817467021665501/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=4560463190032436692&amp;postID=847817467021665501" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/4560463190032436692/posts/default/847817467021665501?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/4560463190032436692/posts/default/847817467021665501?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/ImprovingEnterpriseBusinessProcessManagementSystems/~3/9fEmaJ9sJgo/enterprise-anti-pattern-silo-orieinted.html" title="Enterprise anti-pattern: Silo-Oriented Virtualisation Anarchy (SOVA)" /><author><name>Alexander Samarin</name><uri>https://profiles.google.com/112810118258856486156</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh5.googleusercontent.com/-rb1Di6vctuI/AAAAAAAAAAI/AAAAAAAAAQM/-5VNACIpAaQ/s512-c/photo.jpg" /></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://4.bp.blogspot.com/-84p-Xvh2k2g/TwawHbMl-SI/AAAAAAAAAhg/hvaW8CGJbSs/s72-c/Capture1.PNG" height="72" width="72" /><thr:total>0</thr:total><content type="html">
That was found in the same organisation....



Normally, an organisation of this size should not used more than 2 virtualisation products.

Thanks,
AS
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/muUQsCNdEfQyfr_HGHXila8ekSw/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/muUQsCNdEfQyfr_HGHXila8ekSw/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/muUQsCNdEfQyfr_HGHXila8ekSw/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/muUQsCNdEfQyfr_HGHXila8ekSw/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/ImprovingEnterpriseBusinessProcessManagementSystems/~4/9fEmaJ9sJgo" height="1" width="1"/&gt;</content><feedburner:origLink>http://improving-bpm-systems.blogspot.com/2012/01/enterprise-anti-pattern-silo-orieinted.html</feedburner:origLink></entry><entry gd:etag="W/&quot;D0cASXYzfip7ImA9WhRXEko.&quot;"><id>tag:blogger.com,1999:blog-4560463190032436692.post-8528825816570182394</id><published>2011-12-18T17:32:00.000+01:00</published><updated>2011-12-19T07:10:48.886+01:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-12-19T07:10:48.886+01:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="cloud" /><category scheme="http://www.blogger.com/atom/ns#" term="enterprise patterns" /><title>Enterprise pattern: #Cloud-Ready Estimation and Evaluation Procedure (CREEP)</title><link rel="replies" type="application/atom+xml" href="http://improving-bpm-systems.blogspot.com/feeds/8528825816570182394/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=4560463190032436692&amp;postID=8528825816570182394" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/4560463190032436692/posts/default/8528825816570182394?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/4560463190032436692/posts/default/8528825816570182394?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/ImprovingEnterpriseBusinessProcessManagementSystems/~3/aGL5Ub0R7aM/enterprise-pattern-cloud-ready.html" title="Enterprise pattern: #Cloud-Ready Estimation and Evaluation Procedure (CREEP)" /><author><name>Alexander Samarin</name><uri>https://profiles.google.com/112810118258856486156</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh5.googleusercontent.com/-rb1Di6vctuI/AAAAAAAAAAI/AAAAAAAAAQM/-5VNACIpAaQ/s512-c/photo.jpg" /></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://1.bp.blogspot.com/-GmfTYHMerGI/Tu4Uu_jNy9I/AAAAAAAAAhQ/7vnZsxqjQR0/s72-c/Capture.PNG" height="72" width="72" /><thr:total>0</thr:total><georss:featurename>Gammarth, Tunisia</georss:featurename><georss:point>36.9097222 10.2866667</georss:point><georss:box>36.884329699999995 10.2471847 36.9351147 10.3261487</georss:box><content type="html">
The aim of this post is to consider a systematic procedure for estimation and evaluation of cloudability of an IT service – what type of cloud (GOLD, YELLOW, GREEN, BLUE, VIOLET) is acceptable for a particular IT service and for what cost.

Quick reminder re the zone types (from http://improving-bpm-systems.blogspot.com/2011/07/1-relationships-between-enterprise.html ):



classic within 
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/Zb9Z5WtGz-4XxyyBSVihSx6byrc/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/Zb9Z5WtGz-4XxyyBSVihSx6byrc/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/Zb9Z5WtGz-4XxyyBSVihSx6byrc/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/Zb9Z5WtGz-4XxyyBSVihSx6byrc/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/ImprovingEnterpriseBusinessProcessManagementSystems/~4/aGL5Ub0R7aM" height="1" width="1"/&gt;</content><feedburner:origLink>http://improving-bpm-systems.blogspot.com/2011/12/enterprise-pattern-cloud-ready.html</feedburner:origLink></entry><entry gd:etag="W/&quot;AkcMQX87eyp7ImA9WhRVFU4.&quot;"><id>tag:blogger.com,1999:blog-4560463190032436692.post-1537428406102857094</id><published>2011-10-15T17:28:00.000+02:00</published><updated>2012-01-14T11:48:00.103+01:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2012-01-14T11:48:00.103+01:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="enterprise patterns" /><title>Enterprise pattern: Structuring IT Organisation (SITO)</title><link rel="replies" type="application/atom+xml" href="http://improving-bpm-systems.blogspot.com/feeds/1537428406102857094/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=4560463190032436692&amp;postID=1537428406102857094" title="1 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/4560463190032436692/posts/default/1537428406102857094?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/4560463190032436692/posts/default/1537428406102857094?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/ImprovingEnterpriseBusinessProcessManagementSystems/~3/HGRY0xwRqKg/enterprise-pattern-structuring-it.html" title="Enterprise pattern: Structuring IT Organisation (SITO)" /><author><name>Alexander Samarin</name><uri>https://profiles.google.com/112810118258856486156</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh5.googleusercontent.com/-rb1Di6vctuI/AAAAAAAAAAI/AAAAAAAAAQM/-5VNACIpAaQ/s512-c/photo.jpg" /></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://3.bp.blogspot.com/-bfo5lVF9AHU/Tu3khjs5aRI/AAAAAAAAAgM/bLdBPwb2eN8/s72-c/01.PNG" height="72" width="72" /><thr:total>1</thr:total><content type="html">
How to decompose an IT organisation into smaller units?






Approach

Collect major IT-related functions (approx. 30-50) to be carried out at an IT organisation; potential sources COBIT, ITIL, PMBOK, PRINCE2, HERMES, etc. 
Draw a matrix of mutual relationships between those functions or group of functions (about 10) 
The relationships may be like “synergy” (functions to be carried-out rather 
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/A7RFNMHwF5HUfqhEC-LDaShvLI8/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/A7RFNMHwF5HUfqhEC-LDaShvLI8/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/A7RFNMHwF5HUfqhEC-LDaShvLI8/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/A7RFNMHwF5HUfqhEC-LDaShvLI8/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/ImprovingEnterpriseBusinessProcessManagementSystems/~4/HGRY0xwRqKg" height="1" width="1"/&gt;</content><feedburner:origLink>http://improving-bpm-systems.blogspot.com/2011/10/enterprise-pattern-structuring-it.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DU4FSXc6eyp7ImA9WhdbEUU.&quot;"><id>tag:blogger.com,1999:blog-4560463190032436692.post-1716610975817769192</id><published>2011-10-09T21:17:00.001+02:00</published><updated>2011-10-09T21:18:38.913+02:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-10-09T21:18:38.913+02:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="EA" /><category scheme="http://www.blogger.com/atom/ns#" term="ERM" /><title>EA view on Enterprise Risk Management (ERM) platform</title><link rel="replies" type="application/atom+xml" href="http://improving-bpm-systems.blogspot.com/feeds/1716610975817769192/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=4560463190032436692&amp;postID=1716610975817769192" title="3 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/4560463190032436692/posts/default/1716610975817769192?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/4560463190032436692/posts/default/1716610975817769192?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/ImprovingEnterpriseBusinessProcessManagementSystems/~3/4M6_UWCe2uc/ea-view-on-enterprise-risk-management.html" title="EA view on Enterprise Risk Management (ERM) platform" /><author><name>Alexander Samarin</name><uri>https://profiles.google.com/112810118258856486156</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh5.googleusercontent.com/-rb1Di6vctuI/AAAAAAAAAAI/AAAAAAAAAQM/-5VNACIpAaQ/s512-c/photo.jpg" /></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://2.bp.blogspot.com/-EjTl8k3zncY/TpHyfHgGBXI/AAAAAAAAAcc/iqPilDOuyHY/s72-c/p1.PNG" height="72" width="72" /><thr:total>3</thr:total><content type="html">In many cases, it is impossible to find a single ERM product which spans all business areas to be covers by ERM. So, it is require building an internal ERM platform on top of which different ERM-related applications will be built (following the PEAS enterprise pattern – see http://improving-bpm-systems.blogspot.com/2011/04/enterprise-patterns-peas.html ).

Business architecture viewRisk must be 
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/-Fxvwc3lEndhV67ZUo5L4N_AMuQ/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/-Fxvwc3lEndhV67ZUo5L4N_AMuQ/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/-Fxvwc3lEndhV67ZUo5L4N_AMuQ/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/-Fxvwc3lEndhV67ZUo5L4N_AMuQ/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/ImprovingEnterpriseBusinessProcessManagementSystems/~4/4M6_UWCe2uc" height="1" width="1"/&gt;</content><feedburner:origLink>http://improving-bpm-systems.blogspot.com/2011/10/ea-view-on-enterprise-risk-management.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DUAMQH4yeSp7ImA9WhdVGUk.&quot;"><id>tag:blogger.com,1999:blog-4560463190032436692.post-1452877429180836149</id><published>2011-09-22T14:46:00.008+02:00</published><updated>2011-09-25T12:49:41.091+02:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-09-25T12:49:41.091+02:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="EA" /><category scheme="http://www.blogger.com/atom/ns#" term="IT strategy" /><title>Writing  IT strategy</title><link rel="replies" type="application/atom+xml" href="http://improving-bpm-systems.blogspot.com/feeds/1452877429180836149/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=4560463190032436692&amp;postID=1452877429180836149" title="2 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/4560463190032436692/posts/default/1452877429180836149?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/4560463190032436692/posts/default/1452877429180836149?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/ImprovingEnterpriseBusinessProcessManagementSystems/~3/n6Vk-BluVPI/writing-it-strategy.html" title="Writing  IT strategy" /><author><name>Alexander Samarin</name><uri>https://profiles.google.com/112810118258856486156</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh5.googleusercontent.com/-rb1Di6vctuI/AAAAAAAAAAI/AAAAAAAAAQM/-5VNACIpAaQ/s512-c/photo.jpg" /></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://3.bp.blogspot.com/-o8uoc5JeslU/Tn4tSjypaaI/AAAAAAAAAcQ/GhZAFCiiKws/s72-c/dep2.PNG" height="72" width="72" /><thr:total>2</thr:total><content type="html">
The IT strategy development logic is the following:
Business strategy -&amp;gt; business architecture TO-BE -&amp;gt; application + information architectures TO-BE -&amp;gt; technical architecture TO-BE -&amp;gt; IT (or EA) AS-IS -&amp;gt; IT roadmap 

Main topics in the IT strategy document are the following:
Executive summary (½ page – summary for senior management, e.g. the Board members)
Business context (½ page – WHY the 
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/ee8wokWefBuST3BEBBfUdsJPcqY/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/ee8wokWefBuST3BEBBfUdsJPcqY/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/ee8wokWefBuST3BEBBfUdsJPcqY/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/ee8wokWefBuST3BEBBfUdsJPcqY/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/ImprovingEnterpriseBusinessProcessManagementSystems/~4/n6Vk-BluVPI" height="1" width="1"/&gt;</content><feedburner:origLink>http://improving-bpm-systems.blogspot.com/2011/09/writing-it-strategy.html</feedburner:origLink></entry><entry gd:etag="W/&quot;CUQMQnY8fSp7ImA9WhdQFk0.&quot;"><id>tag:blogger.com,1999:blog-4560463190032436692.post-8050836928421813357</id><published>2011-08-17T19:49:00.000+02:00</published><updated>2011-08-17T19:49:43.875+02:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-08-17T19:49:43.875+02:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="SDLC" /><category scheme="http://www.blogger.com/atom/ns#" term="EA" /><category scheme="http://www.blogger.com/atom/ns#" term="BPM" /><title>Relationship between #BPM and #SDLC and Software Engineering (SE)</title><link rel="replies" type="application/atom+xml" href="http://improving-bpm-systems.blogspot.com/feeds/8050836928421813357/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=4560463190032436692&amp;postID=8050836928421813357" title="2 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/4560463190032436692/posts/default/8050836928421813357?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/4560463190032436692/posts/default/8050836928421813357?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/ImprovingEnterpriseBusinessProcessManagementSystems/~3/1fEn1SrTy3Q/relationship-between-bpm-and-sdlc-and.html" title="Relationship between #BPM and #SDLC and Software Engineering (SE)" /><author><name>Alexander Samarin</name><uri>https://profiles.google.com/112810118258856486156</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh5.googleusercontent.com/-rb1Di6vctuI/AAAAAAAAAAI/AAAAAAAAAQM/-5VNACIpAaQ/s512-c/photo.jpg" /></author><thr:total>2</thr:total><content type="html">In my experience, BPM and SE are very natural friends (with the help from SOA, EA and BA) which work well together within a proper architecture.  

Some basics: Any complex system is a dynamic set of artefacts (or building blocks?), e.g. in case of a typical business system those artefacts are: processes, services, events, data structures, documents, rules, roles, activities, audit trails, KPIs. 
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/Shf6M6BJEW-dsAu7ApesgL0EPwM/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/Shf6M6BJEW-dsAu7ApesgL0EPwM/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/Shf6M6BJEW-dsAu7ApesgL0EPwM/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/Shf6M6BJEW-dsAu7ApesgL0EPwM/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/ImprovingEnterpriseBusinessProcessManagementSystems/~4/1fEn1SrTy3Q" height="1" width="1"/&gt;</content><feedburner:origLink>http://improving-bpm-systems.blogspot.com/2011/08/relationship-between-bpm-and-sdlc-and.html</feedburner:origLink></entry><entry gd:etag="W/&quot;CE4EQnsyfCp7ImA9WhdREEg.&quot;"><id>tag:blogger.com,1999:blog-4560463190032436692.post-4075892908065027478</id><published>2011-07-30T21:00:00.003+02:00</published><updated>2011-07-30T21:08:23.594+02:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-07-30T21:08:23.594+02:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="e-Tunisie" /><category scheme="http://www.blogger.com/atom/ns#" term="e-gov" /><category scheme="http://www.blogger.com/atom/ns#" term="e-Tunisia" /><title>E-Tunisia / e-consultations:  solution architecture</title><link rel="replies" type="application/atom+xml" href="http://improving-bpm-systems.blogspot.com/feeds/4075892908065027478/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=4560463190032436692&amp;postID=4075892908065027478" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/4560463190032436692/posts/default/4075892908065027478?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/4560463190032436692/posts/default/4075892908065027478?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/ImprovingEnterpriseBusinessProcessManagementSystems/~3/JwePbd21ADE/e-tunisia-e-consultations-solution.html" title="E-Tunisia / e-consultations:  solution architecture" /><author><name>Alexander Samarin</name><uri>https://profiles.google.com/112810118258856486156</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh5.googleusercontent.com/-rb1Di6vctuI/AAAAAAAAAAI/AAAAAAAAAQM/-5VNACIpAaQ/s512-c/photo.jpg" /></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://3.bp.blogspot.com/-kO5fYQfVid8/TjRSIZo7J4I/AAAAAAAAAOg/gy_UsIMxGm0/s72-c/1.png" height="72" width="72" /><thr:total>0</thr:total><content type="html">General
 Continuation from the previous post - E-Tunisia / e-consultations: overview


Definition
E-consultations constitute interactive “tell-us-what-you-think” on-line services where ordinary citizens, civic actors, experts, and politicians purposively assemble to provide input, deliberate, inform, and influence policy and decision making.

Privacy considerationsOnly authorized person can 
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/ap4kAsVU1vrzGVHjuez24f4PuGs/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/ap4kAsVU1vrzGVHjuez24f4PuGs/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/ap4kAsVU1vrzGVHjuez24f4PuGs/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/ap4kAsVU1vrzGVHjuez24f4PuGs/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/ImprovingEnterpriseBusinessProcessManagementSystems/~4/JwePbd21ADE" height="1" width="1"/&gt;</content><feedburner:origLink>http://improving-bpm-systems.blogspot.com/2011/07/e-tunisia-e-consultations-solution.html</feedburner:origLink></entry><entry gd:etag="W/&quot;CEEESH89eyp7ImA9WhdREEg.&quot;"><id>tag:blogger.com,1999:blog-4560463190032436692.post-6177708905421585824</id><published>2011-07-29T21:12:00.002+02:00</published><updated>2011-07-30T21:03:29.163+02:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-07-30T21:03:29.163+02:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="e-Tunisie" /><category scheme="http://www.blogger.com/atom/ns#" term="e-gov" /><category scheme="http://www.blogger.com/atom/ns#" term="e-Tunisia" /><title>E-Tunisia / e-consultations: overview</title><link rel="replies" type="application/atom+xml" href="http://improving-bpm-systems.blogspot.com/feeds/6177708905421585824/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=4560463190032436692&amp;postID=6177708905421585824" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/4560463190032436692/posts/default/6177708905421585824?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/4560463190032436692/posts/default/6177708905421585824?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/ImprovingEnterpriseBusinessProcessManagementSystems/~3/Y7y659DVyrg/e-tunisia-e-consultations-overview.html" title="E-Tunisia / e-consultations: overview" /><author><name>Alexander Samarin</name><uri>https://profiles.google.com/112810118258856486156</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh5.googleusercontent.com/-rb1Di6vctuI/AAAAAAAAAAI/AAAAAAAAAQM/-5VNACIpAaQ/s512-c/photo.jpg" /></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://2.bp.blogspot.com/-eHMdUB0HjBc/TjMFeRBDB1I/AAAAAAAAAOY/6axHag8o9FM/s72-c/we.png" height="72" width="72" /><thr:total>0</thr:total><content type="html">
Continuation from the previous post - E-government for Tunisia (E-Tunisia) : Help to move forwards

We, the people, are the government

E-consultations constitute interactive “tell-us-what-you-think” on-line services where ordinary citizens, civic actors, experts, and politicians purposively assemble to provide input, deliberate, inform, and influence policy and decision making. E-consultation 
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/Zdh7LYZbm7LQ2KBGUyAXOHNGJBc/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/Zdh7LYZbm7LQ2KBGUyAXOHNGJBc/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/Zdh7LYZbm7LQ2KBGUyAXOHNGJBc/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/Zdh7LYZbm7LQ2KBGUyAXOHNGJBc/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/ImprovingEnterpriseBusinessProcessManagementSystems/~4/Y7y659DVyrg" height="1" width="1"/&gt;</content><feedburner:origLink>http://improving-bpm-systems.blogspot.com/2011/07/e-tunisia-e-consultations-overview.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DkAGRXk6cSp7ImA9WhdREEk.&quot;"><id>tag:blogger.com,1999:blog-4560463190032436692.post-1682160121467813197</id><published>2011-07-29T21:01:00.003+02:00</published><updated>2011-07-30T18:52:04.719+02:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-07-30T18:52:04.719+02:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="e-Tunisie" /><category scheme="http://www.blogger.com/atom/ns#" term="e-gov" /><category scheme="http://www.blogger.com/atom/ns#" term="e-Tunisia" /><title>E-government for Tunisia (E-Tunisia) : Help to move forwards</title><link rel="replies" type="application/atom+xml" href="http://improving-bpm-systems.blogspot.com/feeds/1682160121467813197/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=4560463190032436692&amp;postID=1682160121467813197" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/4560463190032436692/posts/default/1682160121467813197?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/4560463190032436692/posts/default/1682160121467813197?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/ImprovingEnterpriseBusinessProcessManagementSystems/~3/_syytXItKdU/e-government-for-tunisia-e-tunisia-help.html" title="E-government for Tunisia (E-Tunisia) : Help to move forwards" /><author><name>Alexander Samarin</name><uri>https://profiles.google.com/112810118258856486156</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh5.googleusercontent.com/-rb1Di6vctuI/AAAAAAAAAAI/AAAAAAAAAQM/-5VNACIpAaQ/s512-c/photo.jpg" /></author><thr:total>0</thr:total><content type="html">It has been proven that the deployment of e-government [E-government is the use of information and communication technologies (ICTs) to improve the activities of public sector organisations] brings the following advantages:
streamlining of the interactions of the citizens and business with the central, regional and local governments;
increase in the performance of workers at governmental agencies
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/GNVC6bcd7EIoT39v27NUl0aRhjE/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/GNVC6bcd7EIoT39v27NUl0aRhjE/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/GNVC6bcd7EIoT39v27NUl0aRhjE/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/GNVC6bcd7EIoT39v27NUl0aRhjE/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/ImprovingEnterpriseBusinessProcessManagementSystems/~4/_syytXItKdU" height="1" width="1"/&gt;</content><feedburner:origLink>http://improving-bpm-systems.blogspot.com/2011/07/e-government-for-tunisia-e-tunisia-help.html</feedburner:origLink></entry><entry gd:etag="W/&quot;C0ANRHsyeCp7ImA9WhdSEE8.&quot;"><id>tag:blogger.com,1999:blog-4560463190032436692.post-9125863242109114176</id><published>2011-07-18T22:43:00.000+02:00</published><updated>2011-07-18T22:43:15.590+02:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-07-18T22:43:15.590+02:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="EA" /><title>Linkedin: In one word, what is the single largest problem facing #entarch?</title><link rel="replies" type="application/atom+xml" href="http://improving-bpm-systems.blogspot.com/feeds/9125863242109114176/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=4560463190032436692&amp;postID=9125863242109114176" title="4 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/4560463190032436692/posts/default/9125863242109114176?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/4560463190032436692/posts/default/9125863242109114176?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/ImprovingEnterpriseBusinessProcessManagementSystems/~3/a5Hu01KQCxA/linkedin-in-one-word-what-is-single.html" title="Linkedin: In one word, what is the single largest problem facing #entarch?" /><author><name>Alexander Samarin</name><uri>https://profiles.google.com/112810118258856486156</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh5.googleusercontent.com/-rb1Di6vctuI/AAAAAAAAAAI/AAAAAAAAAQM/-5VNACIpAaQ/s512-c/photo.jpg" /></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://4.bp.blogspot.com/-JspCGDU1CYQ/TiSWVbDo-II/AAAAAAAAAOQ/RHefcHbAar8/s72-c/Capture.PNG" height="72" width="72" /><thr:total>4</thr:total><content type="html">A quick statistical analysis of the responses (with some categorization, e.g.” cacophony” -&amp;gt; “chaos” -&amp;gt; “confusion”) in the linkedin discussion "In one word, what is the single largest problem facing Enterprise Architecture?"  http://www.linkedin.com/groupAnswers?viewQuestionAndAnswers=&amp;amp;discussionID=43593317&amp;amp;gid=36781&amp;amp;commentID=45630743&amp;amp;trk=view_disc
373 unique replies from unique people (the 
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/tFQPTMABVfJ96JRLhn2FifHI8rU/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/tFQPTMABVfJ96JRLhn2FifHI8rU/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/tFQPTMABVfJ96JRLhn2FifHI8rU/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/tFQPTMABVfJ96JRLhn2FifHI8rU/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/ImprovingEnterpriseBusinessProcessManagementSystems/~4/a5Hu01KQCxA" height="1" width="1"/&gt;</content><feedburner:origLink>http://improving-bpm-systems.blogspot.com/2011/07/linkedin-in-one-word-what-is-single.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DUcDRH8_eip7ImA9WhdTFUs.&quot;"><id>tag:blogger.com,1999:blog-4560463190032436692.post-3232260698601286285</id><published>2011-07-13T12:08:00.001+02:00</published><updated>2011-07-13T16:24:35.142+02:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-07-13T16:24:35.142+02:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="enterprise patterns" /><title>Enterprise patterns: Petit Informaticien (PI) for "What is the key to getting business value from IT?"</title><link rel="replies" type="application/atom+xml" href="http://improving-bpm-systems.blogspot.com/feeds/3232260698601286285/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=4560463190032436692&amp;postID=3232260698601286285" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/4560463190032436692/posts/default/3232260698601286285?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/4560463190032436692/posts/default/3232260698601286285?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/ImprovingEnterpriseBusinessProcessManagementSystems/~3/ZSTYpfPbihY/enterprise-pattern-petit-informaticien.html" title="Enterprise patterns: Petit Informaticien (PI) for &quot;What is the key to getting business value from IT?&quot;" /><author><name>Alexander Samarin</name><uri>https://profiles.google.com/112810118258856486156</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh5.googleusercontent.com/-rb1Di6vctuI/AAAAAAAAAAI/AAAAAAAAAQM/-5VNACIpAaQ/s512-c/photo.jpg" /></author><thr:total>0</thr:total><content type="html">As reply to EBIZQ.net question "What is the key to getting business value from IT?"  http://www.ebizq.net/blogs/ebizq_forum/2011/07/what-is-the-key-to-delivering-business-value-with-it.php

I use the algorithm or enterprise pattern “petit informaticien” (PI):

-1) learn the big picture
0) prepare an initial set of tools to implement incrementally business solutions within that big picture
1) 
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/0pAhXJP0mLkn2EMIJn_VDZETKkY/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/0pAhXJP0mLkn2EMIJn_VDZETKkY/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/0pAhXJP0mLkn2EMIJn_VDZETKkY/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/0pAhXJP0mLkn2EMIJn_VDZETKkY/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/ImprovingEnterpriseBusinessProcessManagementSystems/~4/ZSTYpfPbihY" height="1" width="1"/&gt;</content><feedburner:origLink>http://improving-bpm-systems.blogspot.com/2011/07/enterprise-pattern-petit-informaticien.html</feedburner:origLink></entry><entry gd:etag="W/&quot;A04HSHs_eSp7ImA9WhdTEU8.&quot;"><id>tag:blogger.com,1999:blog-4560463190032436692.post-4125098515173317595</id><published>2011-07-08T14:57:00.003+02:00</published><updated>2011-07-08T14:58:59.541+02:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-07-08T14:58:59.541+02:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="SOA" /><category scheme="http://www.blogger.com/atom/ns#" term="cloud" /><category scheme="http://www.blogger.com/atom/ns#" term="BPM" /><category scheme="http://www.blogger.com/atom/ns#" term="enterprise patterns" /><title>Enterprise patterns: CAPS</title><link rel="replies" type="application/atom+xml" href="http://improving-bpm-systems.blogspot.com/feeds/4125098515173317595/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=4560463190032436692&amp;postID=4125098515173317595" title="1 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/4560463190032436692/posts/default/4125098515173317595?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/4560463190032436692/posts/default/4125098515173317595?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/ImprovingEnterpriseBusinessProcessManagementSystems/~3/90CmoDeW_Do/enterprise-patterns-caps.html" title="Enterprise patterns: CAPS" /><author><name>Alexander Samarin</name><uri>https://profiles.google.com/112810118258856486156</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh5.googleusercontent.com/-rb1Di6vctuI/AAAAAAAAAAI/AAAAAAAAAQM/-5VNACIpAaQ/s512-c/photo.jpg" /></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://2.bp.blogspot.com/-He1tzinMqGE/Thb8BWsAhWI/AAAAAAAAAOA/KqYzytXLURc/s72-c/approach-framework-c.png" height="72" width="72" /><thr:total>1</thr:total><content type="html">A quote from my previous blogpost http://improving-bpm-systems.blogspot.com/2011/07/1-relationships-between-enterprise.html about Enterprise Architecture (EA) and cloud computing:  Ideally, a cloud-optimised solution is a set of interrelated and interconnected services which are good cloud citizens (or highly cloudable).

This blogpost describes a pattern Cloud-Aware Processes and Services (CAPS)
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/OAY0VLNMdQ8og4sibVukiy8Magk/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/OAY0VLNMdQ8og4sibVukiy8Magk/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/OAY0VLNMdQ8og4sibVukiy8Magk/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/OAY0VLNMdQ8og4sibVukiy8Magk/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/ImprovingEnterpriseBusinessProcessManagementSystems/~4/90CmoDeW_Do" height="1" width="1"/&gt;</content><feedburner:origLink>http://improving-bpm-systems.blogspot.com/2011/07/enterprise-patterns-caps.html</feedburner:origLink></entry><entry gd:etag="W/&quot;A0QHRXc5eip7ImA9WhZaFk0.&quot;"><id>tag:blogger.com,1999:blog-4560463190032436692.post-2625025691811028721</id><published>2011-07-01T12:27:00.004+02:00</published><updated>2011-07-02T14:22:14.922+02:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-07-02T14:22:14.922+02:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="cloud" /><category scheme="http://www.blogger.com/atom/ns#" term="EA" /><title>Relationships between Enterprise Architecture (EA, #entarch) and #cloud computing</title><link rel="replies" type="application/atom+xml" href="http://improving-bpm-systems.blogspot.com/feeds/2625025691811028721/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=4560463190032436692&amp;postID=2625025691811028721" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/4560463190032436692/posts/default/2625025691811028721?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/4560463190032436692/posts/default/2625025691811028721?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/ImprovingEnterpriseBusinessProcessManagementSystems/~3/vhcWWM6xeI8/1-relationships-between-enterprise.html" title="Relationships between Enterprise Architecture (EA, #entarch) and #cloud computing" /><author><name>Alexander Samarin</name><uri>https://profiles.google.com/112810118258856486156</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh5.googleusercontent.com/-rb1Di6vctuI/AAAAAAAAAAI/AAAAAAAAAQM/-5VNACIpAaQ/s512-c/photo.jpg" /></author><thr:total>0</thr:total><content type="html">Big picture
The effective use of cloud computing at the enterprise level is a two-way street: 
the use of cloud should be architected for the needs and realities of a particular enterprise and 
the application portfolio, technologies, etc. used in an enterprise should be adapted to achieve the full potentials of cloud computing. 
In general, EA deals with a system of systems. In general, those 
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/XR5lyVmAozCCRsv0rUZtq-wZRrE/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/XR5lyVmAozCCRsv0rUZtq-wZRrE/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/XR5lyVmAozCCRsv0rUZtq-wZRrE/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/XR5lyVmAozCCRsv0rUZtq-wZRrE/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/ImprovingEnterpriseBusinessProcessManagementSystems/~4/vhcWWM6xeI8" height="1" width="1"/&gt;</content><feedburner:origLink>http://improving-bpm-systems.blogspot.com/2011/07/1-relationships-between-enterprise.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DU8CQHwzcSp7ImA9WhZbGUQ.&quot;"><id>tag:blogger.com,1999:blog-4560463190032436692.post-8871383497420177116</id><published>2011-06-25T12:31:00.000+02:00</published><updated>2011-06-25T12:31:01.289+02:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-06-25T12:31:01.289+02:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="practical process patterns" /><category scheme="http://www.blogger.com/atom/ns#" term="BPMN" /><title>Practical process patterns: DIP</title><link rel="replies" type="application/atom+xml" href="http://improving-bpm-systems.blogspot.com/feeds/8871383497420177116/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=4560463190032436692&amp;postID=8871383497420177116" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/4560463190032436692/posts/default/8871383497420177116?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/4560463190032436692/posts/default/8871383497420177116?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/ImprovingEnterpriseBusinessProcessManagementSystems/~3/Viu6fDx5qOs/practical-process-patterns-dip.html" title="Practical process patterns: DIP" /><author><name>Alexander Samarin</name><uri>https://profiles.google.com/112810118258856486156</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh5.googleusercontent.com/-rb1Di6vctuI/AAAAAAAAAAI/AAAAAAAAAQM/-5VNACIpAaQ/s512-c/photo.jpg" /></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://4.bp.blogspot.com/-qW0xQMoktIQ/TgW3z3Gt2bI/AAAAAAAAAN4/piQQZIRWyrE/s72-c/GestionSinistres_1.0.png" height="72" width="72" /><thr:total>0</thr:total><content type="html">
Decompose Into Patterns (DIP)
A friend of mine asked me to have a look at his first try of business process modelling in BPMN. The modelled process is well-known – “gestion de sinistres” or “claim processing”.

An apartment owner/leaseholder, who got an accident, inform the property managing company (régie), they call a repair service and validate the repair cost with the insurance company. Then
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/SbBQNnHq_IYiNr3_F2f4qAQwL68/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/SbBQNnHq_IYiNr3_F2f4qAQwL68/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/SbBQNnHq_IYiNr3_F2f4qAQwL68/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/SbBQNnHq_IYiNr3_F2f4qAQwL68/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/ImprovingEnterpriseBusinessProcessManagementSystems/~4/Viu6fDx5qOs" height="1" width="1"/&gt;</content><feedburner:origLink>http://improving-bpm-systems.blogspot.com/2011/06/practical-process-patterns-dip.html</feedburner:origLink></entry><entry gd:etag="W/&quot;AkYDR3g7fip7ImA9WhZbEkU.&quot;"><id>tag:blogger.com,1999:blog-4560463190032436692.post-4862817114320393061</id><published>2011-06-17T07:22:00.000+02:00</published><updated>2011-06-17T07:22:56.606+02:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-06-17T07:22:56.606+02:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="BPM" /><title>EBIZQ.NET: Should the language of #BPM be the language of business?</title><link rel="replies" type="application/atom+xml" href="http://improving-bpm-systems.blogspot.com/feeds/4862817114320393061/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=4560463190032436692&amp;postID=4862817114320393061" title="1 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/4560463190032436692/posts/default/4862817114320393061?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/4560463190032436692/posts/default/4862817114320393061?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/ImprovingEnterpriseBusinessProcessManagementSystems/~3/yVYWW5atykY/ebizqnet-should-language-of-bpm-be.html" title="EBIZQ.NET: Should the language of #BPM be the language of business?" /><author><name>Alexander Samarin</name><uri>https://profiles.google.com/112810118258856486156</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh5.googleusercontent.com/-rb1Di6vctuI/AAAAAAAAAAI/AAAAAAAAAQM/-5VNACIpAaQ/s512-c/photo.jpg" /></author><thr:total>1</thr:total><content type="html">&amp;lt;discussion ref="http://www.ebizq.net/blogs/ebizq_forum/2011/06/should-the-language-of-bpm-be-the-language-of-business.php" /&amp;gt;

In my experience, it is the best option so far. BPM (how to use processes to manage the enterprise) is good as the language of business for the following reasons:
BPM main “tool” -- process (an explicitly-defined coordination of activities to create a particular result) 
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/E0NdHbWoti_lOrV_sJZhIVFipVo/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/E0NdHbWoti_lOrV_sJZhIVFipVo/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/E0NdHbWoti_lOrV_sJZhIVFipVo/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/E0NdHbWoti_lOrV_sJZhIVFipVo/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/ImprovingEnterpriseBusinessProcessManagementSystems/~4/yVYWW5atykY" height="1" width="1"/&gt;</content><feedburner:origLink>http://improving-bpm-systems.blogspot.com/2011/06/ebizqnet-should-language-of-bpm-be.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DkIBQX8_cCp7ImA9WhZUGEw.&quot;"><id>tag:blogger.com,1999:blog-4560463190032436692.post-1360328125183418382</id><published>2011-06-11T19:49:00.000+02:00</published><updated>2011-06-11T19:49:10.148+02:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-06-11T19:49:10.148+02:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="BPMS" /><category scheme="http://www.blogger.com/atom/ns#" term="NetWeaver" /><category scheme="http://www.blogger.com/atom/ns#" term="PI" /><category scheme="http://www.blogger.com/atom/ns#" term="SAP" /><title>First impression -- #SAP #NetWeaver #BPM tool</title><link rel="replies" type="application/atom+xml" href="http://improving-bpm-systems.blogspot.com/feeds/1360328125183418382/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=4560463190032436692&amp;postID=1360328125183418382" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/4560463190032436692/posts/default/1360328125183418382?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/4560463190032436692/posts/default/1360328125183418382?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/ImprovingEnterpriseBusinessProcessManagementSystems/~3/VPQ8yaxllBY/first-impression-sap-netweaver-bpm-tool.html" title="First impression -- #SAP #NetWeaver #BPM tool" /><author><name>Alexander Samarin</name><uri>https://profiles.google.com/112810118258856486156</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh5.googleusercontent.com/-rb1Di6vctuI/AAAAAAAAAAI/AAAAAAAAAQM/-5VNACIpAaQ/s512-c/photo.jpg" /></author><thr:total>0</thr:total><georss:featurename>Gammarth, La Marsa‎, Tunisia</georss:featurename><georss:point>36.91371796006886 10.319380385192858</georss:point><georss:box>36.89007996006886 10.299590885192858 36.93735596006886 10.339169885192858</georss:box><content type="html">SAP NetWeaver BPM 7.2  looks (after the 4-days TZBPM training course) rather good:
Eclipse-based design environment or "composition environment"
Good naming conventions by default 
Business view and technical view 
Explicit definition of events in addition to several other artefacts
One pool is one process
Direct interpretation of BPMN without compiling it into BPEL
A small and reasonable subset 
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/jWMpHe8efVEgJKOCpXolti51O08/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/jWMpHe8efVEgJKOCpXolti51O08/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/jWMpHe8efVEgJKOCpXolti51O08/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/jWMpHe8efVEgJKOCpXolti51O08/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/ImprovingEnterpriseBusinessProcessManagementSystems/~4/VPQ8yaxllBY" height="1" width="1"/&gt;</content><feedburner:origLink>http://improving-bpm-systems.blogspot.com/2011/06/first-impression-sap-netweaver-bpm-tool.html</feedburner:origLink></entry><entry gd:etag="W/&quot;C04FSX86fip7ImA9WhZQEEo.&quot;"><id>tag:blogger.com,1999:blog-4560463190032436692.post-2184820170699779790</id><published>2011-04-17T22:25:00.000+02:00</published><updated>2011-04-17T22:25:18.116+02:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-04-17T22:25:18.116+02:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="enterprise patterns" /><title>Enterprise patterns: PEAS</title><link rel="replies" type="application/atom+xml" href="http://improving-bpm-systems.blogspot.com/feeds/2184820170699779790/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=4560463190032436692&amp;postID=2184820170699779790" title="1 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/4560463190032436692/posts/default/2184820170699779790?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/4560463190032436692/posts/default/2184820170699779790?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/ImprovingEnterpriseBusinessProcessManagementSystems/~3/aUkYL1XcbMA/enterprise-patterns-peas.html" title="Enterprise patterns: PEAS" /><author><name>Alexander Samarin</name><uri>https://profiles.google.com/112810118258856486156</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh5.googleusercontent.com/-rb1Di6vctuI/AAAAAAAAAAI/AAAAAAAAAQM/-5VNACIpAaQ/s512-c/photo.jpg" /></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://1.bp.blogspot.com/-OGrWogrz6Ck/TatLT8m0I-I/AAAAAAAAANY/diGRPz93CHE/s72-c/peas.png" height="72" width="72" /><thr:total>1</thr:total><content type="html">I noticed an enterprise pattern which is Platform-Enabled Agile Solutions (PEAS). It is applicable to situation when it is highly desirable to advance with a new enterprise-wide initiative in an incremental way. It means that developing the final user requirements is virtually impossible because the users just do not know exactly what should be built and they prefer to try those news things in 
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/FphK1hyoNFeRTDYZhArtVUZxEXs/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/FphK1hyoNFeRTDYZhArtVUZxEXs/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/FphK1hyoNFeRTDYZhArtVUZxEXs/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/FphK1hyoNFeRTDYZhArtVUZxEXs/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/ImprovingEnterpriseBusinessProcessManagementSystems/~4/aUkYL1XcbMA" height="1" width="1"/&gt;</content><feedburner:origLink>http://improving-bpm-systems.blogspot.com/2011/04/enterprise-patterns-peas.html</feedburner:origLink></entry><entry gd:etag="W/&quot;CU4GQnY_fSp7ImA9WhZTEEw.&quot;"><id>tag:blogger.com,1999:blog-4560463190032436692.post-8445225240837757198</id><published>2011-02-19T11:24:00.018+01:00</published><updated>2011-03-13T11:58:43.845+01:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-03-13T11:58:43.845+01:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="EA" /><category scheme="http://www.blogger.com/atom/ns#" term="BPM" /><category scheme="http://www.blogger.com/atom/ns#" term="BA" /><title>Explaining EA: business architecture basics 1</title><link rel="replies" type="application/atom+xml" href="http://improving-bpm-systems.blogspot.com/feeds/8445225240837757198/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=4560463190032436692&amp;postID=8445225240837757198" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/4560463190032436692/posts/default/8445225240837757198?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/4560463190032436692/posts/default/8445225240837757198?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/ImprovingEnterpriseBusinessProcessManagementSystems/~3/M1vsvlpxmUw/explaining-ea-business-architecture.html" title="Explaining EA: business architecture basics 1" /><author><name>Alexander Samarin</name><uri>https://profiles.google.com/112810118258856486156</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh5.googleusercontent.com/-rb1Di6vctuI/AAAAAAAAAAI/AAAAAAAAAQM/-5VNACIpAaQ/s512-c/photo.jpg" /></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://2.bp.blogspot.com/-FZfW5m5_Hi8/TV7ZXOah0uI/AAAAAAAAALQ/P6HR5M2aGkc/s72-c/FUnctions-IBM.PNG" height="72" width="72" /><thr:total>0</thr:total><content type="html">
Note: a revised version of these three posts is available at http://www.improving-bpm-systems.com/pubs/Explaining-EA-BA-basics_v7.pdf 

The purpose of this post is to provide an explanation about Business Architecture (BA). Informally speaking, BA defines how work gets done within an enterprise. How work gets done is, of course, not completely unknown, but the knowledge is diffused throughout 
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/ymAD3CHPsXsUd5HZkix_62fafvI/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/ymAD3CHPsXsUd5HZkix_62fafvI/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/ymAD3CHPsXsUd5HZkix_62fafvI/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/ymAD3CHPsXsUd5HZkix_62fafvI/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/ImprovingEnterpriseBusinessProcessManagementSystems/~4/M1vsvlpxmUw" height="1" width="1"/&gt;</content><feedburner:origLink>http://improving-bpm-systems.blogspot.com/2011/02/explaining-ea-business-architecture.html</feedburner:origLink></entry><entry gd:etag="W/&quot;CU4ESH86cSp7ImA9WhZTEEw.&quot;"><id>tag:blogger.com,1999:blog-4560463190032436692.post-9163557529571461250</id><published>2011-02-19T11:24:00.017+01:00</published><updated>2011-03-13T11:58:29.119+01:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-03-13T11:58:29.119+01:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="EA" /><category scheme="http://www.blogger.com/atom/ns#" term="BPM" /><category scheme="http://www.blogger.com/atom/ns#" term="BA" /><title>Explaining EA: business architecture basics 2</title><link rel="replies" type="application/atom+xml" href="http://improving-bpm-systems.blogspot.com/feeds/9163557529571461250/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=4560463190032436692&amp;postID=9163557529571461250" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/4560463190032436692/posts/default/9163557529571461250?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/4560463190032436692/posts/default/9163557529571461250?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/ImprovingEnterpriseBusinessProcessManagementSystems/~3/Et5CXlR4iy8/explaining-ea-business-architecture_19.html" title="Explaining EA: business architecture basics 2" /><author><name>Alexander Samarin</name><uri>https://profiles.google.com/112810118258856486156</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh5.googleusercontent.com/-rb1Di6vctuI/AAAAAAAAAAI/AAAAAAAAAQM/-5VNACIpAaQ/s512-c/photo.jpg" /></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://1.bp.blogspot.com/-L3rd017jLD8/TV7ekbV_zRI/AAAAAAAAALg/rd8CQS1BfKQ/s72-c/ent-1.PNG" height="72" width="72" /><thr:total>0</thr:total><content type="html">
Note: a revised version of these three posts is available at http://www.improving-bpm-systems.com/pubs/Explaining-EA-BA-basics_v7.pdf 

Continued from Explaining EA: business architecture basics 1

4 Linking WHY, WHAT and HOW
So, an enterprise’s value-chain and value-streams are the high-level decomposition of the work of the (whole) enterprise into the work of many different activities. In such
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/EUd2hgUii1-YOY9lYCyZ7AADywA/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/EUd2hgUii1-YOY9lYCyZ7AADywA/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/EUd2hgUii1-YOY9lYCyZ7AADywA/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/EUd2hgUii1-YOY9lYCyZ7AADywA/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/ImprovingEnterpriseBusinessProcessManagementSystems/~4/Et5CXlR4iy8" height="1" width="1"/&gt;</content><feedburner:origLink>http://improving-bpm-systems.blogspot.com/2011/02/explaining-ea-business-architecture_19.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DkAHQ3g7eip7ImA9WhZTEE0.&quot;"><id>tag:blogger.com,1999:blog-4560463190032436692.post-3200497206552103857</id><published>2011-02-19T11:24:00.016+01:00</published><updated>2011-03-13T09:25:32.602+01:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-03-13T09:25:32.602+01:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="EA" /><category scheme="http://www.blogger.com/atom/ns#" term="BPM" /><category scheme="http://www.blogger.com/atom/ns#" term="BA" /><title>Explaining EA: business architecture basics 3</title><link rel="replies" type="application/atom+xml" href="http://improving-bpm-systems.blogspot.com/feeds/3200497206552103857/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=4560463190032436692&amp;postID=3200497206552103857" title="2 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/4560463190032436692/posts/default/3200497206552103857?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/4560463190032436692/posts/default/3200497206552103857?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/ImprovingEnterpriseBusinessProcessManagementSystems/~3/RiNag9puF4Q/explaining-ea-business-architecture_1845.html" title="Explaining EA: business architecture basics 3" /><author><name>Alexander Samarin</name><uri>https://profiles.google.com/112810118258856486156</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh5.googleusercontent.com/-rb1Di6vctuI/AAAAAAAAAAI/AAAAAAAAAQM/-5VNACIpAaQ/s512-c/photo.jpg" /></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://3.bp.blogspot.com/-t8Rcp2SY5h0/TV-XNeAATzI/AAAAAAAAAMg/-KvGwNwslbc/s72-c/func2.PNG" height="72" width="72" /><thr:total>2</thr:total><content type="html">
Note: a revised version of these three posts is available at http://www.improving-bpm-systems.com/pubs/Explaining-EA-BA-basics_v7.pdf 

Continued from Explaining EA: business architecture basics 2

5 Managing the complexity of VEB
The interactions between activities reveal the different relationships between them. In order to manage the complexity, the primary interest of any architecture is to 
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/iOpQfOcVgxuMwXmPRAxTWufOQnQ/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/iOpQfOcVgxuMwXmPRAxTWufOQnQ/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/iOpQfOcVgxuMwXmPRAxTWufOQnQ/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/iOpQfOcVgxuMwXmPRAxTWufOQnQ/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/ImprovingEnterpriseBusinessProcessManagementSystems/~4/RiNag9puF4Q" height="1" width="1"/&gt;</content><feedburner:origLink>http://improving-bpm-systems.blogspot.com/2011/02/explaining-ea-business-architecture_1845.html</feedburner:origLink></entry><entry gd:etag="W/&quot;A0YDSX86eyp7ImA9Wx9UFE0.&quot;"><id>tag:blogger.com,1999:blog-4560463190032436692.post-5444621528084439134</id><published>2011-02-11T08:26:00.000+01:00</published><updated>2011-02-11T08:26:18.113+01:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-02-11T08:26:18.113+01:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="architect enterprise BPM systems" /><title>Illustration to ebizq.net "How big is a process?"</title><link rel="replies" type="application/atom+xml" href="http://improving-bpm-systems.blogspot.com/feeds/5444621528084439134/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=4560463190032436692&amp;postID=5444621528084439134" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/4560463190032436692/posts/default/5444621528084439134?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/4560463190032436692/posts/default/5444621528084439134?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/ImprovingEnterpriseBusinessProcessManagementSystems/~3/QCnssrkJyEs/illustration-to-ebizqnet-how-big-is.html" title="Illustration to ebizq.net &quot;How big is a process?&quot;" /><author><name>Alexander Samarin</name><uri>https://profiles.google.com/112810118258856486156</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh5.googleusercontent.com/-rb1Di6vctuI/AAAAAAAAAAI/AAAAAAAAAQM/-5VNACIpAaQ/s512-c/photo.jpg" /></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://3.bp.blogspot.com/-wTfcHDVaso4/TVTjjdynqEI/AAAAAAAAALE/2bmC7nrTbUI/s72-c/orch-eclipse-c.png" height="72" width="72" /><thr:total>0</thr:total><content type="html">An illustration to http://www.ebizq.net/blogs/ebizq_forum/2011/02/how-big-is-a-process.php

From my book "Improving enterprise business process management systems":

We recommend introducing control-oriented coordination using a step-by-step approach
via the “eclipse” pattern (see figure 5.6). At first, we “cover” only a tiny area of the whole process. Usually we start with the intra-application 
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/j_1r9nqHA8GY2212bWiU66XYgE8/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/j_1r9nqHA8GY2212bWiU66XYgE8/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/j_1r9nqHA8GY2212bWiU66XYgE8/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/j_1r9nqHA8GY2212bWiU66XYgE8/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/ImprovingEnterpriseBusinessProcessManagementSystems/~4/QCnssrkJyEs" height="1" width="1"/&gt;</content><feedburner:origLink>http://improving-bpm-systems.blogspot.com/2011/02/illustration-to-ebizqnet-how-big-is.html</feedburner:origLink></entry><entry gd:etag="W/&quot;AkIHRH08eip7ImA9Wx9UE0g.&quot;"><id>tag:blogger.com,1999:blog-4560463190032436692.post-717270108461895598</id><published>2011-02-10T18:22:00.000+01:00</published><updated>2011-02-10T18:22:15.372+01:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-02-10T18:22:15.372+01:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="practical process patterns" /><category scheme="http://www.blogger.com/atom/ns#" term="BPMN" /><title>Practical Process Patterns: FRAP</title><link rel="replies" type="application/atom+xml" href="http://improving-bpm-systems.blogspot.com/feeds/717270108461895598/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=4560463190032436692&amp;postID=717270108461895598" title="2 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/4560463190032436692/posts/default/717270108461895598?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/4560463190032436692/posts/default/717270108461895598?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/ImprovingEnterpriseBusinessProcessManagementSystems/~3/ys2t2XE2Y_Q/practical-process-patterns-frap.html" title="Practical Process Patterns: FRAP" /><author><name>Alexander Samarin</name><uri>https://profiles.google.com/112810118258856486156</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh5.googleusercontent.com/-rb1Di6vctuI/AAAAAAAAAAI/AAAAAAAAAQM/-5VNACIpAaQ/s512-c/photo.jpg" /></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://1.bp.blogspot.com/-9ToEgUuSRrA/TVQcDlfoGoI/AAAAAAAAAK8/xCyoSii_VCw/s72-c/FRAP.PNG" height="72" width="72" /><thr:total>2</thr:total><content type="html">
Functional roles are pools (FRAP)

BPMN pool is normally associated with a participant. Often such a participant is associated with an organisational role, e.g. CFO.  Obviously, an organisational role may include more than one functional role.  As the result, within the same business process an organisational role may participate with different functional roles to carry out different activities.
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/i4_3iKxq-Fk-jv4R3dEelxmNr-w/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/i4_3iKxq-Fk-jv4R3dEelxmNr-w/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/i4_3iKxq-Fk-jv4R3dEelxmNr-w/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/i4_3iKxq-Fk-jv4R3dEelxmNr-w/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/ImprovingEnterpriseBusinessProcessManagementSystems/~4/ys2t2XE2Y_Q" height="1" width="1"/&gt;</content><feedburner:origLink>http://improving-bpm-systems.blogspot.com/2011/02/practical-process-patterns-frap.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DkYHSHs5fip7ImA9Wx9VEEg.&quot;"><id>tag:blogger.com,1999:blog-4560463190032436692.post-7465567691518821185</id><published>2011-01-26T16:02:00.000+01:00</published><updated>2011-01-26T16:02:19.526+01:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-01-26T16:02:19.526+01:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="EPN" /><category scheme="http://www.blogger.com/atom/ns#" term="BPMN" /><title>From EPN to BPMN</title><link rel="replies" type="application/atom+xml" href="http://improving-bpm-systems.blogspot.com/feeds/7465567691518821185/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=4560463190032436692&amp;postID=7465567691518821185" title="2 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/4560463190032436692/posts/default/7465567691518821185?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/4560463190032436692/posts/default/7465567691518821185?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/ImprovingEnterpriseBusinessProcessManagementSystems/~3/naLKXZ2tbXU/from-epn-to-bpmn.html" title="From EPN to BPMN" /><author><name>Alexander Samarin</name><uri>https://profiles.google.com/112810118258856486156</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh5.googleusercontent.com/-rb1Di6vctuI/AAAAAAAAAAI/AAAAAAAAAQM/-5VNACIpAaQ/s512-c/photo.jpg" /></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://4.bp.blogspot.com/_Yfo0Vz5Aw2E/TUA2P1eqzDI/AAAAAAAAAKY/eg0QYBPdeWY/s72-c/flowers-BPMN.PNG" height="72" width="72" /><thr:total>2</thr:total><content type="html">Book "Event Processing in Action" contains "Fast Flowers Delivery" use case. Below I tried to reproduce this use case in BPMN to see the internal behavior of each participant. 


I think, I have to switch to BPMN 2.0 to better handle exceptions. 

Thanks,
AS



&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/yC6Sxb7B1lrkWcLtGtx7Owdnqvk/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/yC6Sxb7B1lrkWcLtGtx7Owdnqvk/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/yC6Sxb7B1lrkWcLtGtx7Owdnqvk/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/yC6Sxb7B1lrkWcLtGtx7Owdnqvk/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/ImprovingEnterpriseBusinessProcessManagementSystems/~4/naLKXZ2tbXU" height="1" width="1"/&gt;</content><feedburner:origLink>http://improving-bpm-systems.blogspot.com/2011/01/from-epn-to-bpmn.html</feedburner:origLink></entry><entry gd:etag="W/&quot;D0QNSHo8fSp7ImA9Wx9WF0Q.&quot;"><id>tag:blogger.com,1999:blog-4560463190032436692.post-7479878024533748635</id><published>2011-01-23T16:09:00.000+01:00</published><updated>2011-01-23T16:09:59.475+01:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-01-23T16:09:59.475+01:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="ACM" /><category scheme="http://www.blogger.com/atom/ns#" term="BPM" /><title>Contribution to: ACM: Feature or Paradigm</title><link rel="replies" type="application/atom+xml" href="http://improving-bpm-systems.blogspot.com/feeds/7479878024533748635/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=4560463190032436692&amp;postID=7479878024533748635" title="2 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/4560463190032436692/posts/default/7479878024533748635?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/4560463190032436692/posts/default/7479878024533748635?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/ImprovingEnterpriseBusinessProcessManagementSystems/~3/-ClUb3AEOCE/contribution-to-acm-feature-or-paradigm.html" title="Contribution to: ACM: Feature or Paradigm" /><author><name>Alexander Samarin</name><uri>https://profiles.google.com/112810118258856486156</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh5.googleusercontent.com/-rb1Di6vctuI/AAAAAAAAAAI/AAAAAAAAAQM/-5VNACIpAaQ/s512-c/photo.jpg" /></author><thr:total>2</thr:total><content type="html">This is a contribution to a very interesting discussion "ACM: Feature or Paradigm" at http://social-biz.org/2011/01/22/acm-feature-or-paradigm/ and http://mainthing.ru/item/401/

Some of Keith’s arguments do not correspond to my experience with collaborative and process-based applications. Attention, please – those applications were designed for clients (including international ones) based in 
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/sag2TDeZgVv7fA35cWku6wlts9M/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/sag2TDeZgVv7fA35cWku6wlts9M/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/sag2TDeZgVv7fA35cWku6wlts9M/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/sag2TDeZgVv7fA35cWku6wlts9M/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/ImprovingEnterpriseBusinessProcessManagementSystems/~4/-ClUb3AEOCE" height="1" width="1"/&gt;</content><feedburner:origLink>http://improving-bpm-systems.blogspot.com/2011/01/contribution-to-acm-feature-or-paradigm.html</feedburner:origLink></entry></feed>

