Analysis of the vignettes accompanying this chapter show some signs of individuals in the IS groups studied taking up positions that have some prestige or degree of control. For example, Ed Lewis is currently the chair of the IT-030 Committee for Standards Australia that recently published AS8015: 2005 Corporate Governance of Information and Communication Technology and AS8018: 2004 ICT Service Management (now AS/ISO 20000: 2007 Service Management). McDonald is currently editor of the Australasian Journal of Information Systems. Professor Gregor was honoured with an award under the Australian honours system in 2005—possibly the first time that work in an IT field was recognised in this way (Gerry Maynard from Victoria received an honour at the same time).
The consensus of opinion among the authors, however, is that our field is not ‘socially prestigious’. All of us have had experience with appointment and promotion committees where it is clear that the nature of work in IS is not well understood or regarded highly. Many of our staff have had experience in industry before joining academia so they have had relatively limited time to establish a scientific reputation in terms understood by committees of social and physical scientists who have worked almost their whole careers in universities.
To summarise, the best we could say about this aspect of our discipline is that it is possibly emerging, but it is ‘early days’.
A wide range of pedagogical approaches is evident in the teaching at the three universities: lectures, seminars, tutorials, group projects, case studies, presentations, use of online learning management systems (WebCT) and laboratory sessions. There are some discernible differences. The UNSW@ADFA has a philosophy of ‘problem-based learning’, while the UC focuses more explicitly on industry involvement in course development and on team teaching.
A wide range of epistemological approaches is evident in the research undertaken, with the groups tolerant of approaches ranging through quantitative survey work, qualitative case studies, the grounded-theory method, design approaches and interpretive work.
Our view is that we are not accepted as a distinct field in terms of a unique symbol system by outsiders. We do have commonalities in our symbol system with parts of computer science and software engineering, which is understandable, as we are allied fields, with some degree of overlap. We have overlap, however, which is of more concern in that people in application areas, who use IS and IT as tools, also use much of our symbol system. We find it hard to ‘exclude these people as outsiders’ and many cannot see why they should not teach IS topics within their own areas, as in health informatics. People outside IS, even within universities, have very poor understanding of what the term ‘information system’ means, either in relation to the artefacts constructed or as the name of the discipline. The continuing debate within IS about how our discipline should be defined only adds to the confusion.
The domain of knowledge is examined by analysing the commonalities in syllabi across all three institutions. Table 4.6 shows the areas of knowledge that are common across all three of the universities in the core knowledge in their IS majors. Two of the three universities follow ACS guidelines in planning their curriculum but these guidelines, as described in Underwood (1997), leave a great deal of discretion to the institution applying them.
|
ACS core knowledge area nomenclaturea |
UNSW@ADFA course (IS major in BA, BSc) |
ANU course (IS major in BComm) |
UC course (IS major) |
|---|---|---|---|
|
Introductory unitb |
Introduction to IS (problem-solving approach) |
Foundation of IS and e-commerce |
IS in organisations |
|
Program design and implementation (or systems building/software construction) |
Exercises in Perl within IS in organisation; web design within design of IS |
Introduction to programming |
Use of SQL in database design and system building in IT projects; some use of design tools in designing human–computer interaction and systems analysis and modelling |
|
Systems analysis and design |
Design of IS |
IS analysis |
Systems analysis and modelling, advanced information modelling, document and workflow management, knowledge management systems |
|
Database management |
IS in organisations; design of IS |
Relational databases, database systems |
Database design, database systems |
|
Project management and quality assurance |
Selection of systems; management of work systems |
Project management and IS |
Systems project and quality management |
|
Managerial and organisational issuesb |
Management of work systems; selection of systems; project |
IS management |
IS management; IT business alignment |
|
Specialist areasb |
Application of IS (elective choice of topics, including e-commerce, data management) |
Electronic business; accounting IS; electronic commerce strategic issues; IT in electronic commerce |
Document and workflow management; knowledge management systems; business intelligence systems; general systems theory; informatics case studies |
|
Ethics/social implications/professional practice |
IS in organisations; management of work systems |
In many courses |
In many courses, especially IT project |
|
Interpersonal communications |
Introduction to IS; management of work systems; IS project—all courses |
In many courses |
Throughout; specialist unit (professional practice in IT) for international students |
|
Industry project |
Third-year team project, 50% load second semester, canvassed from defence |
Project management and IS |
IT project; business informatics internship |
a ACS Core Body of
Knowledge terminology unless noted
b not named as such in the ACS Core Body of
Knowledge
It can be seen from Table 4.6 that there is some commonality across the institutions in the core of their courses, which is evidence of common understanding of the domain knowledge that is central to the discipline. The areas in common include systems analysis and design, database design and management, project management, managerial and organisational issues, ethics/social implications/professional practice and interpersonal communications. Each university also provides coverage of specialist knowledge and application areas that reflect the interests and capabilities of staff.
There is variation in the degree to which programming and software construction are required. At the ANU, an introductory programming course is mandatory. The UNSW@ADFA provides little education in programming in its IS courses, with its computer science programs covering programming in more depth. The main reason for this is that the careers of the undergraduates are prescribed and they involve no programming on the job, rather the supervision of civilian or service trade-trained personnel. The UC requires no mandatory programming study, which, again, is covered in IT programs, but students do receive experience of systems building in their project courses.
There is a range in the types of knowledge presented in the courses taught in common. In the terms of Fitzgerald (2003):
Rules or laws (as in the natural sciences). Examining the common syllabi shows that there is relatively little core knowledge of the natural-science type—there are few, if any, law-like generalisations; rather the knowledge falls more into the second and third categories in Fitzgerald’s taxonomy. The knowledge, however, does rely on underlying theories of the natural-science type for justification and explanation of system-building knowledge. For example, guidelines for the construction of decision-support systems rely on behavioural science knowledge of human decision making.
Evidenced guidelines. The common syllabi include knowledge that is in the form of guidelines arising from practice. For example, the project management courses include knowledge of project management tools and practices such as software cost estimation that are based on empirical observation.
Normative guidelines. The courses in the common syllabi include what can be termed normative guidelines or ‘design theory’ (see Gregor 2002, 2006; Gregor and Jones 2007). For example, Codd’s relational database theory is taught in all the database courses across the institutions.
Our conclusion is that we have a recognised common domain that might be expressed in this way: the IS discipline analyses human activity, determines the kinds of data, information and knowledge needed to enable people to act effectively and responsibly, designs technology-based systems to support them and evaluates the impact of those systems. Our knowledge is based on theories of information, human activity and organisations, IS studies analysis techniques and methodologies, human–computer interaction, data and knowledge representation and design, systems construction and validation and the impacts of systems on people, organisations and society. In this unique role, IS bridges the essentially content-free information technologies with the content-rich but often unstructured domain knowledge. To perform this function, IS embraces types of knowledge and epistemologies that differ from those that are traditional in the natural sciences and exhibits a more well-grounded, participative style—congruent with a discipline that is at the intersection of science, technology and human and organisational behaviour.
Local contingencies have a fair degree of impact on how the discipline operates in the three universities. There are differences among the universities in terms of the faculties in which they are based and this positioning influences the types of subjects taught and the nature and practice of research. For example, the IS group that is in the College of Business and Economics at the ANU has a strong business orientation in its research and teaching. The case studies also show how the nature of ADFA and its role in educating personnel for the defence forces influences the choice of subjects offered to undergraduates.
Our reflection leads us to conclude that we have a relatively low degree of professionalisation in the discipline, using the criterion of the ‘extent of variation in the nature of IS research’.
In terms of the content of our research endeavours, there is not a great deal of variation, as all our researchers focus on areas that are recognisably within the disciplinary bounds, and we have common understanding of one another’s interests. A number of the people in our schools (and all the authors) do applied research, in that we build or help people to build artefacts.
In terms of the methods used in our research, however, there is very wide variation and the research methods taught to students do not necessarily suit the particular nature of IS as—at least in part—a discipline concerned with the construction of artefacts (as evidenced in our common syllabi). The IS students at the ANU are taught research methods in the same class as accounting, auditing, management and marketing students and do not currently have any exposure in these courses to ‘design theory’ (a shortcoming to be addressed in the near future). The situation at ADFA is similar, with only the UC explicitly addressing design-type research. This disjunction between what is taught as core knowledge and what is taught as research methods leads us to conclude that there is a low degree of professionalisation at the undergraduate level.
The UNSW@ADFA does teach research methods and professional practices as discrete units in its postgraduate courses. The emphasis on a professional approach is made evident in the tenor of the Doctorate of IT—an offering that is unique in the Australian Capital Territory.
At least in the UNSW@ADFA undergraduate courses, the focus is on providing ‘well-informed users’ rather than professional service deliverers. Few of its early graduates will serve as IS specialists while still in the military, except in some logistics or intelligence areas. More will end up as IS professionals after on-the-job training in more senior positions.
|
Framework component |
Assessment |
|---|---|
|
Mechanisms of control |
Emerging, but ‘early days’. |
|
Knowledge base |
|
|
a) Recognised pedagogical approaches |
Yes, but a wide range. |
|
b) Recognised epistemological approaches |
Yes, many recognised and used. |
|
c) Unique symbol set |
No. |
|
d) Agreement on knowledge domain topics |
A discernible common core, but also variation across complete range of offerings. |
|
e) Range of knowledge types |
Yes, although rules of laws as in the natural sciences are used primarily as support knowledge. |
|
Impact of local contingencies |
Yes, placement of groups in faculties within universities and proximity to federal government influences research and teaching. |
|
Degree of professionalism |
Low degree. Research methods taught to students do not necessarily suit the particular nature of IS. There is more professional emphasis in the postgraduate courses. |