Post
The first one is the abstraction hierarchy from Coping With Complexity (1981). This shows how requirements and design tends to go top-down based on goals that must be met by the system. However, signals of problems tend to go bottom-up, from a local issue showing up as disrupted functionality.
2 reposts10 likes
The cool thing though is that he then maps a problem-solving path as a line walking that conceptual path within a "conceptual reasoning space" of operators that is event-independent. Neelam Naikar (doi.org/10.1016/j.ap...) re-renders diagrams Rasmussen had made in a few publications in the mid 80s: