Skip to main content

EH2730 Requirements Engineering 7.5 credits

Requirements describe how the product should behave once in operation. The product itself may be an information system, a space rocket or the service to operate a an underground train service. Simply put, requirements outline what a product should do, and does not bother with the design or implementation of the product.

Requirements engineering is the systematic process of stating  requirements on primarily software systems, but also more complex products involving both hardware and software. To be able to master this type of systematic engineering approach is beneficial to anyone who will be involved in development or procurement projects of any kind.

This course, Requirements Engineering, EH 2730, is an advanced course on methods and principles for system procurement and requirements engineering. Students attending the course Requirements Engineering will learn how to produce a requirements specification for a complex system.

The course focuses on practical, hands-on skills having to do with stating requirements and running procurement projects. Course assignments emphasize written and oral presentation. The course will equip students with tools and ideas that are useful to any future engineer, regardless of chosen business domain or work tasks.

After having completed this course a student should feel comfortable with and be proficient at using methods and techniques within the field of requirements engineering.

Course offerings are missing for current or upcoming semesters.
Headings with content from the Course syllabus EH2730 (Autumn 2010–) are denoted with an asterisk ( )

Content and learning outcomes

Course contents

The main topics of the course are:

  • The role of Requirements Engineering in the software development process.
  • The role of Requirements Engineering in the software procurement process
  • The difference between the User Needs Statement and the requirements specification
  • The concept of stakeholders
  • Creation of a vision statement for a system and identify stakeholders
  • The difference, and be able to identify, design constraints and requirements.

Intended learning outcomes

Upon course completion, a participants shall be able to:

  • Explain and give examples of the context of requirements engineering. Specifically to
  • Explain the significance of the early phases in development and procurement projects
  • Explain the difference between market driven and customer driven development
  • Explain what signifies requirements engineering in a development and a procurement project.
  • To explain and give examples of common process phases of requirements engineering and for each process phase explain and give examples of common
  • Participants and stakeholders
  • Documents
  • Activities
  • Methods
  • Tools
  • Describe and apply methods for modeling systems and system environments from technical as well as business oriented perspective and based on such models to
  • Elicit system requirements
  • Determine system constraints
  • Explain methods for formal evaluations of tender offers from system suppliers.
  • Analyze and appreciate the utility of using different methods, or combination of methods, for requirements elicitation given a set of circumstances.
  • Apply established methods and tools for requirements elicitation from different stakeholders
  • Apply rules of documentation for requirements specifications
  • Describe and apply methods for requirements analysis and negotiation, specifically to
  • Describe available methods for requirements prioritization and to apply at least one of these methods.
  • Apply methods and tools for requirements management from a life-cycle perspective, i.e. from the birth of the development/procurement project to the delivery and operations of the product.

Course disposition

No information inserted

Literature and preparations

Specific prerequisites

For single course students: 120 credits and documented proficiency in English B or equivalent

Recommended prerequisites

EH2720 Management of Projects
EH2710 Projektstyrning
or corresponding project assignments course.


No information inserted


  • To be determined

In addition, selected papers as introduced during the lecture series.

Examination and completion

If the course is discontinued, students may request to be examined during the following two academic years.

Grading scale

A, B, C, D, E, FX, F


  • PRO1 - Project, 1.5 credits, grading scale: P, F
  • PRO2 - Project, 1.5 credits, grading scale: P, F
  • PRO3 - Project, 3.0 credits, grading scale: P, F
  • SEM1 - Lecture, 1.5 credits, grading scale: P, F

Based on recommendation from KTH’s coordinator for disabilities, the examiner will decide how to adapt an examination for students with documented disability.

The examiner may apply another examination format when re-examining individual students.

Other requirements for final grade

Approved project assignment and presence at seminars

Opportunity to complete the requirements via supplementary examination

No information inserted

Opportunity to raise an approved grade via renewed examination

No information inserted


Ethical approach

  • All members of a group are responsible for the group's work.
  • In any assessment, every student shall honestly disclose any help received and sources used.
  • In an oral assessment, every student shall be able to present and answer questions about the entire assignment and solution.

Further information

Course web

Further information about the course can be found on the Course web at the link below. Information on the Course web will later be moved to this site.

Course web EH2730

Offered by

Main field of study

This course does not belong to any Main field of study.

Education cycle

Second cycle

Add-on studies

EH2770 IT Management with Enterprise Architecture I

Contact, Waldo Rocha Flores

Supplementary information

If you have any questions regarding the course, please contact: