Software Requirement Analysis
Software Requirement Analysis
Software Requirement Analysis is also known as a feasibility study. In this phase, the development team visits the customer and studies their system. They investigate the need for possible software automation in the given system. By the end of the feasibility study, the team will furnish a document containing the different recommendations for the candidate system. It also includes the personnel assignments, costs, project schedule, and target dates.
The requirement-gathering process is intensified and focused, especially on software. To understand the nature of the program(s) to be built, the system engineer (“analyst”) must understand the software’s information domain, as well as the required function, behavior, performance, and interface. The essential purpose of this phase is to find the need and define the problem that needs to be solved.
Levels of Requirements
The different levels of software requirements are as follows:
Business Requirements – High-level objectives of the project, which are recorded in the Vision and Scope Document
User Requirements – Tasks and facilities available to the end user are recorded in the Use Cases.
Functional Requirements – Detailed listing of each behavior that the software must exhibit. This, along with the quality attributes and other non-functional requirements, is documented in the Software Requirements Specification (SRS).
Non-Functional Requirements – The requirements unrelated to the system’s functionality. Like security requirements, performance, load, etc.