Search programme

​Use the search function to search amongst programmes at Chalmers. The study programme and the study programme syllabus relating to your studies are generally from the academic year you began your studies.

Syllabus for

Academic year
DAT255 - Software engineering project  
 
Syllabus adopted 2015-02-12 by Head of Programme (or corresponding)
Owner: TKITE
7,5 Credits
Grading: TH - Five, Four, Three, Not passed
Education cycle: First-cycle
Major subject: Computer Science and Engineering, Information Technology
Department: 37 - COMPUTER SCIENCE AND ENGINEERING


Course round 1

The course in sp1 is only open for students enrolled to TKITE and TIDAL
Teaching language: English

Course module   Credit distribution   Examination dates
Sp1 Sp2 Sp3 Sp4 Summer course No Sp
0111 Project 3,0 c Grading: TH   3,0 c    
0211 Written and oral assignments 4,5 c Grading: TH   4,5 c    

In programs

TKITE SOFTWARE ENGINEERING, Year 2 (compulsory)
TIDAL COMPUTER ENGINEERING, Year 3 (compulsory)

Examiner:

Universitetslektor  Jan-Philipp Steghöfer



Course round 2


Teaching language: English

Course module   Credit distribution   Examination dates
Sp1 Sp2 Sp3 Sp4 Summer course No Sp
0111 Project 3,0 c Grading: TH   3,0 c    
0211 Written and oral assignments 4,5 c Grading: TH   4,5 c    

In programs

TKIEK INDUSTRIAL ENGINEERING AND MANAGEMENT - Information technology, Year 3 (compulsory)
TKDAT COMPUTER SCIENCE AND ENGINEERING, Year 3 (elective)

Examiner:

Universitetslektor  Jan-Philipp Steghöfer




  Go to Course Homepage

Eligibility:

In order to be eligible for a first cycle course the applicant needs to fulfil the general and specific entry requirements of the programme(s) that has the course included in the study programme.

Course specific prerequisites

To be eligible for the course the student must have passed a minimum of two courses in programming or programming projects.

Aim

The course is intended to provide the students with the basic knowledge, and first experience, in the area of software engineering through practical project work.

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

After completion of this course the student should possess the following understanding, skills, abilities and judgement:


  1. Knowledge and understanding, the student should:

    1. identify the complexities of software design and development

    2. describe the fundamentals of software engineering, such as stakeholders and requirements

    3. describe the difference between the Customer, the Solution, and the Endeavour as well as the different methods used for each


  2. Skills and abilities, the student should:

    1. elicitate requirements from and design a solution to a real-world problem

    2. plan and execute a small software development project in a team

    3. apply skills from programming courses and other relevant courses in a project-like environment

    4. learn new tools and APIs on his/her own


  3. Judgement and approach, the student should:

    1. reflect on the choice of software engineering methods used in the project



Content

<p>The course provides a practical introduction to Software Engineering. Students work in teams to learn to apply concepts from software engineering, such as requirement elicitation or processes, as well as how to organize and manage a team. A series of lectures introduce software engineering concepts on a theoretical level as well as (technical) background to the task the students are to solve and the tools required. It is up to every team to adapt the theory and use the tools to define their own way of working.</p>

Organisation

The course is organized as a project where the students work in teams of usually six students to address a real-world software engineering task. The teams have weekly supervision meetings. The project is supplemented by lectures that provide insight into the task the students are working on and software engineering in general.

Literature

Course literature will be announced on the course webpage.

Examination

The course is examined in two parts: a project deliverable (source code, binary, and documentation) and a final report that reflects on the project decisions and outcome. These together are weighted and scored on a scale 0 to 100. Detailed weights and grading criteria are available in the Course PM. The scores are set on a group level but are adjusted for individual contribution.


Page manager Published: Mon 28 Nov 2016.