MétaCan
Menu
Back to cohort
Record W2412429475 · doi:10.1016/s1353-4858(14)70031-5

Bring your own software

2014· article· en· W2412429475 on OpenAlexaboutno aff
Daniëlle van Leeuwen

Bibliographic record

VenueNetwork Security · 2014
Typearticle
Languageen
FieldBusiness, Management and Accounting
TopicBig Data and Business Intelligence
Canadian institutionsnot available
Fundersnot available
KeywordsPopularityBring your own deviceWarrantInternet privacyComputer securitySoftwareComputer scienceAnalyticsTerm (time)Quarter (Canadian coin)BusinessMobile deviceData sciencePolitical scienceWorld Wide WebHistoryLawFinance

Abstract

fetched live from OpenAlex

The term Consumerisation of IT (CoIT) has been buzzing for a while in the IT world. The best-known form of this trend is Bring Your Own Device (BYOD), a term even your mother has probably heard by now. The popularity of BYOD in the UK is not as clear as you might think. The researchers of Strategy Analytics saw a decrease of 15% in BYOD in Western Europe in the first quarter of 2013, compared to the first quarter of 2012. 1 The serious concerns of IT managers in this domain seem to have been heard by the company decision makers . But now that this threat seems to be declining, the next buzzword has made its appearance: Bring Your Own Software (BYOS). Is that also a dangerous trend? And what are the expected advantages of BYOS? The term Consumerisation of IT (CoIT) has been buzzing for a while in the IT world, with Bring Your Own Device (BYOD) its best-known manifestation. Yet even as BYOD seems to be fading as a threat, Bring Your Own Software (BYOS) is raising its head as the next potentially dangerous trend. So what are the expected advantages of BYOS? And do they warrant the possible risks? Daniëlle van Leeuwen of G Data Software explains.

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.002
metaresearch head score (Gemma)0.013
Version: metacan-v3-hybrid-931329e0061cValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Not applicable · Consensus signal: Not applicable
GenreCandidate signal: Methods · Consensus signal: none
Teacher disagreement score0.076
Threshold uncertainty score0.255

Distilled classifier scores by category (both heads)

CategoryCodexGemma
Metaresearch0.0020.013
Meta-epidemiology (narrow)0.0010.000
Meta-epidemiology (broad)0.0000.001
Bibliometrics0.0020.002
Science and technology studies0.0030.003
Scholarly communication0.0080.012
Open science0.0010.006
Research integrity0.0040.004
Insufficient payload (model declined to judge)0.0760.063

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.042
GPT teacher head0.263
Teacher spread0.221 · 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 designNot applicable
Domainnot available
GenreMethods

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

Citations8
Published2014
Admission routes1
Has abstractyes

Explore more

Same venueNetwork SecuritySame topicBig Data and Business IntelligenceFrench-language works237,207