You are on page 1of 1

SOFTWARE REQUIREMENTS ANALYSIS & SPECIFICATION Requirements engineering: Requirements describe the what of a system ,not the how.

Requirements engineering produce one large document, written in a natural language ,contains a description of what the system will do without describing how it will do. This process consists of four steps: Requirements Elicitations Requirements Analysis Requirements Documentation Requirements Review

Types of Requirements: Functional Requirements Non Functional requirements

Functional Requirements: describes what the system has to do.They are also called products features. Non Functional Requirements: These requirements mostly quality requirements that stipulate how well the software does what it has to do. Non functional requirements for users are performance,availability,reliability,usability and flexibility. Non functional requirements for developers are maintainability,portability and testability.

Requirements Elicitations:
The real requirements actually reside in users mind. Hence the most important role of requirements engineering is to find out what users really needs. Users need can be identified only if we understand the expectations of the users from the desired software.