Scribd
Upload
70 views

RE Lecture 03

The document discusses requirements engineering for software development projects. It explains that requirements development produces a baseline of agreed upon product capabilities among stakeholders. During requirements management, changes to the baseline and implementation are monitored. Requirements development has four subcomponents: elicitation to understand user needs, analysis to derive detailed requirements, specification to document requirements, and validation to ensure requirements are correct and high quality. The document also distinguishes requirements from design details, planning information, and testing while noting there are different levels of requirements from business needs to user and system requirements.

Uploaded by

Murtaza
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
70 views

RE Lecture 03

The document discusses requirements engineering for software development projects. It explains that requirements development produces a baseline of agreed upon product capabilities among stakeholders. During requirements management, changes to the baseline and implementation are monitored. Requirements development has four subcomponents: elicitation to understand user needs, analysis to derive detailed requirements, specification to document requirements, and validation to ensure requirements are correct and high quality. The document also distinguishes requirements from design details, planning information, and testing while noting there are different levels of requirements from business needs to user and system requirements.

Uploaded by

Murtaza
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 15

Requirements

Engineering
Lecture 03
National University FAST
September 05, 2015, 18:00 21:00

Requirements Engineering
Marketing, Customers, Management
Requirements

Requirements
Development
Requirements
Management
Marketing,
Customers,
Management

Analyze,
Docume
nt,
Review,
Negotiat
e

Baseline Requirements
Current
Baseline

Requirements
Changes

Revised
Baseline
Requireme
nts Change
Process

Project
Changes

Project
Environment
2

Requirements
Engineering
The deliverable from requirements

development is a baseline that constitutes an


agreement among key project stakeholders as
to the new products capabilities
During requirements management, the
project controls changes in the requirements
baseline and monitors requirements
implementation

Subcomponents of
Requirements
Development
Elicitation

Analysis

Specificati
on

Validation
4

Elicitation
Understand our users
Discover their needs
Define the products business requirements
Get extensive user involvement
Focus on user tasks
Define quality attributes

Analysis
Derive more detailed requirements from

higher level requirements


Create multiple views of the requirements
Negotiate priorities
Search for missing requirements
Evaluating technical feasibility, risk, and
failure modes
Analysis provides a feedback loop that refines
the understanding that the analyst developed
during an elicitation activity
6

Specification
Record the various types of requirements

information in forms that will facilitate


communication among the project
stakeholders
Documents containing natural language text
Graphical analysis models
Tables
Mathematical expressions

Store requirements in a management tool


DOORS Quality Systems and Software, Inc.
RequisitePro Rational Software Corporation

Validation
Inspect requirements specifications
Ensure correct requirements , that will
Satisfy customer needs
Have all the characteristics of high quality
requirements
Validation might lead the analyst to
Rewrite some requirements specifications
Reassess the initial analysis
Correct and refine the set of documented
requirements
8

What Requirements Are


Not
Requirements specifications do not include

design or implementation details (other than


known constraints), project planning
information, or testing information
Separate such items from the requirements so
that the requirements activities can focus on
understanding what the team intends to build

What Requirements Are


Not
Projects typically have other kinds of

requirements, including
Development environment requirements
Schedule or budget limitations
The need for a tutorial to help new users get up

to speed
Requirements for releasing a product and
moving it into the support environment

10

Levels of Requirements
A project needs to address three levels of

requirements, which come from different


sources at different project stages
Business Requirements
Describe why the product is being built and identify
the benefits both customers and the business will
reap
User Requirements

Captured in the form of use cases, describe the


tasks or business processes a user will be able to
perform with the product
11

Levels of Requirements
Functional Requirements
Describe the specific system behaviors that must be
implemented
The functional requirements are the traditional shall
statements found in a software requirements specification
(SRS)
System Requirements
The term system requirements describes the top level
requirements for a product that contains multiple
subsystems
A system can be all software or it can include both software
and hardware subsystems
People are a part of a system, too, so certain system
functions might be allocated to human beings
12

Types of Requirements
Business
Requireme
nts

Functional
Business
Rules

Vision and Scope


Document

Quality
Attributes

User
Requireme
nts

External
Interfaces

Use Case Document

System
Requireme
nts

Non
Functional

Functional
Requireme
nts

Constraints

Software Requirements
Specification

13

Non Functional
Requirements
Business Rules
Business rules include corporate policies,
government regulations, industry standards
(such as accounting practices), and
computational algorithms
Quality Attributes
Quality attributes describe the products
characteristics in various dimensions that are
important either to users or to developers and
maintainers. These characteristics include
availability, performance, usability, portability,
integrity, efficiency, robustness, and many

14

Non Functional
Requirements
External Interfaces
External interfaces between the system and the
outside world constitute another class of
nonfunctional requirements
Constraints
These are restrictions imposed on the choices

available to the developer for some legitimate


reason
Some people consider all requirements to be
constraints, but this broad generalization isnt
very helpful
15

You might also like