
Gaia
GAIA.ASU.SP.ESM.00007
Issue 2.00
Page 6 of 79
Astrium Ltd owns the copyright of this document which is supplied in confidence and which shall not be used for any purpose other than that for which it is supplied and shall not in
whole or in part be reproduced, copied, or communicated to any person without written permission from the owner.
GAIA.ASU.SP.ESM.00007 (Avionics SCOE Req Iss 2).doc
1 INTRODUCTION AND SCOPE
1.1 Introduction
This document establishes the design, performance, interface and verification requirements for the Avionics
SCOE for the Gaia Project.
The Avionics SCOE is a primary element of a model-based architecture capable of modelling the satellite
mission environment.
Gaia is a scientific mission of the European Space Agency (ESA) which will rely on the proven principles of
the previous Hipparcos mission to create an extraordinarily precise three-dimensional map of about one
billion stars throughout our galaxy and beyond.
Gaia will provide astrometric measurements of all objects to 20 mag, with multicolour multi-epoch
photometry and radial velocities for objects brighter than 16-17 mag. Accuracies are better than 10
microarcsec at 15 mag. The envisaged experimental operations principle is a continuous scanning of the
sky on great-circles with constant inclination to the Sun. Mainly because of the high thermal stability
requirements, the current orbit baseline, a Lissajous orbit around the L2 Libration point in the Earth-sun
system has been selected.
1.2 Scope
The document in hand comprises the contractually relevant technical requirements and constraints for the
Gaia Avionics SCOE. This includes:
• The performance, design and interface requirements.
• The testing and verification requirements.
Requirements within this document are shown in an italic font. Each requirement is preceded by a summary
line that contains:
• The Doors Requirement Number, in the form AVI-xxx/', where xxx is a unique number.
• A link to the upper level user requirements document, in the form 'GSE-SYS-xxx/', where applicable,
or 'CREATED/' if not.
• The Verification Method(s) to be applied for the requirement, using codes as follows: (where more
than one method is listed, all shall apply)
• T - Test
• A - Analysis
• R - Review
• I - Inspection
• S - Similarity
The requirement text follows the summary line. If tables are considered as part of requirement they are
referenced clearly in the text and inserted after and separated from the requirement and are managed as
free text attached to the identifier requirement.
All document elements, which are not presented in the format explained above are not requirements and will
not be verified or tracked.
Kommentare zu diesen Handbüchern