Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migration of unmigrated content due to installation of a new plugin

...

9:15

...

to

...

10:15 AM

Session 1 - Tools of the trade

Tom Barton

 

We'll showcase some of the tools, methodologies, artifacts, techniques, or tactics that we use to engender increased architectural coherence across the infrastructures and business & operational processes we're connected with. The session will help us to think about the range of ways in which we might influence others by use of the tools with which we engage them.

 

Session Details, Presentations and Notes

Administrative IT Roadmap - UC Davis - Curtis Bray

Tip
titlePresentation and Links
AM* {table-cell} {table-cell:width=50%} *Session 1 - Tools of the trade* {table-cell} {table-cell:width=25%} *Tom Barton* {table-cell} {table-row} {table-row} {table-row} {table-cell} {table-cell} {table-cell}We'll showcase some of the tools, methodologies, artifacts, techniques, or tactics that we use to engender increased architectural coherence across the infrastructures and business & operational processes we're connected with. The session will help us to think about the range of ways in which we might influence others by use of the tools with which we engage them. {table-cell} {table-cell} {table-cell} {table} h3. Session Details, Presentations and Notes h4. Administrative IT Roadmap - UC Davis - Curtis Bray {section} {column:width=5%} {column} {column:width=45%} h5. Presentation [UC Davis IT Road Map.pdf|^UC Davis IT Road Map - ITANA Face 2 Face 2008.pdf] {column} {column:width=45%} h5. Links More information: [

UC Davis IT Road Map.pdf
More information:

http://vpiet.ucdavis.edu/itroadmap.cfm

] {column} {column:width=5%} {column} {section} {section} {column:width=5%} {column} {column:width=95%} h4. Notes: (from Jim Phelps' blog [

Section
Column
width5%

Column
width95%

Notes:

(from Jim Phelps' blog http://www.jimphelps.info/2008/ea/itana-face2face-tools-of-trade

]) {quote} [

)

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.

{quote} {column} {section} h4. PIM - Saint Louis U - Jim Hooper {section} {column:width=5%} {column} {column:width=45%} h5. Presentation [ThePIM_ITANA08.ppt|^ThePIM_ITANA08.ppt] {column} {column:width=45%} h5. Links {column} {column:width=5%} {column} {section} {section} {column:width=5%} {column} {column:width=95%} h4. Notes: {column} {section} h4. IT Ecosystem - U Chicago - Tom Barton {section} {column:width=5%} {column} {column:width=45%} h5. Presentation [U Chicago IT Ecosystem|^200806-f2f-iteco.ppt]\] {column} {column:width=45%} h5. Links [

PIM - Saint Louis U - Jim Hooper

Tip
titlePresentation and Links

ThePIM_ITANA08.ppt

Section
Column
width5%

Column
width95%

Notes:

IT Ecosystem - U Chicago - Tom Barton

Tip
titlePresentation and Links

U Chicago IT Ecosystem]
https://virtus.uchicago.edu/display/integration/IT+Ecosystem

Section
Column
width5%

] {column} {column:width=5%} {column} {section} {section} {column:width=5%} {column} {column:width=95%} h4. Notes: More details and a link to download the "monolithic" form of the software are at [
Column
width95%

Notes:

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

Curtis

Bray's

notes)

{quote}

'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 {quote} (from Jim Phelps' blog [

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

(from Jim Phelps' blog http://www.jimphelps.info/2008/ea/itana-face2face-tools-of-trade

]

)

{quote}

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.

{quote} {column} {section}