Requirement Analysis (SDLC)

What happens in the requirement analysis phase of SDLC?

SDLC Requirement Analysis plays a crucial role in it.

You can build the software product as per the customer requirements. The software product mostly complies with what end the customer had expected, but sometimes the product does not fully comply with the customer expectations.

What is Requirement Analysis?

Requirement Analysis is an important phase of SDLC. Let’s understand its concept with a Requirement Analysis example:

Customer Expectation:

What Customer Receives:
                              


You can easily analyze from the above images that there is a mismatch in the end product to customer expectations. It can be due to many reasons like the incorrect implementation of customer requirements, faulty design, misunderstanding of customer requirements by programmers and quality team, etc.

A reasonable product delivery demands correct requirements gathering, the efficient examination of requirements gathered, and clear requirement documentation as a precondition. This entire process is known as Requirement Analysis in Software Development Life Cycle (SDLC).

Requirements Analysis Process

The Requirement Analysis phase is SDLC’s first activity, followed by Functional Specs and so on. It is a crucial step in SDLC as it resonates with the acceptance testing, critical for product acceptance by customers.

Here, you will learn how to do the requirement analysis phase in SDLC. We will see its various steps, outcomes, challenges, and corrective measures.

Requirement Analysis begins with:

  • Requirement Gathering, which is also known as Elicitation.
  • It is followed by Analyzing the collected requirements to understand the feasibility and correctness of converting the requirements into a possible product.
  • Then, Documenting the gathered requirements.








Comments

Post a Comment

Popular posts from this blog

Design Phase (SDLC)

  What would you do during the design phase in SDLC? The Design Phase is an crucial phase of the  Software Development  Life Cycle. The list of requirements that you develop in the definition phase is used to make design choices. In the design phase, one or more designs are created to achieve the project result. Depending on the project subject, the design phase products includes flow-charts, sketches, site trees, HTML screen designs, photo impressions, prototypes, and UML schemas. The project supervisors use these designs to choose the definitive design that you can produce in the project. The development phase follows it. Once you have selected the design in the definition phase, you cannot make changes in the project’s later stage. The objectives of the SDLC Design Phase are as follows: Objectives Successful completion of the SDLC Design Phase comprises: Transformation of all the requirements into detailed specifications covering all the aspects of the system. Planning...
Read more

UseCase Vs TestCase

What is the difference between use case and test case? Use Cases  and  Test Cases  are two important terms in context of Software Testing. A use case tells how a System will behave or perform a certain task provided the given conditions and a test case contains the actual test data, set of instructions to system and expected result of the interaction with system. Following are the important difference between Use Case and Test Case. Sr. No. Key Use Case Test Case 1 Objective The objective of Use case is to ascertain a certain output after the set of operations. The objective of test case is to ensure that system is working fine for each given instruction and yields the required result. 2 Definition Use case is a representation of actions which describes the behaviour of system to do a particular task. Test case contains the test data, set of instructions to follow and a result(s) of following the instructions. 3 Source Use cases are prepared on requirements. Test cases ar...
Read more

TestCase Vs TestScenario

What is the difference between test case and test scenario? A test case is a set of criteria that a tester uses to verify whether or not a software application is meeting the customer's requirements. Preconditions, case name, input conditions, and intended outcome are all included in the test case design. A test case is a basic activity that is derived from test scenarios. It is a comprehensive document that comprises all potential inputs (both positive and negative) as well as navigation instructions for the test execution process. Writing test cases is a one-time effort that may be reused for regression testing in the future. The test case contains thorough information about the testing approach, procedure, preconditions, and expected results. These are used during the testing phase to see if the software program is capable of executing the purpose for which it was created. By associating a defect with a test case ID, test cases assist testers in defect reporting. The testing tea...
Read more