Software Requirement Engineering Course outline - University of Sargodha

Course Title: Software Requirement Engineering

Course Code: SE-3342

Course Structure: Lectures: 3/Labs: 0

Credit Hours: 3

Prerequisites: CMP-3310 (Software Engineering)

Course Objectives:

To understand Issues in Requirements Engineering, to understand and apply Requirements
Engineering Process, to understand and use Requirements Elicitation and Specification, to
understand and use Formal Techniques, to understand modeling and analysis of Non-Functional
Requirements.

Course Syllabus:

Basics of Requirements Engineering.RE Processes.Requirements Analyst Role, Tasks, Essential

Skills & Knowledge.Dealing with Customers.Prototype Categories. Evaluation, Risks,

Validating the Requirements. Documenting the Requirements.Non Functional Requirements.

Software Quality Attributes. Setting Requirements Priorities.Special Requirements Challenges.

Requirements Development Plans. Requirements Management Principles and

Practices.Requirements Creeping.Tracing Requirements.Tools for Requirements

Management.Software Requirements Risk Management.

Course Outline:

1.     Requirements Engineering (RE): Essential Software Requirement, Bad Requirements,
Characteristics and Benefits Requirement Engineering, Requirements from the Customer's
Perspective [TB: Ch. 1&2]

2.      RE Processes: Requirements Elicitation, Requirements Analysis, Requirements
Specification, Requirements Validation, Requirements Management, and Requirements
Development Process [TB: Ch. 3].

3.      The Requirements Analyst Role, Tasks, Essential Skills & Knowledge, Defining the Vision
through Business Requirements, Vision and Scope Document[TB: Ch. 4&5]

4.      Dealing with Customers: Elicitation Techniques, Interviews, Surveys, Workshops,
Classifying Customer Input, Incomplete Requirements (Finding Missing Requirements) [TB:
Ch. 7+ handouts]

5.      Prototype Categories (Throwaway, evolutionary, paper and electronic), evaluation, Risks,
Validating the Requirements: Requirements Review and Inspection, Requirements Review
Challenges, Acceptance Criteria [TB: Ch. 13 & Ch. 15].

6.      Documenting the Requirements: The Software Requirements Specification, Labelling,
Dealing with Incompleteness, User Interfaces and the SRS, A Software Requirements
Specification Template, The Data Dictionary [TB: Ch. 10].

7.      Non Functional Requirements: Software Quality Attributes: Defining, Performance
Requirements, Defining Non-functional Requirements Using Planguage, Attribute Tradeoffs,
Implementing Non-functional Requirements [TB: Ch. 12].

8.      Setting Requirements Priorities: Why Prioritize Requirements? Play With Priorities, A
Prioritization Scale, Prioritizing Based on Value, Cost, and Risk [TB: Ch. 14].

9.      Special Requirements Challenges: Requirements for Maintenance Projects, Begin Capturing
Information, New Requirements Techniques, Follow the Traceability Chain, Consider
Business Rules, Requirements for Outsourced Projects, Requirements for Emergent Projects
[TB: Ch. 16].

10. Requirements Development Plans, Estimation, Scheduling, From Requirements to Designs,
Code, Tests and Success [TB: Ch. 17].

11. Requirements Management Principles and Practices, Baseline, Procedures, Requirements
Version Control, Tracking Requirements Status, [TB: Ch. 18].

12. Requirements Creeping, Managing Scope Creep, The Change Control Process, The Change
Control Board, Change-Control Tools, Measuring Change Activity, Impact Analysis [TB:
Ch. 19].

13.  Tracing Requirements introduction, The Requirements Traceability Matrix, Tools for
Requirements Traceability, Requirements Traceability Procedure, Is Requirements

Traceability Feasible? [TB: Ch. 20].

14.  Tools for Requirements Management: Benefits and Capabilities of tool for Requirements
Management, Requirements Management Automation, Selecting a Tool, Changing the
Culture [TB: Ch. 21].

15.  Software Requirements Risk Management: Fundamentals, Elements, Documenting Project
Risks, Planning for Risk Management, Requirements-Related Risks [TB: Ch. 23]

Class Assignments:

•         The requirements are for the development of case applications. Ask students to outline
business requirements, the product vision and scope for applications.

•         Use case elicitation using automated tools e.g. UML, Mobile Scenarios and PDA's etc

•         Development of Software Requirement Specification (SRS)

•         Requirement Engineering Group Discussion activity and resource allocation etc

Textbook(s):

•          Software Requirements 2 by Karl Wiegers, 2^nd Edition (2003). Microsoft Press; ISBN-
10:0735618798

Reference Material:

•         Requirements Engineering: Processes and Techniques, Kotonya and Sommerville, John
Wiley Sons, 1998. ISBN-10: 0471972088

•          Software Requirements Engineering, 2^nd Edition by Richard H. Thayer and Merlin
Dorfman, Wiley-IEEE Computer Society Pr; 2^nd Edition (1997). ISBN-10: 0818677384

•         Requirements Engineering: From System Goals to UML Models to Software
Specifications by A. van Lamsweerde, Wiley; 1^st Edition (2009). ISBN-10: 0470012706.

•         Requirements Engineering: Fundamentals, Principles, and Techniques by Klaus Pohl,
Springer; 1^st Edition (July 23, 2010). ISBN-10: 3642125778

rd

•         Requirements Engineering by Hull, Jackson, and Dick, Springer; 3 Edition (October 11,
2010). ISBN-10: 1849964041

Note: This content is obtained from official documents of University of Sargodha and applied on BS Computer Science for Main Campus, Sub Campuses, and Affiliated Colleges.