Course Outline

Course Title Software Requirements Engineering

Course Code SE-391
Course Material Available at:
1- \\printsrv\Teacher Data\MuhammadNadeem\SRE

Course Email Muhammad.Nadeem@pucit.edu.pk

Instructor Muhammad Nadeem
Teacher N/A
Assistant(s) (T.A)
Credit Hours 3
Theory/week:
Weight 3 Cr. hrs.
Lectures: 2
Duration 1.5 hrs.
Prerequisite Course Introduction to Software Engineering
Program Name BS [Software Engineering]]
Aims and This course focuses on the elicitation, documentation, development, evolution,
Objectives validation and management of software requirements using various renown techniques
and templates.
Learning Outcomes 1. Understand what, why and who of software requirements
2. Comprehend requirements elicitation using requirements gathering techniques
3. Capable to avoid ambiguity in writing software requirements
4. Design SRS and models to define and refine the software requirements.
5. Apply software development techniques effectively
6. Train for the management and validation of software requirements.
7. Hands on experience for risk management
8. Capable to select and use appropriate requirements engineering tool
Syllabus Introduction to Requirements Engineering, Software Requirements, classification of
requirements, Requirements process, Levels/layers of requirements, Requirement
characteristics, Analyzing quality requirements, Software requirements in the context
of systems engineering, Requirement evolution, requirement traceability, requirement
prioritization, trade-off analysis, risk analysis and impact analysis, Requirement
management, interaction between requirement and architecture, Requirement
elicitation, elicitation sources and techniques, Requirement specification and
documentation, specification sources and techniques, Requirements validation and
techniques, Management of Requirements, Introduction to Management, Requirements
Management Problems , Managing Requirements in an Acquisition Organization,
Supplier Organizations, Product Organizations, Requirements engineering for agile
methods.
Text Book(s) A. Software Requirements, Wiegers K. &Beatty J., 3rd Ed. Microsoft Press, 2013.
(Available at: https://www.dirzon.com/file/telegram/HiLCoE%20-
%20DRB1802/Microsoft%20Press%20Software%20Requirements%203%203rd
%20Edition%20Aug%202013.pdf )Applying UML and design patterns, 2nd
Edition by Craig Larman.
Reference Material B. Requirements Engineering, Elizabeth Hull, Ken Jackson and Jeremy Dick. 3rd Ed,
Springer-Verlag London Limited, 2011.
C. Engineering and Managing Software Requirements, AybükeAurum and Claes
Wohlin (Eds.), 5th Ed.
D. Requirements Engineering and Management for Software Development Projects,
Chemuturi M., Springer New York, 2013

Assessment Criteria Sessional ………………… Mid ……… Final ………

25% 35% 40%
Quizzes 10 Written Exam Written Exam
……………… ………………
Assignments 10 …35 …40

Project 5

25 35 40
Total
100

Lecture Breakdown
Week Lecture Topic Source
1 1 Introduction of the course Ch. 1 of Book
Introduction to Requirements Engineering, A
Need of Requirements Engineering
Why To Study Requirement Engineering

2 Project Success & Failure Factors Ch. 1, 9 of

Key Success Factors In RE Book A
classification of requirements, Requirements process, Levels/layers of
requirements
2 3 Misconceptions About Requirement Engineering, Introduction to Ch. 1, 2, Table
Requirements process, Development and management , The Expectation 3.1, 3.2 ,Fig.
gap 3.1 of Book A

4 Ch. 3: Table
Requirements engineering good practices, Iterative Process of
3.1, Fig. 3.1 of
Requirements development.
Book A
3 5 Ch. 3: Table
Implementing requirements engineering good practices, A representative
3.2, Fig. 3.2 of
requirements development process
Book A

6 Ch. 3:Fig. 3.1

Requirements Development Process and activities
of Book A

4 7 Ch. 6 of Book
Sources of Requirements including all types of stakeholders
A
8 Ch. 4 of Book
Software requirements in the context of systems engineering
A
5 9 Defining business requirements, Identifying desired business benefits, Ch. 5 of Book
Product vision and project scope with its template A
10 Ch. 5 of Book
Conflicting business requirements, Business Requirements Document
A
6 11 Vision and scope document, Scope representation techniques using Ch. 5 of Book
context diagram A
12 Ch. 5 of Book
Scope representation techniques using feature tree and event list
A
7 13 Requirements elicitation , Requirements elicitation techniques, Planning Ch. 6 of Book
elicitation on your project A

14 Preparing for elicitation, Performing elicitation activities, Ch. 7 of Book

Following up after elicitation, A
8 15 Classifying customer input, Assumed and implied requirements Ch. 7 of Book
A
16 Pre Mid Term review
Mid Term Examination
9 17 Paper Solution and Paper Show
18 Ch. 7 of Book
Requirements Elicitation Techniques (Interviews and workshops,
A, Ch. 2 of
System Interface Analysis with examples)
Book C
10 19 Ch. 7 of Book
Requirements Elicitation Techniques (Observations and Questionnaires,
A, Ch. 2 of
User interface Analysis with examples)
Book C
20 Introduction to Documenting the software requirements: Software Ch. 10 of Book
requirements specification, labeling the requirements, User Interfaces A
and SRS.
11 21 Software Requirements Specification Template (SRS): Ch. 10 of Book
1.Introduction, 2.Overall description, 3.System features, 4. Data A, Ch. 5 of
requirements, 5. External interface requirements, 6. Quality attributes, 7. Book D
Internationalization and localization requirements, 8. [Other
requirements], Appendix A: Glossary, Appendix B: Analysis models
22 Characteristics of Excellent Requirements and Requirements Ch. 11 of Book
Collections A
12 23 Ch. 11, Table
11.2 of Book
Guidelines for Writing Requirements: Writing Styles, Levels of Details, A, FYP
Avoiding Ambiguities Deliverable 1
of PUCIT

24 Requirements Priorities: Reasons to prioritize requirements, Some Ch. 16 of Book

A, Ch. 4 of
prioritization pragmatics, Some prioritization techniques: In or Out,
Book C, FYP
Pairwise comparison and rank ordering, Three-level scale, MoSCoW
Deliverable 1
and $100. of PUCIT
13 25 Requirements Validation and Techniques, Reviewing Requirements, Ch. 17 of Book
Prototyping Requirements, Testing the Requirements with Acceptance A
Criteria, Acceptance Tests
26 Ch. 27 of Book
Requirements Management: Why Manage Requirements? Requirements A, 10.3.3
Management Process, Requirements Version Control, Requirements Requirements
Attributes, Tracking Requirements Status, Resolving Requirements
Management
Issues with respect to Acquisition Organization, Supplier Organizations,
of Book C, Ch. 7
Product Organizations
of Book D
14 27 Requirements Traceability: Tracing Requirements, Motivation for Ch. 29 of Book
Tracing Requirements, The Requirements Traceability Matrix, A, Ch. 9 of
Requirements Tracing tools and procedure Book D,
28 Tools for Requirements Engineering: Elicitation tools, Prototyping Ch. 30 of Book
tools, Modeling tools, Requirements Management tools, Selecting and A
Implementing a requirements tools
15 29 Requirements engineering for agile methods: Agile Development Ch. 20 of Book
Approach, Essential aspects of agile approach to requirements, Adapting A
requirements practices to agile projects
30 Risk Management: Fundamentals of Software Risk Management, Ch. 32 of Book
Elements of Risk Management, Documenting Project Risks, A
Requirements related risk with respect to Requirements Elicitation,
Analysis, Specification, Validation and Management
16 31 Final Project Presentations
32 Post Mid Review and Paper Pattern
Final Term Examination