<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>ProAce - Custom Software Development Austin, Texas &#187; information modeling</title>
	<atom:link href="http://www.proace.com/tag/information-modeling/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.proace.com</link>
	<description>ProAce is a technology consulting company in Austin, Texas focused on building custom software applications, user interface design and online marketing. Let us help you with your Web technology needs.</description>
	<lastBuildDate>Fri, 27 Apr 2012 15:50:59 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
		<item>
		<title>External Uniqueness Constraints</title>
		<link>http://www.proace.com/2010/03/04/external-uniqueness-constraints/</link>
		<comments>http://www.proace.com/2010/03/04/external-uniqueness-constraints/#comments</comments>
		<pubDate>Thu, 04 Mar 2010 15:12:08 +0000</pubDate>
		<dc:creator>Michael</dc:creator>
				<category><![CDATA[Development]]></category>
		<category><![CDATA[domain-driven design]]></category>
		<category><![CDATA[External Uniqueness Constraint]]></category>
		<category><![CDATA[information modeling]]></category>
		<category><![CDATA[NORMA]]></category>
		<category><![CDATA[object-role modeling]]></category>
		<category><![CDATA[ORM]]></category>
		<category><![CDATA[uniqueness constraint]]></category>

		<guid isPermaLink="false">http://www.proace.com/?p=3001</guid>
		<description><![CDATA[<p>External uniqueness constraints are very closely related to <a title="Internal Uniqueness Constraints" href="http://http://www.proace.com/2010/02/18/internal-uniqueness-constraints/" target="_blank">internal uniqueness constraints</a>.  The difference is external uniqueness constraints span multiple roles instead of just one.  Since the concept isn&#8217;t too big of a stretch we&#8217;re going&#8230;</p>]]></description>
		<wfw:commentRss>http://www.proace.com/2010/03/04/external-uniqueness-constraints/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Mandatory Role Constraints</title>
		<link>http://www.proace.com/2010/03/03/mandatory-role-constraints/</link>
		<comments>http://www.proace.com/2010/03/03/mandatory-role-constraints/#comments</comments>
		<pubDate>Wed, 03 Mar 2010 18:15:47 +0000</pubDate>
		<dc:creator>Rex Morgan</dc:creator>
				<category><![CDATA[Development]]></category>
		<category><![CDATA[dev-feb-2010]]></category>
		<category><![CDATA[information modeling]]></category>
		<category><![CDATA[mandatory role constraint]]></category>
		<category><![CDATA[object-role modeling]]></category>

		<guid isPermaLink="false">http://www.proace.com/?p=2816</guid>
		<description><![CDATA[<p>The Mandatory role constraint is used in ORM as a way to model that an entity is required to play a role in a particular fact.</p>
<p>For a quick example, this is what a fact looks like with no mandatory&#8230;</p>]]></description>
		<wfw:commentRss>http://www.proace.com/2010/03/03/mandatory-role-constraints/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Internal Uniqueness Constraints</title>
		<link>http://www.proace.com/2010/02/18/internal-uniqueness-constraints/</link>
		<comments>http://www.proace.com/2010/02/18/internal-uniqueness-constraints/#comments</comments>
		<pubDate>Thu, 18 Feb 2010 15:47:54 +0000</pubDate>
		<dc:creator>Michael</dc:creator>
				<category><![CDATA[Development]]></category>
		<category><![CDATA[dev-feb-2010]]></category>
		<category><![CDATA[domain-driven design]]></category>
		<category><![CDATA[information modeling]]></category>
		<category><![CDATA[Internal Uniqueness Constraint]]></category>
		<category><![CDATA[NORMA]]></category>
		<category><![CDATA[object-role modeling]]></category>
		<category><![CDATA[ORM]]></category>

		<guid isPermaLink="false">http://www.proace.com/?p=2769</guid>
		<description><![CDATA[The simplest and most commonly used constraint in ORM is the internal uniqueness constraint.  This constraint basically specifies a one-to-many relationship on a role.  The easiest way to show this is through an example.  Let's use the following fact:

The Student with ID 1 has Name 'Bob']]></description>
		<wfw:commentRss>http://www.proace.com/2010/02/18/internal-uniqueness-constraints/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>ORM Basics: Entities, Values, Roles, and Facts</title>
		<link>http://www.proace.com/2010/02/17/orm-basics-entities-values-roles-and-facts/</link>
		<comments>http://www.proace.com/2010/02/17/orm-basics-entities-values-roles-and-facts/#comments</comments>
		<pubDate>Thu, 18 Feb 2010 00:38:40 +0000</pubDate>
		<dc:creator>Jarrod</dc:creator>
				<category><![CDATA[Development]]></category>
		<category><![CDATA[dev-feb-2010]]></category>
		<category><![CDATA[information modeling]]></category>
		<category><![CDATA[object-role modeling]]></category>

		<guid isPermaLink="false">http://www.proace.com/?p=2787</guid>
		<description><![CDATA[Object-role modeling is a fantastic tool that allows one to construct incredibly rich and complex information models. Because of this, it can be difficult to identify a starting point to jump in and begin learning ORM. At ProAce, we feel that identifying the primitive building blocks and working our way up is the natural way to begin teaching any new technique. For ORM, these building blocks are the fundamental types: entities, values, roles and facts.]]></description>
		<wfw:commentRss>http://www.proace.com/2010/02/17/orm-basics-entities-values-roles-and-facts/feed/</wfw:commentRss>
		<slash:comments>8</slash:comments>
		</item>
		<item>
		<title>Object-Role Modeling kickoff</title>
		<link>http://www.proace.com/2010/02/12/object-role-modeling-kickoff/</link>
		<comments>http://www.proace.com/2010/02/12/object-role-modeling-kickoff/#comments</comments>
		<pubDate>Fri, 12 Feb 2010 23:03:10 +0000</pubDate>
		<dc:creator>Josh Arnold</dc:creator>
				<category><![CDATA[Development]]></category>
		<category><![CDATA[dev-feb-2010]]></category>
		<category><![CDATA[domain-driven design]]></category>
		<category><![CDATA[information modeling]]></category>
		<category><![CDATA[object-role modeling]]></category>

		<guid isPermaLink="false">http://www.proace.com/?p=2774</guid>
		<description><![CDATA[Our team has been having some great discussions on Object-Role Modeling this month and I really like the topics that we’ve covered. While ORM is a pivotal part of our internal process, it’s been very interesting to discuss how/when/where/why we actually use it. More importantly, discussing the pros/cons has been really enlightening to identify some of our inefficiencies and brainstorm over ways to help improve our process.]]></description>
		<wfw:commentRss>http://www.proace.com/2010/02/12/object-role-modeling-kickoff/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Business domains for developers</title>
		<link>http://www.proace.com/2010/02/02/business-domains-for-developers/</link>
		<comments>http://www.proace.com/2010/02/02/business-domains-for-developers/#comments</comments>
		<pubDate>Tue, 02 Feb 2010 22:00:11 +0000</pubDate>
		<dc:creator>Josh Arnold</dc:creator>
				<category><![CDATA[Development]]></category>
		<category><![CDATA[dev-feb-2010]]></category>
		<category><![CDATA[domain-driven design]]></category>
		<category><![CDATA[information modeling]]></category>
		<category><![CDATA[object-role modeling]]></category>

		<guid isPermaLink="false">http://www.proace.com/?p=2442</guid>
		<description><![CDATA[<img class="size-full wp-image-2499" title="domain-driven-design" src="http://www.proace.com/wp-content/uploads/2010/01/domain-driven-design.gif" alt="domain driven design information modeling" width="514" height="342" /><br />

Among many of its other benefits, Domain-Driven Design has provided our team with a way of approaching software from a domain-centric approach. Domains are often complex; with so much focus on the model and logic in complex domain designs, it’s important to keep track of all of the pieces. Here at ProAce, we use a method called Object-Role-Modeling.]]></description>
		<wfw:commentRss>http://www.proace.com/2010/02/02/business-domains-for-developers/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>

