Scribd
Upload
238 views23 pages

Requirements Specifications

The document discusses requirements specification in software development. It defines requirements specification as the process of creating shared understanding of the problem and needs of the proposed solution. This involves high-level descriptions of what the system will and won't do to clearly define its scope. The requirements specification is also the product of this process - a documentation of the requirements. The document further distinguishes between user requirements, which describe how users will interact with the system, and system specifications, which are the technical building blocks for developers to build the system to meet requirements. It introduces the WRSPM model to help understand the difference between requirements in the problem domain and specifications in the solution domain.

Uploaded by

dude
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
238 views23 pages

Requirements Specifications

The document discusses requirements specification in software development. It defines requirements specification as the process of creating shared understanding of the problem and needs of the proposed solution. This involves high-level descriptions of what the system will and won't do to clearly define its scope. The requirements specification is also the product of this process - a documentation of the requirements. The document further distinguishes between user requirements, which describe how users will interact with the system, and system specifications, which are the technical building blocks for developers to build the system to meet requirements. It introduces the WRSPM model to help understand the difference between requirements in the problem domain and specifications in the solution domain.

Uploaded by

dude
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/ 23

Requirements Specifications

OPERATION AND
REQUIREMENTS DESIGN IMPLEMENTATION VERIFICATION
MAINTENANCE
What do you think is the most difficult
part in software development?
Requirements Specification

PROCESS

REQUIREMENTS

PRODUCT
Requirements Specification

• The process by which we create our shared understanding of both the problem
that exists and eventually the needs of our supposed solution which we want to
build that will solve the specified problem/s.

• Creating high level descriptions of all the concerns we hoped to address in our
work with a primary goal of developing a document which can clearly describe
what the system will do and what it won’t do

• Distinguish between right and wrong in the system


Requirements Specification

• Capture the what not the how of the solution

• It is also the product of that process. The requirement specification is the


documentation that we produce from that process.

• The document can be an informal understanding or a formal software


requirements specification (SRS) document.
Requirements vs Specifications
user

developer
Requirements vs. Specification

• User requirements – often referred to as user needs, describe what the user does
with the system, such as what activities that users must be able to perform

• System Specification – are the building blocks developers use to build the system
Requirements vs. Specification

• User requirements
1. Two people can ride on the motorcycle.

• System Specification
1. Motorcycle should not weigh more than
150kg
2. Top speed of 250 km/h
3. Setting up other motorcycle parts...
Requirements vs. Specification

• User requirements
1. User can withdraw money
2. User can view remaining balance

• System Specification
1. Should provide options for withdrawing
money and viewing remaining balance
2. Provide a slot for inserting ATM card
3. Installing necessary software and
hardware components
Requirements vs. Specification

• User requirements
1. When the patient’s heart stops, a nurse
shall be notified.

• System Specification
1. When the sound from the sensor falls
below a certain threshold, the alarm
shall be actuated.
Requirements vs. Specification

• Requirements are for the user and specifications are for the developer

• Write your requirements in the user language

• Write your specifications in the system language

• Be sure that your specifications meet the requirements


WRSPM Reference Model:
The World Machine Model
WRSPM Model

• It is a reference model that helps us to understand problems in the real world and
it helps us to identify the difference between a requirement and the specification.

• Requirements are always in the problem domain

• Software specification is in the solution domain


WRSPM Model

User-visible elements of
everything in the world
WRSPM Model
WRSPM Model
WRSPM Model
WRSPM Model
WRSPM Model
WRSPM Model
W R S
Drivers stop at red Allow pedestrians to Show red light to the cars
light cross the road safely and green light to the
pedestrians
Pedestrians stop at red
Pedestrians and cars
light
cannot be in the Never show a green light
intersection at the same to both pedestrians and
Drivers drive at green time cars
light

Pedestrians walk when


green

You might also like