Course syllabus adopted 2022-01-27 by Head of Programme (or corresponding).
Overview
- Swedish nameKravhantering och användarupplevelse
- CodeDAT356
- Credits7.5 Credits
- OwnerTKITE
- Education cycleFirst-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 52113
- Maximum participants15
- Open for exchange studentsNo
Credit distribution
Module | Sp1 | Sp2 | Sp3 | Sp4 | Summer | Not Sp | Examination dates |
---|---|---|---|---|---|---|---|
0121 Written and oral assignments 3 c Grading: TH | 3 c | ||||||
0221 Examination 4.5 c Grading: TH | 4.5 c |
|
In programmes
- TIDAL - COMPUTER ENGINEERING - Common branch of study, Year 3 (compulsory elective)
- TKITE - SOFTWARE ENGINEERING, Year 2 (elective)
- TKITE - SOFTWARE ENGINEERING, Year 3 (elective)
Examiner
- Jennifer Horkoff
- Associate Professor, Interaction Design and Software Engineering, 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
To be eligible for this course, students must have completed at least 7,5 higher education credits in object-oriented programming, e.g. TDA548Aim
The course purpose is to prepare students to recognize and successfully apply requirements and UX concepts and methods in practice.Learning outcomes (after completion of the course the student should be able to)
Knowledge and understanding- Identify key RE and UX concepts such as functional and non-functional requirements, usability, and UX design patterns
- Describe important differences between a variety of requirements modeling techniques
- Describe the benefits and drawbacks between specific elicitation techniques
- Explain the role of verification and validation in RE and UX
- Identify key non-functional requirements for software, such as usability and sustainability.
- Apply concepts to write good-quality requirements
- Draw several types of requirements models
- Capture personas and scenarios
- Apply UX design patterns to create prototypes from requirements
- Conduct and report on user studies
- Evaluate and select between available elicitation techniques
- Evaluate benefits and drawbacks of different requirements representations
- Evaluate the appropriateness of specific UX patterns for a design
- Evaluate and improve upon a UX design
- Evaluate the impact of RE & UX projects on sustainability goals such as reduced inequalities or responsible production and consumption
Content
The course provides students with an introduction to the field of requirements engineering and user experience. It provides a solid foundation by defining foundational concepts like stakeholders, requirements, usability and specifications. It also presents the process of identifying, modeling and documenting the requirements of a software product. Emphasis is given to concepts and techniques such as quality requirements (e.g., usability, sustainability, security, privacy), creative requirements, scenarios, and personas. The second part of the course focuses on usability aspects. The course will focus on implementing the requirements gathered in the first part as part of UX designs. Further, the course presents methods of prototyping (for example, digital mockups) and presents some techniques to evaluate the usability of a software product (for instance, via user studies). Finally, the course will provide students with hands-on experience in designing graphical user interfaces (GUI).Organisation
The teaching consists of lectures, group work, exercises, as well as supervision in connection to the exercises.Literature
Course literature to be announced 8 weeks prior to the start of the course.Examination including compulsory elements
The course is examined by an individual written exam carried out in an examination hall at the end of course and written assignments normally carried out in groups ofstudents. The assignments part is examined on the basis of solutions to compulsory problems handed in during the course and on the basis of individual contribution to the
group work.
Retake examinations of the assignments part consist of written group or individual assignments.
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.