På Svenska

EH2730 Requirements Engineering 7.5 credits

Kravhantering

Please note

This course is in the process of being cancelled.

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.

  • Educational level

    Second cycle

  • Academic level (A-D)

    D

  • Subject area

  • Grade scale

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

Last planned examination: Autumn 15

Course offerings

Autumn 12 for programme students

  • Periods

    Autumn 12 P2 (7.5 credits)

  • Application code

    51688

  • Start date

    2012 week: 43

  • End date

    2013 week: 1

  • Language of instruction

    English

  • Campus

    KTH Campus

  • Number of lectures

    18 (preliminary)

  • Number of exercises

    12 (preliminary)

  • Tutoring time

    Daytime

  • Form of study

    Normal

  • Number of places

    No limitation

  • Course responsible

    Robert Lagerström <robertl@kth.se>

  • Teacher

    Hannes Holm <haho@kth.se>
    Waldo Rocha Flores <waldorf@kth.se>

  • Target group

    Open for all programs

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 main content

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.

Eligibility

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

Prerequisites

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

Literature

  • To be determined

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

Examination

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

Requirements for final grade

Approved project assignment and presence at seminars

Offered by

EES/Industrial Information & Control Systems

Contact

EH2730@ics.kth.se, Waldo Rocha Flores

Examiner

Robert Lagerström <robertl@kth.se>

Supplementary information

If you have any questions regarding the course, please contact: EH2730@ics.kth.se

Add-on studies

EH2770 IT Management with Enterprise Architecture I

Version

Course plan valid from: Autumn 10.
Examination information valid from: Autumn 07.