Course syllabus adopted 2024-01-26 by Head of Programme (or corresponding).
Overview
- Swedish nameDatatekniskt projekt
- CodeDAT290
- Credits7.5 Credits
- OwnerTKDAT
- Education cycleFirst-cycle
- Main field of studyComputer Science and Engineering, Electrical 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 49129
- 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 |
|---|---|---|---|---|---|---|---|
| 0112 Project 7.5 c Grading: TH | 7.5 c | 0 c | 0 c | 0 c | 0 c | 0 c |
In programmes
Examiner
Arne Linde- Studierektor, 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
Completed courses in Introduction to Computer Engineering and Embedded Systems Programming.Aim
This course aims to give the student basic and general skills in heading and participating in technical development projects, entailing coordinated work in a project group, involving planning, execution and follow up, with emphasis on written communication. The course also aims to give the student technical skills in the design, integration and verification of hardware and software for processor-based systems.Learning outcomes (after completion of the course the student should be able to)
1. design, verify and demonstrate a microprocessor system that consists of a microprocessor and appropriate peripherals (possibly also some interface electronics and a graphical user interface) to meet specified functionality and performance.2. write a C program for a microprocessor with focus on management of peripherals.
3. demonstrate basic skills in managing and following up a technical development project in a group of a handful of developers, as well as reflecting upon group works with different aspects of equality, diversity, and equal treatment, for example, different group sizes, interdisciplinary constellations, gender, and social backgrounds.
4. with the support of the basic functions of a version control system, organizing ongoing documentation, reports, and program code.
5. write a basic project plan prior to a technical development project.
6. write a project report at the conclusion of a technical development project as well as critically examine another project.
7. reason about choices and conclusions, their background and their consequences, in his/her own project as well as for another project.
Content
Design and verification of a microprocessor system, which includes a microprocessor and some peripheral devices, that is developed for specific functionality and performance. Methodology for project work, including planning, execution, follow up and version control. Technical writing including technical documentation, minutes and final report.Organisation
Initially the lectures introduce the features of the microprocessor system that facilitate technical assessments and system design choices. In addition, the early lectures highlight how to run and document technical development projects, including aspects such as technical writing, group dynamics, and version control.The project team, which is assembled by the teacher team, selects a project from a limited number of offered projects. In connection with the project selection, a project mentor, who provides support during the project, is assigned to each project team. During the first two study weeks, the project team is focused on assimilating technical documents and on preparing a project plan.
The system implementation work commences during study week 3 and runs, supported by weekly project meetings and continuous documentation, until the final two study weeks when the work on system verification, demonstration preparation, and final documentation is intensified.
Literature
Manuals and data sheets.Examination including compulsory elements
The course, which is run with project groups of 6-8 students, leads to individual grades (U, 3, 4 and 5 respectively). The grade is based on different interacting parameters, namely the quality of project work (planning, project effort), technical quality (compliance with project plan, quality of final product), and quality of written communication (disciplinary language, information structure, rhetoric, audience adapted argumentation).Assessments are carried out for four distinct deliverables: 1) project plan, 2) opposition note on another group's draft of the final report, 3) project demonstration, and 4) final report. In addition, assessments are done on several occasions during the course with respect to the project meeting management and version control. The assessments above lead to a group grade. Based on each student's contribution to the project work, an individual grade, which may be higher or lower than the group grade, is established.
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.