1 / 19

Enterprise Architecture

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

Albert_Lan
Télécharger la présentation

Enterprise Architecture

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Enterprise Architecture DAMA MN March16, 2005 as planned to present at Wilshire Meta Data Conference, Orlando, Florida

  2. 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

  3. Four Disciplines • Business Architecture • Information (Data) Architecture • Applications (Solutions) Architecture • Infrastructure(Technical) Architecture

  4. 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 Business Architecture Tools Focus

  5. Data Sources Key Subject Areas Relationships Definitions Business Constraints Acquisition of Data Transformation Requirements Docs ORM Models ER Diagrams Data Dictionaries Enterprise Wide DW Models Data Flow Diagrams Information Architecture Tools Focus

  6. 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 Solutions Architecture Tools Focus

  7. Technology Location “Abilities” – Capability, Availability…etc. Servers Tele-Communication Back-up & recovery Licenses Vendor relationships Network Diagrams Budget Docs Schedules Disaster Recovery Plan Schematics Infrastructure Architecture Tools Focus

  8. Sample Business Artifact

  9. Information Artifacts Models Taxonomies, Glossaries

  10. Solutions Artifacts “Swim Lanes”

  11. Infrastructure Artifacts

  12. Business Architect MBA Knows the business Recognized leader Seeking Process Improvements Staffing • Solutions Architect • Deep skills in multiple tools • Intrigued by integration • Trusted by IT & business peers • Information Architect • Data Modeler/Analyst • Strategic Thinker • Seeks documentation • Passionate about Data • Infrastructure Architect • Technically savvy • Competent Negotiator • Not afraid of 7x24

  13. 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

  14. Metrics • Solutions Architecture • Tool concentration • Portfolio analysis • License capacity • Minimized tool redundancy • Infrastructure Architecture • Technical currency • Maintenance agreements • Recoverability • Uptime

  15. 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

  16. 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

  17. 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)

  18. 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 • Dawn.michels@Andersencorp.com • 651-264-7985

  19. 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)

More Related