An appropriate analogy can be made with mathematics. Mathematics, to a greater or lesser degree, is used in each of the previous examples. No one would seriously propose that only qualified government regulated mathematicians should have done the mathematics. Instead, the proper application of a tool is deemed to be the responsibility of the profession using the tool. It is the responsibility of the engineer, architect, physician, accountant, or other professional who uses the mathematics to know when they are competent, and when they should call in an expert for advice.
Software falls into the same category.
We want every profession to have appropriate knowledge of computing science. And in particular, we want them to know when they are exceeding their expertise. The accountant has to know when to call in the data modelling and workflow experts, the computer engineer has to know that you don't build safety critical systems if you don't understand the notion of a critical section. If software engineering is the discipline of building software, then there is no question that computing science has staked its claim. Computer scientists, quite simply, build more software than any other group.