Документ взят из кэша поисковой машины. Адрес
оригинального документа
: http://www.mso.anu.edu.au/nifs/manuals/man0003.htm
Дата изменения: Fri Sep 7 03:34:22 2001 Дата индексирования: Tue Oct 2 01:50:00 2012 Кодировка: Поисковые слова: п п п п п п п п п п п п п п п п п р п р п р п р п р п |
|
AUSTRALIAN
NATIONAL UNIVERSITY Software Maintenance Manual Created: 23 February 2001 Last modified: 21 March 2001 |
SOFTWARE MAINTENANCE MANUAL
Mark Jarnyk and Peter Young
Research School of Astronomy
and Astrophysics
Institute of Advanced
Studies
Australian National
University
Revision History
Revision No. |
Author & Date |
Approval & Date |
Description |
Revision 1 |
Mark Jarnyk 9 January 2001 |
|
Draft Document Outline. |
Revision 2 |
Peter Young 23 February 2001 |
Peter J. McGregor 8 March 2001 |
Revisions and included DC |
Contents
6 Software Implementation Detail
8 Software Building Instructions
[Note:
in the final document, the table of contents will be to third level]
The Software Maintenance Manual describes the procedures for installation and maintenance of the software for the Gemini Near-infrared Integral Field Spectrograph (NIFS).
Document ID |
Source |
Title |
SPE-I-G0074 |
IGPO |
Programmatic Requirements for Gemini Instrumentation Development |
NIFS-CDR |
RSAA |
NIFS CDR Documentation |
Section 19.4.3 of the document “Programmatic Requirements for Gemini Instrumentation Development” states the requirements for the Software Maintenance Manual.
This manual should describe the software at a sufficient level of detail so that a programmer familiar with the Gemini environment, but not initially familiar with the software, can maintain it properly. It should include:
· Detailed written descriptions of all software systems and sub-systems.
· Systems analyses.
· Data flow diagrams.
· Data dictionaries.
· Structure charts.
· Specifications.
· Listings of all software including firmware (DSP code).
This section will include an identification of the system. It will summarize the purpose and content of the manual, and indicate the intended audience.
A brief description of the intended
uses of the software – what it does.
Identifies the hardware, software,
manual operations, and all other resources needed to perform the actions
described in this manual. This will include things such as:
This section will contain snam
& inam stuff etc.
This section will contain snam
& inam stuff etc.
This section will contain snam
& inam stuff etc.
This section will describe startup
scripts and Tcl/Tk programs for generating the mechanisms lookup tables.
This section will describe the
directory structure and locations of different software components.
This section will describe the
VxWorks build configuration.
This section will describe which
shell variables to change, how to create the NIFS login file, and how to run
applSetup which creates UAE.
This section will describe how to
run make from the top level. This will generate the EPICS databases,
generate the engineering interface, and compile the C support routine, the C++
classes, the SNL code, and the detector DSP code.
This section will describe how to
use pvload files to initialize the EPICS database.
This section will describe the
configuration set and tools available for manipulating it.
This section will describe a set of
test procedures using the engineering interface to verify correct operation.
This section will be a users manual
for the engineering interface.
This section will describe how to
run the system using the CAD/CAR/Apply records.
This section will describe the use
of the Instrument Sequencer control screen which simulate OCS sequence commands
including the OBSERVE command.
This section will describe how to
setup parameters for an observation.
This section will describe how to
directly access the low level EPICS records.