• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
SAP_NetWeaver_CE_Overview_April2008
 

SAP_NetWeaver_CE_Overview_April2008

on

  • 805 views

 

Statistics

Views

Total Views
805
Views on SlideShare
803
Embed Views
2

Actions

Likes
1
Downloads
34
Comments
0

1 Embed 2

http://www.slideshare.net 2

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    SAP_NetWeaver_CE_Overview_April2008 SAP_NetWeaver_CE_Overview_April2008 Presentation Transcript

    • Enterprise Architecture Introduction to the SAP Enterprise Architecture Initiative Benjamin Herrmann SAP Deutschland AG & Co. KG
    • Positioning EA and SOA Enterprise Architecture SOA © SAP 2008
    • SOA needs EA to succeed © SAP 2008
    • A strategic initiative for SAP © SAP 2008
    • What are the new EA and SOA enablers? NEW Global Hub SKILLS & RESOURCES of Enterprise Architects EAF NEW SAP Enterprise Architecture METHODOLOGY Framework for SOA SAP EAF toolset NEW Enhanced Discovery System TOOLS & PRODUCTS ES Bundles IVN & ES Community NEW Creation of the ESEC – Enterprise PROCESSES Services Enablement Centre NEW Enterprise Architecture Services SERVICES Enhanced SOA Portfolio NEW Dedicated training and certification TRAINING for SOA roles © SAP 2008
    • SAP has recruited a group of Enterprise Architects Role Support business strategy Define & build corporate IT strategy Evangelise for SOA Set frameworks for success of SOA Skillset Architecture skills mix (Business, Application, Information, Technology) Experienced in strategic IT landscape planning Enterprise Architecture Frameworks (e.g. TOGAF) Technical knowledge of business processes Strong SOA and Web Services concepts knowledge NCC AMERICAS EMEA APAC © SAP 2008
    • What’s in a framework? A translation process A process to create useful models Develop a consistent and comprehensive model Show multiple views to communicate the model effectively A process to manage the architecture A communication tool: Persuade management that architecture principles cannot be ignored Show system designers that architecture simplifies the problem © SAP 2008
    • SAP’s Framework is based on TOGAF - why? The Open Group Architecture Framework A reliable, proven method for developing an Enterprise Architecture developed by the Open Group An open standard Vendor neutral TOGAF considered to be the most relevant Framework Results from 2006 survey of TechEd attendees (54 % of ASUG members and 2006 TechEd attendees) and online ASUG survey Freely licensed Intended to be tailored http://www.opengroup.org © SAP 2008
    • Collaboration SAP and Open Group Platinum Membership Board members of the Open Group Participate on strategy, policies and processes Main interests of SAP: TOGAF and ITAC TOGAF 9.0 Final draft approval September 2008 Public release planned for November 2008 TOGAF 9.0 contains lots of contents from EAF Delta document on TOGAF 9.0 and EAF in October 2008 © SAP 2008
    • A recap on the TOGAF ADM Architectural phases TOGAF ADM Narrative of architecture phase Cross-phase summaries on requirements management Concept of architecture building blocks ARCHITECTURE PHASE © SAP 2008
    • What‘s missing from TOGAF? #1 TOGAF ADM does not distinguish between Solution Architecture and Enterprise Architecture. TOGAF does not acknowledge two distinct disciplines and requires the use of ADM for all engagements. Process tuning for specific engagement styles, durations or scales is not addressed. © SAP 2008
    • What‘s missing from TOGAF? #1 #2 TOGAF ADM does not distinguish between Solution Architecture and Enterprise Architecture. TOGAF is a multi-vendor framework TOGAF does not acknowledge two distinct It seeks to integrate existing content and process disciplines and requires the use of ADM for all frameworks within an industry standard model. engagements. As a result, the ADM is not prescriptive about Process tuning for specific engagement styles, terminology definitions, specific deliverables, durations or scales is not addressed. deliverable format, content metamodel or content representation. © SAP 2008
    • What‘s missing from TOGAF? #1 #2 TOGAF ADM does not distinguish between Solution Architecture and Enterprise Architecture. TOGAF is a multi-vendor framework TOGAF does not acknowledge two distinct It seeks to integrate existing content and process disciplines and requires the use of ADM for all frameworks within an industry standard model. engagements. As a result, the ADM is not prescriptive about Process tuning for specific engagement styles, terminology definitions, specific deliverables, durations or scales is not addressed. deliverable format, content metamodel or content representation. #3 TOGAF is an “abstract” method, specifically intended to be extended or instantiated before it can be used in practice. This philosophy results in the majority of definitions within TOGAF being vague and open. © SAP 2008
    • What‘s missing from TOGAF? #1 #2 TOGAF ADM does not distinguish between Solution Architecture and Enterprise Architecture. TOGAF is a multi-vendor framework TOGAF does not acknowledge two distinct It seeks to integrate existing content and process disciplines and requires the use of ADM for all frameworks within an industry standard model. engagements. As a result, the ADM is not prescriptive about Process tuning for specific engagement styles, terminology definitions, specific deliverables, durations or scales is not addressed. deliverable format, content metamodel or content representation. #3 #4 TOGAF is designed to cope with all situations, and designed to be extended where necessary TOGAF is an “abstract” method, specifically intended to be extended or instantiated before it This means that TOGAF is closer to an abstract can be used in practice. template for architecture engagements This philosophy results in the majority of A more concrete product that is suitable for definitions within TOGAF being vague and open. immediate, direct usage on architecture engagements where service-orientation and/or packaged solutions are a given is needed © SAP 2008
    • SAP Enterprise Architecture Framework SAP Enterprise Architecture Resource Base Framework extensions Extensions Usage Guidelines SAP Business Framework Reference Models extensions Architecture Content Development Metamodel Method SAP Technology Templates, Examples and Case Reference Models Studies SAP Mapping Extensions SAP SAP Tooling Extensions Extensions SAP Content SAP Implementation EA Modelling Tools Tools Tools TOGAF TOGAF TOGAF Architecture Resource Foundation Development Base Method © SAP 2008
    • Metamodel ARCHITECTURE VISION, CONTEXT AND ROADMAP Associated With All Principle Constraint Requirement Gap Work Package Objects BUSINESS ARCHITECTURE Operates in Participates Organisation Unit in Owns and Is motivated by Contains Owns Produces governs Operates in Interacts with, Supports, Is Is Produced Motivates Belongs to Performs performed by Is owned by by Supplies or Consumes Product Driver Actor Function Can be Process Extension Consumes Generates, accessed by Creates Resolves Performs Supports, Is Is bounded by Is Produced task in realised by by Participates Addresses in Goal Is Performed Orchestrates, by decomposes Produces Is realised through Involves Role Process Realises Accesses Involves Is guided Generates, Orchestrates, decomposes Objective Resolves by Is tracked Control against Ensures correct Process Extension operation of Sets performance Is Resolved by, criteria for Is Generated by Applies to Meets Is Resolved by, Is Generated by Service Quality Contract Measure Event Governance Governance Contains Contains Governance Extension Process Extension Extension Extension Sets performance Is Resolved by Applies to Governs, Measures criteria for Supports, Is Is governed and Location Is tracked against Is Provided to Resolves realised by Meets measured by Infrastructure Consolidation Is owned and (Business, Information System) Service Extension governed by Services are Contained in Core, Business / IS split supports the Business / IT Alignment Extension Provides governed interface to access Provides, consumes Is realised Is implemented on through Is Supplied or Consumed by Is accessed and Is processed Operates Provides updated through by on Implements platform for Supplies Contains Contains Is Hosted Is Supplied By Contains Physical Information in Logical Application Logical Technology Component Data Entity Component Data Extension Component Platform Service Infrastructure Consolidation Resides within Resides within Extension Encapsulates Is Realised by Realises Logical Information Physical Application Component Component Physical Technology Data Extension Infrastructure Component Consolidation Extension Encapsulates Is Hosted in Is Hosted in APPLICATION DATA ARCHITECTURE ARCHITECTURE TECHNOLOGY ARCHITECTURE Infrastructure Process Modelling Business / IT Alignment Consolidation Extension Extension Extension Governance Extension Data Modelling Extension Core Content © SAP 2008
    • Enterprise Architecture toolset: ARIS IT Architect Easier maintenance of architecture as the business and IT landscape changes More effective knowledge sharing across the whole organization Provides stakeholders with models most relevant to their role More effective governance Promotes re-use of models Promotes more consistent quality as the models are integrated Provides one source of the truth properly managed ……not unmaintained, unconnected Visio and Excel files ! © SAP 2008
    • The SAP EA Framework and integrated Services The SAP Enterprise Architecture Framework (EAF) is a methodology and toolset It is designed to be applied to all engagements The SAP EA Services are targeted at specific customer requirements They apply Industry Best Practice to real- life engagement issues They apply the SAP EAF Processes, Templates, and Accelerators to specific architecture pain points © SAP 2008
    • SAP Tiered Certification: New Program Framework Master Master Level: 7+ years of experience in Enterprise Architecture Expert In- and externally recognized as an expert in his/her knowledge in Enterprise Architecture field Deep practical EA experience, integration, Enterprise optimization and architectural knowledge Architecture Ability to provide strategic vision and realization Ability to articulate EA at CxO level Leading teams and projects Professional Professional Level: 3-7 years of experience in Enterprise Architecture Advanced Professional ERP experience, advanced solution knowledge in and process knowledge, industry expertise Enterprise Deep knowledge of at least 1-2 domains in Enterprise Architecture Architecture T-shaped: broad view across several dimensions, plus deep capability to understand a specific area Associate Works independently within teams to realize EA Level: projects, capability of mentoring others Foundation level knowledge Associate 1-3 years of experience in Enterprise Architecture in Enterprise Hands-on skills to successfully implement ERP Architecture. solutions Skills to Foundation knowledge of at least one domain in contribute to EA Enterprise Architecture projects. Works in a mentored position within an experienced team © SAP 2008
    • Adoption of methodology and services Adoption High adoption on EA services Increasing adoption of methodology Upcoming EA reference customer success story © SAP 2008
    • NCC Feedback on Banking* Top EA characteristics in Banking Critical systems very old and very large (> 20 years) Systems due to age operated in silos Integration hubs as „black boxes“ for silo communication Quote: „Changing these systems is like being a thief in a bank“ Quote: „Consideration of moving to a standardized software solution is very low“ Top EA challenges How-to introduce change to these systems in a controlled and secure manner How-to reduce complexity on integration efforts Most important: Tie all of the various systems together in a management reporting systems to: – Support the various sub-ledgers required for internal management (cost allocations, ABC, Profitability, etc.) – Required external and regulatory reporting (IFRS, BASEL, GAAP, etc.) Top EA areas from SAP‘s perspective Information Architecture and MDM Integration with a heavy SOA emphasis Reporting architecture with a specific focus on BI Bank Analyzer and the financial capabilities of Business Objects *These statements are from the National Competence Center from Enterprise Architects with engagements in the banking sector. © SAP 2008 The statements reflect the views of the Enterprise Architects themselves
    • Enterprise Architecture Framework: The methodology for SOA adoption The New SAP Enterprise Architecture Framework is based on open standards and may be used free of charge by our customers and partners It is specifically designed to support the effective adoption of packaged solutions in an SOA environment The New SAP Enterprise Architecture Framework is holistic, practical and agile Education materials, certification and service offerings are available A global Enterprise Architecture Community is already created – with user groups, customers and partners © SAP 2008
    • Questions THANK YOU FOR YOUR ATTENTION! © SAP 2008 Contact: benjamin.herrmann@sap.com