<?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 -  Working Toward Architectural Principles for APU</title>
 <link>http://groups.apu.edu/awg</link>
 <description>Architecture Working Group - a select group of IT architecture experts who understand the strategic link between design and future opportunity.&amp;nbsp; This group's ongoing discipline is to create and apply technical models, standards, and design patterns throughout IMT in order to increase agility.</description>
 <language>en</language>
<item>
 <title>The Data Must Flow</title>
 <link>http://groups.apu.edu/awg/node/271</link>
 <description>&lt;p&gt;I ran across a phrase that reminded me of &amp;quot;the spice must flow&amp;quot; line that rings in the head of any fan of Dune.&lt;br /&gt; &lt;/p&gt; &lt;blockquote&gt; &lt;p&gt;&lt;strong&gt;enabling the flow of data in such a way as to make its location immaterial&lt;/strong&gt;&lt;br /&gt; &lt;/p&gt; &lt;/blockquote&gt; &lt;p&gt;What a great way to describe our recently proposed architecture principle relating to data:&lt;/p&gt; &lt;p&gt;&lt;strong&gt;Leveraged Data&lt;/strong&gt; - Data is an enterprise asset that should be leveraged across the organization over time. &lt;/p&gt;</description>
 <pubDate>Thu, 19 Oct 2006 19:37:19 -0700</pubDate>
</item>
<item>
 <title>First Draft of "IT Architecture Principles" Completed</title>
 <link>http://groups.apu.edu/awg/node/266</link>
 <description>&lt;p&gt;The Architecture Working Group has completed its first draft of &lt;a href="principles" target="_self" title="See the Principles Draft"&gt;Enterprise IT Architecture Principles&lt;/a&gt;.&amp;nbsp; The work took just over one month, and we really do feel that we have a good list of primary principles that can strategically guide future decisions.&lt;br /&gt; &lt;/p&gt;&lt;p&gt;The principles will now be reviewed by the Business Architecture Review Team, and then the IMT Cabinet.&lt;br /&gt;&lt;/p&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;</description>
 <pubDate>Fri, 22 Sep 2006 12:57:58 -0700</pubDate>
</item>
<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>Current IT Issues Report: IdM and Portfolio Management float to the surface</title>
 <link>http://groups.apu.edu/awg/node/242</link>
 <description>&lt;p&gt;&amp;nbsp;&lt;br /&gt;The seventh annual &lt;a href="http://www.educause.edu/apps/eq/eqm06/eqm0622.asp?bhcp=1"&gt;Educause Current IT Issues Survey Report&lt;/a&gt; highlights two areas which I have been following.&amp;nbsp; First, &lt;em&gt;Security &amp;amp; Identity Management&lt;/em&gt; (IdM) rose to the top, displacing IT Funding as the most strategic issue needing to be resolved for future success.&amp;nbsp; Second, &lt;em&gt;Portfolio Development &amp;amp; Management&lt;/em&gt; was a new category this year and immediately received attention, appearing among the top-ten issues expected to become more significant in the coming year.&amp;nbsp; Other issues I have been tracking of late were also covered, including ERP, Academic Alignment, and Web Services (SOA).&amp;nbsp; &lt;/p&gt;     &lt;p&gt;Here are some of the highlights from the report, with additional resources referenced at the end.&amp;nbsp; Overall, this report is a treasure trove of Higher Education IT strategic thinking:&lt;br /&gt;   &lt;/p&gt;</description>
 <pubDate>Wed, 07 Jun 2006 14:04:36 -0700</pubDate>
</item>
<item>
 <title>AWG Reviews Supported Web Browsers</title>
 <link>http://groups.apu.edu/awg/node/195</link>
 <description>&lt;p&gt; IMT's list of supported browsers has not changed in several years. We have been supporting Netscape since its inception, and Internet Explorer since it rose to popularity. Much has changed in the operating system and web browser market, and its time to re-evaluate which browsers we should support.&lt;/p&gt;     &lt;p&gt;IMT's Architecture Working Group (AWG) was asked to conduct a review and make a recommendation. In order to attempt a comprehensive and objective review, we developed standard Browser Evaluation Criteria which can be used for current and future evaluations.&amp;nbsp; We then conducted reviews of all current and candidate browsers in Fall 2005, and produced a recommendation.&lt;/p&gt;     &lt;p&gt;The recommendation is being reviewed&amp;nbsp; by IMT Cabinet.&amp;nbsp; If approved, it will then go to UIMC for review.&lt;/p&gt;   &lt;p&gt;&lt;a href="/awg/system/files?file=IMT%20Browser%20Standards%20Recommendation%20-%20Fall%202005.pdf" target="_self" title="Download PDF"&gt;Executive Summary (pdf)&lt;/a&gt; |&amp;nbsp; &lt;a title="Supported Browser Evaluation (Fall 2005)" target="_self" href="/awg/node/172"&gt;Read the Full Report online&lt;/a&gt;&amp;nbsp; |  &lt;a title="Print the full report (approx 25 pages)" target="_self" href="/awg/book/print/144"&gt;Printable Version&lt;/a&gt;&lt;br /&gt; &lt;/p&gt;</description>
 <pubDate>Mon, 12 Dec 2005 14:49:12 -0800</pubDate>
</item>
<item>
 <title>Connecting the Dots</title>
 <link>http://groups.apu.edu/awg/node/158</link>
 <description>&lt;p&gt;As the infrastructure maintenance and PC support operations mature, an IT department must continue to innovate. Its value proposition is the packaging and distribution of meaningful services aligned with the business needs. It includes partnering and consulting with customer groups in innovative spaces like collabortion, web publishing, and self-service. A higher level information creation and distribution channel needs to be created to support rapid assembly of reusable components. If given tools, advanced user groups should be able to build communities which can meet their own lightweight application needs, filling gaps that a centralized transaction system is not meant to.&lt;/p&gt;&lt;p&gt;Will IT Departments Still Exist in 2010? ...&lt;/p&gt;</description>
 <pubDate>Thu, 19 Oct 2006 18:54:44 -0700</pubDate>
</item>
<item>
 <title>ECM or Something Simpler?</title>
 <link>http://groups.apu.edu/awg/node/122</link>
 <description>&lt;p&gt;In &lt;a href="http://www.dmreview.com/editorial/dmreview/print_action.cfm?articleId=1016230"&gt;The Continuing Disappearance of Document Management&lt;/a&gt;, James Till, vice president of Marketing for &lt;a href="http://www.xythos.com/"&gt;Xythos Software Inc.&lt;/a&gt;, describes how the advent of Open Standards such as HTTP, SSL and WebDAV have shaken up the traditional Document Management Industry, as well as call to question complicated Enterprise Content Management (ECM) suite approaches to handling content within your organization.&lt;/p&gt;

&lt;p&gt;I too have been stepping back from previous declarations of ECM as the solution, only because the implication is that an ECM strategy equals and ECM product.  This is not always the case.  In the emerging agile architecture environment, simple solutions that act as a bridges between personal productivity software running on desktops and distributed storage and workflow might fit the bill....&lt;/p&gt;</description>
 <pubDate>Fri, 29 Apr 2005 12:53:16 -0700</pubDate>
</item>
<item>
 <title>IdM - Technological Implementation of Policy</title>
 <link>http://groups.apu.edu/awg/node/121</link>
 <description>&lt;p&gt;&lt;em&gt;Identity and Access Management: Technological Implementation of Policy&lt;/em&gt; &lt;a href="http://www.nmi-edit.org/pdf/CUJ8002_munkwitz-smith.pdf"&gt;(PDF)&lt;/a&gt;, provides another great overview of the identity management opportunity.  One of the things I appreciated the most about this paper is the clarity of the business case based on "other than IT" perspectives.  Besides the amazingly effective Ann West, &lt;a href="http://www.nsf-middleware.org/"&gt;nsf middleware&lt;/a&gt; and &lt;a href="http://www.nmi-edit.org/"&gt;nmi-edit&lt;/a&gt; outreach coordinator, the article was written by Jeff von Munkwits-Smith, the University Registrar at the University of Connecticut.&lt;/p&gt;

&lt;h3&gt;A functional definition - Identity and Access Management:&lt;/h3&gt;

&lt;ul&gt;
   &lt;li&gt;&lt;strong&gt;Integrates&lt;/strong&gt; all the pertinent information about people from multiple authoritative source systems, reconciles the accounts, and joins identities together under one campus unique identity.&lt;/li&gt;
   &lt;li&gt;&lt;strong&gt;Processes&lt;/strong&gt; and transforms information about people including their affiliations with the institution, resource access etc. and pushes out and stores the information where it can be of use to applications.&lt;/li&gt;
   &lt;li&gt;&lt;strong&gt;Acts&lt;/strong&gt; as a focus for implementation of policy concerning visibility and privacy of identity information and entitlement policies across the systems.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Some more take-away notes and highlights below...&lt;/p&gt;</description>
 <pubDate>Tue, 29 Mar 2005 12:36:56 -0800</pubDate>
</item>
<item>
 <title>The Power of Who</title>
 <link>http://groups.apu.edu/awg/node/119</link>
 <description>&lt;p&gt;Clever slogan in the title of a recent article, &lt;a href="http://www.campus-technology.com/article.asp?id=10405"&gt;Authentication - The Power of Who&lt;/a&gt; from Campus-Technology Magazine.&lt;/p&gt;

&lt;p&gt;Identity Management is all about an organization knowing &lt;em&gt;who&lt;/em&gt; its constituents are.  I thought the article was a bit random, and incorrectly labeled as all about "athentication" since authorization and provisioning topics are covered.  However, it is a good overview of several of the approaches that schools are taking to meet the opportunity.  So from a case study perspective its worth a read...&lt;/p&gt;</description>
 <pubDate>Mon, 10 Jan 2005 10:12:21 -0800</pubDate>
</item>
<item>
 <title>After 5 years, Firefox turns 1.0</title>
 <link>http://groups.apu.edu/awg/node/112</link>
 <description>Well its finally happened, Mozilla Firefox has hit 1.0!  Its getting quite a bit of &lt;a href="http://news.google.com/news?hl=en&amp;ie=UTF-8&amp;q=firefox+1.0&amp;scoring=d"&gt;news coverage&lt;/a&gt;, so there is probably not a whole lot more to say here.

I will say though, it has come a long way... far surpassing its heritage.  If you have been along for the Web ride from early on, you will have realized that browsers started off as simple rather efficient tools, but quickly became bloated and yet lacked real innovation.  Firefox 1.0 is lean and mean 4.7MB, and a completely different experience from the early Mozilla days, or even the repackaged Netscape 6/7 series.  You may remember downloads of the later Netscape series as well surpassing 30MB.  Until Firefox, Mozilla's browser code still had fragments of the original Netscape code which was open sourced in 1998...</description>
 <pubDate>Tue, 09 Nov 2004 19:26:53 -0800</pubDate>
</item>
<item>
 <title>Desktop Search from Google</title>
 <link>http://groups.apu.edu/awg/node/106</link>
 <description>Today, I was talking to a friend, and he told me about this new Beta utility from Google, and I thought, wow, these guys come up with new cool stuff everyday!

This one is called Google Desktop at http://desktop.google.com.

Basically, it indexes your whole computer including your files, email, web history (including secure web content), and makes them available in a snap through a "localhost" website on your machine.

I haven't had it on my laptop for too long yet, so not everything is indexed, but from what I've seen so far, you can search for ANYTHING on your computer in snap ... (literally).</description>
 <pubDate>Fri, 15 Oct 2004 13:49:56 -0700</pubDate>
</item>
<item>
 <title>Reducing Complexity, the Discipline</title>
 <link>http://groups.apu.edu/awg/node/105</link>
 <description>&lt;p&gt;A recent article in CIO Magazine, raises a valid point about the communicated purpose of Enterprise Architecture.  Enterprise Architecture can be an overwhelmingly complex undertaking if approached comprehensively from the top down.  In order to avoid getting lost in the matrix of the Zachman Framework, EA should be attached to solving business problems, and according to GM CTO Tony Scott, business peers shouldn't even know its called &amp;quot;enterprise architecture&amp;quot;.    &lt;/p&gt;&lt;p&gt;The goal of EA is to &lt;a href="http://www.cio.com/archive/090104/gm.html"&gt;Reduce Complexity&lt;/a&gt;, not increase it.  EA is described simply as the mapping of business requirements and processes to IT systems which support them.  But its not a technology platform, or a one time mapping.  It is a discipline.  We don't sell disciplines, we practice them.  &lt;/p&gt;&lt;p&gt;The EA discipline is practiced when key problem areas, inefficient processes, legacy systems, those things which can no longer be directly connected with the  business need are re-evaluated.  The goal is to provide agility, reduce complexity, so that the organization can &amp;quot;change the business rules&amp;quot; when need dictates without reinventing the IT systems that support them.  &lt;/p&gt;&lt;p&gt;Often IT is viewed as slowing down the advancement of the organization, rather than enabling it.  Strategic alignment has been thwarted by the increasing complexity of ad hoc computing solutions.  IT is too busy just keeping the plethora of individual PC's, components, and nich products running.  It seems like products are always being added, never removed.  Clearly re-alignment is necessary, discipline is the key.</description>
 <pubDate>Fri, 27 Jan 2006 16:01:44 -0800</pubDate>
</item>
<item>
 <title>Identity Management Roadmap</title>
 <link>http://groups.apu.edu/awg/node/104</link>
 <description>I have posted the Identity Management Roadmap, which is an attempt to break down the broader Identity Management initiative into projects which could be achieved if given appropriate focus and resources over the next year or so.  These tasks represent our success in implementing more of the &lt;a href="http://www.apu.edu/imt/awg/node/view/91"&gt;Identity Management Architecture&lt;/a&gt; in order to provide APU with complete identity lifecycle management.

&lt;a href="node/128"&gt;&lt;img src="http://groups.apu.edu/awg/images/thumbs/thumb_idm-roadmap-0.4-128.png" alt="" /&gt;&lt;/a&gt;

You'll notice that in order to be successful both business process and technical issues need to be addressed.  The overlap of boxes represents the concurrent nature of the tasks, with progress being made on infrastructure while policy and workflow are being refined.  This concurrence can be seen in NSF Middleware Initiatives's &lt;a href="http://www.nmi-edit.org/roadmap/directories.html"&gt;Enterprise Directory Implementation Roadmap&lt;/a&gt;.  The breakdown is not only based on concurrence but also considers that each of these projects would be handled by slightly different teams with distributed project leadership.  I think that this approach would be more successful than a single large  monolithic multi-phased project.  There will of course need to be coordination between projects, with overall leadership provided by an iniative sponsor.  

I would love feedback on this roadmap so that we can procede to write project requests for each of these areas.  The future of IMT's ability to deliver transformational self-service as outlined in the IMT Strategic Priorities, is dependent on APU's facilities to manage identity.</description>
 <pubDate>Mon, 02 May 2005 17:23:11 -0700</pubDate>
</item>
<item>
 <title>Playing Catchup with Jabber Summer News</title>
 <link>http://groups.apu.edu/awg/node/102</link>
 <description>&lt;p&gt;It appears as though more of the industry is waking up to &lt;a href=""&gt;Presence Being the Killer App&lt;/a&gt;.  With Jabber Inc. being a leader in this space.  &lt;q&gt;Jabber, Inc., which develops real-time communication server platforms for developing IM and presence-enabled applications, is fashioning its XCP platform into an application server of sorts not only for presence, but also for messaging, routing and XML-application development. In September, it will release a publish-and-subscribe technology called Information Broker for pushing content out to users.&lt;/q&gt;

&lt;p&gt;Interesting too, is the increase in adoption of Enterprise IM (EIM) and consequent integration of presence in business applications.  &lt;q&gt;A recent Osterman Research study shows 44% of companies use IM with business applications, up from 21% just three years ago. Furthermore, 34% of users have standardized on an internally run IM platform, up from 24% just two years ago.&lt;/q&gt;

&lt;p&gt;Jabber Inc. is has &lt;a href="http://www.jabber.com/index.cgi?CONTENT_ID=447"&gt;announced new versions&lt;/a&gt; of its commercial Jabber server and client.&lt;/p&gt;</description>
 <pubDate>Tue, 21 Sep 2004 12:17: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>
</channel>
</rss>
