1 / 14

Integrating NDI Services: Analysis and Trends in e-Services Deployment

This report analyzes the growth trends and integration challenges faced by NDI-based applications, with a focus on e-Services projects at USC. It discusses the increase in CBA (Cost-Benefit Analysis) implementation from 28% in 1997 to 70% in 2002, and highlights survey findings from the Standish Group demonstrating similar trends within the industry. Through interface, internal assumptions, and dependency analyses, the report identifies potential communication failures arising from incompatible components, particularly in CRM systems and Microsoft Access integrations. Recommendations for improved connector usage in data-intensive interactions are included.

silver
Télécharger la présentation

Integrating NDI Services: Analysis and Trends in e-Services Deployment

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. NDI/Services Integration Analysis Pongtip Aroonvatanaporn October 16, 2009

  2. Outline • Introduction • Assignment • Demo

  3. Motivation

  4. NDI-Based Applications Growth Trend • Number of systems using NDI components steadily increasing • USC e-Services projects show number of CBA’s rise from 28% in 1997 to 70% in 2002 • Standish group’s 2000 survey found similar results (54%) in the industry [Standish 2001 - Extreme Chaos] CBA Growth Trend in USC e-Services Projects Standish Group Results

  5. Microsoft Access Database Java CRM JDBC ADODB • COTS products are created with their own set of assumptions which are not always compatible • Example: Java-Based Customer Relationship Management (CRM) and Microsoft Access integration • CRM supports JDBC, MS Access supports ADODB • CRM assumes database always active, MS Access requires to be activated

  6. Outline • Introduction • Assignment • Demo

  7. Pre-Assignment • Survey • List of NDI/Services products used/to be used • Deployment diagram • Simple lines and boxes sufficient • Hardware & Software • COTS deployed • Used to find NDI/Services definitions

  8. NDI Integration Analysis Assignment • Use iStudio • Develop deployment diagram • Specify hardware/software definitions • Define connections • Analyses • Interface analysis • Internal assumptions analysis • Dependency analysis

  9. Interface Analysis • ‘Failure due incompatible error communication’ • Pre-conditions • 2 components (A and B) communicating via data &/or control (bidirectional) • One component’s (A) error handling mechanism is ‘notify’ • Two components have incompatible error output/error input methods • Result • Failure in the component A will not be communicated in component B causing a permanent block or failure in component B

  10. Component B Component A Internal Assumptions Analysis • ‘Data connectors connecting components that are not always active’ • Pre-conditions • 2 components connected via a data connector • One of the component does not have a central control unit • Result • Potential data loss Pipe

  11. Dependency Analysis • ‘Parent node does not support dependencies required by the child components’ • Pre-condition: • Component in the system requires one or more software components to function • Result: • The component will not function as expected

  12. Example Deployment Diagram

  13. Analysis Report • HTML • Contains the following analyses: • Interface mismatches between components • Internal assumption mismatches components • NDI dependencies • Recommendation of connectors to be used for data intensive interactions. • Used by Project/System Analyst

  14. Outline • Introduction • Assignment • Demo • iStudio Tool

More Related