Requirements analysis is a software engineering task that bridges the gap between system level software allocation and software design.
It enables the system engineer to specify software function and performance indicate software’s interface with other system elements and establish constraints that software must meet.
Requirement analysis allows the software engineer (i.e. analysis) to refine the software allocation and build models of the data, functional and behavior domains that will be treated by software.
Finally, the requirement specification provides the developer and the customer with the means to assess quality once software is built.
Requirement analysis divided into five areas:
1) Problem recognition
2) Evaluation and synthesis
Requirement analysis Task
1). Problem Recognition
Initialize the system analyst studies the system specification of the software and project plan and the analyst must establish contact with management and technical staff of the user or customer organization and software development organization. The project manager can serve as a coordinator for establishment of communications paths. The goal of the analysis is to reorganization the basic problem element which is perceived by the user or customer.
2). Synthesis and evaluation
Problem evaluation and solution synthesis is the next major area of effort for analysis. The analyst must evaluate the flow and content of information, define and expand all software function, understand software behavior in the context of event of the effect system, establish system interface characteristics and on cover design constrains. Each of these tasks serves to describe the problem so that and overall approach or solution may be synthesis. Evaluating current the problems and desired information and input and the output the analyst begins to synthesis one or more solution.
Throughout evaluation and solution synthesis the analyst’s primary focus of analyst is on “What” or “How” what data does the system produce and consume what functions must the system perform what interfaces are define and what constrains applied.
During the evaluation and solution synthesis activities the analyst creates models of the system in an effort to better understand data and control flow, functions processing and behavior operation. The model serves the foundation for software design and the basic for the creation of a specification for the software.
4). Requirement Specification
After making the module analyst makes a plan and schedule for development. The information gathered during the system study was analyzed to determine the requirement specifications. Based on the issues governing the system, requirements in non-technical terms formulated.
1. We need to develop rough prototype to check the basic functionality of the software.
2. If the major modules are not working properly then the software might not satisfy the user.
3. Interaction between the operator and system must be fast and reliable.