WIKIPEDIA - In systems engineering and software engineering,

requirements analysis encompasses those tasks that go into

determining the needs or conditions to meet for a new or altered
product or project, taking account of the possibly conflicting
requirements of the various stakeholders, analyzing, documenting,
validating and managing software or system requirement

Requirements analysis is the process of determining

user expectations for a new or modified product
• Requirements analysis is critical to the success of a software project
• The requirements should be documented, actionable, measurable,
testable, traceable, related to identified business needs or opportunities,
and defined to a level of detail sufficient for system design
• Requirements analysis includes three types of activities:

Requirements Requirements Requirements

Gathering Analysis Recording

determine whether the Requirements may be documented

collected and declared in various forms, usually including a
requirements are clear, summary list and may include
complete, consistent and natural-language documents, use
unambiguous, and cases, user stories, process
resolving any apparent specifications and a variety of
conflicts models including data models
• Requirements analysis may also be split into 4 types of activities:

Requirements
Requirements Requirements Requirements
Review and
Gathering Analysis Modeling
Retrospective

Requirements might be Team members reflect

documented in various on what happened in
forms, such as natural- the iteration and
language documents, use identifies actions for
cases, user stories, or improvement going
process specifications forward
• Requirements analysis can be a long and tiring process during which
many delicate psychological skills are involved
• It is important to identify all the stakeholders, take into account all their
needs and ensure they understand the implications of the new systems
• After collecting the requirements and producing the requirement 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 the gathering
methods seen before to establish the exact requirements of the
stakeholders
Requirements quality can be improved through the following methods:

• Visualization. Using tools that promote better understanding of the desired

end-product such as visualization and simulation
• Consistent use of templates. Producing a consistent set of models and
templates to document the requirements
• Documenting dependencies. Documenting dependencies and
interrelationships among requirements, as well as any assumptions and
congregations
• 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
• 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
• 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
• Here are the main activities involve in requirement analysis
• Identify customer's needs
• Evaluate system for feasibility
• Perform economic and technical analysis
• Allocate functions to system elements
• Establish schedule and constraints
• Create system definitions
 REQUIREMENT ANALYSIS TECHNIQUES

• Requirement analysis helps organizations to determine the actual

needs of stakeholders
• At the same time, it enables the development team to
communicate with stakeholders in a language they understand
(like charts, models, flow-charts,) instead of pages of text
• Once the requirements are gathered, we document the
requirements in a Software Requirements Specification (SRS)
document, use cases or as User Stories, which are shared with the
stakeholders for approval
 REQUIREMENT ANALYSIS TECHNIQUES

• This document is easy to understand for both normal users and

developers
• Any changes in the requirements are also documented and go
through a change control procedure and finalized on approval