<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE rss [<!ENTITY % HTMLlat1 PUBLIC "-//W3C//ENTITIES Latin 1 for XHTML//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml-lat1.ent">]>
<rss version="0.92" xml:base="http://groups.apu.edu/awg">
<channel>
 <title>AWG - ETA</title>
 <link>http://groups.apu.edu/awg/taxonomy/term/83/0</link>
 <description>Enterprise Technical Architecture</description>
 <language>en</language>
<item>
 <title>AWG Works Toward Overarching IT Architecture Principles</title>
 <link>http://groups.apu.edu/awg/node/255</link>
 <description>&lt;p&gt;AWG has set out to define a logically consistent and easy to understand set of principles that guide the engineering of APU's information systems and technology infrastructure.&amp;nbsp; By establishing overarching principles, IMT can better interpret the details of daily decisions in light of an overall strategy. &lt;br /&gt;  &lt;/p&gt;   &lt;p&gt;One thing that has become clear to AWG, is that we can't be everywhere at once.&amp;nbsp; We can't be on every project team and aren't always able to review project designs and outputs.&amp;nbsp; These activities keep us rather busy, and movement toward a formalized written &lt;a title="see posts related to ETA" target="_self" href="/awg/eta"&gt;Enteprise Technology Architecture&lt;/a&gt; has been slower than expected.&amp;nbsp; We have determined that most beneficial output that we can achieve in short order, are &amp;quot;Architecture Principles&amp;quot; which can be applied across the design decision activities within IMT.&lt;br /&gt;   &lt;/p&gt;      &lt;p&gt;We will do this by considering industry direction, and nailing down the &lt;a href="http://techrepublic.com.com/5102-6314-1054512.html"&gt;Big Rules&lt;/a&gt; that are consistent with our strategy. These should be broad enough to apply to a range of technologies, and stated in clear enough business terms that they can be communicated effectively to both management and user communities.&amp;nbsp; What we should end up with is something similar to the &lt;a href="http://www.cio.com/archive/061503/architecture.html"&gt;Seven Pillars of Architecture&lt;/a&gt;.&lt;/p&gt;</description>
 <pubDate>Wed, 09 Aug 2006 10:31:07 -0700</pubDate>
</item>
<item>
 <title>ETA Model Draft 0.5</title>
 <link>http://groups.apu.edu/awg/etamodel</link>
 <description>&lt;p&gt;I have updated the &lt;a href="/awg/image/tid/83" target="_self"&gt;Enterprise Technical Architecture Model&lt;/a&gt;.&lt;/p&gt;  &lt;p&gt; &lt;a href="node/127"&gt;&lt;img src="http://groups.apu.edu/awg/images/thumbs/thumb_enterprisetechnicalarchitecture-0.5-127.png" alt="" /&gt;&lt;/a&gt; &lt;/p&gt;  &lt;p&gt;Most of the changes were related to clearing up the confusion as to what this model is not.&lt;/p&gt;   &lt;p&gt;This model is not a complete list of vendor branded components that we will use to build every solution IMT delivers. It is a high level model that abstracts a desired agility in our systems and covers the delivery infrastructure for our applications. It emphasizes principles, open protocols, and web based delivery to enable transformational self-service. Each of these areas will eventually need detailed sub-architectures to better define solution patterns, combinations of components used in various scenarios. Different requirements need different solution patterns, and no single list of building blocks can ever be pre-established for every potential problem domain.&lt;/p&gt;</description>
 <pubDate>Tue, 06 Dec 2005 16:53:09 -0800</pubDate>
</item>
<item>
 <title>ETA Sub-Architectures</title>
 <link>http://groups.apu.edu/awg/node/82</link>
 <description>The Enterprise Technical Architecture (ETA) will consist of several sub-architectures to be completed over time.</description>
 <pubDate>Thu, 20 May 2004 12:41:13 -0700</pubDate>
</item>
<item>
 <title>ETA Model (png 1450x1114)</title>
 <link>http://groups.apu.edu/awg/node/79</link>
 <description>&lt;img class="thumb" src="http://groups.apu.edu/awg/images/thumbs/thumb_enterprisetechnicalarchitecturemodel-0.5-1450x-79.5-1450x" /&gt;</description>
 <pubDate>Wed, 28 Jul 2004 14:43:26 -0700</pubDate>
</item>
<item>
 <title>ETA Model (png 800x615)</title>
 <link>http://groups.apu.edu/awg/node/78</link>
 <description>&lt;img class="thumb" src="http://groups.apu.edu/awg/images/thumbs/thumb_enterprisetechnicalarchitecturemodel-0.5-800x-78.5-800x" /&gt;</description>
 <pubDate>Wed, 28 Jul 2004 14:42:56 -0700</pubDate>
</item>
<item>
 <title>ETA Model (png 1024x787)</title>
 <link>http://groups.apu.edu/awg/node/77</link>
 <description>&lt;img class="thumb" src="http://groups.apu.edu/awg/images/thumbs/thumb_enterprisetechnicalarchitecturemodel-0.5-1024x-77.5-1024x" /&gt;</description>
 <pubDate>Wed, 28 Jul 2004 14:42:30 -0700</pubDate>
</item>
<item>
 <title>Enterprise Technical Architecture</title>
 <link>http://groups.apu.edu/awg/eta</link>
 <description>&lt;p&gt;The Enterprise Technical Architecture (ETA) details the enterprise's technology strategies, its extended technology linkages, and their impact on project initatives.&lt;/p&gt;

&lt;p&gt;Defines a logically consistent set of principles that guide the engineering of an organization's information systems and technology infrastructure.&lt;/p&gt;

&lt;p&gt;Describes the future state model of the infrastructure and technology platforms required to support the Enterprise Application Architecture (EAA) and enable rapid engineering, solution development, and technical innovation.&lt;/p&gt;</description>
 <pubDate>Thu, 20 May 2004 11:57:13 -0700</pubDate>
</item>
</channel>
</rss>
