Instructional root-cause analysis fishbone diagram for diagnosing the CP course¶

Design · All designs
Evidence · no claims cited

Description¶

Before redesigning the course, the author integrated instructional and root-cause analysis techniques, using a fishbone diagram (Figure 1) with the main problem statement "poor PS sk ills and knowledge transfer". The main branches were Programming Language, Learners, Instructors and Instructional Approach, with sub-branches such as the language paradigm, learner attitudes, instructors' teaching styles and learning goals. The analysis "guided how to assess the current needs, learners, environment, tasks and goals" and informed the choice of C, PS strategies and web support.

Design Implications¶

Context¶

Requirements¶

Systematic identification of potential main and sub-causes "before jumping to a conclusion"

Constraints¶

Diagnosis was specific to the faculty's three-decade-old teacher-directed CP course context

Target Learners¶

first-year undergraduate novice programmers

Learning Goals¶

problem-solving skills
knowledge transfer from lectures to labs

Claims¶

Jonassen's Instructional Design Model for Well-Structured Problems (seven-step sequence)

Examples¶

-

Key Sources¶

Uysal, M. P. (2014). Improving First Computer Programming Experiences: The Case of Adapting a Web-Supported and Well-Structured Problem-Solving Method to a Traditional Course. Contemporary Educational Technology, 5(3), 198-217. https://doi.org/10.30935/cedtech/6125

Page metadata

Field	Value
`type`	`design`
`id`	`instructional-root-cause-analysis-fishbone`
`title`	`Instructional root-cause analysis fishbone diagram for diagnosing the CP course`
`description`	`Before redesigning the course, the author integrated instructional and root-cause analysis techniques, using a fishbone diagram (Figure 1) with the main problem statement "poor PS sk ills and knowledge transfer".`
`status`	`review`
`generated`	by `process:settle-candidates` on `2026-11-01`
`trust`	unverified — no one has confirmed this page's content
`sources`	1 — `uysal-2014`

Frontmatter is the page's machine-readable record — see the Schema & Guide.