MétaCan
Menu
Back to cohort

Appreciative Methods Applied to the Assessment of Complex Systems

2019· article· en· W2976461980 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

VenueINCOSE International Symposium · 2019
Typearticle
Languageen
FieldDecision Sciences
TopicComplex Systems and Decision Making
Canadian institutionsLockheed Martin (Canada)
Fundersnot available
KeywordsComplex systemComplexity managementSystem of systemsComputer sciencePerspective (graphical)Management scienceSystem of systems engineeringSystems engineeringData scienceSoftware engineeringArtificial intelligenceSystems designEngineeringManagement

Abstract

fetched live from OpenAlex

Abstract Complex systems have characteristics that challenge traditional systems engineering processes and methods. These characteristics have been defined in various ways. INCOSE has previously identified characteristics of complex systems and potential methods to deal with complexity in system development. The purpose of this paper is to provide definitions and describe distinguishing characteristics of complexity using example systems to illustrate approaches to assessing the extent of complexity. The paper applies Appreciative Inquiry to identify and assess complex system characteristics. The characteristics are used to examine several different examples of systems to illuminate areas of complexity. These examples range from seemingly simple systems to complicated systems to complex systems. Different tiers of complexity are identified as a result of the assessment. The paper also identified and introduces topics on managing complexity and the integrating system perspective that represent new directions for the engineering of complex systems. The Appreciative Inquiry approach provides a method for systems engineering practitioners to more readily identify complexity when they encounter it, and to deal more effectively with this complexity once it has been identified.

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.006
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesInsufficient payload (model declined to judge)
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Not applicable · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: none
Teacher disagreement score0.922
Threshold uncertainty score1.000

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0060.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.001
Science and technology studies0.0000.000
Scholarly communication0.0000.000
Open science0.0020.001
Research integrity0.0000.000
Insufficient payload (model declined to judge)0.0010.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.136
GPT teacher head0.487
Teacher spread0.351 · 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