10:30 to Noon |
Session 2 - Case Studies: Architecture on Your Campus |
Jim Hooper |
|
|---|---|---|---|
|
This session will focus on Case Studies from several institutions including: Descriptions of ongoing Enterprise Architecture programs in your university. How, Who, What, and any impacts the program has had/is having on your IT environment. Descriptions of specific projects that have been significantly impacted (positively) by the Enterprise Architecture program. |
|
|
Session Details, Presentations and Notes
Duke University - Kevin Miller &Mark McCahill
Presentations and Links
ITANA Architectural_Principles_final.pdf
Session Details, Presentations and Notes
Duke University - Kevin Miller &Mark McCahill
Presentations and Links
ITANA Architectural_Principles_final.pdf
Duke University
Tech Architecture group at Duke is charged:
to track emerging technology and raise issues for the CIO's consideration
review major decisions
integrate into the project management lifecyle
pay attention and champion certain solutions
Developed small set of principles - few enough that they could remember them around four areas:
Data
Infrastructure
Services
Support
Each of these areas are highlighted in each principle's page (http://oit.duke.edu/tag/principles/p-robust-systems.html)The principles:
Robust Secure Systems
Link don't copy
Design for scalability
Design for information lifecycles (not only the data but the overall system)
Adapt to realities of people and technology (has to work in real life)
There is tension between all of the principles. You are picking a failure mode when/if you don't meet a principles.TAG drafted the principles. Focus groups used to refine the principles. The "adapt to the realities" principle came from the focus groups. Did an OIT-wide staff survey. Then followed a communications plan to evangelize the principles. They showed practical application via case studies - looked at situations that went badly or tough decisions that had to be made. The case studies are very valuable for communications and for the change management. They chose failures that where inside the group so that they would be criticizing themselves.
They also use Issue Reviews when there is a failure (http://oit.duke.edu/tag/issues/index.html). Each write-up has a list of recommendations with the principle highlighted.
The idea is build a volume of case-law and to evaluate the principles. "You're making stories... the legend that becomes part of the culture".
PIM - Saint Louis U - Jim Hooper
Presentations and Links
IT Ecosystem - U Chicago - Tom Barton
Presentations and Links
[U Chicago IT Ecosystem|^200806-f2f-iteco.ppt]
[https://virtus.uchicago.edu/display/integration/IT+Ecosystem]
Random notes:
'It's hard to see the big picture from your patch."
Logic description of how one things depends on another
Graphical application that builds data into a graph with relationships between nodes
Applications
Hardware
Populated through conversations - not SNMP walks
Tom is constant factor to get commonality across systems
One ecosystem but have test instance (crash test dummy)
Transactions for rollback
Logs
Security
High level stuff
Good for next 6 month window
Balance of maintenance vs. currency
Can answer questions
Rank dependencies of nodes
Show dependencies
More details and a link to download the "monolithic" form of the software are at [https://virtus.uchicago.edu/display/integration/IT+Ecosystem]. The link to the client-server version is restricted to local U Chicago folks for some reason, but contact Tom if you'd like to have it.
(from Jim Phelps' blog [http://www.jimphelps.info/2008/ea/itana-face2face-tools-of-trade])
Protege based ontology for mapping the relationships between Applications, Platforms, Networks. They have a defined a set of relationships: Hosts, Is-part-of, is-server-to, etc.
Produces a cool drill-able graph of relationships. The relationships have structural properties.
They have captured 1300 relationships. They have limited things to objects that are production.
The production shop is looking at this tool for mapping the flows of data files in batch jobs.
Limited to the amount of information that they can reasonably gather and manage with a 6 month refresh rate.
Overview
Content Tools