Contextual view of human error, after [7].

Contexts in source publication

Context 1

... understand failures properly, one needs to avoid the perils of hindsight and understand the accident context from the insiders' point of view. Dekker drives home his point by illustrating the contextual view on error with a tube or pipe-like diagram (see Figure 1). This illustration serves to highlight that accident investigators are likely to have much wider access to information pertaining to an accident than the protagonists involved in its evolution. ...

Context 2

... devices such as automobiles now become systems of systems as shown in Figure 1. Figure 1 depicts a relation- ship among four kinds of systems: traffic systems, energy supply systems, information systems, and distribution sys- tems which can be considered as sub systems of consumer de- vices. ...

Context 3

... devices such as automobiles now become systems of systems as shown in Figure 1. Figure 1 depicts a relation- ship among four kinds of systems: traffic systems, energy supply systems, information systems, and distribution sys- tems which can be considered as sub systems of consumer de- vices. They face with various requirements and changes from environments: safety, quality, cleanness, climate changes to traffic systems; efficiency to energy supply system; security to information system; and increasing population to distri- bution systems. ...

Context 4

... has been getting popular for physical model- ing applied to the description of controlled object dynamic behavior. We can realize the MBD process shown in Figure 10 once we have the models developed in the high level. In MBD process, the control process and the implementa- tion process are separated to each other. ...

Context 5

... these variables reflecting physics and the variables with sufficient resolutions are considered as continuous event variables. There are many logical branches like the C-code in Figure 11. It can be considered as an approximation of required continuous logic as shown in the right side of Figure 11. Figure 12 shows the comparison between the logic and the physically desired curve. ...

Context 6

... are many logical branches like the C-code in Figure 11. It can be considered as an approximation of required continuous logic as shown in the right side of Figure 11. Figure 12 shows the comparison between the logic and the physically desired curve. ...

Context 7

... can be considered as an approximation of required continuous logic as shown in the right side of Figure 11. Figure 12 shows the comparison between the logic and the physically desired curve. ...

Context 8

... means the divided portions are ex- ponentially increasing with the logical branches. Discrete events make verification very difficult as the state space is di- vided into the many pieces by the logical branches as shown by the dotted line in Figure 13 is replaced by the solid line Figure 12: Example of logical branch in automotive engine control Figure 13: dividing the state space by logical branches corresponding continuous event. Evaluation needs a huge number of the tests such that a divided portion is evaluated by the trajectory going through the divided portions. ...

Context 9

... means the divided portions are ex- ponentially increasing with the logical branches. Discrete events make verification very difficult as the state space is di- vided into the many pieces by the logical branches as shown by the dotted line in Figure 13 is replaced by the solid line Figure 12: Example of logical branch in automotive engine control Figure 13: dividing the state space by logical branches corresponding continuous event. Evaluation needs a huge number of the tests such that a divided portion is evaluated by the trajectory going through the divided portions. ...

Context 10

... means the divided portions are ex- ponentially increasing with the logical branches. Discrete events make verification very difficult as the state space is di- vided into the many pieces by the logical branches as shown by the dotted line in Figure 13 is replaced by the solid line Figure 12: Example of logical branch in automotive engine control Figure 13: dividing the state space by logical branches corresponding continuous event. Evaluation needs a huge number of the tests such that a divided portion is evaluated by the trajectory going through the divided portions. ...

Context 11

... the reduction of the logical branches is very effec- tive to mitigate the difficulty. For the purpose, an idea is that the logical branch shown in Figure 12 is regarded as the corresponding continuous event. The logical branch can be transformed to the continuous system or neglected in the verification process. ...

Context 12

... example of the verification based on the concept is shown in the Figure 14. The application is an engine cold start control. ...

Context 13

... feature has resulted in the many logical branches inserted by many developers. The figure in Figure 14 shows the sections of the state space. The steep decrease of the fuel injection is seen in the left figure and the isolated mountain appears in the right figure. ...

Context 14

... basic SysML syntax allows the construction of models that are ambiguous in some respects. Consider the IBD in Figure 1, which contains three parts b1, b2 and b3. Part b1 requires interfaces: i1 and i2. ...

Context 15

... SysML standard states that each required interface must be linked with a provided interface. For such a link to be valid, either the required and provided interfaces must refer to the same interface type (as in the i2 interfaces in Figure 1), or the provided interface must be a specialisation of the required interface in that it must contain at least the same operations and properties as the required interface. In modelling a SoS, greater flexibility may be required than is a↵orded by this definition. ...