Course syllabus for Object-oriented programming project

Course syllabus adopted 2025-02-03 by Head of Programme (or corresponding).

Overview

  • Swedish nameObjektorienterat programmeringsprojekt
  • CodeTDA367
  • Credits7.5 Credits
  • OwnerTKITE
  • Education cycleFirst-cycle
  • Main field of studySoftware Engineering
  • DepartmentCOMPUTER SCIENCE AND ENGINEERING
  • GradingTH - Pass with distinction (5), Pass with credit (4), Pass (3), Fail

Course round 1

  • Teaching language Swedish
  • Application code 52141
  • Open for exchange studentsNo
  • Only students with the course round in the programme overview.

Credit distribution

0109 Project 7.5 c
Grading: TH		 7.5 c

In programmes

Examiner

Eligibility

General entry requirements for bachelor's level (first cycle)
Applicants enrolled in a programme at Chalmers where the course is included in the study programme are exempted from fulfilling the requirements above.

Specific entry requirements

The same as for the programme that owns the course.
Applicants enrolled in a programme at Chalmers where the course is included in the study programme are exempted from fulfilling the requirements above.

Course specific prerequisites

Passed the course TDA548 'Introductory software development' or equivalent, and TDA552 'Object-oriented Programming and Design' or equivalent.

Aim

The project course is designed to give knowledge and experience in professional development of software.

Learning outcomes (after completion of the course the student should be able to)

After completion of the course the student should have the following knowledge, skills, and abilities:

Knowledge and understanding

  • Describe basic concepts in software development, e.g. requirements and development process.
  • Explain development methods in technical projects, especially software projects.

Skills and abilities

  • Run a small-scale object-oriented software project in a group according to predefined development process and schedule.
  • Write a report of the project, containing basic specifications of requirements and design.
  • Apply skills from previous programming courses, such as design principles and patterns, in the design and development phase of the project.
  • Use modern software development tools, such as testing frameworks, build automation, and version management.
  • Design a clear and well-structured manual, aimed at end users.
  • Plan and conduct an oral presentation with a professional and academic approach.
  • Apply and describe skills, methods and tools to support inclusive collaboration in teams, and to handle common challenges in collaborative team work, including aspects of diversity, equity, and inclusion.

Judgement and approach

  • Reflect on good object-oriented design and implementation in the project.
  • Reflect on communicative, relational and organisational strategies that support inclusive collaboration in teams.
  • Reflect on the various parts of a software development project: problem identification, problem description, user analysis, specification, design, implementation, user feedback, testing, etc.

Content

The course presents a simple, test-driven, object-oriented process. Concepts such as iterative development, object-oriented analysis and design, and domain and design model, are introduced. Different aspects of design are reviewed: testability, dependencies, requirements, etc.

Organisation

We will have:

  • a few lectures,
  • a mandatory seminar,
  • and a couple of workshops.

In parallel to the above activities, the students will run a small but complete software project. The students will be divided into groups of four. The project includes mandatory weekly supervision meetings and an oral final presentation.

Literature

Possible course literature will be announced on the course webpage.

Examination including compulsory elements

The project is assessed based on several aspects (product, process, and presentation) and is then adjusted for each team member based on individual contribution. Assessment criteria for different aspects (e.g. quality, functionality, design, inclusivity, etc) and how they are weighed can be found in the course PM.

Passing the course requires:
  • a passable individual contribution to the project
  • participation in weekly supervision meetings
  • participation in the course’s compulsory presentations
  • submission of the course’s compulsory reflections
To obtain at least a passing grade (3) in the course, passing grades are required for the team project (process and product), for the individual contribution to the project, and for the oral presentations of the project. For a higher grade (4 or 5), the same aspects are required but with higher expectations. The final grade for an individual is calculated by weighing together the team grade and the individual contribution.

The course examiner may assess individual students in other ways than what is stated above if there are special reasons for doing so, for example if a student has a decision from Chalmers about disability study support.