Requirements engineering
Why is this work in the frame?
A frame that forgets how it found something cannot be audited. These are the routes that admitted this work.
Machine scores (provisional)
Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.
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.
- Teacher spread
- 0.244 · how far apart the two teachers sit on this one work
- Validation status
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
Abstract
Better modelling and analysis of problem domains, as opposed to the behaviour of s oflwa re. Development of richer models for capturing and analysing non-functional requirements. Bridging the gap between requirements elicitation approaches based on contextual enquiry and more formal specification and analysis techniques. Better understanding of the impact of software architectural choices on the prioritisation and evolution of requirements. Reuse of requirements models to facilitate the development of system families and the selection of COTS. Multi-disciplinary training for requirements practitioners.
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.
The record
- Venue
- Topic
- Advanced Software Engineering Methodologies
- Field
- Computer Science
- Canadian institutions
- University of TorontoUniversity of New Brunswick
- Funders
- Engineering and Physical Sciences Research Council
- Keywords
- Computer science
- Has abstract in OpenAlex
- yes