MD703 Class 8 DRAFT Agenda

1
MD703 Class 8 DRAFT Agenda

• Midterm Return and Review
• The Big Fix Discussion
• Application Integration
• Workflow
• EAI
• Service Oriented Architecture
• Chapters 4, 10 Review

2
The Big Fix

• IT Governance
• Projects Management
• Projects Ownership
• Projects Portfolio
• Projects Environment
• Application Development Environment
• Standard tools, functions
• Common libraries, scheduling, Access control

3
Workflow Transactions

• Definition A single logical business event, that
  involves one or more technical events, that
  should not be subdivided.
• Rules
• Atomic
• Consistent inputs
• Isolated
• Durable
• Requirements
• Availability of all inputs
• Near simultaneous actions

4
Workflow Process

• Definition The logical linking of transactions
  and business processes to accomplish a complex
  business event the assembly line
• Examples Purchase Order
• Issues
• Time
• Multiple persons, servers, locations
• Notification of status
• Options, sequence, parallel steps
• Non-technical steps

5
Workflow Goals

• Identification
• Process definition
• Process stability
• Routing
• Triggering
• Status availability
• Parallel processing
• Performance metrics

6
Service Oriented Architecture

• Purpose
• Modular Structure
• Web services are the components
• Accessed via email or http using XML
• Reusable Logic
• Dynamic linking of functions w/o hierarchy
• Aspects
• Std for defining the service (WSDL)
• Std for invoking the service (SOAP)
• Web Services Registry (UDDI)
• Std for presenting data (XML)

7
SOA Problems Solved

• JAVA issues
• Write once, use often
• Context
• Location of service fixed
• Strategic Development
• Components can be built w/o hierarchy
• Possible multiple service providers
• Applications are built by dynamic linking of the
  services
• Linking to external services no harder, just a
  different URL and XML format

8
SOA Lines and Circles

• Typical development model
• Hierarchy of functions
• Context of processes
• SOA makes linkage very inexpensive
• Liquid Computing
• Write once, deploy once

9
SOA Opportunities

• SCM or Channel applications
• Service may be bid dynamically
• Switching costs minimal
• Invocation is programmed in, not dynamic
• Rapid Application Development
• Focus on presentation, integration of services
• Easy modification, w/o integration testing

10
SOA Discussion

• How can web Services and SOA help protect
  intellectual property in program logic, etc. ?

11
Chapter 4 Review

• 3 Forms of Planning
• Strategic
• Tactical
• Operational
• Sense and Respond
• Digital Assets
• Not consumed
• Asset aspect
• Liability aspect

12
Chapter 10 Review

• Change Mgmt
• Risk Mgmt
• Legacy Evolution
• Metrics

13
Discussion

• Reconcile Most critical IT decisions are
  infrastructure (pg 145) with the sense-respond
  model of flexible access.
• What aspects guide decision to build on legacy
  systems or replace them?