Course syllabus adopted 2021-02-26 by Head of Programme (or corresponding).
Overview
- Swedish nameIndustriellt projekt i mjukvaruutveckling
- CodeDAT306
- Credits15 Credits
- OwnerMPSOF
- Education cycleSecond-cycle
- Main field of studyComputer Science and Engineering, Software Engineering
- DepartmentCOMPUTER SCIENCE AND ENGINEERING
- GradingTH - Pass with distinction (5), Pass with credit (4), Pass (3), Fail
Course round 1
- Teaching language English
- Application code 24111
- Open for exchange studentsNo
Credit distribution
Module | Sp1 | Sp2 | Sp3 | Sp4 | Summer | Not Sp | Examination dates |
|---|---|---|---|---|---|---|---|
| 0118 Written and oral assignments 15 c Grading: TH | 15 c |
In programmes
Examiner
Regina Hebig- Senior Lecturer, Interaction Design and Software Engineering, Computer Science and Engineering
Eligibility
General entry requirements for Master's level (second 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
English 6 (or by other approved means with the equivalent proficiency level)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
To be eligible for the course, at least 45 credits must come from courses on the advanced level withing the area of software engineering, including the following courses: DAT231 Requirements Engineering, DAT321 Software Quality, DAT246 Empirical Software Engineering, and DAT366 Project Management, or equivalent.
"To be admitted to the course the student must
1) demonstrate by a signed letter of support that there is interest in a company to collaborate with the student under conditions described in the course objectives,
2) identify an academic supervisor who is committed to supervise the student and monitor the progress towards the learning goals,
3) provide a planning report that clearly defines the project goals, the project execution, and how the project relates to the learning goals.
Students get admitted on approval of the planning report."
"The subject of the proposed project should be in the field of software engineering. The planning report should describe:
- which company offers the practice placement to the student, including the contact persons and written consent/invitation from the company,
- which academic supervisor will monitor the progress towards the learning goals,
- project assumptions in the form of initial problem formulation,
- forms of project work, including the timeframe,
- deliverables from the student project to the company,
- how potential questions about intellectual property rights should be resolved."
Aim
The course aims to apply theoretical knowledge in practice to learn about considerations and trade-offs between theory and practice, and to build an in-depth understanding of a selected problem area in software engineering.Learning outcomes (after completion of the course the student should be able to)
After completing the course, students should be able to:
1: Knowledge and understanding
- describe the differences between the theoretical and practical principles (and assumptions) of how - software engineering methods are or should be used
- identify a number of software engineering methods applicable to solve the problem at hand and point to the appropriate empirical research showing their capability to solve the industrial problem
- distinguish software engineering problems from other types of problems, e.g. those related to hardware
2: Competence and skills
- solve the problem at hand using the chosen methods
- apply the knowledge from courses in the area of software engineering to contribute to the development of the host company
- choose the most appropriate method under the circumstances which are relevant for the host company
3: Judgement and approach
- reflect over the theoretical assumptions of the applied software engineering methods
- evaluate the contribution of the project to the development of the host company both in the short and in the long run
Content
This course is formed mainly by an individual project placed at a software development company. The project contains parts which in practice test whether the knowledge obtained in the program is applicable in the practice.The students in this course are expected to apply in practice their knowledge and contribute to the normal operations of the hosting company. The students have to show that they are capable to identify industrial problems where advanced knowledge in software engineering can be applied. The problem should also be solved.
The project should include comparison of different methods which could potentially be used to solve the problems. The comparison should include a reflection over theoretical principles and assumptions of the methods and their relation to the industrial constraints and practices.
Organisation
Literature
The course literature will be decided before the start of the course.Examination including compulsory elements
The course is assessed through an individual written final report, and a demonstration of the project results.
The final report is a written document which describes how the learning outcomes of the course were achieved and in which way the project contributed to the development of the company. The report should be accompanied by a demonstration of the main results of the project to the examiner.
The grading scale comprises Fail (U), 3, 4 or 5.
"In order to pass the course both the final report and the demonstration have to be approved.
The final grade in the course is decided from the grade of the final report."
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.