Requirements

Engineering
Lecture 01
National University FAST
August 22, 2015, 18:00 21:00

Course Outline
Software
Requirements
Engineering
Overview

Business Value
of Better
Requirements

The Role of
Requirements
Analyst

Good Practices
for
Requirements
Engineering

Documenting
Software
Requirements

Course Outline
Quality Aspect
of
Requirements
Engineering

Requirements
Management
Principles and
Practices

Use Cases

Improving
Requirements
Processes

Risk
Management &
Software
Requirements

Marks Distribution
20%

50%

10%

Final
Midterm
Quiz
Report
Class Participation

15%
5%
4

Numbers to Remember
Minimum
passing
marks

Minimum
attendan
ce

Maximum
members
in a
group

Minimum
members
in a
group

62

80
%

2
5

Books to Read
Software Requirements
Karl E. Wiegers
Microsoft Press
More About Software
Requirements
Karl E. Wiegers
Microsoft Press
6

Course Objectives
To know what software requirements
engineering is
To understand the need of requirements
engineering
To understand your customers and how to
interact with them
To learn about the skills of a business analyst
7

Course Objectives
To develop, manage and document software
requirements
To improve the process of managing software
requirements
To define project scope
To reduce risks while managing the
requirements
8

What is Requirements
Engineering
Requirements engineering is primarily a

communication activity not a technical

activity
Requirements engineering is one of the most
challenging aspects of software development
It is also the most important aspect, as it lays
the foundation for all the subsequent project
work

Requirements
According to Ian Sommerville and Pete

Sawyer
A specification of what should be implemented
They are descriptions of how the system should

behave, or of a system property or attribute

They may be a constraint on the development
process of the system

10

Requirements
According to IEEE Standard Glossary of

Software Engineering Terminology

1. A condition or capability needed by a user to

solve a problem or achieve an objective

2. A condition or capability that must be met or
possessed by a system or system component
to satisfy a contract, standard, specification,
or other formally imposed document
3. A documented representation of a condition or
capability as in 1 or 2
11

Levels of Requirements
Business Requirements
User Requirements
Functional Requirements
System Requirements
Business Rules
Quality Attributes
External Interfaces
Constraints

12