SOFTWARE REQUIREMENT,

SPECIFICATION
Lecturer: Engr. Niqash Ahmad
COURSE INFORMATION
Lecture:
Engr: Niqash Ahmad
Monday: 09:00-10:00 PM (Section A), 12:45-01:45 PM
(Section C)
Tuesday: 11:20-12:20 PM (Section C)
Wednesday: 09:00-10:00 AM (Section B), 10:10-11:10 AM
(Section A), 12:45-01:45 PM (Section C)
Thursday: 09:00-10:00 AM (Section B), 10:10-11:10 AM
(Section A)
Friday: 09:00-10:00 AM (Section B)
Office Hours: Monday to Friday From 9:00am-04:00PM
(Any Time)
Course Title:
SE 313- Software Requirement Specification
Textbook
Managing Software Requirements: A Use Case Approach,
Second Edition By Dean Leffingwell, Don Widrig
COURSE OBJECTIVE
Objective of this course is to make students the
in-depth look at software requirement,
Specification.

Concepts will be reinforced by their

implementation in Documentation and semester
project
BOOKS
Text Book:
Managing Software Requirements: A Use Case
Approach, Second Edition By Dean Leffingwell,
Don Widrig
Reference Books
Chapter 7/8 Software engineering By Ian
Sommerville. 8th edition.
Karl E. Wiegers, Software Requirements, 2nd
Edition, 2003, Microsoft Press
Hull, Jackson, and Dick, Requirements
Engineering, 2004, Springer
GRADING
Quiz 5% (in the beginning of the class; on
previous lecture)
Homework/Programming Assignments 5%
(typically every week)
Attendance 5%

Semester Project 15%

Midterm 20%

Comprehensive Final 50%

COURSE POLICY
Your work MUST be your own
Zero tolerance for cheating
You get an F for the course if you cheat in anything
however small NO DISCUSSION
Homework
There will be penalty for late assignments (15% each
day)
Ensure clarity in your answers no credit will be given
for vague answers
INTRODUCTION TO SOFTWARE
REQUIREMENT ENGINEERING
A requirement is a technical objective which is
imposed upon the software, i.e., anything that might
affect the kind of software that is produced
A requirement may be imposed by Stakeholder.
the customer
the developer
the operating environment
The source, rationale, and nature of the requirement
must be documented
Requirements fall into two broad categories
functional
non-functional
OVERVIEW OF THE PROBLEM DOMAIN
AND THE SOLUTION DOMAIN
OVERVIEW OF THE PROBLEM DOMAIN
AND THE SOLUTION DOMAIN
Problem Domain:
we use a set of team skills as our map and compass to
understand the problem to be solved.
Needs:
to understand the needs of users and other
stakeholders whose lives will be affected by our
solution.
OVERVIEW OF THE PROBLEM DOMAIN
AND THE SOLUTION DOMAIN

Solution Domain:
To solve the problem by gathering there futures and
with there specific requirement.
1. Features:
A service provided by the system that fulfils one or
more stakeholder needs.
For Example futures of the system.
"The car will have power windows."
"The program will allow Web-enabled entry of sales
orders."
2. Software Requirements:
WHAT IS A SOFTWARE REQUIREMENT?
A software capability needed by the user to solve
a problem to achieve an objective
A software capability that must be met or
possessed by a system or system component to
satisfy a contract, standard, specification, or
other formally imposed documentation