Monash Hub

Units / FIT2102

FIT2102 · Programming paradigms

Official Handbook

2027 Handbook6 credit pointsLevel 2Faculty of Information Technology

Last checked: 30 Sep 2026 UTC

Overview

This unit introduces the major ways of thinking about programs by comparing imperative, object-oriented, functional, and declarative styles of programming. It focuses on the underlying ideas that make languages expressive and useful, including abstraction, composition, data modelling, state and side effects, evaluation strategies, and the role of types in program design. You will learn to solve problems in more than one programming style, compare the clarity and maintainability of alternative solutions, and explain why different paradigms suit different types of problems. Through practical work, the unit develops the conceptual flexibility needed for later study in compilers, logic programming, and high-performance computing.

Areas of study: Advanced computer science Computational science

Offerings

CampusTeaching periodMode
MalaysiaSecond semesterTeaching activities are on-campus (ON-CAMPUS)
ClaytonSecond semesterTeaching activities are on-campus (ON-CAMPUS)

Assessment

The Handbook does not list a final examination among the assessment items. That is not a guarantee there is none.

#AssessmentTypeWeightHurdle
1Assignment 1 Functional Reactive ProgrammingProject30%—
2Assignment 2 Haskell ProgrammingProject30%—
3Applied quizzesQuiz / Test20%—
4Applied classworkExercise20%—

Assessment details may change. Please refer to the assessment information in Moodle closer to the start of the teaching period.

Requisites

Learning outcomes

  1. Identify gaps in your knowledge of programming paradigms to build independent capability across multiple styles of programming.
  2. Investigate programming problems by selecting and comparing appropriate paradigms, evaluating trade-offs in clarity, maintainability and expressive power.
  3. Design, code, test and document programs across imperative, object-oriented, functional and declarative styles, applying agreed conventions and verifying behaviour systematically.
  4. Examine software designs in a paradigm-appropriate form, contributing to design documentation that explains why a chosen abstraction or composition is suited to the problem at hand.

Workload

Minimum total expected workload to achieve the learning outcomes for this unit is 144 hours per semester typically comprising a mixture of scheduled online and face to face learning activities and independent study. Independent study may include associated reading and preparation for scheduled teaching activities.

ActivityDuration
Applied sessions24 hours
Workshops24 hours

Ask about FIT2102

Answered from the Handbook fields above — no AI, no guessing. Every answer links back to the source.

Community discussions about FIT2102

Community

Student experience, not official rules. Nothing here changes what the Handbook says.

No discussions yet

Be the first to share what this unit was actually like.