Date: Tue, 19 Mar 2024 01:17:51 +0000 (UTC)
Message-ID: <1326455794.964.1710811071719@ip-10-10-7-29.ec2.internal>
Subject: Exported From Confluence
MIME-Version: 1.0
Content-Type: multipart/related;
boundary="----=_Part_963_735276764.1710811071717"
------=_Part_963_735276764.1710811071717
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Content-Location: file:///C:/exported.html
Version 2.0, Adopted December 8, 2011
Background
Enterprise, Business and Technical Architecture has grown in importance =
as complexity has increased. Universities facing pressures to eliminate was=
teful duplication and to ensure sound stewardship of resources are looking =
to standardize and streamline delivery of processes. Solutions are now orch=
estrated across technical silos and business units. They are highly integra=
ted to carry out complex business processes. Security risks are compounded =
and distributed with every file transfer and every integration point. The c=
ost and complexity of maintaining, upgrading and integrating systems has ri=
sen. The need for enterprise-wide principles, business process driven desig=
ns and holistic requirements is driving the need for architected solutions.=
The need to implement new strategic initiatives quickly is driving the nee=
d for a well architected organization.
Mission
ITANA is focused on developing the skills, tools and a suite of resource=
s to assist institutions with their enterprise, business and technical arch=
itectural needs. ITANA serves higher education while drawing from other arc=
hitecture groups (The Open Group, Microsoft, etc.) and vendors as needed.=
p>
Goals
(See the ITANA Capability Map)
There are four strategic goals for ITANA:
Practice Development<=
/h3>
- Provide a space for new architects to get their feet wet, ask questions=
, get help and guidance.
- Share the workload on large projects among several institutions and, by=
doing so, deliver a more universal solution.
- Develop common artifacts and practices that are useful to many institut=
ions rather than hidden away in a single institution.
- Share representative architectures and approaches to common problems fo=
r others to learn from and build upon.
Knowledge Transfer
- Aid in knowledge transfer to build architects who are well founded in t=
heir skills.
- Provide a pool of expertise from a range of institutions and areas of i=
nterest for other projects that are looking for participation and input.
- Build a repository of artifacts that is available to architects across =
academia.
- Provide a point of contact for other groups regarding the practice of a=
rchitecture and act as a conduit for collaboration on architectural efforts=
with vendors.
- Link architects to their peers, mentors and partners at their own insti=
tutions as well as across higher education.
- Bring architects together virtually via conference calls, webinars, soc=
ial media and for Face2Face meetings.
Outreach
- Increase the awareness of the role of Enterprise, Business and Technica=
l Architects in the enterprise and their value to the organization.
- Act as a liaison to other groups of interest such as other architecture=
groups, middleware groups and software projects.
Activities
Meetings
- Provide and support a variety of meetings including conference calls, l=
onger and more focused Screen2Screen webinars and Face2Face meetings.
Instruction
- Provide educational opportunities via on-line learning or Face2Face mee=
tings.
- Create a series of on-line tutorials focused on best practices in archi=
tecture.
Publications
- Produce a variety of published artifacts ranging from wiki pages and a =
web posting and more formal publications.
- Publish artifacts focused on the development of =E2=80=9Ccommon practic=
e=E2=80=9D include: frameworks, base requirement documents, common artifact=
s and best practices.
- Support of professional development by sharing: lessons-learned, succes=
s and failure stories, reviews and assessments of various software packages=
.
Co=
llaboration Spaces and Social Networking
- Create spaces for collaboration between architects including a wiki, we=
bsitand web presence in many social networks.
- Drive outreach within Higher Education =E2=80=93 this includes activiti=
es explaining the role of architects in higher education, how various insti=
tutions have implemented architecture and lessons learned.
- Provide broader outreach and education outside of Higher Education =E2=
=80=93 this includes outreach to enterprise, business and technical archite=
cts outside of higher education and product architects for vendors who serv=
e higher education.
------=_Part_963_735276764.1710811071717--