PMAS Arid Agriculture University Rawalpindi

University Institute of Information Technology

CSE-454 Software Requirement Engineering

Credit Hours: 3(2-3) Prerequisites: None

At the end of course the students will be able to: Domain BT Level*
1. Explain the requirements engineering process C 2
2. Apply appropriate method(s) to specify a set of software C 3
requirements for a medium-sized software system.
3. Apply use case(s) to analyze system behavior and C 3
requirements.
4. Prepare both functional and non-functional requirements C 3
along with validation for a medium-size software system.
5. Describe how requirements engineering in agile projects C 2
differs from traditional requirements engineering.

Mapping of CLO with PLO

Program Learning CLO’s for Software Requirement Engineering
Outcomes (PLO’s) CLO-1 CLO-2 CLO-3 CLO-4 CLO-5
PLO-1  
PLO-2
PLO-3  
PLO-4 
PLO-5
PLO-6
PLO-7
PLO-8
PLO-9
PLO-10
PLO-11
PLO-12
Course Contents:
The focus of this course is how to find and collect requirements from relevant sources
both at the start and during software development. The topics include: Fundamentals of
software requirements engineering; Role of requirements engineering in software
lifecycle;requirements engineering process; requirements elicitation process and
techniques; requirements analysis and negotiation,; functional and non-functional
requirements; requirements engineering methods ;requirements modeling, requirement
documentation, requirements validation; requirement management and requirement
engineering for agile development.
Course Objective:
The aim of course is enable Software Engineering students in terms of requirement and
its types understanding, requirement elicitation, requirement analysis and negotiation,
requirement validation and management.
Teaching Methodology:
Lectures, Assignments, labs, Projects, Presentations, etc. Major component of the
course should be covered using conventional lectures.
Courses Assessment:
Exams, Assignments, Quizzes, Project, Presentations. Course will be assessed using a
combination of written examinations and project(s). Practical evaluation, using rubrics,
is encouraged and suggested to make up around 20% of the course.
Reference Materials:
Text Book(s):
1. Software Requirements, Wiegers K. &Beatty J., 3rd Edition (2013), Microsoft Press.
Reference Book(s):
2. Requirements Engineering and Management for Software Development Projects,
Chemuturi M., (2013), Springer New York.
3. Visual Models for Software Requirements, Beatty J. &Chen A., (2012), Mocrosoft
Press.
4. Requirements Engineering, Hull E., Ken Jackson K. &DickJ. 3rd Edition (2011),
Springer-Verlag.
5. Software & Systems Requirements Engineering: In Practice, Berenbach B., Paulish
D. J., Kazmeier J. &Rudorfer A., (2009) McGraw Hill.

Week Lecture Theory Practical

#
Introduction to the course, discussion
on preliminary concepts of Software
Lecture-I
Engineering and the importance of
Requirements Engineering process.
Week
Fundamental of Software requirements
1 Lecture-
engineering, What are requirements,
II
Some interpretations of” requirement”
Lecture-
III Types of requirements
Week Lecture-I Working with the three levels, Product Jira
2 vs. project requirements, Requirements
 development and management,
Reason behind bad requirements,
Benefits from a high-quality
requirements process.
Requirements development process
Lecture- framework. Good practices of
II Requirements elicitation, analysis,
specification
Lecture-
III Validation and management.
What are business requirements, Jira
Identifying business requirements,
Lecture-I vision and scope statement and
document, controlling and managing
Week project scope?
3 Defining requirement elicitation
Lecture-
process, requirement elicitation inputs
II
and outputs.
Lecture-
III Requirement elicitation task.
Lecture-I What are stakeholders? Jira
Lecture- Importance of stakeholder in
Week
II requirement elicitation process.
4
Lecture- Requirement elicitation techniques,
III Interviews, Workshops,
Focus groups, Observations,
Lecture-I
Questionnaires
Week Lecture- System interface analysis, User RCM
5 II interface analysis.
Lecture- Document analysis.
III
Class activity on requirement elicitation RCM
Lecture-I
process.
Presenting software project idea and
Lecture-
class exercise of performing
II
Week requirement elicitation activities.
6 Following up after elicitation,
Organizing and sharing the notes,
Lecture-
documenting open issues, classifying
III
customer input, Some cautions about
elicitation
Assumed and implied requirements, RCM
Lecture-I
Finding missing requirements.
Week Lecture- Understanding user requirement, Use
7 II cases, The use case approach.
Lecture- Use cases and usage scenarios,
III Identifying use cases.
Week Defining Business Rules, Classification Traceability
Lecture-I
8 of Business Rules,
Lecture- Documenting Business Rules,
 II Discovering business rules.
Lecture-
III Business rules and requirements.
Midterm Exam
Writing functional requirements, Traceability
Lecture-I deriving functional requirements from
the use case.
Characteristics of excellent
requirements, Characteristics of
Week
Lecture- requirement statements,
10
II Characteristics of requirements
collections, Guidelines for writing
requirements.
Lecture-
III System or user perspective.
Writing style, Level of detail, Traceability
Representation techniques, avoiding
Lecture-I
ambiguity, Avoiding incompleteness,
Week Sample requirements.
11 Lecture- What are Software Quality attributes or
II non-functional requirements?
Lecture- Classification of non-functional
III requirements.
Exploring and specifying non-functional Prioritization tool
Lecture-I
requirements
Conflicts related to non-functional
Week Lecture-
requirements, trade off to resolve
12 II
conflicts.
Lecture- Class exercise to elaborate non-
III functional requirements.
Requirements modeling, Data flow Prioritization tool
Lecture-I diagram, Swim lane diagram, State-
transition diagram, state table
Week
Lecture- Dialog map, Decision tables, decision
13
II trees
Lecture-
III Event-response tables
Documenting the requirements, Prioritization tool
Software requirement specifications,
Lecture-I
Discussing software requirements
specification template
Week
Requirements validation and
14 Lecture-
verification, Reviewing requirements,
II
inspection process.
Lecture-
III Requirements review challenges.
Week Prototyping requirements, Testing the
Lecture-I
15 requirements
Lecture- Validating requirements with
II acceptance criteria, Acceptance
 criteria,
Lecture-
III Acceptance tests.
Requirements Management: Planning
for requirements management,
Lecture-I
Requirements change management
process.
Week
Requirements tracing, Requirement
16 Lecture-
Traceability. Backward and forward
II
tractability, tracking and reporting
Lecture-
III Presentations
Finalterm Exam