Document Fragment View
Fragment Information
Showing contexts for: Software Source code in In Re: Airports Authority Of India vs Unknown on 15 December, 2004Matching Fragments
3. In the case of software maintenance support, on detecting any fault, the applicant has to fill a site anomaly form and send the same to RC with crash data and system sub-data. The applicant is also to collect and supply additional failure data as and when requested by RC. On verification by RC's facilities outside India, if it is noticed that the SAR does not impact the automation system (no change in the software is required), RC would provide explanation for the anomaly and its resolution either by phone or fax or e-mail. But, if SAR impacts the automation service (requires change in the software), the System Trouble Report (STR) will be generated and accordingly changes will be made in various modules (each such change is referred to as STR fix). Various STR fixes will be combined to form a software build which, after due verification, will be sent to Delhi or Mumbai by RC's facilities along with a version description document, executive software DAT Tape and source code DAT Tape. RC software engineers will visit site for a total period of 10 days (5 days at New Delhi and 5 days at Mumbai) for verification of the fixes/software build (which will not exceed 3). After testing the same on a simulator and downloading it on to the operational system, it will be monitored for 48 hours.