Upload
hp-software-solutions
View
4.504
Download
2
Tags:
Embed Size (px)
DESCRIPTION
As an applications or enterprise architecture executive, you are facing a perfect storm of quickening business requirements, constrained resources, and new technologies and architectural patterns that promise value. But how do you ensure that your investments in application modernization and new application delivery don’t get mired in the complexity of adopting new technologies and best practices? Attend this session and learn how to apply the principles of application governance at key points in the application lifecycle. We’ll show you how, by putting in place a process and automation for application governance, you will see measurable results in technical quality, application delivery, and operational hand-offs that will help you realize business benefits faster and with fewer resources and less cost.
Citation preview
1 ©2010 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice
Application governance in action: delivering measurable benefits throughout the application lifecycle
Kelly EmoSr. Manager, Applications Products
HP Software and Solutions
2
Product& ServiceLeadership
OperationalExcellence
The Business Is Demanding… IT to Be a Source of Competitive Advantage
Source of Competitive Advantage*
CustomerIntimacy
ENABLERS
*Source: Market Discipline, Dr. Michael Treacy,
Professor, MIT’s Sloan School of Management
Business agility relies on…
IT agility, which relies on…
A foundation of architecture and applications
3
Your business demands faster, better, cheaper
You face decades of existing applications and architecture
Some legacy, some packaged, some proprietary
and pressure to globalize, virtualize and scale
You want to respond but what you have limits you..
The Need Drives You to Modernize…
4
“Driven by growing demand for business agility, the monolithic application is and will be rapidly evolving into granular, compose-able and re-useable
building blocks.”
Kathy HarrisGartner Research, June 16, 2008
5
The amount of moving parts, componentized services and actionable metadata explodes.. The promise of agility comes
with the price of complexity
Business expects IT response in “Google” time
Powerful technologies available at an accelerating
pace
Modernization Is a “Perfect Storm” for IT
6
PROCESSES
• Increasing pace of change drives adoption of Agile Methodology
• Distributed teams need visibility
• Collaboration and consistency is key
• Dependency management is critical
PEOPLE
• Resources are distributed
• Across time zones, languages
• Teams have dependencies, and must learn to share
• Trust becomes paramount
TECHNOLOGIES
• Silos get split up, functionality becomes modular
• Capabilities delivered as services
• Rise of the intermediary
• Metadata is everywhere
The IT organization
Modernization Requires Changes Across…
7
All Modern Apps Create Similar IT Challenges
7 3 June 2010
What do we have?
Where did it come from?
Can I use it?
Who owns it? Who maintains it?
Can I trust it? Will it work for me?
What happens when something changes?
Where do I go to learn more?
To get a handle on this, start with visibility… create a way to share information across teams
8
Support Visibility:You Can’t Modernize What You Can’t Find
I’ve built a Checking Account Service
A Governance Repository provides the information that enables Applications and Services to be shared and
helps drives the application lifecycle
App or Service creator/provider
Composite AppDeveloperService and
Application Catalog
My eBanking application needs a Checking Account Service
9
Lifecycle Management Lowers Costs & Speeds Time to Service
The Application Lifecycle?
App/Service design
Service Development and Quality Management
Service stagingService deployment
Operations
Business and IT collaboration
Design-time
Run-time
Change eventBusiness or
operations-driven
Go/no-go decision“Ready for
Deployment/ Consumption”
Architecture team
Information flow
Collaboration creates efficiency
10
Visibility, collaboration and lifecycle management… what are we talking about?
11
IT’s Navigation System for Modern Applications
Application Governance
• Enable visibility
• Automate lifecycle
• Establish control by defining and enforcing policies
• Foster trust
• Measure progress and results
Governance Activities Drive Adoption of Enterprise Standards
Collaboration
Policy Def &Enforcement
Measurement & Feedback
Policy Def &Enforcement
Collaboration
Consumption/Contract
Management
LifecycleManagement
12
Application Governance in Action–Four Basic Use Cases
– Subtitle goes here
13
Establish Consistent Adoption of Best Practices and Standards
Use Case #1
Best-practice driven lifecycles
Pre-build Policies
Guided behavior
• In app dev, how can you be certain what is being built is consistent with your organization’s
•Best practices?
•Standards?
•How can you enforce consistency across the organization in the face of application and people changes?
Example: How to enforce development on JDK 1.6 across distributed dev teams?
14
Running Through the Use Case
1. Define and agree on policy to enforce
2. Educate organization to new policy
3. Adopt automated governance software
4. Configure a design-time policy (“JDK must be
1.6 or later”)
5. Determine point in application lifecycle to
check policy (associate policy with stage in
governed lifecycle)
6. Guide behavior through automated policy
compliance checking and reporting
7. If developers are out of compliance, actions
can be taken earlier in the lifecycle
15
Visual interpretation of Use Case
– Using slide shots – a mini fast-tourAutomated Governance software
allows technical and business policies to be associated with tasks and
lifecycle advancement – checks can be automated or manual, reporting
aggregated to drive action
16
Guide the Work of Outsourced Development Teams
Use Case #2
•Ongoing cost, talent and competitive pressures drive us to build or source virtual or off-shore teams
•How can you off-load development to an external org yet maintain compliance to standards and policies?
Example: How to maintain compliance with development policies when you do not directly manage the people doing the work?
Agile Business CapabilitiesShared Services / Composite Apps
Desired state
17
(based on an HP public-sector customer in EMEA)
Running Through the Use Case
1. Define the role of the outsourced, virtual team
(i.e. development of application code)
2. Use automated governance software
3. Define a lifecycle with handoff points driving
transition to the virtual team
4. Define and implement explicit, documented
standards enforced by policies for how code
is constructed/built, published in a repository,
and validated against standards
5. Enforce that code and artifacts get validated, published in repository for
discovery by downstream teams
18
Define a custom governance lifecycle with guided handoffs
to the virtual team
Guide the virtual team with documented and
enforced policies guiding development
of code and repository publishing
19
Use Case #3Minding the Gap Between Application and Operations
Example: How to automate the Development-to-Operations application hand-off
20
Running Through the Use Case(based on an HP Telecommunications
customer use case)1. Define a Governance Lifecycle process for
applications or services that ensures key runtime
metadata is captured during the design/develop
phases
2. Capture the metadata in a usable form in the
governance repository
3. Define the lifecycle point in which ownership is
passed from the applications teams to the
operations teams
4. At that point, ensure the metadata flows to the
operations teams in the form of detailed requirements for deployment
5. Use the performance, availability and run-time policy data to automate
SLA management at run-time
MIND THE GAP
21
Ensure the Service or Application has associated
metadata in the form of documented run-time requirements/SLAs
This Metadata can be made available automatically to
Operations through lifecycle transition notification. Then, the metadata can drive the set up and on-going management of
business-motivated SLAs
22
Provide Adoption of Enterprise Architecture Requirements Across All Development Teams
Use Case #4
The Challenge
Distributed, shared, agile and virtual teams
Internal team
North America
Virtual team
Internal team
Europe
Outsourced team
South Amer
• Foster collaboration• Assimilate best practices• Optimize costs through
globalization
Designed to
Requiring
•How can you maintain desired architectural compliance?
•Over time?
•Across distributed development teams?
•How can you prove that new and improved architectural approaches are followed when code and apps are actually developed?
Example: How to enforce that no modules will make direct, point-to-point calls to databases?
Asia
23
(Based on HP’s Own Systinet R&D Team)
Running Through the Use Case
1. Document desired Architectural Pattern
2. Communicate broadly across Application teams
3. Determine point in development lifecycle to
validate architectural policy
4. Adopt Automated Governance software
5. Develop policy to check architectural pattern
compliance
6. Associate policy with lifecycle stage “progress
to build”
7. Check compliance before build system accepts a completed package
8. Communicate results of policy check to development and architecture
teams
24
– Using slide shots – a mini fast-tour
Associate architecture policy check with a business service or application in development
phase…
25
“True enterprise-level agility requires the architectural coherency that comes with an architecture vision realized through conscientious governance.”
Avoid The EA Governance Versus Agility Trap Altering Your View Of EA Governance Won’t Result In Chaosby Henry Peyret with Gene Leganza and Mimi AnForrester Research, September 24, 2008
© 2008 TIBCO Software Inc. All Rights Reserved. Confidential and Proprietary.
Adopting Enterprise Architecture Standards: The SOA Scenario enabled by TIBCO ActiveMatrix
Dan Enache
Sr Manager Engineering
TIBCO Software Inc
© 2008 TIBCO Software Inc. All Rights Reserved. Confidential and Proprietary.27
Top Reasons for Adopting SOA
Business:
Eliminate/Reduce Vendor Lock-inIncrease ROI with Re-useShorten time-to-market
Technical:
Avoid Proprietary APIsNormalize Operations and Management of Services
Organization:
Governance
© 2008 TIBCO Software Inc. All Rights Reserved. Confidential and Proprietary.28
What do customers want from a SOA platform?
Rapid Service Enablement Rapid exposure of their application via Web Services
Ability to compose new applications with existing services
Choices of: Implementation Technologies
Where to deploy and run
Flexibility and Agility Make ad-hoc changes post deployment
Visibility and Control Operational and Lifecycle Governance
SLA management
© 2008 TIBCO Software Inc. All Rights Reserved. Confidential and Proprietary.29
TIBCO’s Vision for a Unified Application Platform
Unified Design
time Framework
Unified Runtime
Platform
Unified Process
Engines
SOA & Governance
Enabled Technologies
Integrated BPM,
SOA &
Optimization
© 2008 TIBCO Software Inc. All Rights Reserved. Confidential and Proprietary.30
Challenges with Traditional SOA Applications
SOAP-Service-http ()
{
registerProcessOrder();
}
OnMsg::ProcessOrder ()
{
invokePartner();
}
SOAP-Reference-http ()
{
call.setEndPtAddr();
call.setOpsName();
call.invoke();
}
Transport is embedded to
provide services
Transport is embedded to
consume services
Difficult to reuse the business logic outside of the application
Difficult to scale the business logic independently
Difficult to version the business logic w/o major disruption
Difficult to re-implement with a different technology
© 2008 TIBCO Software Inc. All Rights Reserved. Confidential and Proprietary.31
Challenges with Traditional Orchestration Projects
Transport is embedded to
provide services
Transport is embedded to
consume services
Difficult to reuse the business logic outside of the application
Difficult to scale the business logic independently
Difficult to version the business logic w/o major disruption
Difficult to re-implement with a different technology
© 2008 TIBCO Software Inc. All Rights Reserved. Confidential and Proprietary.32
Solution: Componentization and Virtualization
Componentization is about breaking down
complex applications into smaller
components with the opportunity to reuse
Virtualization is about abstracting
components so they can be assembled into
new composite applications
All the components are built following
industry standards (WS-*, OSGI, SCA, etc)
© 2008 TIBCO Software Inc. All Rights Reserved. Confidential and Proprietary.33
Componentizing the Application Logic
ReserveCar_HTTP GetPrice_PartnerGetCarModel
SOAP-Service-http ()
{
registerProcessOrder();
}
OnMsg::ProcessOrder ()
{
invokePartner();
}
SOAP-Reference-http ()
{
call.setEndPtAddr();
call.setOpsName();
call.invoke();
}
Composite Application
Traditional SOAP
embedded app
Service Provider transport
is decoupledService Consumer transport
is decoupled
Virtualized business logic becomes reusable
Virtualization presents a choice of other implementation types
GetCarModel
© 2008 TIBCO Software Inc. All Rights Reserved. Confidential and Proprietary.34
Componentizing the Orchestration Logic
ReserveCar_HTTP GetPrice_Partner
Composite Application
Service Provider transport
is decoupledService Consumer
transport is decoupled
Virtualized business logic becomes reusable
GetCarModel
GetCarModel
Virtualization presents a choice of other implementation types
© 2008 TIBCO Software Inc. All Rights Reserved. Confidential and Proprietary.35
In 2010, a lack of working SOA
governance arrangements is the
most common reason for SOA
failure.
(Gartner)
What is the problem? What experts have to say ?
In 2010, a lack of working SOA
governance arrangements is the most
common reason for SOA failure.
(Gartner)
© 2008 TIBCO Software Inc. All Rights Reserved. Confidential and Proprietary.36
TIBCO’s Solution: ActiveMatrix Platform
SOA Guided by Application Governance
Lifecycle Governance
AMX Lifecycle Governance Framework
Operational Governance
AMX Policy ManagerAMX Service
Performance Manager
AMX Service Grid
ActiveMatrix Runtime Foundation & Administrator
JavaPOJO/
Spring
.NET C++ RubyBW
IT
Perl/
PHPPython
ESB: AMX Service Bus
TIBCO EMS
Active
Ma
trix
Bu
sin
essW
ork
s
Ad
ap
ters
37
Governance
Applications IT Operations
App & Service creationApp or Service Owner
ConsumersComposite App Dev
Strategy Applications Operations
Manage the lifecycle of delivering apps and services with visibility, automated processes for architectural consistency
and control, information and feedback
Manage quality complexity while
accelerating functional,
performance and security validation
Architecture
Manage services and traditional
applications using a single unified
management system
ManagementQuality
Get the Most from Governance–Integrate With the Complete Application Lifecycle
Re-use modules in composite applications
HP Application Lifecycle Management – enabled with software integration
38
HP SOA Systinet
HP SOA Policy Enforcer
The HP Governance Software Portfolio
HP SOA Registry Foundation
• Seamless integration with HP SOA Systinet
• Automation of run-time policy configuration and enforcement
• Provides key run-time metrics to Systinet
• Complete Governance platform• Manage the complete lifecycle• Define and enforce policy• Manage consumption• Information for measure-
ment and feedback
• Embeddable UDDI registry• Jumpstart ISVs, developers and
solution providers building SOA composite apps
• Simplify integration and discovery
Governance Interoperability
Framework
39
Take Away…
Drill down into managing the application lifecycle with Governance
Engage in an application modernization discovery day
When modernizing, realize that governance can be a guidance system
Learn more at www.hp.com/go/ALM
See Application Governance at the HPSU Solution Showcase
40
Q&A
41 ©2010 Hewlett-Packard Development Company, L.P.
To learn more on this topic, and to connect with your peers after
the conference, visit the HP Software Solutions Community:
www.hp.com/go/swcommunity
42