Professional Documents
Culture Documents
Hirao, Carmela Dawn V. Gelito, Ryan
Hirao, Carmela Dawn V. Gelito, Ryan
Gelito, Ryan
It is a process through which you define
and evaluate the business needs of your
network system.
Also called needs assessment
Purpose of requirements defines what
the software is supposed to do.
Basis for all the future design, coding,
and testing that will be done on the
project.
Requirements analysis
process aims to identify and
document the customer's
requirements for a proposed
system.
1. A trained software
practitioner called the
Requirements Analyst (RA)
communicates with
knowledgeable users to
understand what the
requirements are.
2. The Analyst's jobs is to flesh it
out, add implied requirements
and mandatory or regulatory
requirements the client may not
be aware of and create a
document called the Software
Requirements Specifications, or
SRS.
3. At the end of the process, the SRS
turn out to be the blue print of the
product. A reference point for the
client, the project manager, the
tester and the designer. The SRS
should ideally restrict itself to
specifying “What” the product
should do rather than “How” to do it
Ideally, an SRS should include at the
least the following information:
Functional Requirements