<?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 - AWG</title>
 <link>http://groups.apu.edu/awg/taxonomy/term/97/0</link>
 <description>AWG Documentation</description>
 <language>en</language>
<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>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>AWG Members</title>
 <link>http://groups.apu.edu/awg/members</link>
 <description>&lt;p&gt;&lt;strong&gt;Chair:&lt;/strong&gt;  James Janssen - IT Architect &amp;nbsp;   | &lt;a href="blog/jjanssen"&gt;blog&lt;/a&gt;&lt;/p&gt;  &lt;p&gt;&lt;strong&gt;Members:&lt;/strong&gt;  &lt;/p&gt;&lt;ul&gt;  &lt;li&gt;Jarod Beekman - Manager of Network Engineering&amp;nbsp; | &lt;a href="/awg/blog/jbeekman"&gt;blog&lt;/a&gt;&lt;/li&gt;&lt;li&gt;Rob Davis - Manager of Computer Technicians&lt;br /&gt;&lt;/li&gt;         &lt;li&gt;Kevin Ford - Student Lab and Network Services Coordinator&lt;br /&gt;     &lt;/li&gt;         &lt;li&gt;Mark Holmes - Software Engineer Lead&lt;br /&gt;     &lt;/li&gt;         &lt;li&gt;Ken Litwak -&amp;nbsp; Software Engineer III&lt;/li&gt;         &lt;li&gt;Patrick McCarty - Media Services Integration Engineer&lt;br /&gt;&lt;/li&gt;         &lt;li&gt;Clifton Pee - Student Services Manager&lt;/li&gt;  &lt;/ul&gt;            &lt;p&gt;&amp;nbsp;&lt;br /&gt;&amp;nbsp;&lt;br /&gt;     Membership is handled according to the &lt;a title="Read Terms of Reference" target="_self" href="/awg/charter"&gt;Terms of Reference&lt;/a&gt;.&amp;nbsp; If you have any questions, please contact James Janssen.  &lt;/p&gt;</description>
 <pubDate>Wed, 03 Jan 2007 10:44:51 -0800</pubDate>
</item>
<item>
 <title>Architecture Working Group Charter</title>
 <link>http://groups.apu.edu/awg/charter</link>
 <description>&lt;h2&gt;Background&lt;/h2&gt;    &lt;p&gt;Azusa Pacific University is a learning community that values information as a strategic resource.&amp;nbsp; IMT is pursuing Enterprise Architecture (EA) in order to make information and services universally accessible and appropriate to the changing needs of our organization.&amp;nbsp; EA represents a discipline of creating strategic maps, models and standards which, when followed, enable the organization to continue achieving its objectives in a constantly changing environment.&lt;/p&gt;      &lt;h2&gt;Purpose&lt;/h2&gt;    &lt;p&gt;The purpose of the IMT Architecture Working Group is to gather those experts together who understand the broad range of information technologies within the organization to assist the IT Architect in creating and maintaining the Enterprise Technical Architecture (ETA) and the Enterprise Applications Architecture (EAA).&amp;nbsp; Primary responsibilities include research, analysis, architecture reviews, and modeling with a view toward connecting domain expertise with overall IMT strategy.&amp;nbsp; This is done through the capture of current architecture and the creation of working models, principles, and standards for future state strategic architecture.&lt;/p&gt;    &lt;h2&gt;Composition and Leadership of Working Group&lt;/h2&gt;    &lt;p&gt;Unlike other technical groups and teams, membership in this working group is based on the individual ability and desire to contribute effectively in areas of information technology architecture, and is therefore not representative of IMT organizational structure.&amp;nbsp; The goal is for the working group to be inclusive of those with a desire for architecture, however, in order to maintain an effective working group, membership will be kept to a relatively small group with names being approved by the current membership.&amp;nbsp; The group is always open to nominations of new members, however minimum commitment to serve will be one year, and must be approved by the employee&amp;rsquo;s supervisor. &amp;nbsp;Open communication and publishing of research will be pursued, and additional experts may be brought in as needed.&lt;/p&gt;    &lt;p&gt;To provide leadership, the IT Architect will chair this working group and assumes the role of facilitating group dynamics, monitoring progress, and sharing the working group direction with IMT as a whole.&amp;nbsp; The chair will facilitate meetings, communications and general process management.&amp;nbsp; For the growth of new and existing members, the IT Architect will also be responsible for seeking training in architecture skills and knowledge where applicable.&lt;/p&gt;       &lt;h3&gt;Responsibility of Members&lt;/h3&gt;&lt;ul&gt;&lt;li&gt;  Attend meetings, participate in working group activities (research, analysis, reviews, discussion, etc), and architecture work as assigned by the IT Architect [consideration for other responsibilities and assignments related to your position will be made] &lt;br /&gt;&lt;/li&gt;&lt;li&gt;Individually meet with the IT Architect regularly&lt;/li&gt;&lt;li&gt;Provide Architecture leadership in contexts in which you work (teams, projects, etc.), gently providing guidance according to current and future architecture standards, models etc.&lt;/li&gt;&lt;li&gt;Pro-actively bring architecture issues to the group, identifying problems with current standards, or drivers for future standards.&lt;/li&gt;&lt;li&gt;Inform the IT Architect of any inability to continue to perform these duties&lt;/li&gt;&lt;li&gt;Pray for one another&lt;/li&gt;&lt;/ul&gt;&lt;h3&gt;Decision Making Authority&lt;/h3&gt;    &lt;p&gt;The role of this working group is to make recommendations, suggest standards, and provide expertise to influence decision making individuals and bodies; as such it does not have decision-making powers outside of the direction of the IMT Cabinet.&lt;/p&gt;    &lt;h2&gt;AWG Functions&lt;/h2&gt;&lt;ul&gt;&lt;li&gt;    Create and Maintain Technical and Application Architecture&lt;/li&gt;&lt;li&gt;Review Project Requirements for technical architecture considerations (Requirements Phase)* &lt;/li&gt;&lt;li&gt;Review Logical Designs for Projects (Logical Design Phase)*&lt;/li&gt;&lt;li&gt;Review Physical Designs for Projects (End of Physical Design Phase)*&lt;/li&gt;&lt;li&gt;Provide recommendations, suggest standards, and provide expertise&lt;/li&gt;&lt;li&gt;Forum for interaction and cross-functional growth of technical architecture experts    &lt;/li&gt;&lt;/ul&gt;&lt;p&gt;&lt;em&gt;*&amp;nbsp; Tied to Project Methodology&lt;/em&gt;&lt;/p&gt;    &lt;h3&gt;Project Methodology Interaction - Technical Architecture Reviews&lt;/h3&gt;&lt;h3&gt;&amp;nbsp;&lt;/h3&gt;    &lt;p&gt;&lt;strong&gt;II.&amp;nbsp; Requirements&lt;/strong&gt; - AWG reviews business requirements, and then analyzes architectural implications.&amp;nbsp; Develops &lt;em&gt;technical architecture considerations&lt;/em&gt; with participation from project team.&lt;br /&gt;  &lt;br /&gt;  &lt;strong&gt;III.&amp;nbsp; Logical Design&lt;/strong&gt; - AWG Reviews Logical Design to make sure it provides a conceptual framework for seeking technology solution(s) in physical design.&amp;nbsp; Checks against Architecture Standards as well as project &lt;em&gt;technical architecture considerations&lt;/em&gt;.&lt;br /&gt;  &lt;br /&gt;  &lt;strong&gt;IV.&amp;nbsp; Physical Design&lt;/strong&gt; - AWG reviews Project Team recommendation.&amp;nbsp; Provides a measurable rating of technical architectural compliance to each solution offered as an &amp;quot;additional&amp;quot; resource for Sponsor and IMT Cabinet approval.&lt;br /&gt;  &lt;br /&gt;  &lt;strong&gt;VII.&amp;nbsp; Post Implementation&lt;/strong&gt; - AWG representative sits in on post implementation meeting.&amp;nbsp; Assists with update of service, technology, and application portfolios if needed, and captures life-cycle implications learned from project team.&amp;nbsp; AWG updates any architecture documents changed by new solutions or services.&lt;/p&gt;  &lt;p&gt;&amp;nbsp;&lt;/p&gt; &lt;em&gt; &lt;p&gt;AWG Terms of Reference&lt;/p&gt; &lt;p&gt;Status: Version 3.0      &lt;/p&gt; &lt;p class="MsoHeader"&gt;Date:&amp;nbsp; 2006-06-02&lt;br /&gt;  Date of last Approval: 2006-07-24&lt;br /&gt;  Date of implementation:&amp;nbsp; 2003-04-08&lt;/p&gt;&lt;/em&gt;</description>
 <pubDate>Thu, 27 Jul 2006 15:57:39 -0700</pubDate>
</item>
</channel>
</rss>
