<?xml version="1.0" encoding="UTF-8"?><rss version="0.92">
<channel>
	<title>Integrated Modelling Method</title>
	<link>http://integrated-modeling-method.com</link>
	<description>Your Passport to Modeling Execellence</description>
	<lastBuildDate>Wed, 01 Feb 2012 09:01:48 +0000</lastBuildDate>
	<docs>http://backend.userland.com/rss092</docs>
	<language>en</language>
	<!-- generator="WordPress/3.0.4" -->

	<item>
		<title>The As Is Logic Chasm</title>
		<description><![CDATA[This post is an extract from the book I am currently writing on Procedure Modelling. The book explains the approach to take in order to build quality Procedures and the pitfalls to avoid when doing so.  One of the pitfalls is what I call the 'As Is Logic Chasm', into which so many BAs and business managers fall. <a href="http://integrated-modeling-method.com/as-is-to-be/logic-chasm/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
		<link>http://integrated-modeling-method.com/as-is-to-be/logic-chasm/</link>
			</item>
	<item>
		<title>Process Modelling or Process Mapping?</title>
		<description><![CDATA[There is constant confusion between process modelling and process mapping.  The following are a set of definitions that will help dispel the confusion and provide other definitions that will help you produce better business models. Process The definition of the &#8230; <a href="http://integrated-modeling-method.com/process-modeling/process-modelling-mapping/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
		<link>http://integrated-modeling-method.com/process-modeling/process-modelling-mapping/</link>
			</item>
	<item>
		<title>Customer &amp; Supplier are Roles &#8211; But What Type?</title>
		<description><![CDATA[Customer &#038; Supplier are NOT Master Data Entities in Master Data Management (MDM).  They are in fact Roles that can be played by the entity Third Party. But are there roles derivable or declarative, i.e. must they be declared and defined?  Using the concept of declarative Roles allows unlimited number of Roles to be defined for any third party over time.  <a href="http://integrated-modeling-method.com/dataquality/customer-supplier-roles-type/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
		<link>http://integrated-modeling-method.com/dataquality/customer-supplier-roles-type/</link>
			</item>
	<item>
		<title>Data Quality: Objective or Subjective?</title>
		<description><![CDATA[Data quality cannot be looked at and defined objectively unless you know the context in which it is to be applied, i.e. the Business Functions the data is meant to support.  All other definitions are subjective and, as such, prevent Data Quality being achieved. <a href="http://integrated-modeling-method.com/dataquality/data-quality-objective-subjective/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
		<link>http://integrated-modeling-method.com/dataquality/data-quality-objective-subjective/</link>
			</item>
	<item>
		<title>Logical Data Model for Customer &amp; Supplier</title>
		<description><![CDATA[The logical data model below shows the data structure needed to support Customer, Supplier and Employee.  Pardoxically, none of these appear as an enitity on model! How can that be? There is a very good reason for this, which is &#8230; <a href="http://integrated-modeling-method.com/dataquality/logical-data-model-customer-supplier/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
		<link>http://integrated-modeling-method.com/dataquality/logical-data-model-customer-supplier/</link>
			</item>
	<item>
		<title>Customer is Not a Master Data Enitity.</title>
		<description><![CDATA[Having Customer and Supplier as Master Data Entities is about as sensible as having Creditor and Debtor. Why? Because all of these terms refer to derivable relationships and implementing them as Master Data Entities is both a modelling and business &#8230; <a href="http://integrated-modeling-method.com/dataquality/customer-master-data-enitity-2/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
		<link>http://integrated-modeling-method.com/dataquality/customer-master-data-enitity-2/</link>
			</item>
	<item>
		<title>Will Best Practice Keep Your Data Quality Boat Afloat?</title>
		<description><![CDATA[Some of attendees at a recent workshop that I ran told me that data quality was assured in their enterprise because they always followed industry best practice.  On the surface this seems to be a compelling argument.  If you are &#8230; <a href="http://integrated-modeling-method.com/dataquality/practice-data-quality-boat-afloat/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
		<link>http://integrated-modeling-method.com/dataquality/practice-data-quality-boat-afloat/</link>
			</item>
	<item>
		<title>Data Quality: Driven by Function and Form or Glue and String?</title>
		<description><![CDATA[Is the data quality in your enterprise driven by function and form or held together by string and glue?  How did you map and build the data structures required to support the functions of the enterprise? Did you start with &#8230; <a href="http://integrated-modeling-method.com/dataquality/data-quality-driven-function-form-glue-string/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
		<link>http://integrated-modeling-method.com/dataquality/data-quality-driven-function-form-glue-string/</link>
			</item>
	<item>
		<title>Data Quality: Dead Crows Kill Customers!</title>
		<description><![CDATA[Dead Crows also Kill Suppliers! While recently doing a webinar on with Dylan Jones, of Dataqualitypro, I was the describing the essential role of Logical Data Model plays in Data Quality.  During our discussions, Dylan asked me to give examples &#8230; <a href="http://integrated-modeling-method.com/dataquality/data-quality-dead-crows-kill-customers/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
		<link>http://integrated-modeling-method.com/dataquality/data-quality-dead-crows-kill-customers/</link>
			</item>
	<item>
		<title>The Pitfalls of Data Re-Use</title>
		<description><![CDATA[The reuse, though seemingly an eminently sensible practice, is fraught with danger. The only data that is truly safe to re-use is genuinely raw data. All other data should carry a health warning.  

Read on on to find out what these dangers are and how to avoid them. <a href="http://integrated-modeling-method.com/dataquality/pitfalls-data-re-use/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
		<link>http://integrated-modeling-method.com/dataquality/pitfalls-data-re-use/</link>
			</item>
</channel>
</rss>

