1. University of Southern California Center for Systems and Software Engineering NDI/Services Integration Analysis Pongtip Aroonvatanaporn October 16, 2009

2. University of Southern California Center for Systems and Software Engineering Outline Introduction Assignment Demo 10/16/092

3. University of Southern California Center for Systems and Software Engineering Motivation 10/16/093

4. University of Southern California Center for Systems and Software Engineering 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 10/16/094

5. University of Southern California Center for Systems and Software Engineering 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 Java CRM Microsoft Access Database JDB C ADOD B 10/16/095

6. University of Southern California Center for Systems and Software Engineering Outline Introduction Assignment Demo 10/16/096

7. University of Southern California Center for Systems and Software Engineering 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 10/16/097

8. University of Southern California Center for Systems and Software Engineering NDI Integration Analysis Assignment Use iStudio Develop deployment diagram –Specify hardware/software definitions –Define connections Analyses –Interface analysis –Internal assumptions analysis –Dependency analysis 10/16/098

9. University of Southern California Center for Systems and Software Engineering 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/16/099

10. University of Southern California Center for Systems and Software Engineering 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 10/16/0910 Component AComponent B Pipe

11. University of Southern California Center for Systems and Software Engineering 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 10/16/0911

12. University of Southern California Center for Systems and Software Engineering Example Deployment Diagram 10/16/0912

13. University of Southern California Center for Systems and Software Engineering 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 10/16/0913

14. University of Southern California Center for Systems and Software Engineering Outline Introduction Assignment Demo –iStudio Tool 10/16/0914