IT is mainly concerned with the selection and use of already-available software and hardware.
CS asks: what new system, as a collection of code and electronics, can be designed and should be built? Would it be useful, either immediately or in the future?
IT asks: what new system, selected from catalogues of available code and electronics, should be purchased and employed? And how should it be employed, and people trained to use it?
IT largely takes the internal workings for granted.
Both CS and IT look outwards in much the same way, studying how to provide systems for people to use efficiently or innovatively.
But, when they look inwards, they do so in very different ways.
CS does not normally ask, how does a transistor work? But it must ask, how does a computer work?
IT does not need to ask, how does a computer work? But it must ask, how does an office system work?
A computer scientist/engineer might ask: to make it possible for me (or others) to do this, what new system do I need to design and build?
An information technologist might ask: to make it possible for me (or others) to do this as soon as possible, and with the least disruption, what is there in the catalogues that I can choose to buy?
But both the computer scientist/engineer and the information technologist are likely to be concerned with cost and effectiveness.
Consider a mobile field-wide network for search and rescue in hard real time and in a hazardous environment, with safety-critical requirements. Is that CS or IT? Well, it all depends on your role in the requirements, specification, design, procurement, deployment and operation of the system.
Consider a static planet-wide network for airline seat reservation in soft real time and in a benign environment, with commercial-critical but not safety-critical requirements. Is that CS or IT? Well, it all depends on your role in the requirements, specification, design, procurement, deployment and operation of the system.
Later, other people improved the design and improved the implementation and marketed competitors. They interacted with customers.
The activities of choosing and using a spreadsheet, and finding ways of using it more effectively, and educating other people about its choice and its use, are all IT.
This example is instructive because it shows that the extremes here are CS and IT; but, more importantly, that there is a large grey area at the cross-over, where the 'CS or IT' question has no clear answer and is largely pointless. Nevertheless, one must do one's best to answer it.
Those same engineers, when they are using spreadsheets and graphics and other design tools in order to carry out the clerical and draughting activities that are part of their operations, are making use of IT. And so are the personnel staff who appointed the engineers, and the accountants who are costing the design and production of the engines, and and the marketing and sales staff who are going to sell the engines. They will be using software that has had its own requirements analysis and that has been selected against competing systems, and for whose use there will have been a training programme. All of that is IT.
Similarly, new computer hardware and software in a medical MRI scanner. Or a new intelligent software system for medical diagnosis, or for the automatic prescription and design of pharmaceutical drugs. That is CS in collaboration with medicine.
But when well-established software of this kind is marketed, and appears in catalogues, and is evaluated and chosen and purchased and used by people who see themselves as medics rather than engineers, they regard it as IT, not CS. That is IT in collaboration with medicine.
Suppose you looked in the UCAS Handbook, and found a programme called Airliner Studies. What would you think it was about?
And they said, 'Oh, no, no. It is about managing an airline, of course'.
And they said, 'Oh, no, no. It is about designing airliners, of course'.
And they both said, 'Oh, yes, of course we cover all that'.
On the other hand, you might conclude that is was they who were confused.
You might offer yourself as a programme-naming consultant, and (when suitably remunerated) recommend that the first university call its programme Airline Management and the second call its programme Aeronautical Engineering.
(Both programmes would, of course, include a module called Airline Economics.)
You would be helped by the fact that some universities already have programmes called Airline Management or Aeronautical Engineering
There are many programmes called Computer Science, and even more called Computing Science, Computer Studies, Computing Studies or Information Technology that take an approach similar to the imaginary department of Airline Management just referred to.
There are other programmes called Computer Science, Computer Systems, Computer Systems Engineering, and so on, that have an approach similar to Aeronautical Engineering in the sense of the previous discussion.
So, what would you recommend in your role as a programme-naming consultant?
They search for Computer Science. They look up Computer Science. They have heard of Computer Science. But they may get very different things - very different approaches - from different universities.
That is why we have a programme called Computer Systems and Software Engineering.
It means Computer Systems Engineering; but also, just in case you thought software was not included, Computer Software Engineering as well.
That is, in effect, Computer (Systems and Software) Engineering.
We know we might not have got them quite right.
Please let us know what you think.