Requirements in Agile Development

5 credits

Syllabus, Master's level, 1MD200

A revised version of the syllabus is available.
Education cycle
Second cycle
Main field(s) of study and in-depth level
Computer Science A1F, Human-Computer Interaction A1F, Technology A1F
Grading system
Pass with distinction, Pass with credit, Pass, Fail
Finalised by
The Faculty Board of Science and Technology, 30 August 2018
Responsible department
Department of Information Technology

Entry requirements

120 credits. 15 credits in human-computer interaction at Master's level, or 30 credits in computer science/information systems including Software Engineering and Project Management. Proficiency in English equivalent to the Swedish upper secondary course English 6.

Learning outcomes

On completion of the course, the student should be able to:

  • describe and apply elicitation and handling of users' and other stakeholders' requirements;
  • descibe the conditions for measurability of both functional and non-functional requirements;
  • describe and apply usability and evaluation work in agile software engineering projects;
  • critically account for, categorize and compare agile development to other software engineering models and justify and defend their analysis orally and in writing;
  • adapt software engineering models, roles and processes to actual conditions, given the goal of delivering an end product that corresponds to the intended users' needs.


The aim of this course is to provide practical knowledge in how one applies theories from human-computer interaction in agile software engineering processes to develop computerized systems and tools that corrspond to intended users' needs. Topics covered are:

Introduction to usability, user centred design, software engineering and software engineering processes. Agile development, analysis of the context of use, requirement specifications and analysis, use cases. Techniques for observation-interview, contextual design, prototyping and participatory design. Evaluation methods. Specification of roles and processes for user centred system design.


Lectures, exercises, and project.


Verbal and written presentation of individual assignments and group project. Optional take-home exam for higher grades.

If there are special reasons for doing so, an examiner may make an exception from the method of assessment indicated and allow a student to be assessed by another method. An example of special reasons might be a certificate regarding special pedagogical support from the disability coordinator of the university.

Other directives

The course may not be included in the same higher education qualifications as 1MD000 User-Centred Systems Design.