enterprise architecture dama mn march16, 2005 as planned to present at wilshire meta data...
TRANSCRIPT
Enterprise Architecture
DAMA MN March16, 2005 as planned to present at
Wilshire Meta Data Conference, Orlando, Florida
Agenda
The four facets of Architecture Sample artifacts for each discipline Staffing each Architecture role Metrics of success for each discipline Interdependencies between each
type Conclusion
Four Disciplines
Business Architecture Information (Data) Architecture Applications (Solutions) Architecture Infrastructure(Technical) Architecture
Business Architecture
Business Requirements
Process Improvement
“Bottom Line” Project Initiation Project Process
Project Planning Requirements
Gathering Matrices ROI indicators Business Process
Flows Corporate
Strategies Project Charter or
Initiation Document
Focus Tools
Information Architecture
Data Sources Key Subject Areas Relationships Definitions Business
Constraints Acquisition of Data Transformation
Focus Tools Requirements
Docs ORM Models ER Diagrams Data Dictionaries Enterprise Wide
DW Models Data Flow
Diagrams
Solutions Architecture
What applications can support the processes
Integration strategies Cost of ownership Portfolio Analysis Redundant
applications Decommissioning
Integration Diagrams
Process Flows Data Flow
Diagrams Trade journals RFPs
Focus Tools
Infrastructure Architecture
Technology Location “Abilities” –
Capability, Availability…etc.
Servers Tele-
Communication Back-up & recovery
Licenses Vendor
relationships Network Diagrams Budget Docs Schedules Disaster Recovery
Plan Schematics
Focus Tools
Sample Business Artifact
Type of RequirementFunctionalTechnical
Legal
Process or Activity Description of Process or Activity
Metric - defines how we know this requirement is satisfied
OwnerPerson (s) who can: - identify what the
requirement is, - when it is met
Priority1= High2= Med3= LowNA= not needed
Follows is a partial example
Functional Dept Business Process Process Description New New PriorityAccounts Payable Check Printing Ability to print checks 1
Invoice Management 1Recurring Invoices 3Vendor Return's Ability to process Vendor
returnsCredits applied where appropriate
3
Integration -- Recvd PO s populate AP file 1Variance Recon 1
Business Requirements DocumentA brief overview of the intented purpose of the project.
Information ArtifactsModels
Taxonomies, Glossaries
Solutions Artifacts
Fu
nct
ion
Fu
nct
ion
Fu
nct
ion
Process ProcessProcess
app module
app module
app module
Fu
nct
ion
Fu
nct
ion
Fu
nct
ion
Process ProcessProcess
app module
app module
app module
“Swim Lanes”
Infrastructure Artifacts
Staffing
Business Architect MBA Knows the business Recognized leader Seeking Process
Improvements
Information Architect Data Modeler/Analyst Strategic Thinker Seeks documentation Passionate about Data
Infrastructure Architect Technically savvy Competent Negotiator Not afraid of 7x24
Solutions Architect Deep skills in multiple tools Intrigued by integration Trusted by IT & business
peers
Metrics
Business Architecture Requirements scored Business customer satisfaction Seeking corporate wide process improvements On time, on budget..
Information Architecture Number of sources defined Minimal redundancy Stewardship in place Standard processes in place
Metrics
Solutions Architecture Tool concentration Portfolio analysis License capacity Minimized tool redundancy
Infrastructure Architecture Technical currency Maintenance agreements Recoverability Uptime
Interdependencies
Business Architect Sets stage for all disciplines Educates other team members on business
needs Secures counsel in order to write feasible
proposals
Information Architect Uses requirements to drive data analysis Supplies input to solution requirements Identifies data points of integration
Interdependencies
Solutions Architect Uses requirements and models as input Explores already available solutions Secures counsel from TA regarding feasible
technology
Infrastructure Architect Uses solutions artifacts to analyze resource/server
match Supplies input to RFP requirements Identifies system/technology timing and recovery
Key Take Aways
There is no right or wrong way to do Enterprise Architecture
Determine what the org needs and staff accordingly
Establish a baseline of relevant metrics for each discipline
Try to get executive sponsorship (report to CIO directly or near directly)
Thanks for your time and interest!
Dawn Michels Information Architect Past Pres DAMA MN Past VP Chapter Services DAMA-I Adjunct Faculty Member College of
St. Catherine Passionate data Architect
651-264-7985
Resources/Acknowledgements
http://www.cas.mcmaster.ca/~cs4eb3/samples/TourOperator/TourOper.html (SAMPLE ER Model)
http://www.conceptdraw.com/en/sampletour/uml_erd/ (great downloadable samples)
http://iainstitute.org/pg/ (The Information Architecture Institute http://www.iawiki.net/DefiningTheDamnThing (Good
organization of materials) http://www.tdan.com/i001fe01.htm (David Hay article –
introduces Zachman Framework from a practical application standpoint)