Discussions with Context or Domain

It seems to me that having a discussion about some favorite topic in the absence of a domain or context leads to (as a business friend from Houston used to say) "the weeds hitting the windshield. In other words "we're in the ditch."
At a course in June of 2005, titled "Systems Engineering in the Information Age," the notion that systems are multifaceted (an obvious statement) and that speaking about processes, process artifacts, and decisions about applying processes needs some framework for discussion to avoid "the weeds hitting the windshield."
This picture is extracted from the document "System of Systems Systems Engineering Guide: Considerations for Systems Engineering in a System of Systems Environment," Dec 22, 2006, For System of System Pilot Project, Version 0.9, Director, Systems and Software Engineering Deputy Under Secretary of Defense (Acquisition and Technology) Office of the Under Secretary of Defense (Acquisition, Technology and Logistics).
    The point  is that when it is suggested something like "testing is a waste," and a reply is provided like "probably depends on the context and domain," this is one approach to classifying the context and domain.
A New Years Resolution

I have resolved to define when ever possible the context and domain of the posts I create here. And I hope the responses would do the same.

Got something to say?