Browse Prior Art Database

System and Method for System Integration visualisation testing application

IP.com Disclosure Number: IPCOM000215405D
Publication Date: 2012-Feb-26
Document File: 5 page(s) / 104K

Publishing Venue

The IP.com Prior Art Database

Abstract

In a Software Lab Environment, there is a requirement to test enterprise class systems not only in isolation but integrated with other Enterprise systems. Development, Test and Management teams require a clear understanding of the exact nature of the integration between products. However each team requires a different level of abstraction of how systems are wired together. Furthermore as product teams move through subsequent releases, it is necessary to articulate which versions of product A work with product B and finally which versions of each product have been tested with each other.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 24% of the total text.

Page 01 of 5

System and Method for System Integration visualisation testing application
In a Software Lab Environment, there is a requirement to test enterprise class systems not only in isolation but integrated with other

Enterprise systems. Development, Test and Management teams require a clear understanding of the exact nature of the integration between products. However each team requires a different level of abstraction of how systems are wired together. Furthermore as product teams move through subsequent releases , it is necessary to articulate which versions of product A work with product B and finally which versions of each product have been tested with each other.

To articulate the integration points between systems requires diagrams to be created where the target audience is known. However as the target audience changes, diagrams need to be rewritten or edited to suit the audience. This is a time consuming process.

Therefore it is necessary to have an application system and method which provides the following solutions:


1) Illustrates the integration points between one or many systems at different levels of abstraction (e.g. API, Protocol, Physical, Usecase level)


2) For an integrated product solution set, stores the product versions that are supported with one another


3) For an integrated product solution set, stores the product versions that have been tested by test teams.


4) The aggregation of knowledge related to supported product versions within an integrated solution to guide upgrade paths for Integrated customer solutions

A Note on Prior art found Vs What ideas we are trying to protect

The prior art searches below indicate that there is some prior art in the field of visualization and in the abstraction of different view types., particularity in the invention "Application view component for system integration". However the union of prior art falls short in the following claims: For an integrated product solution set, stores the product versions that are supported with one another, For an integrated product solution set, stores the product versions that have been tested by test team and The aggregation of knowledge related to supported product versions within an integrated solution to guide upgrade paths for Integrated customer solutions. No prior art could be found related to these three ideas proposed.

The IBM* OMA tool currently does not provide the functionality around what products product NFA's are supported with each other.

Search terms used (and Prior Art Results)

System Integration schematic


System Integration diagram
System Integration visual representation

Application view component for system integration

http://www.google.com/patents?id=nz2RAAAAEBAJ&pg=PA2&dq=System+Integration+Application&source=gbs_selected_pages&cad=2 #v=onepage&q&f=false - Deals primarily with system integration architecture and abstraction, but does not have the ability to show different levels of abstraction nor store supported products within...