An investigation into the adoption of CDIO in distance learning

The Conceive, Design, Implement and Operate Initiative (CDIO) uses integrated learning to develop deep learning of the disciplinary knowledge base whilst simultaneously developing personal, interpersonal, product, process and system building skills. This is achieved through active and experiential learning methods that expose students to experiences engineers will encounter in their profession. These are incorporated not only in the design-build-test experiences that form a crucial part of a CDIO programme but also in discipline focused studies. Active and experiential learning methods are, of course, more difficult to incorporate into distance education. This paper investigates these difficulties and the implications in providing a programme that best achieves the goals of the CDIO approach through contemporary distance education methods. First, the key issues of adopting the CDIO approach in conventional oncampus courses are considered with reference to the development of the CDIO engineering programmes at the University of Liverpool. The different models of distance based delivery of engineering programmes provided by the Open University in the UK, and Deakin University and the University of Southern Queensland in Australia are then presented and issues that may present obstacles to the future adoption of the CDIO approach in these programmes are discussed. The effectiveness and suitability of various solutions to foreseen difficulties in delivering CDIO programmes through distance education are then considered. These include the further development, increased use and interinstitutional sharing of technology based facilities such as Internet facilitated access to laboratory facilities and computer aided learning (CAL) laboratory simulations, on campus workshops, and the development of a virtual engineering enterprise

Curriculum Guidelines for Undergraduate Programs in Data Science

The Park City Math Institute (PCMI) 2016 Summer Undergraduate Faculty Program met for the purpose of composing guidelines for undergraduate programs in Data Science. The group consisted of 25 undergraduate faculty from a variety of institutions in the U.S., primarily from the disciplines of mathematics, statistics and computer science. These guidelines are meant to provide some structure for institutions planning for or revising a major in Data Science

Latin American perspectives to internationalize undergraduate information technology education

The computing education community expects modern curricular guidelines for information technology (IT) undergraduate degree programs by 2017. The authors of this work focus on eliciting and analyzing Latin American academic and industry perspectives on IT undergraduate education. The objective is to ensure that the IT curricular framework in the IT2017 report articulates the relationship between academic preparation and the work environment of IT graduates in light of current technological and educational trends in Latin America and elsewhere. Activities focus on soliciting and analyzing survey data collected from institutions and consortia in IT education and IT professional and educational societies in Latin America; these activities also include garnering the expertise of the authors. Findings show that IT degree programs are making progress in bridging the academic-industry gap, but more work remains

Information Systems Undergraduate Degree Project: Gaining a Better Understanding of the Final Year Project Module

The place of an individual project in the final year of Information Systems (IS) undergraduate degrees at UK universities is well established. In this paper we compare the final year project modules at four UK universities: the University of Brighton, the University of South Wales, University of West London and the University of Westminster. We find that the aims of the projects are similar, emphasising the application of the knowledge and skills from the taught element of their course in a complex development project, often including interactions with a real client. Although we show in this analysis that projects serve a similar purpose in the IS degree courses, the associated learning outcomes and the assessment practice varies across the institutions. We identify some gaps in the skills and abilities that are not being assessed. In further work we are planning to consult final year students undertaking their projects and their supervisors, in order to gain an understanding of how project assessment criteria are actually put to use

A collaborative and experiential learning model powered by real-world projects

Information Technology (IT) curricula\u27s strong application component and its focus on user centeredness and team work require that students experience directly real-world projects for real users of IT solutions. Although the merit of this IT educational tenet is universally recognized, delivering collaborative and experiential learning has its challenges. Reaching out to identify projects formulated by actual organizations adds significantly to course preparation. There is a certain level of risk involved with delivering a useful solution while, at the same time, enough room should be allowed for students to experiment with, be wrong about, review, and learn. Challenges pertaining to the real-world aspect of problem-based learning are compounded by managing student teams and assessing their work such that both individual and collective contributions are taken into account. Finally, the quality of the project releases is not the only measure of student learning. Students should be given meaningful opportunities to practice, improve, and demonstrate their communication and interpersonal skills. In this paper we present our experience with two courses in which teams of students worked on real-world projects involving three external partners. We describe how each of the challenges listed above has impacted the course requirements, class instruction, team dynamics, assessment, and learning in these courses. Course assessment and survey data from students are linked to learning outcomes and point to areas where the collaborative and experiential learning model needs improvement

Web Science: expanding the notion of Computer Science

Academic disciplines which practice in the context of rapid external change face particular problems when seeking to maintain timely, current and relevant teaching programs. In different institutions faculty will tune and update individual component courses while more radical revisions are typically departmental-wide strategic responses to perceived needs. Internationally, the ACM has sought to define curriculum recommendations since the 1960s and recognizes the diversity of the computing disciplines with its 2005 overview volume. The consequent rolling program of revisions is demanding in terms of time and effort, but an inevitable response to the change inherent is our family of specialisms. Preparation for the Computer Curricula 2013 is underway, so it seems appropriate to ask what place Web Science will have in the curriculum landscape. Web Science has been variously described; the most concise definition being the ‘science of decentralized information systems’. Web science is fundamentally interdisciplinary encompassing the study of the technologies and engineering which constitute the Web, alongside emerging associated human, social and organizational practices. Furthermore, to date little teaching of Web Science is at undergraduate level. Some questions emerge - is Web Science a transient artifact? Can Web Science claim a place in the ACM family, Is Web Science an exotic relative with a home elsewhere? This paper discusses the role and place of Web Science in the context of the computing disciplines. It provides an account of work which has been established towards defining an initial curriculum for Web Science with plans for future developments utilizing novel methods to support and elaborate curriculum definition and review. The findings of a desk survey of existing related curriculum recommendations are presented. The paper concludes with recommendations for future activities which may help us determine whether we should expand the notion of computer science

Learning requirements engineering within an engineering ethos

An interest in educating software developers within an engineering ethos may not align well with the characteristics of the discipline, nor address the underlying concerns of software practitioners. Education for software development needs to focus on creativity, adaptability and the ability to transfer knowledge. A change in the way learning is undertaken in a core Software Engineering unit within a university's engineering program demonstrates one attempt to provide students with a solid foundation in subject matter while at the same time exposing them to these real-world characteristics. It provides students with a process to deal with problems within a metacognitive-rich framework that makes complexity apparent and lets students deal with it adaptively. The results indicate that, while the approach is appropriate, student-learning characteristics need to be investigated further, so that the two aspects of learning may be aligned more closely

Involving External Stakeholders in Project Courses

Problem: The involvement of external stakeholders in capstone projects and project courses is desirable due to its potential positive effects on the students. Capstone projects particularly profit from the inclusion of an industrial partner to make the project relevant and help students acquire professional skills. In addition, an increasing push towards education that is aligned with industry and incorporates industrial partners can be observed. However, the involvement of external stakeholders in teaching moments can create friction and could, in the worst case, lead to frustration of all involved parties. Contribution: We developed a model that allows analysing the involvement of external stakeholders in university courses both in a retrospective fashion, to gain insights from past course instances, and in a constructive fashion, to plan the involvement of external stakeholders. Key Concepts: The conceptual model and the accompanying guideline guide the teachers in their analysis of stakeholder involvement. The model is comprised of several activities (define, execute, and evaluate the collaboration). The guideline provides questions that the teachers should answer for each of these activities. In the constructive use, the model allows teachers to define an action plan based on an analysis of potential stakeholders and the pedagogical objectives. In the retrospective use, the model allows teachers to identify issues that appeared during the project and their underlying causes. Drawing from ideas of the reflective practitioner, the model contains an emphasis on reflection and interpretation of the observations made by the teacher and other groups involved in the courses. Key Lessons: Applying the model retrospectively to a total of eight courses shows that it is possible to reveal hitherto implicit risks and assumptions and to gain a better insight into the interaction...Comment: Abstract shortened since arxiv.org limits length of abstracts. See paper/pdf for full abstract. Paper is forthcoming, accepted August 2017. Arxiv version 2 corrects misspelled author nam

Opiskelijoiden valmistaminen työelämään yliopiston sisäisen ohjelmisto-startupin avulla

Tertiary education aims to prepare computer science students for the working life. While much of the technical principles are covered in lower-level courses, team-based capstone projects are a common way to provide students hands-on experience and teach soft skills. Although such courses help students to gain some of the relevant skills, it is difficult to simulate in a course context what work in a professional software engineering team really is about. Our goal is to understand ways tertiary education institutions prepare students for the working life in software engineering. Firstly, we do this by focusing on the mechanisms that software engineering capstones use to simulate work-life. A literature review of 85 primary studies was conducted for this overview. Secondly, we present a more novel way of teaching industry-relevant skills in an university-lead internal software startup. A case study of such a startup, Software Development Academy (SDA), is presented, along with the experiences of both students and faculty involved in it. Finally, we look into how these approaches might differ. Results indicate that capstone courses differ greatly in ways they are organized. Most often students are divided in teams of 4–6 and get assigned with software projects that the teams then develop from an idea to a robust proof-of-concept. In contrast, students employed in the SDA develop production-level software in exchange for a salary for university clients. Students regarded SDA as a highly relevant and fairly irreplaceable educational experience. Working with production-quality software and having a wide range of responsibilities was perceived integral in giving a thorough skill set for the future. In conclusion, capstones and the internal startup both aim to prepare students for the work-life in software engineering. Capstones do it by simulating professional software engineering in a one-semester experience in a course environment. The internal startup adds a touch of realism to this by being actual work in a relatively safe university context