Your Experts in Travel Technology

• Dynamic Travel Components (DTC) is the core development strategy of the ISO group
• Technical and methodical platform where most of ISO’s products are based on
• Enables integration of data and functionalities from external systems into your infrastructure
• Each function is created as individual “service” in Java and it is your decision which function you would like to use and how it should be configured
• 100% browser-based
• Multilingual (UTF-8 / up to 4 Byte)
• Highly scalable
• Designed for multi-user-disposition
• Unified proceeding on technical base
• Reusability of components
• Components as integrated overall solution or as individual/single elements
• Supported usage of the following systems: SAP Netweaver, IBM Websphere, BEA Weblogic, Oracle AS, JBoss

• New software development and system architecture
• Tour operators have the opportunity to select only those modules/services which are really needed (tailor-made configuration according to customer requirements)
• Small and flexible units
• Web-based technology systems
• Focus less on technology but rather on business processes

SOA advantages:

• Split single tasks, functions and processes instead of having to deal with a complex system
• Communicate in a better and easier way with your clients and suppliers by cutting down one entire process into various single processes
• Benefit from flexible changes which can be made faster
• Enhance your service quality

• All applications are 100% browser-based
• Developed for and based on the Web frameworks Tapestry (Version 4.0)
• Compliant with J2EE-Standard
• Unified DTC processing model
• Unified design of entire business logic
• Reusability of business logic due to components generation
• Performance and regression testing in own DTC testing cluster
• Distinct separation of GUI-Design (HTML/CSS) and Logic
• Ensured customization
• Build-up of own GUI component library/infrastructure

Our tool for specification and design: Enterprise Architect

• Our tools for developing processes: Eclipse, Boss

• Tools we use for regression tests:

             Grinder, Selenium HQ, JUnit

• Integration and configuration tools:

             Subversion, ivy, Hudson, Cobertura

• Frameworks and library tools:

             Hibernate, jQuery, tapestry, Logging Services

• Enterprise Architect as key modeling tool
• Usage of all UML 2.1 types of diagram and modeling elements
• Specification and design is stored in the project repository
• Generating of functional specifications, technical design/interface specifications of the project repository
• Designed model is used to create the implementation model
• Basis for code generation
• Support of round-trip-engineering procedure

Testing phases and used tools (extract):

• Unit testing: JUnit: verifies the correctness of individual modules
• Testing of integration: JUnit, Cobertura, Hudson: verifies the correct workflows/ operating principle of interdependent components
• System testing: Selenium, The Grinder, JMeter: verification of the entire system