Scribd
Upload
112 views3 pages

Requirement Analysis

Requirements analysis involves gathering user expectations for a new product and documenting them. It is an important part of project management that requires communication with users to determine features and resolve conflicts. Requirements analysis establishes the exact needs of stakeholders so a system can be developed to meet business needs. It follows a three step process of gathering requirements, creating a software requirements specification document, and validating the requirements.

Uploaded by

Rohit Chouhan
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
112 views3 pages

Requirement Analysis

Requirements analysis involves gathering user expectations for a new product and documenting them. It is an important part of project management that requires communication with users to determine features and resolve conflicts. Requirements analysis establishes the exact needs of stakeholders so a system can be developed to meet business needs. It follows a three step process of gathering requirements, creating a software requirements specification document, and validating the requirements.

Uploaded by

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

Requirement analysis

Requirements analysis, also called requirements engineering, The process to gather the
software requirements from client, analyze and document them is known as requirement
engineering .
Requirement engineering is the process of determining user expectations for a new or
modified product. These features, called requirements, must be quantifiable, relevant and
detailed. In software engineering, such requirements are often called functional
specifications.
Requirements analysis is an important aspect of project management.
Requirements analysis involves frequent communication with system users to determine
specific feature expectations, resolution of conflict or ambiguity in requirements as
demanded by the various users or groups of users, avoidance of feature creep and
documentation of all aspects of the project development process from start to finish.
Energy should be directed towards ensuring that the final system or product conforms to
client needs rather than attempting to mold user expectations to fit the requirements.
Requirements analysis is a team effort that demands a combination of hardware, software
and human factors engineering expertise as well as skills in dealing with people.

Overview
Requirements analysis can be a long and tiring process during which many delicate
psychological skills are involved. Large systems may confront analysts with hundreds or
thousands of system requirements.
New systems change the environment and relationships between people, so it is important
to identify all the stakeholders, take into account all their needs and ensure they
understand the implications of the new systems. Analysts can employ several techniques to
elicit the requirements from the customer. These may include the development of
scenarios , the identification of use cases, the use of workplace observation or ethnography,
holding interviews, or focus groups and creating requirements lists.
Prototyping may be used to develop an example system that can be demonstrated to
stakeholders.
Where necessary, the analyst will employ a combination of these methods to establish the
exact requirements of the stakeholders, so that a system that meets the business needs is
produced.
It is a three step process, which includes –

 Requirement Gathering
 Software Requirement Specification
 Software Requirement Validation

Requirement Gathering
If the feasibility report is positive towards undertaking the project, next phase starts with
gathering requirements from the user. Analysts and engineers communicate with the client
and end-users to know their ideas on what the software should provide and which features
they want the software to include.

Software Requirement Specification


SRS is a document created by system analyst after the requirements are collected from
various stakeholders.
SRS defines how the intended software will interact with hardware, external interfaces,
speed of operation, response time of system, portability of software across various
platforms, maintainability, speed of recovery after crashing, Security, Quality, Limitations
etc.
The requirements received from client are written in natural language. It is the
responsibility of system analyst to document the requirements in technical language so
that they can be comprehended and useful by the software development team.

Software Requirement Validation


After requirement specifications are developed, the requirements mentioned in this
document are validated. User might ask for illegal, impractical solution or experts may
interpret the requirements incorrectly. This results in huge increase in cost if not nipped in
the bud.
Requirements can be checked against following conditions –

1. If they can be practically implemented


2. If they are valid and as per functionality and domain of software
3. If there are any ambiguities
4. If they are complete
5. If they can be demonstrated
Functional requirements

Functional requirements explain what has to be done by identifying the necessary task,
action or activity that must be accomplished. Functional requirements analysis will be used
as the top level functions for functional analysis.
1. User Registration
2. User Login
3. Booking Instructions
4. Book Flights
5. Add/Delete or Modify Customer information
6. Add/Delete or Modify flight information
7. Cancellation of Reservations
8. User Logout

Non-functional requirements
Non-functional requirements are requirements that specify criteria that can be used to
judge the operation of a system, rather than specific behaviors.

1. Performance Requirements
2. Security Requirements

You might also like