1. Enterprise Planning, Transformation, and Collaboration With System Architect Presented by: Sherry Vivona – Account Manager David Kruse – Application Engineer See Where You’ve Been Know Where You are Going Get There with Confidence
2. Today’s Agenda… Introductions Gartner’s EA Magic Quadrant Enterprise Architecture Product Overview System Architect SA/XT Publisher Process Integrator Product Demonstration Q & A
5. Enterprise Architecture 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. What is an enterprise? Any collection of organizations that has a common set of goals and/or a single bottom line. An enterprise can be a: Entire Corporation Division of a corporation Single department Chain of geographically distant organizations linked together by common ownership Government agency
6. Enterprise Architecture - continued The term "enterprise" in the context of “Enterprise Architecture" can be used to denote both an entire enterprise, or a specific domain within the enterprise. Typically made up of 5 Architecture domains: Strategy Business processes Data/Information Systems/Applications Technology/Infrastructure Identify the relationships between different aspects of the enterprise Business to applications that support them Infrastructure to applications Data to business processes Identify the impact across these domains Identify ‘What if’, Gaps, redundancies…etc, for the enterprise *An extended enterprise frequently includes partners, suppliers, and customers.
7. ‘What If’ scenarios throughout the enterprise… What is the Impact on application (s) if a business process is changed? What is the impact of an application outage on other applications and business processes? What data is shared between applications and business processes? What is the impact on existing systems and networks if security requirements change (i.e. new regulation or statute)? What applications run on which technical platforms? What is the impact on existing applications and business units when retiring a particular platform? Are there business processes that are supported by multiple (possibly redundant) applications? Are business critical functions supported by highly available applications and servers?
8. Top Ten reason why an organization would not care about Enterprise Architecture… Your business processes will never change The technology platform on which you deploy your business applications will never change No new employees or contractors will ever be hired to evolve and maintain your applications Work done by separate development teams does not need to fit together Your company will never acquire another company and require multiple processes and applications to be integrated. New members of architecture group don’t need to understand what they are doing Will never incorporate industry architecture frameworks ( i.e., MDA, TOGAF, J2EE, .Net) Do not need to rapidly understand impact of changes Well-defined relationships among different groups’ work products is not important Don’t care about consistently and effectively leveraging organizational assets
26. strategy accountability corporate centers of excellence implementation initiatives guidance projects Governance Governance is primarily about defining and enforcing organizational policies and standards whatdecisions must be made who should make decisions how are decisions monitored Key areas: policy definition and enforcement lifecycle management discovery and mediation configuration and monitoring
27. SA XT SA SA Publisher Who are your stakeholders? Modeling Collaboration and User Interface for All Stakeholders SA/XT SA Publisher System Architect Information Portals Business Owners Executives Process Followers Enterprise Solution Business Architects Enterprise Architects Solutions Architects Web Interface Business Analysts Consumers Operations Analysis Power Modeling Simplicity Information Sharing
28. System Architect™/Process Integrator Visio Add-on: Provides the simplicity of Visio with the power of System Architect Key Features: Visio templates and error checking ensure adherence to BPMN and organization chart standards Visio “Anchor Window” displays all diagrams and artifacts in System Architect repository for error checking, tracking and reuse Visio models saved in repository can be opened in System Architect for editing, analysis, and reporting Off-line and on-line access provides multi-user workflow to System Architect repository Common artifacts can be reused across Visio models, and updated automatically wherever a change to that object is made
29. Goals Objectives Capture and Model all Domains of the Organization Behavior Models Matrix Views Network Topologies Organizational Charts Process Models Application Models Data Models Class Diagrams
39. Location Business Process Organizational Unit Impact AnalysisManaging changeacross the Enterprise SA gives you modeling domain views of the Enterprise Architecture for fast analysis!
40. Location Business Process Organizational Unit Impact AnalysisManaging changeacross the Enterprise SA gives you modeling domain views of the Enterprise Architecture for fast analysis!
41. Location Business Process Organizational Unit Impact AnalysisManaging changeacross the Enterprise SA gives you modeling domain views of the Enterprise Architecture for fast analysis!
42. Location Business Process Organizational Unit Impact AnalysisManaging changeacross the Enterprise SA gives you modeling domain views of the Enterprise Architecture for fast analysis!
43. Location Business Process Organizational Unit Impact AnalysisManaging changeacross the Enterprise SA gives you modeling domain views of the Enterprise Architecture for fast analysis!
46. Modeling SOA: Service Oriented Architecture Service Collaboration Diagram Creating Services models is key Impact Analysis of Service Implementation Gives a common enterprise view of the SOA project
47. SOA Analysis Services Roadmap - Availability of each Service - Service component to which applications Application Landscaping Report clearly how services are supported over time Compare the current and future state of IT service environments
48. Analyze your ERP Implementation System Architect/ERP is an auto discovery tool designed for exploring ERP system metadata Imports ERP metadata directly into System Architect to provide visibility into the ERP deployment SAP PeopleSoft/Oracle JD Edwards/Oracle Siebel/Oracle Provides Visibility into the ERP Deployment
49. XMI IDL CSV Disparate Data Rose Excel Visio DDL XML is Imported, Applications and IT Business Strategy Organization & Process Structured,Linked and Traced, To Produce Reports of Managed Information The System Architect Lifecycle
52. DoDAFCustomer Support “GREAT JOB!!! I truly appreciate your professionalism and your ability to solve a customer's issue quickly.” – Large defense contractor “Thank you again for a job well done.” – US Government Agency “You should feel very fortunate that such talented and nice people work in your facility.” – Fortune 500 User
53. EA Certification Certification from Carnegie Mellon University Tool agnostic Delivered via Telelogic Professional Services Courseware created by Carnegie Mellon Certification Testing (Dual certification, CMU & Telelogic) Worldwide Program Offering Three Certification Levels Fundamentals of Enterprise Architecture Applied Enterprise Architecture Concepts Advanced Enterprise Architect Concepts
