5 ECTS credits/134 hours of work
|Language of instruction
rd year, autumn semester, period 2
After completing this course, the student can analyse the
requirements from the problem-domain and solution-domain
viewpoints, and understands the special issues associated with
these viewpoints. The student can distinguish the roles of
problem-domain and solution-domain requirements for the customer
and developer; he/she is able to identify various project types and
knows which requirement style fits best to each project type. The
student will be familiar with various requirement definition styles
together with their pros and cons, and is able to use some of the
most important definition styles. Several requirements of
elicitation techniques will be added to the student’s toolbox
with the skills of mastering some of them. The principles of
requirements management, validation and verification during the
product life cycle will be familiar to the student at the end of
Concepts of problem and solution domain. Requirements in
different use contexts. Description styles for functional and
non-functional requirements. Validation and verification of
requirements. Requirements negotiation and prioritisation. Release
planning. Requirements management during the product life cycle.
|Mode of delivery
The tuition will be implemented as face-to-face teaching.
|Learning activities and teaching methods
Lectures 32h, weekly assignments and project assignment about
|Prerequisites and co-requisites
We assume the basic skills from the following courses:
“811169P Introduction to Information System Design”,
“812346A Object-Oriented Analysis and Design”,
“811380A Basics of Databases”, “811335A Software
Engineering” and “812334A Information Systems
|Recommended optional programme components
|Recommended or required reading
S. Lauesen, Software Requirements – Styles and Techniques.
Pearson Education 2002; chapters 1–4 and 6–9. A.M.
Davis, Just Enough Requirements Management, Dorset House Publishing
2005; parts. Lecture slides.
|Assessment methods and criteria
Two ways of passing:
1) Active participation: weekly assignments and
project assignment (only for Finnish-speaking students)
2) Conventional exam
Active participation will be evaluated based on the weekly
assignments and the project work; the scale will be 1–5. The
exam will be evaluated on a scale of 1–5.
|Working life cooperation