You are welcome to add requirements related to the astronomical usage of a Future Software Environment on this page. At this moment, they are not sorted in any way so just add yours at the end. Use an ordered list and add your name/date for reference.

---

1. It must be possible to associate uncertainty and unit to any data value. (PrebenGrosbol, 2004-03-09)
2. When operations are done on data, errors and units must be migrated to the result using a standard statistical model. It should be possible to disable this or specify the model. (PrebenGrosbol, 2004-03-09)
3. Besides simple data types (such as integer, real, complex and logical), special astronomical data types should exist such as: celestial coordinates. (PrebenGrosbol, 2004-03-09)
4. The following composit data types must be supported (PrebenGrosbol, 2004-03-09):
   1. Records containing a set of heterogeneous data items
   2. Tables consisting of collections of similar records
   3. Matrixes in the mathematical sense
   4. Maps which are representations of one or more dimensional functions sampled at equidistant intervals
5. It must be possible to import and export data in FITS and VOTable formats. (PrebenGrosbol, 2004-03-09)

to top