From the stand point of Systems Analysis/System Engineering, I've got some problems with the papers cited. It could simply be the way concepts are expressed/presented, but I don't think so. As an example, in the second paper, the concept of "Reframing" is discussed:
"Reframing is an intellectual activity to identify new opportunities and overcome obstacles to progress when interactions with the real world situation or new sources of information reveal issues with a current problem. Reframing shifts attention from trying to solve the current problem right to asking whether the right problem is being solved. It is a way for designers to pull back and reassess the operational environment, allowing them to challenge their situational understanding and review expectations of actor behavior against the evidence.12 When operators consciously and critically select theories and hypotheses that help to structure their view of reality, they gain the freedom to operate beyond the limitations of any single perspective." (Emphasis added.)
Asking whether your tackling the right problem should be done at the beginning. (That's pretty much old school SE 101.) If you wait until you're trying to implement a solution, or in trouble, you're already screwed.
The intent is solid. But there look to be some serious tweaks needed in the implementation. I'd suggest a DTIC search on "Missions and Means Framework." I think it will give a much more solid starting point, and one that dovetails with some other activities.
Bookmarks