Saibm

979 views
912 views

Published on

Rational System Architect Overview

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
979
On SlideShare
0
From Embeds
0
Number of Embeds
12
Actions
Shares
0
Downloads
9
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Saibm

  1. 1. Enterprise Planning, Transformation, and Collaboration<br />With<br />System Architect<br />Presented by:<br />Sherry Vivona – Account Manager<br />David Kruse – Application Engineer<br />See Where You’ve Been Know Where You are Going Get There with Confidence<br />
  2. 2. Today’s Agenda…<br />Introductions<br />Gartner’s EA Magic Quadrant<br />Enterprise Architecture <br />Product Overview<br />System Architect<br />SA/XT<br />Publisher<br />Process Integrator<br />Product Demonstration<br />Q & A<br />
  3. 3. Gartner’s Leader for Enterprise Architecture<br />4 Years Running<br />2004-2005<br />2006-2007<br />
  4. 4. System Architect<br />Standards based company …with standards compliant tools!<br />
  5. 5. Enterprise Architecture<br />Enterprise Architecture is a term used to describe the practice of documenting (Blueprint) the elements of your organization. i.e. Business case, business model and supporting data, applications, technologies, policies and infrastructures that make up an enterprise.<br /> What is an enterprise?<br />Any collection of organizations that has a common set of goals and/or a single bottom line. <br />An enterprise can be a:<br />Entire Corporation<br />Division of a corporation<br />Single department<br />Chain of geographically distant organizations linked together by common ownership<br />Government agency<br />
  6. 6. Enterprise Architecture - continued<br />The term &quot;enterprise&quot; in the context of “Enterprise Architecture&quot; can be used to denote both an entire enterprise, or a specific domain within the enterprise. <br />Typically made up of 5 Architecture domains:<br />Strategy<br />Business processes<br />Data/Information <br />Systems/Applications <br />Technology/Infrastructure <br />Identify the relationships between different aspects of the enterprise<br />Business to applications that support them<br />Infrastructure to applications<br />Data to business processes<br />Identify the impact across these domains<br />Identify ‘What if’, Gaps, redundancies…etc, for the enterprise<br />*An extended enterprise frequently includes partners, suppliers, and customers.<br />
  7. 7. ‘What If’ scenarios throughout the enterprise…<br />What is the Impact on application (s) if a business process is changed?<br />What is the impact of an application outage on other applications and business processes?<br />What data is shared between applications and business processes?<br />What is the impact on existing systems and networks if security requirements change (i.e. new regulation or statute)?<br />What applications run on which technical platforms?<br />What is the impact on existing applications and business units when retiring a particular platform? <br />Are there business processes that are supported by multiple (possibly redundant) applications? <br />Are business critical functions supported by highly available applications and servers?<br />
  8. 8. Top Ten reason why an organization would not care about Enterprise Architecture…<br />Your business processes will never change<br />The technology platform on which you deploy your business applications will never change<br />No new employees or contractors will ever be hired to evolve and maintain your applications<br />Work done by separate development teams does not need to fit together<br />Your company will never acquire another company and require multiple processes and applications to be integrated.<br />New members of architecture group don’t need to understand what they are doing<br />Will never incorporate industry architecture frameworks ( i.e., MDA, TOGAF, J2EE, .Net)<br />Do not need to rapidly understand impact of changes<br />Well-defined relationships among different groups’ work products is not important<br />Don’t care about consistently and effectively leveraging organizational assets<br />
  9. 9. owner<br />business<br />IT<br />enterprise<br />architect<br />solution<br />architect<br />Why do I need a EA tool?<br /><ul><li>Single Repository
  10. 10. Central management of enterprise documentation
  11. 11. Models and definitions across 5 domains
  12. 12. Strategy
  13. 13. Business Processes
  14. 14. Data/Information architecture
  15. 15. Systems/Applications architecture
  16. 16. Technology/Infrastructure architecture
  17. 17. Cross Domain Visualization
  18. 18. Impact analysis
  19. 19. Gap analysis
  20. 20. Governance
  21. 21. Business standards, business processes and rules
  22. 22. Guidance
  23. 23. planning to deployment
  24. 24. infrastructure requirements
  25. 25. best practices</li></li></ul><li>Guides IT initiatives<br />BPM/BPA<br />Align to business priorities<br />Application Portfolio Mgmt<br />Master Data <br /> Mgmt<br />Asset Mgmt<br />Configuration Mgmt<br />Enterprise Architecture with System Architect<br />Improve Visibility, Enhance Analysis<br />Model across business units and domains<br />Enterprise Strategies & Direction<br />Business Processes<br />Applications<br />Data<br />IT Infrastructure<br />Risk Mgmt<br />Production<br />Operations<br />Marketing<br />Security<br />Sales<br />Quality<br />Aligning business priorities throughout the Enterprise Architecture<br />
  26. 26. strategy<br />accountability<br />corporate<br />centers of <br />excellence<br />implementation<br />initiatives<br />guidance<br />projects<br />Governance<br />Governance is primarily about defining and enforcing organizational policies and standards<br />whatdecisions must be made<br />who should make decisions<br />how are decisions monitored<br />Key areas:<br />policy definition and enforcement<br />lifecycle management<br />discovery and mediation<br />configuration and monitoring<br />
  27. 27. SA XT<br />SA<br />SA Publisher<br />Who are your stakeholders?<br />Modeling Collaboration and User Interface for All Stakeholders<br />SA/XT<br />SA Publisher<br />System Architect<br />Information Portals<br />Business Owners<br />Executives<br />Process Followers<br />Enterprise Solution<br />Business Architects<br />Enterprise Architects<br />Solutions Architects<br />Web Interface<br />Business Analysts<br />Consumers<br />Operations<br /> Analysis Power Modeling Simplicity Information Sharing<br />
  28. 28. System Architect™/Process Integrator<br />Visio Add-on: Provides the simplicity of Visio with the power of System Architect<br />Key Features:<br />Visio templates and error checking ensure adherence to BPMN and organization chart standards <br />Visio “Anchor Window” displays all diagrams and artifacts in System Architect repository for error checking, tracking and reuse <br />Visio models saved in repository can be opened in System Architect for editing, analysis, and reporting <br />Off-line and on-line access provides multi-user workflow to System Architect repository<br /> Common artifacts can be reused across Visio models, and updated automatically wherever a change to that object is made<br />
  29. 29. Goals<br />Objectives<br />Capture and Model all Domains of the Organization<br />Behavior Models<br />Matrix Views<br />Network Topologies<br />Organizational Charts<br />Process Models<br />Application Models<br />Data Models<br />Class Diagrams<br />
  30. 30. Capture and Model all Domains of the Organization<br />
  31. 31. Capture and Model all Domains of the Organization<br />
  32. 32. Simulate and Optimize Processes<br />Analyze resource utilization<br />Determine cost structures<br />Capture and Model all Domains of the Organization<br />
  33. 33. Data Modeling:<br />Conceptual<br />Logical<br />Physical<br />UML Class<br />Capture and Model all Domains of the Organization<br />
  34. 34. Capture and Model all Domains of the Organization<br />Application and Service Models<br />
  35. 35. Capture and Model all Domains of the Organization<br />Network Infrastructure<br />
  36. 36. Supports: <br /><ul><li>X in cell
  37. 37. Text in cell
  38. 38. Multidimensional</li></ul>Capture and Model all Domains of the Organization<br />
  39. 39. Location Business Process Organizational Unit<br />Impact AnalysisManaging changeacross the Enterprise<br />SA gives you modeling domain views of the Enterprise Architecture for fast analysis!<br />
  40. 40. Location Business Process Organizational Unit<br />Impact AnalysisManaging changeacross the Enterprise<br />SA gives you modeling domain views of the Enterprise Architecture for fast analysis! <br />
  41. 41. Location Business Process Organizational Unit<br />Impact AnalysisManaging changeacross the Enterprise<br />SA gives you modeling domain views of the Enterprise Architecture for fast analysis! <br />
  42. 42. Location Business Process Organizational Unit<br />Impact AnalysisManaging changeacross the Enterprise<br />SA gives you modeling domain views of the Enterprise Architecture for fast analysis! <br />
  43. 43. Location Business Process Organizational Unit<br />Impact AnalysisManaging changeacross the Enterprise<br />SA gives you modeling domain views of the Enterprise Architecture for fast analysis! <br />
  44. 44. Visualizing the Impact of Change<br />
  45. 45. Architecture Frameworks Organize & Visualize Data<br />Custom<br />FEA<br />Zachman<br />TOGAF<br />Fully configurable for custom frameworks<br />
  46. 46. Modeling SOA: Service Oriented Architecture<br />Service Collaboration Diagram<br />Creating Services models is key<br />Impact Analysis of Service Implementation<br />Gives a common enterprise view of the SOA project<br />
  47. 47. SOA Analysis<br />Services Roadmap<br />- Availability of each Service<br />- Service component to which<br />applications<br />Application Landscaping<br />Report clearly how services are supported over time <br />Compare the current and future state of IT service environments<br />
  48. 48. Analyze your ERP Implementation<br />System Architect/ERP is an auto discovery tool designed for exploring ERP system metadata<br />Imports ERP metadata directly into System Architect to provide visibility into the ERP deployment<br />SAP<br />PeopleSoft/Oracle<br />JD Edwards/Oracle<br />Siebel/Oracle<br />Provides Visibility into the ERP Deployment<br />
  49. 49. XMI<br />IDL<br />CSV<br />Disparate Data<br />Rose<br />Excel<br />Visio<br />DDL<br />XML<br />is Imported,<br />Applications and IT<br />Business Strategy<br />Organization & Process<br />Structured,Linked and Traced,<br />To Produce Reports of Managed Information<br />The System Architect Lifecycle<br />
  50. 50. Complete Solutions from IBM<br />Professional Services<br />Tool Training<br />EA Quick Start Programs<br />Pilot Project Workshop<br />Methodology Training<br />Rapid Deployment Program<br />On-Site/Public Training<br /><ul><li>Business Process Modeling and Simulation
  51. 51. Power User (Advanced)
  52. 52. DoDAF</li></ul>Customer Support<br />“GREAT JOB!!! I truly appreciate your professionalism and your ability to solve a customer&apos;s issue quickly.” – Large defense contractor<br />“Thank you again for a job well done.” – US Government Agency<br />“You should feel very fortunate that such talented and nice people work in<br />your facility.” – Fortune 500 User<br />
  53. 53. EA Certification<br />Certification from Carnegie Mellon University<br />Tool agnostic<br />Delivered via Telelogic Professional Services<br />Courseware created by Carnegie Mellon<br />Certification Testing (Dual certification, CMU & Telelogic)<br />Worldwide Program Offering<br />Three Certification Levels<br />Fundamentals of Enterprise Architecture<br />Applied Enterprise Architecture Concepts<br />Advanced Enterprise Architect Concepts<br />
  54. 54. Thank You!<br />On to the Demo!<br />

×