140 likes | 248 Views
NDI/Services Integration Analysis. Pongtip Aroonvatanaporn October 16, 2009. Outline. Introduction Assignment Demo. Motivation. NDI-Based Applications Growth Trend. Number of systems using NDI components steadily increasing
E N D
NDI/Services Integration Analysis Pongtip Aroonvatanaporn October 16, 2009
Outline • Introduction • Assignment • Demo
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
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
Outline • Introduction • Assignment • Demo
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
NDI Integration Analysis Assignment • Use iStudio • Develop deployment diagram • Specify hardware/software definitions • Define connections • Analyses • Interface analysis • Internal assumptions analysis • Dependency analysis
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
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
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
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
Outline • Introduction • Assignment • Demo • iStudio Tool