Search

The demand for graduates with exposure in Cloud Computing is on the rise. For many educational institutions, the challenge is to decide on how to incorporate appropriate cloud-based technologies into their curricula. In this paper, we describe our design and experiences of integrating Cloud Computing components into seven third/fourth-year undergraduate-level information system, computer science, and general science courses that are related to large-scale data processing and analysis at the University of Queensland, Australia. For each course, we aimed at finding the best-available and cost-effective cloud technologies that fit well in the existing curriculum. The cloud related technologies discussed in this paper include open-source distributed computing tools such as Hadoop, Mahout, and Hive, as well as cloud services such as Windows Azure and Amazon Elastic Computing Cloud (EC2). We anticipate that our experiences will prove useful and of interest to fellow academics wanting to introduce Cloud Computing modules to existing courses. (Contains 3 tables and 11 figures.)

Over the past few years Australian universities have sought to establish generic graduate attributes statements to meet the demands of external stakeholders. Within the area of information and communication technology (ICT), for example, professional organizations and employers want new ICT graduates to be able to talk with clients, create persuasive arguments and present work confidently. To meet such requirements, Australian ICT educators have explored a variety of methods to implement graduate attributes. The selection and content of delivery models, however, vary according to university policies and departmental cultures. In this paper we critically examine the dedicated, infused, and embedded approaches to the delivery of generic graduate attributes. To do this, we first trace the development of graduate attributes. Secondly, we present three diverse approaches by two ICT departments within the same university and discuss factors that lead to sustainable generic graduate attribute programmes. We conclude our paper with issues to consider when adopting implementation models and map out suggestions for further research. [ABSTRACT FROM AUTHOR]

In a Finnish study of four different academic disciplines, Ylijoki (2000) found that in Computer Science there was a disparity between the conceptions held by undergraduate students and staff about their discipline; students viewed it as being far more pragmatic and results focused than did their instructors. Not surprisingly, here at our Australian university where the undergraduate Computer Science program emphasizes programming and problem solving skills, the authors had noticed a similar inconsistency between staff and student beliefs. This paper reports on an effort to realign these conceptions and broaden student experience using an assessment task. Centered on solutions to the popular 'Sudoku' puzzle (Sudoku, 2005), the task was designed and introduced into an Intelligent Systems course, a final year elective of a Computer Science degree. The goal was to expose students to some of the 'pure' rather than applied aspects of the Computer Science discipline (Becher & Trowler, 2001), by using assessment to encourage experimental learning (Kolb & Fry, 1975). The assessment specification instructed students to design and conduct several 'in silica' Computer Science experiments to solve and/or create Sudoku puzzles. Importantly, students were asked to keep a Research Diary documenting their thoughts, attempts, backtracking and progresses as they attempted the assignment. Most unique from a student's perspective was that 'failure' to solve the given problem by experimentation was a viable option; their efforts would be rewarded given they conducted themselves 'scientifically' in their attempt. The inclusion of a Research Diary as part of the assessment proved beneficial to both students and staff, particularly as the Diaries focused students on the doing, rather than on the results achieved. For staff, these journals allowed the privilege of seeing what students were thinking and doing as they engaged in the problem. An early analysis of Diary entries shows evidences of students 'thinking scientifically', that is, understanding and thinking about the problem before formalizing an approach to a solution. In addition, Diary entries also show evidences of students 'behaving scientifically' as they reported conducting experiments and analyzing their results, before concluding about their experiences. For students, regardless of whether they able to complete the task, the Research Diaries were valuable testaments to their efforts and experimentations. [ABSTRACT FROM PUBLISHER]