A framework for the requirements engineering process development
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
As one of the processes in software engineering, requirements engineering (RE) plays a vital role in ensuring the overall success of the software engineering process. However, many of the substantial problems that the software industry faces today are still the same as the ones discovered during the software engineering crisis 36 years ago. Poor RE practices have been blamed as one of the major reasons contributing to the vicious circle. RE is a discipline emphasizing the implementation of engineering disciplines into the RE process by using various good practices, techniques and methodologies. A sound RE process is the foundation for the overall quality of any software product. Even though numerous process models, good practices, and techniques have been developed which aim at providing necessary support for RE processes, a huge gap still exists between the theory and practices. One of the major reasons contributing to this phenomenon is that there is a lack of suitable tools and/or guidance to support developing the most suitable RE process model and selecting the most suitable RE techniques for a software project. The effective ways have to be found to help fill in the gap. The objectives of this research were, therefore, to investigate a theoretically sound and practically feasible framework which can provide constructive and productive solutions to the problems identified by combining the theories and technologies of advanced software engineering, requirements engineering, knowledge engineering, and decision support. The outcome of this is the A Fbramework for Rbequirements Ebngineering pRbocess dEbvelopment (FRERE), which consists of a requirements engineering knowledge base, methodologies for RE process development and RE techniques selection, RE process assessment models, and a prototype of the FRERE tool. The framework provides constructive methodologies, with the help of the requirements engineering knowledge base and process assessment models, to develop the most suitable RE process model and suitable RE techniques for the given software project. The FRERE tool is a knowledge-based decision support system which can advise the requirements engineers during the development of RE process. The case study conducted during the research has shown the feasibility of the framework.
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.000 | 0.000 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.000 | 0.000 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.000 | 0.000 |
| Open science | 0.001 | 0.000 |
| Research integrity | 0.000 | 0.000 |
| Insufficient payload (model declined to judge) | 0.000 | 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