Systems Integration & Consulting June 2009. 2 Copyright ® 2009 Ayenda Agenda Introduction to Systems Integration System Integration Challenges and Opportunities.
Published byModified over 5 years ago
Presentation on theme: "Systems Integration & Consulting June 2009. 2 Copyright ® 2009 Ayenda Agenda Introduction to Systems Integration System Integration Challenges and Opportunities."— Presentation transcript:
2 Copyright ® 2009 Ayenda Agenda Introduction to Systems Integration System Integration Challenges and Opportunities Ayenda Methodology Ayenda Assets and Offerings Summary
3 Copyright ® 2009 Ayenda Systems Integration “ Systems Integration enables Systems, Applications, People and Processes to communicate and share data to ensure business components function together.” Systems Enablement of enterprise level communication across organizational domains. Applications Enablement of disparate applications and products to share and transfer data. People Enabling executives, architects, domain representatives and team members to have a coherent view of the enterprise. Processes Enabling workflows that meets business requirements and organizations policy guidelines.
4 Copyright ® 2009 Ayenda Ayenda’s expertise on Systems Integration Systems Integration and Consulting Improve business process execution Standardized data integration Industry Best Practices and Principles Provide Services across Industries Defense & Government Retail Systems Banking Systems Entertainment Industry Ayenda’s core focus is Systems Integration
5 Copyright ® 2009 Ayenda Agenda Introduction to Systems Integration System Integration Challenges and Opportunities Ayenda Methodology Ayenda Assets and Offerings Summary
6 Copyright ® 2009 Ayenda System Integration Challenges and Opportunities Challenges IT continues to seek solutions that enable simpler, more flexible systems at a lower cost of ownership and that provide for better integration across multiple platforms. Enterprises are under pressure to increase business operations by using IT strategically to enable differentiated business capabilities. Enterprises want to de-tangle their systems and interfaces to better manage and maintain changes across the organization. The biggest challenge to Application Development (AD) departments is training on new technology, followed by the changing technology standards and the overall lack of technical skills. Opportunities The primary benefit of SOA is that it helps business managers and analysts develop new business processes and modify processes more quickly and at a lower cost. The capability to create or receive alerts or notifications could be one of the most attractive benefits of SOA. An SOA software service is usually designed to correspond to a business concept, facilitating communication among business analysts and software engineers. Organizations are turning to external service providers (ESPs) to offload IT routine issues to focus their internal resources on business processes instead. Source: “The Business Impact of Service-Oriented Architecture”; Gartner: Publication Date: 24 December 2007
7 Copyright ® 2009 Ayenda Agenda Introduction to Systems Integration System Integration Challenges and Opportunities Ayenda Methodology Ayenda Assets and Offerings Summary
8 Copyright ® 2009 Ayenda Ayenda’s Methodology “We measure success of IT not only by how well it is being leveraged for business-as-usual (BAU) activities, but also by how it is utilized to facilitate the enterprise to be a key differentiator in the market.” System Integration through Governance. Partner with Industry leaders to quickly and efficiently integrate systems. Leverage Ayenda’s key assets. Vendor Agnostic and promote Open Source Software. Staffing Model that is based on unique needs and requirements.
9 Copyright ® 2009 Ayenda SOA Capability Offering Map Legacy and Disparate Systems Service Enabled Enterprise Services Bus and SOA Platform Enterprise SOA SOA Governance SOA Roadmap SOA Operations Our SOA Maturity Model help clients adopt SOA and increase their maturity level throughout the Software Development Lifecycle. SOA and Business Process Management Web Service Compliance Strategy & Planning OfferingsCapability Development OfferingsSOA Industrialization Offerings Phase 1 Phase 2 Phase 3Phase 4 Integration Methodology Model
10 Copyright ® 2009 Ayenda Phase 1: Legacy and Disparate Systems Infrastructure Basic service infrastructure and tools. Dedicated management tools for applications. Servers and hardware may be redundant to support different systems. Architecture Point-to-Point interfaces. Architecture does not have a clear separation of concerns between technology and business logic. Legacy applications written in outdated code. File based transfer protocols and hard to maintain. Operation File based logging and limited operational visibility. Multiple vendor tools are used to support operations. Project is in constant need for production support and maintenance.
11 Copyright ® 2009 Ayenda Phase 2: Service Enabled Architecture Infrastructure Basic service infrastructure and tools with support for core WS standards wsdl, soap, xml. Transport level security for services. Architecture Clear view of enterprise architecture. SOA strategy formulated. SOA infrastructure and tooling standards in use across one or more departments. Key industry standards identified, e.g. industry XML, WS-Addressing. Initial SOA-based application reference architecture defined. Operation Security, logging and auditing policies captured in code rather than using a gateway solution. Delivery teams structured traditionally around applications and projects. Rapid application development techniques evaluated for SOA projects.
12 Copyright ® 2009 Ayenda Phase 3: Enterprise Service Bus and SOA Platform Infrastructure Initial project level use of ESB and BPEL for service integration and orchestration. Service-level access to Information Sources, Enterprise Applications through WS standards: WSIF, JCA, JMS. Basic service management infrastructure for monitoring. Common Enterprise SOA Platform for Service Delivery includes foundation technical services such as messaging and transformation. Architecture SOA Roadmap Planning Initiated. Business processes and their supporting technologies become modules that can be reused for efficiency and recombined for agility. Metrics to measure SOA adoption and success identified. Infrastructure and applications standardization across lines of business to address efficiency, and reduce fragility. Operation Web Services Management solution to enable declarative policy definition and centralized monitoring and enforcement. Capacity planning for services.
13 Copyright ® 2009 Ayenda Phase 4: Enterprise SOA Infrastructure Use of Business Process Modeling Tools and Standards (BPMN, BPDM) Advanced service management monitoring, alerting, logging and application of security policies external to services. Use of Business Rules Engines For isolating policies from application code and enabling easier change to business policies. Architecture Strict enforcement of architectural standards. Metrics on process variances, changes, service reuse tracked. Clearly defined reference architecture covering applications, information, technology, security architectures. Business policies abstracted out of application code and captured as business rules which are available as services. Operation SLAs, QoS incorporated into service contracts. Composite Application Management, including ability to perform analysis to determine the affects of service outages on business processes. Advanced service management monitoring, alerting, logging and application of security policies outside services.
14 Copyright ® 2009 Ayenda Agenda Introduction to Systems Integration Ayenda Methodology System Integration Challenges and Opportunities Ayenda Assets and Offerings Summary
15 Copyright ® 2009 Ayenda Data Management Framework Jumpstart data retrieval and persistence High performance object/relational persistence and query service. Leverages Hibernate and Spring Data Access Framework. Based on best data access practices and principles. Standardized and configurable libraries.
16 Copyright ® 2009 Ayenda Service Oriented Architecture Framework Standardizes legacy systems to catch up to today’s integration standards. Enables organizations to easily follow a Service Oriented Architecture (SOA) integration methodology. Web Service Interpretability Standardized exception handling, auditing, and message routing. SOAP message parsing, Security and message validation.
17 Copyright ® 2009 Ayenda Agenda Introduction to Systems Integration Ayenda Methodology System Integration Challenges and Opportunities Ayenda Assets and Offerings Summary
18 Copyright ® 2009 Ayenda Summary Systems Integration Core focus is Systems Integration Systems are build using standard methodologies and best practices and principles. Methodology Staffing model is uniquely balanced between onshore and offshore resources to meet business requirements. Roadmap is established to ensure project scope and maturity model. IT Governance is enabled at the start of project to ensure successful delivery. Assets and offerings Standardized assets are built and managed to jump start System Integration. Common problems are identified and solved using best practices and patterns.