International Workshop on Software Measurement (IWSM'01) 137 Montral, Qubec, Canada -- August 28-29, 2001
Why this work is in the frame
A frame that forgets how it found something cannot be audited. These are the routes that admitted this work.
Bibliographic record
Abstract
This paper describes and illustrates a methodology for identifying the correctness of software functional requirements on the basis of a logic-based dynamic framework. It focuses on the issues related to user and/or system functional requirements; quality attributes, measures and analysis methods, and integrates the core concepts of the Graphical Requirement Analysis (GRA) and COSMIC-FFP techniques:The proposed approach provides a structured procedure for arranging functional software requirements into a graphical framework, thereby providing a means for evaluating their clarity and their presence/absence. Moreover, the architecture of this approach makes it possible to trace specific entities forwards, from system/user requirements to design, and backwards. The way in which the proposed Integrated Measure for Functional Requirements (IMFR) captures critical aspects of functional requirements such as ambiguous or incomplete requirements, incomplete linkages from software requirements to system requirements and to design and/or to test cases is illustrated . Using a sub-system of the Generic Westinghouse Reactor Protection (GWRP) control system case study as an example, we identify and demonstrate various ambiguities of textual software requirements.
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.
Full frame distilled prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.
Codex and Gemma teacher scores by category
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.002 | 0.001 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.000 | 0.001 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.000 | 0.000 |
| Open science | 0.002 | 0.000 |
| Research integrity | 0.000 | 0.000 |
| Insufficient payload (model declined to judge) | 0.001 | 0.000 |
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 it