Course syllabus adopted 2021-02-26 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 52139
- Open for exchange studentsNo
- Only students with the course round in the programme overview.
Credit distribution
Module | Sp1 | Sp2 | Sp3 | Sp4 | Summer | Not Sp | Examination dates |
|---|---|---|---|---|---|---|---|
| 0109 Project 7.5 c Grading: TH | 7.5 c |
In programmes
Examiner
Jonas Almström Duregård- Senior Lecturer, Computing Science, Computer Science and Engineering
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
- Explain development methods in technical projects, especially software projects.
- Describe the phases of a development project: problem identification, problem description, user analysis, specification, design, implementation, testing, evaluation, etc.
- Describe basic concepts in software development, e.g. requirements and development process.
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 a basic requirements specification and the 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.
Judgement and approach
- Reflect on good object-oriented design and implementation in the project.
Content
The course presents a simple, test-driven, object-oriented process. We introduce concepts such as: iterative development, object-oriented analysis and design, and domain and design model. 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 page in due time.
Examination including compulsory elements
The course will be examined with an oral presentation of the project, submission of source code as well as a final report, in which the students document the project specification and the design. In addition, students will do a peer review of others' design and code, which is included in the final report. These three parts (oral presentation, report, and code) are weighed together for the final grade. The details of the grading criteria and the weights will be made available in the course-pm. The grades will be given on the group level, but the final grade is given individually, based on the students' individual contribution.
We use the following grading scale: failed (U), 3, 4, 5.
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 on educational support due to disability.