It's like grouping "Industrial Design" and "Theoretical Physics" under the term "Physics", if "Industrial Design" also included "Product Managment".
The same kind of experiments happen in lots of other CS sub-fields: high performance computing, security, etc.
Note that most computer "science" classes are stuff like learning java, learning UML, learning software engineering. This stuff is barely engineering, let alone science. It has more in common with a fine art.
Algos and data structures etc are arguably a form of math, depending on the class most likely applied math.
It's not a natural science, and what you're doing is similar to the way artists will use, say, a picture of a DNA molecule to create a cool painting. If they use scientific principles in their art, does that make it a science?
No - what you are describing is a "craft" - a very informal kind of engineering. Architecture is not a science either.
For example: product design. You make hypothesis, create a prototype to test it, and then draw conclusions from that.
Maybe "science" depends on the methods, and not on the fields. Maybe everything can be Science if approached scientifically.
In some countries, there are "Exact Sciences" (basically Math and all the derivatives like statistics and computing) and "Natural Sciences" (like physics, chemistry and biology).
But it's all semantics, the important thing (and the thing most people seem to agree upon) is that the status of CS as Science depends of the status of Mathematics as Science.
Computer science makes stuff like psychology, sociology and anthropology look rigorous. They actually do experiments and case studies and use real world evidence you know!
CS papers have more in common with Literature than they do with the widely disparaged soft sciences like psychology.
Depending on how the university works, students can cheat on homework then barely the exam (thanks to easy, formulaic questions that they can cram the night before), and still get decent marks. The university will compensate, with harder homework and an easier exam the next year.
(So I got Z-specs, automata and big-O notation. Umm. Thanks guys.)
If you don't add them, the people on the side of software engineering, will say it's not relevant to business needs.
If you try to compromise they both moan about university not being relevant...
And they are even harder to teach inside science or engineering schools.
Two opposing views, but they think the argument is both in their favour.
There is also a massive backlash against universities in the UK at the moment. I am seeing many 'apprentice' software developers, and freelance developers skipping university. They tell me they know more than the average university graduate. So I ask them about complexity? Nope. Predicate Logic? Nope. These are things taught in even the lowest polytechnic school and they don't know them. They don't know the bounds of their own ignorance because they think cs is just knowing a few programming languages, whipping up a few apps and websites. They know more languages the average graduate? Maybe. Can they do software engineering? The easy business stuff. Do they know cs? No. I think they have never been exposed to cs and don't how deep it goes.
I've seen the accredited software developer apprenticeship curriculum and it's mostly java and design patterns.
I think the focus on apprenticeships at the moment is creating a generation of software developers who don't know what NP-Complete means.
Computer science is not whipping up applications with fancy design patterns, that's why you're better than them. Give them a few years and their cs background + Software engineering experience will begin to shine.