• Stars
    star
    101
  • Rank 338,166 (Top 7 %)
  • Language
  • Created over 4 years ago
  • Updated about 2 years ago

Reviews

There are no reviews yet. Be the first to send feedback to the community and the maintainers!

Repository Details

Cognitive Systems Engineering

This page lists resesarch papers in the field of cognitive systems engineering.

Many cognitive engineering researchers went on to do work in the field of resilience engineering. See http://resiliencepapers.club for resilience engineering papers.

Some papers have a (TWRR) link next to them. This stands for Thai Wood's Resilience Roundup. Thai publishes a newsletter that summarizes resilience engineering papers.

Definitions

Joint cognitive system

A cognitive system produces "intelligent action", that is, its behavior is goal oriented, based on symbol manipulation and uses knowledge of the world (heuristic knowlege) for guidance. Furthermore, a cognitive system is adaptive and able to view a problem in more than one way. A cognitive sytem operates using knowledge about itself and its environment, in the sense that it is able to plan and modify its actions on the basis of that knowledge. It is thus not only data driven, but also concept driven. Man is obviously a cognitive system. Machines are potentially if not actually, cognitive systems. A [Man-Machine System] regarded as a whole is definitely a cognitive system.

The revised definition of a cognitive system is a system that can modify its behavior on the basis of experience so as to achieve specific anti-entropic ends.

Hollangel, Roth, and I were looking at a new kind of system―an emergent system that rises in the interactions among (1) the demands the world imposes on cognitive work, (2) the interplay of multiple agents who do cognitive work (joint and distributed cognition), and (3) the properties of the artifacts, reprsentations, and tools that enable cognitive work.

Cognitive systems engineering

The central tenet of CSE is that a [Man-Machine System] needs to be conceived, designed, analyzed and evaluated in terms of a cognitive system.

We define cognitive systems engineering as the effort to support the cognitive requirements of work.

The core ideas of Cognitive Systems Engineering shift the question from overcoming limits to supporting adaptability and control. The base unit of analysis is the Joint Cognitive System, not people versus technology; and the key process to study, model and support is how people cope with complexity.

Though it was never written down in this way, I still maintain today that the core of an effective cognitive systems engineer is the ability to design problems that challenge the boundaries of plans, procedures, and technologies. And the inverse holds as well. All plans, procedures, and technologies have bounds; these are hard to find and they move around over time; plus designers ovestestaimte the range of situations the artifacts they create can handle.

Videos

Lectures on the study of cognitive work by R.I. Cook. (My notes are at https://github.com/lorin/cook-lectures-notes)

Publications

Case studies

These papers are case studies referenced in Joint Cognitive Systems: Patterns in Cognitive Systems Engineering.

Being Bumpable

Domain: Medical (hospital intensive care unit)

Artifact: the bed book

Voice Loops as Coordination Aids in Space Shuttle Mission Control

Domain: space (mission control)

Artifact: voice loops

How a Cockpit Remembers its Speeds

Domain: aviation (cockpit)

Artifact: speed bugs

Concepts

Questions operators ask about systems

From Joint Cognitive Systems: Patterns of Cognitive Systems Engineering by Woods and Hollnagel (p119)

  • What is it doing now?
  • What will it do next?
  • How did it get into this mode?
  • Why did it do this?
  • Stop interrupting me while I am busy.
  • I know there is some way to get it to do what I want.
  • How do I stop this machine from doing this?
  • Unless you stare at it, changes can creep in.

Info we can get from stories

From Working Minds by Crandall, Klein, and Hoffman, p70

  • The cues and patterns that experts perceive
  • The rules of thumbs they have devised
  • The kinds of decisions they have to make
  • The features that make decisions tough
  • The features that make cases typical
  • The features of rare cases

Levels of Supervisory Control

From To Intervene or not to Intervene: The Dilemma of Management by Exception by Dekker and Woods:

The subordinate:

  1. offers no assistance: human supervisor must do it all;
  2. offers a complete set of action alternatives, and
  3. narrows the selectiond own to a few, or
  4. suggests one, or
  5. executes the suggestion if the supervisor approves, or
  6. allows the supervisor a restricted time to veto before automatic excecution, or
  7. executes automatically, then necessarily informs the supervisor, or
  8. informs them after execution only if they ask, or
  9. informs them after execution if the subordinate decides to
  10. decides everything and acts autonomously, ignoring the supervisor.

Other resources

Journals

People

  • Lisanne Bainbridge
  • Jeffrey M. Bradshaw
  • Matthieu Branlat
  • Beth Crandall
  • Steven Deal
  • Sidney Dekker
  • Cynthia Dominguez
  • Robert Eggleston
  • Paul Feltovich
  • Kenneth Ford
  • L.P. Goodstein
  • Marisa R. Grayson
  • Robert R. Hoffman
  • Erik Hollnagel
  • Edwin Hutchins
  • Matthew Johnson
  • Devorah Klein
  • Gary Klein
  • Morton Lind
  • Gavan Lintern
  • Laura Maguire
  • Laura Militello
  • Brian Moon
  • Donald Norman
  • Annelise Mark Pejtersen
  • Jens Rasmussen
  • Karol Ross
  • Emilie Roth
  • Nadine B. Sarter
  • Robert Sorkin
  • Kim Vicente
  • Sterling Wiggins
  • David D. Woods

Terms

  • attention
  • basic compact
  • bumpy transfer of control
  • clumsy automation
  • cognitive task analysis
  • cognitive work analysis
  • common ground
  • complexity
  • critical decision method
  • coordination
  • decision-centered design
  • demands
  • ecological design
  • directability
  • interpredictability
  • joint cognitive systems
  • macrocognition
  • naturalistic decision making
  • work-centered design
  • workload

More Repositories

1

resilience-engineering

Resilience engineering papers
2,803
star
2

ansible-quickref

Quick reference for Ansible variables
964
star
3

ansiblebook

Code samples from the book "Ansible: Up and Running"
Python
324
star
4

awesome-limits

Examples of OS / system limits
250
star
5

systems-reading

Systems and failure reading list
180
star
6

devstack-vm

Boot a VM and auto-install devstack
Python
80
star
7

messiness

Messiness reading list
55
star
8

availability-reading

High availability reading list
49
star
9

res-eng-short-course-notes

Notes on David Woods's Resilience Engineering short course
39
star
10

dns-alloy

Modeling DNS with Alloy
36
star
11

tla-linearizability

Reading the linearizability paper with TLA+
TLA
31
star
12

openstack-hackspace

Exercises for OpenStack Hackspace at USENIX LISA '13
30
star
13

systems-thinking

Overview of different schools of systems thinking
29
star
14

ansible-docker-connection

Docker connection plugin for Ansible
Python
26
star
15

engineering-reading

Engineering reading list
21
star
16

cheat-sheets

Ruby
20
star
17

major-incidents

A sample of major outages and incidents
18
star
18

epidemic-register

Beating the CAP theorem with the epidemic register
TLA
16
star
19

booknotes

Notes about books I've read
16
star
20

alb-alloy

Modeling AWS application load balancers using Alloy
13
star
21

tla-boat

9
star
22

image-guide

Guide to creating VM images
7
star
23

ansible-resources

User contributed modules, playbooks, scripts, and articles
6
star
24

mezzanine-example

Python
5
star
25

raft-pluscal

TLA
4
star
26

vim.ftplugin

FoldingText plugin for vim bindings
JavaScript
4
star
27

ansible-mezzanine

Python
4
star
28

try-except-c

Playing with setjmp/longjmp
C
4
star
29

alloy-consistency

Modeling eventual consistency with Alloy
Alloy
4
star
30

sheetdown

Google Sheets β†’ Markdown
Clojure
3
star
31

tla-tortoise-hare

TLA
3
star
32

mezzanine-paas

Deploy Mezzanine on PaaS platforms
JavaScript
3
star
33

cook-lectures-notes

Notes on Dr. Richard Cook's lectures on the study of cognitive work
3
star
34

tla-prophecy

Applying Prophecy variables in TLA+ to the Herlihy & Wing paper
TLA
3
star
35

mysetup

Personal config stuff
3
star
36

big-ideas

Big ideas that have influenced me
3
star
37

code-reviews

Guidance on doing code reviews
3
star
38

paxos-poec

Paxos modeled in Alloy using Burckhardt's approach
Alloy
3
star
39

eng-qua-eng

Engineering as described by engineers
2
star
40

shelllogger

Automatically exported from code.google.com/p/shelllogger
Python
2
star
41

failure-mode-bestiary

A collection of failure modes observed in software systems
2
star
42

alloy-consistency-models

Reading "A Framework for Transactional Consistency Models with Atomic Visibility" with alloy
Alloy
2
star
43

camp-devops-talk

1
star
44

roamjs-daily-zettles

A RoamJS plugin to show zettles each day
TypeScript
1
star
45

ipython-cumsum

1
star
46

clh-tla

Modeling a CLH lock in TLA+
TLA
1
star
47

ostack

Humane Python bindings for OpenStack
Python
1
star
48

uvalde

1
star
49

minecraft-forge-tutorial

Simple Minecraft Forge tutorial
CSS
1
star
50

cheat

Generate Dash cheat sheets
Go
1
star
51

md-alloy

Alloy models of aspects of Managed Delivery
Alloy
1
star
52

zotero-bb

Script for randomly selecting a paper from a zotero collection
Clojure
1
star
53

dotfiles

Vim Script
1
star
54

teaching-concurrency

Proof of the problem in Lamport's "Teaching Concurrency" paper
TLA
1
star
55

tla-tree

1
star
56

lorin.github.com

HTML
1
star
57

futex-tla

Modeling futexes in TLA+
TLA
1
star
58

transactions-reading-list

A reading list of interesting papers related to database transactions
1
star