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. |
|
|
Presentations and Links
(from Jim Phelps' blog [http://www.jimphelps.info/2008/ea/itana-face2face-tools-of-trade])
[http://vpiet.ucdavis.edu/]
Created an Administrative Services Map with eight domains. Each domain has a Domain Convener. All the Domain Conveners gather on a single governance board.
Academic Personnel Adminstration
Enterprise Asset Management and Planning
Student and Curriculum Support
Finance
Information Technology
Alumni and University Relations
Research
Payroll and HR
Just bringing this fruition.Currently moving to Kuali Financials - this is a "big rock" project that they stage. Above this is their SOA, ESB and Infrastructure layer. With IdM above that. Then Portal.
Use the roadmap to help guide the School and Department works. Hope to align the work in the School and Departments with the roadmap.
Having a transparency, rich communication and agree on principles helps with the alignment across domains and the schools and departments.
If you look down the road, you could see that the IT domain would grow as more stuff moves into the infrastructure layer. This would also allow for more modular developments.
The roadmap is application centric - the infrastructure layer should have its own roadmap.
Presentations and Links
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.