At the end of this course the students will be able to:

 understand the importance of requirement engineering in system development Know the tech-
niques of requirement elicitation
 Understand the role of requirement document in the development process
 Write requirement specification documents
 Appreciate how the requirement directly or indirectly affects the product.
 Know about different types of requirements
 Understand the role of stakeholders in the RE process
 Elicit requirements using different elicitation techniques
 Specify and document requirements
 Validate documents
 Prioritize requirements

Course Contents
Weeks Lecture Topics Reading /Assignments
1 Chapter 1: Introduction to Requirement R1: pg.1-24, 187-214
Engineering R2: pg.1-36
 What is requirement engineering? R3: pg.1-16, 135-202
 Software Requirements Engineering: R4: pg.1-14,
What, Why, Who, When, and How R5: Part I (Chapter 1, 2 & 3)
 Non-functional requirements R6: pg.1-60
2 Chapter 2;Requirement Engineering Process R1: pg. 25-52
 Process Models R3: pg. 19-63, 283 - 302
 Actors in Requirements engineering process R4: pg.25-46
 Process support R5: pg. part II (chapter 5, 6 &
 Process Improvement 7)
3-5 Chapter 3:Requirement Elicitation and Analysis R1: pg. 53-86
 Elicitation and Analysis Process R2: pg. 63-160
 Elicitation Techniques R3: pg. 67-92
 Prototyping R6: pg. 61-105
 Requirement Analysis and Negotiation R12, R13 & R16
R11: Part II (Chapter 7)
6 Chapter 4:Requirement Specification R2: pg. 161;188, 299-330
 Modelling R3: pg. 223-258
 Writing requirement documents R4: pg. 47-92
R11: Part II (Chapter 13)
7-8 Chapter 5:Requirement Validation R1: pg. 87-112
 Requirement review R2: pg. 189-214
 Prototyping R4: pg. 159-180
 Model validation R5: Part II (Chapter 15)
 Requirement testing R11: Part II (Chapter 17)
9-10 Chapter 6: Requirement Management R1: pg. 133-136
 Stable and volatile requirements R2: pg. 215-254
 Requirements identification and storage R6: pg. 109-126
 Change management R5: Part III (All chapters)
 Traceability R15
11 Chapter 7: Requirement Engineering tools R11:Part IV (chapter 30)
 12- Chapter 8: Requirement Engineering Techniques R1: pg. 137-186
13  Methods for RE R2: pg. 359-388
 Viewpoint-oriented Requirements Methods
14 Chapter 9: Software Requirements and Risk R5: Part IV (Chapter 23)
Management R11:Part V (chapter 32)

Summary of Teaching Learning Methods

The teaching-learning methodology will be student-centered with appropriate guidance of instructor/s
during the student’s activities .There will be Lecture, Demonstrations, Tutorials, Reading assignments
and Group Discussions
Assessment Methods: - As per the academic regulation

References
R1. Gerald Kotonya and Ian Sommerville (1998). Requirement Engineering: Process and
Techniques. UK, John Wiley and Sons LTD. (Textbook)
R2. Ian Sommerville & Pete Sawyer (1997). Requirement Engineering : A Good Practice Guide. UK,
John Wiley and Sons LTD.
R3. Suzanne Robertson, James Robertson (2006). Mastering the requirements Process Second Edition,
Addison Wesley Professional.
R4. Hull, Jackson and Dick(2010).Requirements Engineering, 2nd ed. Spring.
R5. Karl E. Wiegers (2003). Software Requirements, Second Edition.
R6. Ralph R. Young (2004). The Requirements Engineering Handbook. ARTECH HOUSE,INC.
R7. Soren Lauesen (2002).Software requirements: Styles and techniques. Addison-Wesley.
R8. Ian K Bray and Ian Bray (2002). An Introduction to Requirements Engineering.
R9. Johan F. Hoorn(2006). Software Requirements: Update, Upgrade, Redesign- Towards a Theory of
Requirement Change. Vrije Universiteit.
R10. Catherine Courage and Kathy Baxter (2005). A Practical Guide to User Requirements Methods,
Tools, and Techniques. Elsevier Inc.
R11. Karl E. Wiegers , Software Requirements, Third Edition Microsoft Press 2013