Use of requirements engineering within the Thirty Meter Telescope project
Bibliographic record
Abstract
The Thirty Meter Telescope is comprised of thirty five individual sub-systems which include optical systems, instruments, adaptive optics systems, controls, mechanical systems, supporting software and hardware and the infrastructure required to support their operation. These thirty five sub-systems must operate together as a system to enable the telescope to meet the science cases for which it is being developed. These science cases are formalized and expressed as science requirements by the project's Science Advisory Committee. From these, a top down requirements engineering approach is used within the project to derive consistent operational, architectural and ultimately detailed design requirements for the sub-systems. The various layers of requirements are stored within a DOORS requirements database that also records the links between requirements, requirement rationale and requirement history. This paper describes the development of the design requirements from science cases, the reasons for recording the links between requirements and the benefits that documenting this traceability will yield during the design and verification of the telescope. Examples are given of particular science cases, the resulting operational and engineering requirements on the telescope system and how individual sub-systems will contribute to these being met.
Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.046 | 0.070 |
| Meta-epidemiology (narrow) | 0.002 | 0.002 |
| Meta-epidemiology (broad) | 0.001 | 0.002 |
| Bibliometrics | 0.004 | 0.003 |
| Science and technology studies | 0.002 | 0.004 |
| Scholarly communication | 0.008 | 0.009 |
| Open science | 0.004 | 0.007 |
| Research integrity | 0.002 | 0.004 |
| Insufficient payload (model declined to judge) | 0.004 | 0.002 |
Machine scores (provisional)
The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.
Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".