Last update: 2002-04-18.
The following table provides a trace of all requirements expressed in the ACS Requirements Document [RD01].
A Release column specifies when the described requirement will be implemented.
What follows is the planned set of releases (1 major release every year, with an intermediate minor release):
When only partial functionality if implemented in a release, the release number is put in parenthesis. Some requirements (like 2.3, 3.1.1 and so on) are at the core of the whole ACS and therefore it does not make any sense to specify a release for implementation. In this case the release is marked as Not Applicable (N/A).
|
ACS Architecture |
Release |
|
|
2.3. Reference Architecture |
1.3 |
N/A |
|
3.1.1. Scope. |
1.2 |
N/A |
|
3.1.2. Design. |
1.2, 2.1 |
N/A |
|
3.1.3. Use. |
1.2 |
N/A |
|
3.2.1. Users. |
1.2 |
N/A |
|
3.2.2. Value retrieval. |
3.6.3 |
1.0 |
|
3.2.3. Value setting. |
2.5.11.2 |
0.0 |
|
3.2.4. Local and central operation. |
2.2 |
(0.0) 1.0 |
|
3.2.5. Remote access. |
2.2 |
1.0 |
|
3.3.1. Size. |
4.4 |
0.0 |
|
3.3.2. Serialization. |
3.5.3.1, 3.5.5 |
2.0 |
|
3.3.3. Migration. |
3.5.6 |
2.0 |
|
3.3.4. Simulation. |
3.5.9 |
2.0 |
|
4.1.1. Direct value retrieval. |
3.5.11.1 |
0.0 |
|
4.1.2. Indirect value retrieval. |
3.6.3 |
1.0 |
|
4.1.3. Rate |
3.5.12.2, 3.5.12.3 |
1.0 |
|
4.1.4. Transparency. |
3.6.3 |
1.0 |
|
4.1.5. Values at given time. |
3.5.12.3 |
(0.0) 1.0 |
|
4.1.6. Event and Notification System. |
3.6 |
1.0 |
|
4.1.7. Quality. |
Change request to remove requirement submitted (ALMASW2001080) |
|
|
4.2.1. Configuration Database. |
3.5.3, 3.13.14 |
(0.0) 2.0 |
|
4.2.2. Database design. |
3.5.3.2 |
1.0 |
|
4.3.1. Sampling. |
3.15.4, 3.15.7 |
(1.0) 2.0 |
|
5.1.1. Framework. |
3.18.1 |
2.0 |
|
5.1.2. Procedures. |
3.11.1 |
2.0 |
|
5.1.3. Browser. |
3.11.10 |
1.0 |
|
5.1.4. Analysis tool. |
3.15.5 |
1.0 |
|
5.2.1. Scripts. |
3.17.1, 3.17.2 |
(0.0) 1.0 |
|
5.2.2. Functionality. |
3.17.3 |
0.0 |
|
5.3.1. Time conversion |
3.9.3.1 |
1.0 |
|
5.3.2. Mathematics |
3.19 |
2.0 |
|
5.3.3. Astrometry |
3.10 |
2.0 |
|
6.1.1. Messages |
3.13.3 |
(0.0) 1.0 |
|
6.1.2. Commands. |
3.13.1 |
0.0 |
|
6.1.3. Syntax Check. |
3.13.2 |
2.0 |
|
6.1.4. Validation. |
3.13.2 |
1.0 |
|
6.1.5. Programmatic use. |
3.13.7, 3.13.14 |
(1.0) 2.0 |
|
6.1.6. Command delivery. |
- |
|
|
6.1.7. Mode. |
3.13.3 |
(0.0) 1.0 |
|
6.1.8. Timeout. |
3.13.3 |
(0.0) 1.0 |
|
6.1.9. Intermediate replies. |
- |
|
|
6.2.1. Logging. |
3.8.2, 3.8.4 |
(0.0) 1.0 |
|
6.2.2. Persistency. |
3.8.6 |
2.0 |
|
6.2.3. Filtering. |
3.8.11 |
(0.0) 1.0 |
|
6.3.1. Definition. |
3.7.6 |
N/A |
|
6.3.2. Tracing. |
3.7.3 |
1.0 |
|
6.3.3. Severity. |
3.7.10 |
1.0 |
|
6.3.4. Presentation. |
3.7.8 |
(0.0) 1.0 |
|
6.3.5. Configuration. |
3.7.9 |
2.0 |
|
6.3.6. Scope. |
3.7.2 |
0.0 |
|
6.4.1. Definition. |
3.14 |
N/A |
|
6.4.2. Behavior. |
3.14.4 |
2.0 |
|
6.4.3. Severity. |
3.14.4 |
2.0 |
|
|
3.14.4 |
2.0 |
|
6.4.5. Hierarchy. |
3.14.5 |
2.0 |
|
6.4.6. Alarm logging. |
3.14.3 |
1.0 |
|
6.4.7. Configuration. |
3.14.4 |
2.0 |
|
6.4.8. Binding. |
3.14.6 |
2.0 |
|
7.1 Bulk data transfer |
3.19.1 |
2.0 |
|
7.1.1. Image pipeline |
3.19.1 |
2.0 |
|
7.2.1. FITS format shall be supported. |
3.19 |
2.0 |
|
8.1.1. Standard. |
3.9.2 |
1.0 |
|
8.1.2. API. |
3.9.3.1 |
1.0 |
|
8.1.3. Distributed timing. |
3.9.1 |
1.0 |
|
8.1.4. Services. |
3.9.3.3 |
1.0 |
|
8.1.5. Resolution. |
3.9.5 |
1.0 |
|
9.1. Security. |
4.1 |
1.0 |
|
9.2.1. All human and machine safety |
4.2 |
0.0 |
|
9.2.2. The use of software limits shall be supported |
4.2 |
1.0 |
|
9.3 Reliability |
4.3 |
1.0 |
|
9.4 Performance |
4.4 |
0.0 |
|
10.3.1. RTOS. |
5.1.1 |
0.0 |
|
10.3.2. High level operating system. |
5.1.1 |
0.0 |
|
10.3.3. Compiled Languages. |
2.2, 5.1.1 |
0.0 |
|
10.3.4. IDL. |
3.13.1.2 |
0.0 |
|
10.4.1. CORBA. |
3.13.1 |
0.0 |
|
10.4.2. ORB independence. |
3.5.8 |
0.0 |
|
10.4.3. LAN. |
1.3 |
0.0 |
|
10.4.4. Backbone. |
1.3 |
0.0 |
|
10.4.5. Field-bus. |
1.3 |
0.0 |
|
10.5.3. RTOS |
3.4.2, 5.1.1 |
0.0 |
|
10.5.4. OS |
3.4.2 |
0.0 |
|
10.5.5. Configuration DB |
3.5.3.2 |
(0.0) 1.0 |
|
10.5.6. Scripting language |
2.2, 3.17.4 |
(0.0) 1.0 |
|
10.5.7. Analysis and plotting |
3.15.5 |
1.0 |
|
10.5.8. CORBA ORB |
3.5.8 |
0.0 |
|
10.5.9. Data transfer |
4.4 |
(0.0) 1.0 |
|
10.5.10. The XML format |
3.5.5 |
(0.0) 1.0 |
|
10.5.11. LAN |
1.3 |
0.0 |
|
10.5.12. Field-bus |
1.3, 3.4.1 |
0.0 |
|
11. Life cycle aspects |
5 |
0.0 |
|
11.1.1. Prototyping |
5 |
0.0 |
|
12.1.1. Portability |
3.16.1.2 |
0.0 |
|
12.1.2. Extended portability |
3.16.1.2, 3.16.1.3 |
(0.0) 1.0 |
|
12.1.3. Tools |
3.16.2 |
0.0 |
|
12.1.4. Modularity |
3.16.4 |
0.0 |
|
12.1.5. ACS GUIs |
3.16.3 |
(0.0) 1.0 |
|
12.1.6. Location |
2.2 |
1.0 |
|
12.2.1. Hardware interfaces |
3.4.1 |
(0.0) 1.0 |
|
12.3.1. The ACS shall be integrated and tested |
5.1 |
(0.0) 1.0 |
|
13.1.1. Distributed Objects and Commands. |
2.1, 3.5, 3.5.1.5, 3.13.1 |
0.0 |
|
13.1.2. Standard methods. |
3.5.4 |
2.0 |
|
13.1.3. Groups. |
Change request to remove requirement submitted (ALMASW2001079). |
|
|
13.1.4. Events. |
3.5.12.1 |
(0.0) 1.0 |
|
13.1.5. Configuration. |
5.1 |
1.0 |
|
13.1.6. Modularity. |
5.1 |
1.0 |
|
13.1.7. Portability. |
5.1.1 |
0.0 |
|
14.1.1. Logging of commands |
3.8.3 |
1.0 |
|
14.1.9. Dynamic configuration |
3.5.3.5 |
1.0 |
|
14.1.13. States |
3.5.4 |
2.0 |
Notes:
The following table provides a trace of the requirements on ACS expressed in TICS Design Concept [RD26] into this document.
|
Item in TICS Design Concept[RD26] |
ACS Architecture |
Release |
|
6. Event and Notification System |
3.6 |
1.0 |
|
7. Configuration Database |
3.5.3 |
(0.0) 2.0 |
|
8.1. Scripting |
3.17 |
(1.0) 2.0 |
|
8.3 GUIs |
3.16 |
(0.0) 1.0 |
|
9.3. Time System |
3.9 |
1.0 |
|
10.5.1. Device |
3.5 |
0.0 |
|
11.1. Monitor point collecting |
3.12 |
1.0 |
|
14.1. Logging |
3.8 |
1.0 |
|
14.2. Errors |
3.7 |
1.0 |
|
14.3. Alarms |
3.14 |
(1.0) 2.0 |