Computational Literacies (Autumn 2022)

Abstract

This course introduces key concepts from computing and enables students to understand software in an organisational, historical, and cultural context. The course is at an introductory level and is well-suited for students with limited or no technical background.

Description

Computational Literacies is designed to introduce a wide range of topics from computing to students with limited or no prior technical background. Students will learn key concepts from computing and perform hands-on learning activities in order to be able to meaningfully participate in the management of software development projects. Students will also gain a background in the cultural and organisational contexts in which software has historically been developed.

Formal prerequisites

Intended learning outcomes

After the course, the student should be able to:

• Relate computational concepts and theories to real-world cases and applications of IT
• Describe complexities in organisational software development processes
• Recognise and reflect upon elements of software code and software artefacts in existing systems
• Explore computing as a socio-cultural phenomenon with political and ethical implications
• Discuss current trends, debates and controversies in approaches to IT development

Learning activities

Lectures - Students are expected to come to lecture prepared with reflections on the assigned readings. Lectures will introduce key topics from the course curriculum and syllabus and provide introduction to various approaches to IT development, relevant topics in organisational software, and current debates and controversies in IT development.

Exercises - This course has a high level of engagement through hands-on exercises for skills development. Students are expected to seek out and find resources for building up knowledge about real-world IT systems and existing computational practices. Exercises will provide a foundation of skills for completing the mandatories outside of class.

Readings - Readings will introduce students to key terms, trends, debates, and controversies in IT development and provide case studies relating to real-world organisational software contexts.

Written assignment - Students will contribute to a peer-reviewed library of key terms, concepts, and software artefacts relevant to computation and IT development. These will be written individually, sometimes drawing upon group-based work. These will be drawn from a variety of sources including desk research, interviews, readings of case studies, close readings of software artefacts, and analyses of online fora for professional IT developers. The purpose of this activity is not only to become familiar with key concepts but to relate them to real-world cases and debates, trends, and controversies in IT development. Through this exercise students will also become familiar with resources for finding out more about particular IT concepts to further future self-teaching in IT topics. The library of key terms will include, for example, concepts related to programming, IT development methods, software languages and paradigms.

Oral presentation- Students will work in groups to deliver a presentation at a course “demo day”. Details about the requirements for this demo will be shared during the course. The format will be a poster presentation or demo table where it is mandatory that all group members are present for the duration of the course meeting. 

Peer review and group work - Students will work individually as well as collaboratively in this course. The written mandatories will be written individually sometimes drawing upon group work conducted in and out of class. The mandatory assignments include not only individual written work but the peer-review of classmates’ assignments. This means that the course will collaboratively build up a library of terms that have been reviewed and augmented through peer review work. 

Mandatory activities

The course runs for 14 weeks and is made of up seven two-week modules. For modules 1-6 there will be a required mandatory assignment, for a total of six mandatory assignments. 

Five of the mandatory assignments will be short written submissions contributing to a peer-reviewed library of key concepts. The final mandatory assignment will be an individual reflection on the mandatory demo day.

To complete the mandatories, students must submit not only their written assignment but also the peer review of two of their classmates' assignments. 

A make-up assignment for missed mandatories will be provided in the final module.

The student will receive the grade NA (not approved) at the ordinary exam, if the mandatory activities are not approved and the student will use an exam attempt.

Course literature

The course literature is published in the course page in LearnIT.

Student Activity Budget

Estimated distribution of learning activities for the typical student

• Preparation for lectures and exercises: 26%
• Lectures: 15%
• Exercises: 15%
• Assignments: 20%
• Project work, supervision included: 4%
• Exam with preparation: 20%

Ordinary exam

Exam type:
C: Submission of written work, External (7-point scale)
Exam variation:
C11: Submission of written work

reexam

Exam type:
C: Submission of written work, External (7-point scale)
Exam variation:
C11: Submission of written work

Time and date