Requirement Analysis

This is the first and fore most step in any Software Life Cycle.
There are basically three steps involved in this phase. They are,

1.Eliciting the requirements: In this step, the clients and the software team sit down and discuss about the project. The clients and user tell the requirements, what they expect out of the software. The software twm makes a note of everything the client has to offer.

2.Analysing the Requirements: All the stuff provided by the users cannot be possible to implement. The software team sits down and analyses the requirements and make sure there are no conflicting requirements. Some requirements may be ambigous or impossible. They are deleted.

3.Recording the Requirements: The third and final part is this step. All the analysed requirements are documented and from now on the software twm can focus on the next process.

Scope Document:

The requirements are recorded in adocument called "Scope Document".In case the cclients and the software team end up in a conflicting situation later about the software being develpoed, this document can help out to solve the issue and also can be used as a legal document.

USE-CASE: Use-case is one famous methodology used to make sure the requirements are very correct. In this method, each and every feature of the software is explained as an scenario between the user and the software.