Search programme

​Use the search function to search amongst programmes at Chalmers. The study programme and the study programme syllabus relating to your studies are generally from the academic year you began your studies.

Syllabus for

Academic year
DAT231 - Requirements engineering
 
Syllabus adopted 2015-02-12 by Head of Programme (or corresponding)
Owner: MPSOF
7,5 Credits
Grading: TH - Five, Four, Three, Not passed
Education cycle: Second-cycle
Major subject: Computer Science and Engineering, Industrial Engineering and Management, Information Technology
Department: 37 - COMPUTER SCIENCE AND ENGINEERING

The current course round has limited places. Please contact the student center if you are not able to add the course to your selection.
Teaching language: English
Open for exchange students

Course module   Credit distribution   Examination dates
Sp1 Sp2 Sp3 Sp4 Summer course No Sp
0114 Project 3,5c Grading: TH   3,5c    
0214 Examination 4,0c Grading: TH   4,0c   25 Oct 2016 pm L,  21 Dec 2016 pm L,  15 Aug 2017 am L

In programs

MPIDE INTERACTION DESIGN AND TECHNOLOGIES, MSC PROGR, Year 2 (elective)
MPSOF SOFTWARE ENGINEERING AND TECHNOLOGY, MSC PROGR, Year 1 (compulsory)

Examiner:

Univ lektor  Eric Knauss


Replaces

DAT230   Requirements engineering


  Go to Course Homepage

Eligibility:


In order to be eligible for a second cycle course the applicant needs to fulfil the general and specific entry requirements of the programme that owns the course. (If the second cycle course is owned by a first cycle programme, second cycle entry requirements apply.)
Exemption from the eligibility requirement: Applicants enrolled in a programme at Chalmers where the course is included in the study programme are exempted from fulfilling these requirements.

Course specific prerequisites

To be eligible for this course the student should 1) have a bachelor degree in Software Engineering, Computer Science or equivalent, including a successfully completed course in programming (e.g. DAT042, DAT050, DAT055, DAT170, TDA545, TDA550 or equivalent), and 2) a successfully completed course in practical software development or software engineering project (e.g. DAT255 Software Engineering Project).

Aim

One of the main challenges in software development is to make sure one is developing the right system, i.e. to understand the requirements that need to be fulfilled. The purpose of this course is how to learn how to find and collect requirements from relevant sources, both at the start and during a software development project, following established principles and formats for documenting and maintaining requirements..

Learning outcomes (after completion of the course the student should be able to)

Knowledge and understanding - after completion of the course the student must to be able to

  • explain why requirements engineering is a key to successful software engineering,
  • describe the challenges involved in requirements engineering,
  • explain the importance of identifying stakeholders and their knowledge, context and goals,
  • explain the difference between functional and quality requirements,
  • describe how to conduct bespoke (in-project/single-customer) requirements engineering in terms of common processes and techniques,
  • explain how market-driven differs from bespoke (in-project/single-customer) requirements engineering,
  • describe how requirements engineering in agile projects differ from traditional requirements engineering.


Skills and abilities - after completion of the course the student must to be able to

  • skilfully elicit software requirements,
  • clearly document software requirements according to industry standards and state-of-the-art,
  • prioritise requirements,
  • assure the quality of requirements and requirements specifications,
  • be able to assess current requirements engineering practices in a software project or a software development company.

 

Judgement and approach - after completion of the course the student must to be able to

  • suggest relevant improvements on requirements engineering processes in a convincing way,
  • trade-off the choice of requirements engineering methods and processes given a certain project context.

Content

One of the main challenges in software development is to make sure you are developing the right system, i.e. to understand the requirements that need to be fulfilled. The focus of this course is how to find and collect requirements from relevant sources both at the start and during a software development project. Different methods for this as well as different underlying principles and formats for documenting and maintaining requirements are covered.

In particular the course covers the problems that arise when requirements engineering is conducted in a fast-paced, cost-sensitive industrial reality. The following topics are included in the course:

Stakeholder Identification and Management

  • Requirements Elicitation
  • Writing Requirements and Requirements Specifications
  • Quality Assurance of Requirements
  • Prioritising Requirements
  • Connections and Alignment between Requirements Engineering and other Software Engineering activities
  • Requirements Engineering in In-Project vs. Market-driven Development
  • Requirements Engineering in Agile and Iterative/Incremental Development

Organisation

The course is organised as a series of lectures, workshops as well as project assignments.

Examination

The student is examined on the basis of assignments done in the project, a written exam done individually in an examination hall, and participation in all workshops.


Page manager Published: Mon 28 Nov 2016.