Skip to content

Requirement Analysis

August 10, 2009

Requirement analysis is also referred as requirement capture, requirement gathering, and requirement specification.

It is critical to the success of a development project.
It is the process of understanding the customer needs and expectation.
Requirement Eliciting is communicating with the customer and end user to determine what the requirements are?
Analyzing Requirement is whether the stated requirements are unclear, incomplete, and then resolving these issues.
Recording Requirements is documented in various forms such as use case, natural language document, or process specification.
Requirement Documenting
Requirements are mainly written for the communication between different stakeholders which means the requirements should be clearly understood for both the developer and the normal user.
Change in Requirement
Requirements can change in time. Requirements can be altered before the system is complete.
Requirement Specification
It can be documented as user requirement and system requirement.
User Requirement: should be clear, natural language, use case for the benefit
Of customer and end user
System Requirement: Expressed as a programming language or mathematical
Model addressing the development team, QA and testing team.

One Comment leave one →
  1. pravesh permalink
    September 27, 2009 4:21 pm

    i need more details about recording requirement..i have an assigment on it..

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

%d bloggers like this: