Requirement specifications Computer Science Engineering (CSE) Notes | EduRev

Computer Science Engineering (CSE) : Requirement specifications Computer Science Engineering (CSE) Notes | EduRev

 Page 1


Requirement Specifications
Page 2


Requirement Specifications
Requirements engineering
• The process of establishing the services that 
the customer requires from a system and the 
constraints under which it operates and is 
developed. developed.
• The requirements themselves are the 
descriptions of the system services and 
constraints that are generated during the 
requirements engineering process.
Page 3


Requirement Specifications
Requirements engineering
• The process of establishing the services that 
the customer requires from a system and the 
constraints under which it operates and is 
developed. developed.
• The requirements themselves are the 
descriptions of the system services and 
constraints that are generated during the 
requirements engineering process.
What is a requirement?
• It may range from a high-level abstract statement of 
a service or of a system constraint to a detailed 
mathematical functional specification.
• This is inevitable as requirements may serve a dual 
function function
– May be the basis for a bid for a contract - therefore must 
be open to interpretation;
– May be the basis for the contract itself - therefore must be 
defined in detail;
– Both these statements may be called requirements.
Page 4


Requirement Specifications
Requirements engineering
• The process of establishing the services that 
the customer requires from a system and the 
constraints under which it operates and is 
developed. developed.
• The requirements themselves are the 
descriptions of the system services and 
constraints that are generated during the 
requirements engineering process.
What is a requirement?
• It may range from a high-level abstract statement of 
a service or of a system constraint to a detailed 
mathematical functional specification.
• This is inevitable as requirements may serve a dual 
function function
– May be the basis for a bid for a contract - therefore must 
be open to interpretation;
– May be the basis for the contract itself - therefore must be 
defined in detail;
– Both these statements may be called requirements.
Requirements abstraction (Davis)
• Needs must be defined in a sufficiently abstract way that a 
solution is not pre-defined.  
• The requirements must be written so that several 
contractors can bid for the contract, offering, perhaps, 
different ways of meeting the client organisation’s needs.  different ways of meeting the client organisation’s needs.  
• Once a contract has been awarded, the contractor must 
write a system definition for the client in more detail so that 
the client understands and can validate what the software 
will do.  
• Both of these documents may be called the requirements 
document for the system. 
Page 5


Requirement Specifications
Requirements engineering
• The process of establishing the services that 
the customer requires from a system and the 
constraints under which it operates and is 
developed. developed.
• The requirements themselves are the 
descriptions of the system services and 
constraints that are generated during the 
requirements engineering process.
What is a requirement?
• It may range from a high-level abstract statement of 
a service or of a system constraint to a detailed 
mathematical functional specification.
• This is inevitable as requirements may serve a dual 
function function
– May be the basis for a bid for a contract - therefore must 
be open to interpretation;
– May be the basis for the contract itself - therefore must be 
defined in detail;
– Both these statements may be called requirements.
Requirements abstraction (Davis)
• Needs must be defined in a sufficiently abstract way that a 
solution is not pre-defined.  
• The requirements must be written so that several 
contractors can bid for the contract, offering, perhaps, 
different ways of meeting the client organisation’s needs.  different ways of meeting the client organisation’s needs.  
• Once a contract has been awarded, the contractor must 
write a system definition for the client in more detail so that 
the client understands and can validate what the software 
will do.  
• Both of these documents may be called the requirements 
document for the system. 
Types of requirement
• User requirements
– Statements in natural language plus diagrams of the 
services the system provides and its operational 
constraints. Written for customers.
• System requirements • System requirements
– A structured document setting out detailed descriptions of 
the system’s functions, services and operational 
constraints. Defines what should be implemented so may 
be part of a contract between client and contractor.
Read More
Offer running on EduRev: Apply code STAYHOME200 to get INR 200 off on our premium plan EduRev Infinity!

Related Searches

video lectures

,

Objective type Questions

,

Semester Notes

,

past year papers

,

Extra Questions

,

shortcuts and tricks

,

Requirement specifications Computer Science Engineering (CSE) Notes | EduRev

,

Viva Questions

,

Free

,

mock tests for examination

,

Sample Paper

,

Requirement specifications Computer Science Engineering (CSE) Notes | EduRev

,

Important questions

,

Exam

,

study material

,

pdf

,

MCQs

,

practice quizzes

,

Requirement specifications Computer Science Engineering (CSE) Notes | EduRev

,

ppt

,

Previous Year Questions with Solutions

,

Summary

;