MétaCan
Menu
Back to cohort
Record W2536554064 · doi:10.1109/mere.2008.5

Requirements in Conflict: Player vs. Designer vs. Cheater

2008· article· en· W2536554064 on OpenAlexaff
David Callele, Eric Neufeld, Kevin A. Schneider

Bibliographic record

Venuenot available
Typearticle
Languageen
FieldComputer Science
TopicAdvanced Malware Detection Techniques
Canadian institutionsUniversity of Saskatchewan
Fundersnot available
KeywordsNegotiationComputer scienceRequirements engineeringStakeholderSecurity engineeringRequirements analysisProcess (computing)Domain (mathematical analysis)Context (archaeology)Requirements elicitationComputer securitySecurity serviceSoftware security assuranceInformation securityPublic relations

Abstract

fetched live from OpenAlex

There are significant interactions between video game stakeholder emotional requirements and security requirements. Counter-intuitively, some traditional security requirements are not necessarily met by the game implementation some forms of security breaches are condoned by the stakeholders (if not actually demanded by them) and the requirements engineering process must support these contradictions. We present an overview of security requirements for video games and show how stakeholder diversity introduces significant complexities to the requirements negotiation process. Our analysis of certain security threats, and their emotional motivations, shows that these motivations form an important element of the emotional requirements and that significant context is necessary for properly capturing the emotional requirements related to security. Finally, we show how emotional requirements can be used to guide security goal development for this domain and propose the use of in-game justice systems to allow players to address security violations in realtime.

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.011
metaresearch head score (Gemma)0.040
Version: metacan-v3-hybrid-931329e0061cValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Theoretical or conceptual · Consensus signal: Theoretical or conceptual
GenreCandidate signal: Empirical · Consensus signal: none
Teacher disagreement score0.011
Threshold uncertainty score0.059

Distilled classifier scores by category (both heads)

CategoryCodexGemma
Metaresearch0.0110.040
Meta-epidemiology (narrow)0.0010.001
Meta-epidemiology (broad)0.0010.001
Bibliometrics0.0010.000
Science and technology studies0.0030.005
Scholarly communication0.0080.007
Open science0.0010.005
Research integrity0.0020.003
Insufficient payload (model declined to judge)0.0060.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.

Opus teacher head0.051
GPT teacher head0.285
Teacher spread0.234 · 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 designTheoretical or conceptual
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

Citations5
Published2008
Admission routes1
Has abstractyes

Explore more

Same topicAdvanced Malware Detection TechniquesFrench-language works237,207