1 INTRODUCTION

1.1 PURPOSE

The purpose of this document is to specify requirements and to give guidelines for the development of VLT Application Software. In particular it gives guidelines on how to use the Central Control Software for applications on the workstation and the LCU Common Software for LCU applications.

This document is intended to be a practical guide for both ESO and external people developing VLT software.

1.2 SCOPE

The requirements section is applicable to the development of all VLT software, while the guidelines are intended to guide through the development of an application.

1.3 APPLICABLE DOCUMENTS

The following documents, of the exact issue shown, form a part of this document to the extent specified herein. In the event of conflict between the documents referenced herein and the contents of this document, the contents of this document shall be considered as a superseding requirement.

[1] VLT-MAN-ESO-17210-0619, 1.9 --- VLT Central Control Software User Manual

[2] VLT-MAN-SBI-17210-0001, 3.5 --- LCU Common Software User Manual

[3] VLT-MAN-ESO-17210-0707, 1.6 --- CCS On Line Database Loader User Manual

[4] VLT-MAN-ESO-17210-0375, 2.2--- Driver Development Guide

[5] VLT-SPE-ESO-10000-0228, 1.0 --- VLT Software Programming Standards

[6] VLT-MAN-ESO-17210-0770, 1.7 --- Extended CCS User Manual

[7] VLT-MAN-ESO-17210-0771, 1.7 --- CCS Event Toolkit User Manual

[8] VLT-MAN-ESO-17210-0855, 3.0 -- VLT Software Environments Common Configuration User Manual

[9] VLT-MAN-ESO-17210-2252, 1.0 -- LCU Server Framework User Manual

1.4 REFERENCE DOCUMENTS

The following documents are referenced in this document.

[10] VLT-SPE_ESO-10000-0015, 3 --- Electronic Design Specification

[11] VLT-TRE-ESO-00000-0001, 3 --- VLT Maintenance Concept

[12] VLT-SPE-ESO-10000-0011, 2.0 --- VLT Software Requirements Specification

[13] VLT-SPE-ESO-17230-0001, 1.0 --- HOS Functional Specification

[14] VLT-MAN-ESO-17210-0642, 1.11 --- VLT Common Software - Installation Manual

[15] VLT-SPE-ESO-11720-0001, 1.1 --- Telescope Control System Functional Specification

[16] VLT-SPE-ESO-10000-0013, 4--- Service Connection Point Technical Specification

[17] VLT-LIS-ESO-10000-0551, 3.2 --- List of Service Connection Points

[18] VLT-MAN-ESO-17200-0888, 1.0 --- VLT Common Software - Overview

[19] VLT-MAN-ESO-17200-0981, 3.0 --- VLT Software Problem Report/ Change Request

[20] VLT-MAN-ESO-17300-473, 2 --- VLT TRS Time Interface Module Technical Manual

[21] J.Rumbaugh et al., Prentice Hall, 1991 --- Object-Oriented Modelling and Design

[22] G.Booch, Benjamin Cummings Pub., 1994 --- Object Oriented Analysis and Design with Applications

[23] ANSI X3J16/95-0087, 1995 --- Working Paper for Draft Proposed International Standard for Information Systems, Programming Language C++

[24] VLT-VER-ESO-17230-0893, 1.0 --- TCS Tracking WS Modular Test Plan

[25] VLT-VER-ESO-17230-0894, 1.0 --- TCS Tracking WS Modular Test Report

[26] VLT-MAN-ESO-17200-0908, 1.3 --- Tools for Automated Testing User Manual

[27] ARC-SPE-ESO-00000-0001, 1.3 --- ESO Archive Data Interface Requirements.

[28] GEN-SPE-ESO-00000-794, 1.1 --- ESO Data Interface Control Document.

1.5 ABBREVIATIONS AND ACRONYMS

The following abbreviations and acronyms are used in this document:

CCS Central Control Software

CDT Command Definition Table

CI Command Interpreter

CIT Command Interpreter Table

FDDI Fiber Distributed Data Interface

DBMS Database Management System

HOS High Level Operating Software

HW Hardware

I/O Input/Output

LAN Local Area Network

LCC LCU Common Software

LCU Local Control Unit

LRU Line Replaceable Unit

N/A Not Applicable

TBC To Be Confirmed

SCCP Software Configuration Control Plan

SRS Software Requirements Specification

SW Software

TBD To Be Defined

TCS Telescope Control Software

UIF (Portable) User Interface (Toolkit)

VLT Very Large Telescope

WS Workstation

1.6 GLOSSARY

Environment is defined in section 4.13.3.

(VLT software) Module, as defined in the VLT Software Requirements Specification [12]

A major subdivision of a package software. Examples are the software for the LCU of a subsystem or instrument, the on-line database software, the user interface toolkit.

(VLT software) Package, as defined in the VLT Software Requirements Specification [12]

One of the major functional software packages of the VLT software, for which requirements are specified in the VLT Software Requirements Specification. These are:

Telescope Control Software, Instrument Software, Remote Operations Software, High Level Operations Software and Central Control Software.

Software Device

A Message System based application performing a well defined task. It can be an application controlling some hardware functional unit, but can also be a pure software device, e.g. coordinating other software devices or performing some general service.

Simulation - Hardware Simulation, as defined in the VLT Software Requirements Specification [12]

The software of various modules, including subsystems and instruments is required to have simulation modes. By this is meant that the software can work without any real hardware connected and nevertheless appears as if it were executing commands. Simulation can also be applied to individual control functions, in case some hardware is missing.

Simulation - Software Simulation, as defined in the VLT Software Requirements Specification [12]

It can also be that some of the software has to be simulated, as for example it cannot be used at the moment, e.g. preparations of observations off-line. In this case commands to the simulated software cannot be sent, but get nevertheless a realistic reply. The syntax and parameters are checked but independently of the existence of the destination software.

Subsystem, as defined in the TCS Functional Specification[15]

A subsystem is made up of:

a. The equipment to be controlled

b. LCU(-s) (usually one, but in some cases more than one) with LCU Common Software

c. Subsystem specific application software in the LCU(-s)

d. Possibly also subsystem specific application software outside the subsystem LCU

1.7 STYLISTIC CONVENTIONS

The following styles are used:

bold
in the text, for commands, file names, pre/suffixes as they have to be typed.

italic
in the text, for parts that have to be substituted with the real content before typing.

teletype
for examples.

<name>
in the examples, for parts that have to be substituted with the real content before typing.

bold and italic are also used to highlight words.

1.8 Problem Reporting / Change Request

The form described in [19] shall be used.

Quadralay Corporation http://www.webworks.com Voice: (512) 719-3399 Fax: (512) 719-3606 sales@webworks.com