SOA Implementation Methodology: What to look for?
Organizations planning to implement SOA should implementation methodologies which covers end-to-end implementation of the SOA roadmap. It should help organization to select the appropriate approach for SAO implementation and set up the IT goal. The methodology should provide visibility of challenges, risks and ROI.
It should be classified into phases:
• Formalizing the roadmap, domain model and goal model
• Providing the component, message, service and information specifications
• Providing the final implementation based upon standards
SOA Governance framework:
Enterprises SOA governance framework should be based upon Open-Source platform. Framework refers to the standards and policies that govern the design, build and implementation of an SOA solution and the policies that must be enforces during runtime. Organizations should also indentify complete testing framework for Unit Testing, Functional Testing, Integrated Testing and Process-level Testing to ensure a high quality of service.
|
---|
Service-Oriented Architecture is a concept used in development and integration of IT systems. The primary goal of SOA is to expose application functions in a standardized way, so that they can be leveraged across multiple applications. This approach greatly reduces the time, effort and costs required to maintain and expand solutions to meet business needs. The blog is for SOA testing. If SOA testing is your area, you are welcome to have a glance of the blog.
Tuesday, January 31, 2012
SOA Implementation Methodology: What to look for?
iTKO LISA Vs QTP
Feature | iTKO LISA | Quick Test Professional |
---|---|---|
Cross browser testing | IE, Firefox, Safari, etc | IE and Firefox possible |
Supported Technologies | LISA supports DTHML/JavaScript, AJAX, Java Applet, Swing, Flash/Flex, Microsoft ActiveX, Oracle Apps | Separate license required |
SOA Test validation | LISA has advantage of connecting middle layer interfaces to test SOA Architecture | Scripting required to connect interfaces. Limited to Request and response validations |
Validations or Check points | Assertions available with support for more than 60 middle layer technologies | Check points possible for supported technologies |
User friendly Interface | Test flow is represented diagrammatically and easy to understand. | Test Flow is complex |
Control test flow | Easy to rearrange test flow as it is Drag & drop | Rearranging the Test flow is complex and there is dependency on QTP resource |
Implementing Validation | Codeless filters and assertions | Scripting by use of “if conditions” |
Synchronization | Easy to create Sync point at step level as well globally. | Scripting required |
Creating Functions | Easy to convert test cases in to sub process. | Function creation is possible using scripting |
Database Validation | Codeless effort for DB connectivity , fetching data and comparing with application | Scripting required to validate data base , there are some check points through which we can connect data base without code but still required coding to validate application |
QC Integration | Available | Available |
Load & Performance Testing | Available | Not Possible |
Stubs and Drivers | LISA Virtualization available to overcome testing constraint | Not Possible |
Object Identification (GUI) | Customization is difficult to implement. Record and Playback option available | Customization possible like Descriptive programming |
Coding according to Functionality to validate Data on App(GUI & Web Services) | Required Java coding knowledge | Possible with VB scripting in QTP |
Customized report | Supports Excel, CSV and pdf without single line of scripting | We can customize reports into various formats with the help of scripting |
Web Services Testing | Easier way without scripting | Scripting required or else can use Web service add-in still need some scripting for validations |
Automation using Design documents | Not Possible | Possible |
Subscribe to:
Posts (Atom)