Identification, specification and measurement, using international standards, of the system non functional requirements allocated to real-time embedded software
Bibliographic record
Abstract
During the system requirements phase, the focus is often on the functional requirements of the system, while non-functional requirements (NFR) are captured by system analysts at a very global level only: in this system analysis phase, these NFR are typically described at the system level and not at the software level. Detailing these NFR is typically left to be handled (i.e., defined at the necessary level of detail) much later by system designers in the system architecture and design phases. As yet, there is no consensus on how to describe and measure the system non-functional requirements (system-NFR); it is therefore challenging to take them into account in software project estimation and software project productivity benchmarking. In the software requirements engineering step, the system-NFR can be detailed and specified as software functional user requirements (software-FUR), to allow a software engineer to develop, test, and configure the final deliverables to the system users. The research project motivation is to contribute to the improvement of the estimation models of software development effort by including the system-NFR in the software estimation process through a quantitative view of such NFR. The goal for this research project is to help project managers, organizations, and researchers to make informed decisions on project planning and software development projects in the early identification, specification, and measurement of the system-NFR for the embedded software. More specifically, this research project aims at contributing to better define, describe, and measure the system-NFR allocated to software-FUR for real time and embedded software. The research objective is the early specification and measurement of software-FUR derived from system-NFR, using as a basis the systems and software engineering standards. To achieve this research objective the following two specific research sub-objectives must be reached: • Designs of standard-based generic models for the identification and specification of software-FUR for system-NFR; • Measurement of the functional size of software-FUR for system-NFR using the COSMIC ISO 19761 standard. The results of this research will be a set of standard-based specification and measurement models for system-NFR for real-time embedded software. The main outcome of this research study is the set of fourteen (14) standard-based models of software-FUR for the early identification, specification, and measurement of system non-functional requirements allocated to software. Keywords: Software Engineering, Non functional requirement (NFR), ECSS, ISO 9126 and IEEE830 International Standards, Software-FUR Measurement, COSMIC – ISO 19761.
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.107 |
| Meta-epidemiology (narrow) | 0.002 | 0.001 |
| Meta-epidemiology (broad) | 0.001 | 0.002 |
| Bibliometrics | 0.015 | 0.011 |
| Science and technology studies | 0.002 | 0.004 |
| Scholarly communication | 0.008 | 0.009 |
| Open science | 0.004 | 0.006 |
| Research integrity | 0.003 | 0.005 |
| Insufficient payload (model declined to judge) | 0.004 | 0.004 |
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".