Course syllabus adopted 2025-02-03 by Head of Programme (or corresponding).
Overview
- Swedish nameKravhantering
- CodeDAT357
- 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 52150
- Maximum participants15
- 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 |
|---|---|---|---|---|---|---|---|
| 0125 Written and oral assignments 3 c Grading: TH | 3 c | ||||||
| 0225 Examination 4.5 c Grading: TH | 4.5 c |
In programmes
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 a 7.5 credits course in programming (e.g., Fundamentals of Programming, or equivalent) and 7.5 credit project course (e.g., Project: Agile Software Project Management).Aim
The course purpose is to prepare students to recognize and successfully apply requirements engineering in practice.Learning outcomes (after completion of the course the student should be able to)
Knowledge and understanding- Identify key RE concepts such as functional and non-functional
- requirements, stakeholders, assumptions, constraints, specifications, priority, and scenarios
- Understand quality characteristics of requirements
- 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
- Identify key non-functional requirements for software, such as usability, security, safety, and sustainability.
- Apply creativity techniques to generate requirements
- Apply concepts to write and evaluate requirements with high quality
- Capture requirements in different textual formats
- Draw several types of requirements models
- Link textual requirements to requirements as captured in models
- Use various techniques to prioritize requirements
- Evaluate and select between available elicitation techniques
- Evaluate the suitablity of ideas generated via requirements creativity techniques
- Evaluate benefits and drawbacks of different requirements representations
- Evaluate the impact of RE 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. It provides a solid foundation by defining foundational concepts like stakeholders, requirements, and specifications. It presents the process of eliciting, identifying, modeling, and documenting the requirements of a software product. The course covers desired characteristics of requirements. Emphasis is given to concepts and techniques such as quality requirements (e.g., usability, sustainability, security, privacy), creative requirements, and scenarios.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 of students.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 about disability study support.