Lessons learnt from five years of experience in ERP requirements engineering
Bibliographic record
Abstract
Generic off-the-shelf requirements engineering (RE) processes have been packaged by enterprise resource planning (ERP) vendors since 1997, and adopted by client organizations as the key strategy for getting the business requirements and the conceptual design for their complex solutions. We summarize one company's five years of experience in making a generic ERP RE model a live process. It rests on previously published ERP RE process assessment results and reports on what we learnt with particular focus on typical issues organizations face when adopting a standard model and solutions that can be used to avoid those issues in the future. Each of our lessons is described together with a RE practice, technical foundation for the practice and engineering techniques for the RE practitioner. The lessons were used to refine our corporate documentation model, a process-focused and template-based ERP-architecture 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.
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.013 | 0.025 |
| Meta-epidemiology (narrow) | 0.001 | 0.001 |
| Meta-epidemiology (broad) | 0.001 | 0.001 |
| Bibliometrics | 0.002 | 0.002 |
| Science and technology studies | 0.003 | 0.003 |
| Scholarly communication | 0.005 | 0.010 |
| Open science | 0.002 | 0.005 |
| Research integrity | 0.002 | 0.004 |
| Insufficient payload (model declined to judge) | 0.003 | 0.001 |
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".