MétaCan
Menu
Back to cohort
Record W1935843737 · doi:10.1109/wcre.1999.806968

Reverse engineering legacy interfaces: an interaction-driven approach

2003· article· en· W1935843737 on OpenAlexaff
Eleni Stroulia, Mohammad El‐Ramly, Lanyan Kong, Paul Sorenson, B. Matichuk

Bibliographic record

Venuenot available
Typearticle
Languageen
FieldComputer Science
TopicUsability and User Interface Design
Canadian institutionsUniversity of Alberta
Fundersnot available
KeywordsComputer scienceTask (project management)Interface (matter)Human–computer interactionUser interfaceConstruct (python library)Domain (mathematical analysis)Graphical user interfaceTraverseGraphical user interface testingReverse engineeringUser interface designProgramming languageUser experience designEngineeringOperating systemSystems engineering

Abstract

fetched live from OpenAlex

Legacy systems constitute valuable assets to the organizations that own them. However, due to the development of newer and faster hardware platforms and the invention of novel interface styles, there is a great demand for their migration to new platforms. We present a method for reverse engineering the system interface that consists of two tasks. Based on traces of the users interaction with the system, the "interface mapping" task constructs a "map" of the system interface, in terms of the individual system screens and the transitions between them. The subsequent "task and domain modeling" task uses the interface map and task-specific traces to construct an abstract model of a user's task as an information exchange plan. The task model specifies the screen transition diagram that the user has to traverse in order to accomplish the task in question, and the flow of information that the user exchanges with the system at each screen. This task model is later used as the basis for specifying a new graphical user interface tailored to the task in question.

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 imitation

Not 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.

metaresearch head score (Codex)0.007
metaresearch head score (Gemma)0.020
Version: metacan-v3-hybrid-931329e0061cValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Bench or experimental · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: none
Teacher disagreement score0.007
Threshold uncertainty score0.036

Distilled classifier scores by category (both heads)

CategoryCodexGemma
Metaresearch0.0070.020
Meta-epidemiology (narrow)0.0020.002
Meta-epidemiology (broad)0.0010.003
Bibliometrics0.0030.001
Science and technology studies0.0010.004
Scholarly communication0.0060.006
Open science0.0050.006
Research integrity0.0030.004
Insufficient payload (model declined to judge)0.0030.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.

Opus teacher head0.038
GPT teacher head0.256
Teacher spread0.218 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it

Classification

machine, unvalidated

Machine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.

The models applied no category: nothing in the taxonomy fit this work.
Study designBench or experimental
Domainnot available
GenreEmpirical

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".

Quick stats

Citations40
Published2003
Admission routes1
Has abstractyes

Explore more

Same topicUsability and User Interface DesignFrench-language works237,207