1. June 15, 2009GITB Open Meeting, Brussels1 GITB Alternative Architectures and Business Models CEN/ISSS eBIF Global eBusiness Interoperability Test Bed Methodologies Project Prof. Dr. Asuman Dogac and Tuncay Namlı SRDC Ltd. Ankara, Turkey

2. June 15, 2009 GITB Open Meeting, Brussels 2 Outline Alternative Architectures: 1. Single Testbed Architecture with a single TDL and an Execution Engine 2. Network of Multiple Testbeds and Test Services Alternative Business and Organizational Models 1. GITB System with Single Governance 2. GITB System with External Test Suite Governance 3. Free Market with an Abstract Testbed Specification 4. Using Existing Testbed Functionality through GITB Test services

3. June 15, 2009 GITB Open Meeting, Brussels 3 Alternative I: Single Testbed Architecture with a single TDL and an Execution Engine

4. June 15, 2009 GITB Open Meeting, Brussels 4 Alternative I: Single Testbed Architecture with a single TDL and an Execution Engine (Continued) Building a global testbed from scratch  A generic Test Description Language (TDL) and  A Test Execution Engine Main improvements over existing testbeds:  Standard modular interfaces to support utilization of external applications, services, data structures as plug-ins  Addressing the detailed testing requirements gathered in GITB  Exploiting the know-how and the existing work It should be possible to utilize the related software parts of the existing test frameworks in the GITB

5. June 15, 2009 GITB Open Meeting, Brussels 5 Alternative II: Network of Multiple Testbeds and Test Services

6. June 15, 2009 GITB Open Meeting, Brussels 6 Alternative II: Network of Multiple Testbeds and Test Services (Continued) The aim is to improve the reusability of testing facilities among stand-alone and dedicated test environments To support the collaboration among existing and future testbeds  Ability to share testing facilities and resulting test reports remotely among testbeds  The main role of the GITB is to define Standard Test Service interfaces and Standard Test Reporting format in order to enable this collaboration

7. June 15, 2009 GITB Open Meeting, Brussels 7 Alternative II: Network of Multiple Testbeds and Test Services (Continued)

8. June 15, 2009 GITB Open Meeting, Brussels 8 Alternative II: Network of Multiple Testbeds and Test Services (Continued) The GITB Test Service is the remote service which can be configured and executed for a specific test purpose with the inputs provided over the Web  Example: A test service for code validation  Example: An organization can serve some of its test scenario descriptions as a highly parameterized test service to the outside world When called remotely, the Test Service generates the validation report according to the test purpose and returns it to the caller The GITB can define different interfaces for different test purposes GITB can provide the guidelines which describe the key points and good practices for Test Service implementation

9. June 15, 2009 GITB Open Meeting, Brussels 9 Alternative II: Test Service Registry and its Associated Metadata (Continued) In this architecture a Test Service Registry will be very helpful for the discovery and the use of GITB test services The GITB should define a metadata standard to be used to describe the Test Services The metadata defined should cover all the capabilities, inputs, outputs, and the report formats of the Test Service GITB can provide and maintain the registry The Test Service implementers may register their services to this registry to make them available to be discovered and used by other test developers or testers

10. June 15, 2009 GITB Open Meeting, Brussels 10 Alternative Business and Organizational Models The business and organizational models specify the role and scope of the GITB project (or its representative organizations) How the specified testbed architectures can be setup and managed: 1. GITB System with Single Governance 2. GITB System with External Test Suite Governance 3. Free Market with an Abstract Testbed Specification 4. Using Existing Testbed Functionality through GITB Test services

11. June 15, 2009 GITB Open Meeting, Brussels 11 1. GITB System with Single Governance

12. June 15, 2009 GITB Open Meeting, Brussels 12 1. GITB System with Single Governance (Continued) A Global Interoperability Test Bed (GITB) is implemented at the end of the GITB Project An organization is established for its governance GITB Organization is responsible to develop and maintain the Test Suites Eventually, the GITB will have many test suites for different standards from different domains Several business models can be pursued with this organizational model:  In the simplest case, there can be a commercial agreement between the GITB Organization and the organization that requests the development and maintenance of test suites  Then, the GITB Organization is not concerned with the relationship or agreements between the software vendors that use the GITB for executing the test suites  As another alternative, there can be tripartite agreements which are based on the business models like pay-per-use

13. June 15, 2009 GITB Open Meeting, Brussels 13 1. GITB System with Single Governance: Federated Architecture (Continued) Setting up only one instance of the GITB platform throughout the world can be problematic from both the technical and the organizational perspectives From the technical point of view, it can cause performance bottlenecks Additionally, it would be hard to manage many procedures and relationships with the other stakeholders Therefore a federated architecture with single governance may be preferable

14. June 15, 2009 GITB Open Meeting, Brussels 14 2. GITB System with External Test Suite Governance

15. June 15, 2009 GITB Open Meeting, Brussels 15 2. GITB System with External Test Suite Governance (Continued) GITB system is implemented at the end of the GITB Project The GITB organization, this time, is only responsible for the maintenance and management of GITB platform not the test suites Test Suite development and maintenance process are open to any organization The GITB organization can charge the Test Suite maintainers for the maintenance cost of the GITB system It can also provide consultancies or education programs on GITB test description languages, and guidelines and methodologies for conformance and interoperability test design The Test Suite developers (the intermediary organizations) can setup their own business model

16. June 15, 2009 GITB Open Meeting, Brussels 16 3. Free Market with an Abstract Testbed Specification

17. June 15, 2009 GITB Open Meeting, Brussels 17 3. Free Market with an Abstract Testbed Specification (Continued) In this model, GITB project only publishes a specification to define  The GITB Test Description Language and its operational semantics  The pluggable module interfaces and  The metadata of the services There is no implementation; only the specification A competitive environment for the organizations and the companies to develop testbeds based on the abstract GITB Specification The group in charge of the GITB Specification can provide consultancy and education to the testbed or test suite implementers

18. June 15, 2009 GITB Open Meeting, Brussels 18 4. Using Existing Testbed Functionality through GITB Test services GITB defines standard Test Service interfaces The GITB defines a metadata standard to be used to describe the GITBTest Services GITB can provide and maintain the registry of Test Services The group in charge of the GITB Specification can provide consultancy and education to the testbed or test suite implementers GITB can charge for the maintenance of the Test Service Registry

19. June 15, 2009 GITB Open Meeting, Brussels 19 Thank you for your attention!