User interface requirements engineering: a scenario-based framework
Bibliographic record
Abstract
Effective user interface is an important component to the success of an interactive system as any of the components that manage the underlying functionality of the system. The development of an effective user interfaces highly depends on the quality of the requirements where the end-user should be actively involved. Therefore, there is a need to accurately capture, interpret, and represent the voice of the end-user when specifying the user interface requirements. The objective of the thesis is to advance the state of the art in bridging the gap between specifying the User Interface Requirements for interactive systems on the one hand and the design and development of it on the other hand. Towards this objective, a software framework called SUCRE (acronym for Scenario and Use-Case based Requirements Engineering) was developed as a part of this thesis work. Use Case Maps (UCMs) that were introduced in the literature were examined and have been enriched with new visual notation for modeling and specifying the user interface requirements. This enriched UCM for User Interface (UCM-UI) model formed a basis for SUCRE. Thus, scenarios and use cases are used as a means to represent the user interface requirements and communicate with end-users. In addition, the thesis explores two other objectives, namely validation of user interface requirements and usability prediction of the intended user interface. SUCRE was used to build operators that validate the consistency, completeness, and precision of the UCM-UI model using heuristics for constructing a formal analysis of the requirements. SUCRE was also used to define a metrics suite to predict usability from scenarios and use cases. This metrics suite includes simple structural measures as well as content-sensitive and task-sensitive metrics. Considering the difficulties in the specification and design of user interfaces, the thesis aimed also to identify the need for a mix of both informal and formal representation in specifying user interface requirements. Therefore, SUCRE was successfully used to bridge the gap between the semi-formal requirement UCM-UI and detailed formal requirements such as UML, LOTOS specifications, and XML.
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.014 | 0.015 |
| Meta-epidemiology (narrow) | 0.003 | 0.002 |
| Meta-epidemiology (broad) | 0.001 | 0.004 |
| Bibliometrics | 0.007 | 0.005 |
| Science and technology studies | 0.002 | 0.004 |
| Scholarly communication | 0.008 | 0.009 |
| Open science | 0.006 | 0.004 |
| Research integrity | 0.004 | 0.004 |
| Insufficient payload (model declined to judge) | 0.005 | 0.002 |
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".