﻿<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:trackback="http://madskills.com/public/xml/rss/module/trackback/">
  <channel>
    <title>Karen Lopez: Musings on Data, Process, and Architecture </title>
    <description>Insights and thoughts about data and IT-related concepts.</description>
    <link>http://www.infoadvisors.com/Home/tabid/36/BlogId/1/Default.aspx</link>
    <language>en-US</language>
    <managingEditor>website@infoadvisors.com</managingEditor>
    <webMaster>karen@Infoadvisors.com</webMaster>
    <pubDate>Fri, 25 Jul 2008 01:13:02 GMT</pubDate>
    <lastBuildDate>Fri, 25 Jul 2008 01:13:02 GMT</lastBuildDate>
    <docs>http://backend.userland.com/rss</docs>
    <generator>Blog RSS Generator Version 3.4.0.39853</generator>
    <item>
      <title>Zachman Framework 2</title>
      <description>&lt;p&gt;One of the more exciting announcements at the DAMA Conference is that John Zachman has a new version of the Zachman Framework, appropriately named Zachman Framework 2 &lt;p&gt;Rob Drysdale blogs about this announcement. &lt;p&gt;John Zachman introduced a new version of the Zachman Frame.work with new names and one more row in the earlier session. &lt;p&gt;Stan took the new framework and broke it down into various parts and showed how it really is an enterprise model and put it all into business terms. &lt;p&gt;He began by breaking it into into four quadrants that can be used by business leaders to help manage an enterprise. &lt;p&gt;The four quadrants are: &lt;p&gt;Resource ideas (top left) &lt;p&gt;Behavior ideas (top right) &lt;p&gt;Resource reality (bottom left) &lt;p&gt;Behavior reality (bottom right) &lt;p&gt;Stan then went on to show how each row and column can be broken down and put into basic English to describe what each row and column means and give more meaning to it than the simple row and column headings. &lt;p&gt;Each row can be represented by what is in it: &lt;p&gt;Row 1 is lists &lt;p&gt;Row 2 is semantic models &lt;p&gt;Row 3 is schematic models &lt;p&gt;Row 4 is blueprint models &lt;p&gt;Row 5 is listings &lt;p&gt;Row 6 is instances &lt;p&gt;Then the actions and perspectives and outcomes of each row can be analyzed &lt;p&gt;If you put each of these together you end up with a sentence describing the row. For example the architects' semantic models define business. &lt;p&gt;The underlying idea here is to stop referring to these concepts by the row or column position, but by the name or what is in each box. This is how it can be the most help to everyone especially business users and leaders. &lt;p&gt;Note from Karen:  I think that last point is a really good one.  I've seen many eyes glaze over so fast when a team of data architects starting talking about "row 2 and row 3 column 1 models".  &lt;p&gt;I do like these new names and approaches to the Zachman Framework. &lt;p&gt;_________________________________________________________ &lt;p&gt;&lt;b&gt;Zachman Framework² for Management Control&lt;/b&gt; &lt;p&gt;&lt;img alt="Stan Locke" src="http://md2008.wilshireconferences.com/uploads/images/bios/314.jpg" width="90" border="1"&gt;&lt;br&gt;&lt;b&gt;Stan Locke&lt;/b&gt;&lt;br&gt;Managing Director&lt;br&gt;&lt;i&gt;Zachman Framework Assoc&lt;/i&gt; &lt;p&gt;Wednesday, March 19, 2008&lt;br&gt;10:00 AM - 11:00 AM  &lt;p&gt;Level:  &lt;br&gt;&lt;b&gt;Intermediate&lt;/b&gt; &lt;p&gt;Until the Enterprise Architecture artifacts are employed by senior management in the day-to-day operations of the business, Enterprise Architecture is going to be perceived as overhead and will always be vulnerable to short term, cost saving, budget cuts. This presentation explores using the Framework as a senior management tool in control of the business of the Enterprise.  &lt;hr width="440"&gt;  &lt;p&gt;&lt;em&gt;Stan lectures on the implementation of the framework concepts, bringing a practical business perspective to the framework logic. Since graduate school, his special interest is in the management methodologies required to define an enterprise and the ways in which this can be represented in repository technology. Stan has been the architect of the Zachman standards under John’s direction, model builder of the hexagon implementation constructs and directs the applied research through ZFA.&lt;/em&gt;&lt;/p&gt;&lt;div class="d_itc_f" style="clear:both;height:11px;"&gt;&lt;a class="a_itc" style="float: right;" href="http://www.itcrossing.com/"&gt;&lt;img alt="powered by metaPost" style="border: none ;" src="/DesktopModules/itcMetaPost/images/m.gif"&gt;&lt;/a&gt;&lt;script src="/DesktopModules/itcMetaPost/js/m.js" type="text/javascript"&gt;&lt;/script&gt;&lt;/div&gt;</description>
      <link>http://www.infoadvisors.com/Home/tabid/36/EntryID/190/Default.aspx</link>
      <author>website@infoadvisors.com</author>
      <comments>http://www.infoadvisors.com/Home/tabid/36/EntryID/190/Default.aspx#Comments</comments>
      <guid isPermaLink="true">http://www.infoadvisors.com/Default.aspx?tabid=36&amp;EntryID=190</guid>
      <pubDate>Wed, 19 Mar 2008 20:54:21 GMT</pubDate>
      <slash:comments>0</slash:comments>
      <trackback:ping>http://www.infoadvisors.com/DesktopModules/Blog/Trackback.aspx?id=190</trackback:ping>
    </item>
  </channel>
</rss>