I've been involved the last week with a module for engineering post graduate MSc students on information systems;
and it occurred to me that were I to run a moduloe called computing literacy, there would be little debate about what it should contain? We might know, or oculd find out, what on a building site, in a factory, a graduate engineer needs to know?
But if it is called information literacy, among the engineers, rather than the librarians, there is not likely to be any prior received ideas? This is turn could be tested, or has been (which is of course an information literacy topic, eevl isn't it :)
When it comes to information systems design, it seems to me a genuine puzzle. What do I as a designer expect the victims to know, and what do they need to know in order to be able to communicate?
When I coined the work for the British Commputer Society to look at information literacy as a professional chartered body, I coined infocy in order to construct a string. That work was reported a long time ago, and is still I think available. But do people on this list try to qualified graduate engineers (ie not undergraduate courses) to understand the concepts of engineering information literacy? perhaps from that I can move to information systems (though of course it might be the wrong way round.)
This email has been scanned for all viruses by the MessageLabs Email