MétaCan
Menu
Back to cohort
Record W2600652449 · doi:10.1145/3083726

The Role Clarity Framework to Improve Requirements Gathering

2017· article· en· W2600652449 on OpenAlex

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.

affAt least one author lists a Canadian institution in the pinned OpenAlex snapshot.

Bibliographic record

VenueACM Transactions on Management Information Systems · 2017
Typearticle
Languageen
FieldComputer Science
TopicAdvanced Software Engineering Methodologies
Canadian institutionsUniversity of British Columbia
Fundersnot available
KeywordsCLARITYComputer scienceProcess managementTask (project management)Requirements analysisOrder (exchange)Knowledge managementWork (physics)Business requirementsRequirements elicitationBusiness processBusinessEngineeringSystems engineeringOperations managementWork in process

Abstract

fetched live from OpenAlex

Incorrect and incomplete requirements have been reported as two of the top reasons for information systems (IS) project failures. In order to address these concerns, several IS analysis and design studies have focused on understanding the business needs and organizational factors prior to specifying the requirements. In this research, we add to the existing incremental solutions, such as the work system method and goal-oriented requirements engineering, by proposing the Role Clarity Framework drawn from the theories of “role dynamics” and “goal setting and task performance” in organization studies. The Role Clarity Framework consists of three main concepts related to any organizational role: expectations, activities, and consequences. Based on the interactions among different roles, this framework demonstrates how the business goals and activities of each role, as played out by IS users, are formed and/or changed in the organization. Finally, the Role Clarity Framework helps IS analysts to improve their communication with users and anticipate changes in their requirements, thus improving the gathering of requirements for IS design.

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 imitation

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

metaresearch head score (Codex)0.001
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesScience and technology studies, Scholarly communication
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Other design · Consensus signal: none
GenreCandidate signal: Methods · Consensus signal: Methods
Teacher disagreement score0.758
Threshold uncertainty score1.000

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0010.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.000
Science and technology studies0.0010.000
Scholarly communication0.0010.003
Open science0.0020.000
Research integrity0.0000.000
Insufficient payload (model declined to judge)0.0000.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.

Opus teacher head0.037
GPT teacher head0.308
Teacher spread0.271 · 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