sit a common use integration processes cuss 12

8/3/2019 Sit a Common Use Integration Processes CUSS 12

1/15

SITA CUSS Integration Process Document


2/15

Status: Version 1.2

File: SITACommonUseIntegrationProcesses_CUSS_1.2.doc

Format: MS Word 2000

Date: Friday, April 02, 2010

Control Level: SITA ADS Non - Confidential

Certified by: Certification

2010 SITA All Rights Reserved

The information contained herein is the property of SITA.

WARNING: This document may contain information proprietary to SITA Group and shall not be distributed

outside the company or its business operations, unless duly authorized.

SITAs Application Services

Business Unit Integration

Process for

Applications Running on

CUSS Platform

Certification Group


3/15

SITA CUSS Integration Process Document Version 1.2

Copyright SITA 2010 Page - 1 -

Revision Table

Revision Date Change Dept.

1.2 2-Apr-10 Updated remote cert inclusion cert


4/15



Acronyms, Abbreviations, & Terminology

SITA Socit Internationale De Tlcommunications

Aronautiques

Airline Telecommunications and Information Services

IATA International Air Transport Association Airline

Tlcommunications and Information Services

ASBU Application Services Business Unit

SIG System Integration Group of SITA ASBU

TFS Technical Field Support group of SITA ASBU

SITA CUSS Common Use Self Service platform designed to optimize

airport terminal utilization and improve services.

PDR Product Deficiency Report

RFA Request For Action

Alpha Test First (major) Test Phase of Certification Process (conducted

at SITA in Bohemia, New York)

Beta Test On-site (airport) trial run test phase following a successful

Alpha test


5/15



Table of Contents1. Overview........................................................................................................................................ 4

1.1. Purpose and Scope of the CUSS Integration Process........................................................... ......... 42. Requirements for CUSS Integration ........................................................................................... 5

2.1. Applications that require Integration and Testing................................................................ ........ 5

2.2. Business Logic only changes to Applications ............................................................. ................... 5

2.3. Posting Applications to SITA CCG ......................................................... ....................................... 6

3. The CUSS Integration Process ................................................................................................... 7

3.1. Process Overview ........................................................ ................................................................. ..... 7

3.2. Pre-testing ............................................................ ................................................................ ............... 8

3.3. Alpha Testing ................................................................ ................................................................. .... 9

3.4. Beta Testing ........................................................ ................................................................. ............. 103.5. Release of the Application ............................................................... ............................................... 11

3.6. Follow-up and Feedback.................................................................. ............................................... 12

4. Application Integration Request Form..................................................................................... 13

4.1. WEB Site............................................................... ................................................................ ............. 13

List of IllustrationsFigure 3-1 Overview of the entire certification process ............................................................7Figure 3-2 The Alpha Testing Process.......................................................................................9

Figure 3-3 The Beta Testing Process .......................................................................................10

Figure 3-4 The pre-release decision process............................................................................11

Figure 3-5 The Release Process...............................................................................................11


6/15



1. Overview

1.1. Purpose and Scope of the CUSS Integration Process

This document is intended to serve as a guide to SITA customers for the submission of

applications for integration for use in SITA CUSS, and to provide an overview of the steps

involved in the entire process from beginning to end.

The Certification Group has the goal of ensuring that customer applications that are to be run

on the SITA CUSS platform:

Conform to IATA CUSS Standards,

Operate properly on the SITA CUSS platform and Does not adversely affect either the stability of the platform or other customers ability

to utilize the system subsequent to the applications operations.

In addition, the Certification Group documents the installation and packages the application

for use by our Installation, Field Support and Site Administration staff around the world.

Comprehensive test specifications are used and test results are reported and tracked in a

dedicated database.


7/15



2. Requirements for CUSS Integration

2.1. Applications that require Integration and Testing

All applications that meet one or more of the below conditions require full integration:1. The application is new (has not been fully integrated onto the CUSS platform before).

2. The Integrated application will be supporting additional hardware and functionality (1dbc

vs 2dbc).

All application changes, regardless of status, will be packaged and tested to assure viability

on the SITA CUSS platform.

Integrations will be performed in the SITA CCG lab, in Bohemia, New York where suitable

certification test systems and support personnel are available.

Where possible SITA will perform application integration without the active participation of

the airline. When this is not feasible, SITA CCG will inform the customer of the options

available to complete integration.

Remote testing is made available in cases where the application has successfully passed

previous platform integration. In this mode the integration will take place in the CCG lab

with remote participation from the airline and as needed the developer. The integration

engineer will execute tests, with guidance and active participation of the customer via remote

connection.

In some cases with new applications or cases where integration was problematic, and in an

effort to increase reliability of deployment for the customer, remote integration may not be

seen as viable. The determination of suitability of remote testing will be made at time of

scheduling, and the customer so informed.

The customer will always have the option of requesting participation in testing on site in the

New York CCG labs.

2.2. Business Logic only changes to Applications

Applications that have only business logic changes and have been integrated onto the SITA

CUSS platform shall be packaged and validated at the central certification premises in New

York. This validation shall not include testing of the validity of the business logic changes,

but rather that the applications basic functionality is not adversely affected by the changes.

An application that meets all of the following conditions can be included within the database

guidelines and will not require a full certification:


8/15



The application is already integrated.

The update does not support new functionality or devices

The update is restricted to changes to: Business logic, screen enhancements

2.3. Posting Applications to SITA CCG

The customer will post the application files directly to ftp://205.232.222.23.

FQN: FTP.ADS.SITA.AERO

CCG will execute integration and will then release the updated application to SITA

Operations for distribution to all requested sites.


9/15



3. The CUSS Integration Process

3.1. Process Overview

The figure below provides a general overview of the steps that comprise the entire process forintegration of applications onto the SITA CUSS Platform. In the Pre-testing stage the

customer or customer account representative will submit a completed CUSS Request form

(see Appendix) to the SITA Certification Group. The Certification Group personnel will

review the form and then determine if all required information has been submitted. If there is

a need for more information or clarification, the customer and/or customer account

representative will be contacted and queried on such. The process then proceeds to a

Scheduling and Costing sub-phase in which the SITA Certification Group will review all

contractual and pricing issues. Details on this (and subsequent) phase(s) follow below.

When Pre-testing is completed, the application will move to the Alpha test phase at the SITAcentral Certification lab in Bohemia, New York. Following a successful Alpha, the

application will proceed to Beta, and upon a successful Beta, a final Global Release will be

issued.

Figure 3-1 Overview of the entire certification process


10/15



3.2. Pre-testing

The integration process begins when the customer has determined that they would like to

submit their application to the SITA Certification Group for testing and integration. The

following sequence of events comprises the Pre-Testing phase:

1. The customer submits a CUSS Request Form online at

https://se.ads.sita.aero/certification.

2. The SITA Certification Group will review the request and schedule a Test Slot for the

customer's application.

3. Within five business days following submission of the request online, the customer and/or

the customers Account Representative will be informed of the scheduled date of

certification, assigned an Integration Engineer, cost for certification and will receive a

Network Request Option form for connectivity to the Certification lab.

4. After obtaining agreement from the customer on the price and schedule, the SITACertification Group will perform the Integration on the customer's application, according

to the agreed-upon schedule and cost.


11/15



3.3. Alpha Testing

Figure 3-2 the Alpha Testing Process

The customer will deliver the application and all associated items (all software,

documentation, etc.) to SITAs Certification Group two weeks prior to the onset of the Alpha

Test Slot that had been scheduled in the Pre-test phase. The SITA Certification Group will

then make all appropriate and necessary accommodations in the CUSS Integration test lab for

testing to occur. As illustrated in Figure 3-3 above, the Alpha test then commences.

Note: In the event that additional work is realized during performance of the

agreed services, SITA Certification Management will contact the customer

and/or the customers Account Representative for expanding the scope of therequest. Any additional work will be accommodated by extension of the

original agreed timeframe only if the resources are available for the unplanned

extension. It is possible that additional work would have to be scheduled for a

later date.


12/15



3.4. Beta Testing

Figure 3-3 The Beta Testing Process

The following sequences of events comprise the Beta test phase:

Beta Preparation:

The Integration Engineer, upon successful completion of Alpha testing, will package

the application and documentation for release to the Beta site.

Tracking the Beta:

The local staff at the airport and or Beta site will conduct the Beta test of the

application.

The local staff will report to the operations support team and the Integration Engineer

when any bugs are found, and upon completion of the Beta test period.

Beta Conclusion:

At the conclusion of the Beta phase, the operations support team and Integration

Engineer tracking the product will review Beta status and proceed to the next phase.


13/15



3.5. Release of the Application

Figure 3-4 The pre-release decision process

Based on the results of the Beta test, a "Decision" is undertaken, as described in Figure 3-5

above. Next, the analysis and decision depicted in Figure 3-6 below is implemented. Upon

completion of the integration work (after Beta but before the Release/Rejection), the SITA

Certification Group will inform the customer and/or the customers Account Representative

of the results. The customer will either approve the application for Global Release or take

other appropriate action in cases of rejection. The customer will be billed for the work

performed by the SITA Certification Group.

Figure 3-5 The Release Process


14/15



3.6. Follow-up and Feedback

Upon Global Release the CUSS Integration Process is concluded. The Application is

transferred to SITA Operations for distribution and support.

Any questions on a beta or globally released applications should be sent [email protected].


15/15



4. Application Integration Request Form

4.1. WEB Site

The CUSS Request Form can be located at:

https://se.ads.sita.aero/certification

sit a common use integration processes cuss 12

Documents