Software requirements specification
Introduction: -IEEE defines a requirement (1) the condition of the user's ability to solve a problem or achieve a purpose; (2) a condition or a capacity to fulfill a contract Should be completed by any system or, standard, specification, or other formally applied documents. Targets the requirements of the activity of the software requirements specific Is to produce SRS, which states that the proposed software should describe how the software will do this.
One basic limit for this is that the user should keep changing the environment in which the change works with the system over time. Even accepting that some requirement change requests are inevitable, are still due to the pressures that why the intensive work should be done in the phase of the requirements to produce high-quality and relatively stable SRS.
Requirement of SRS
Most software systems are in the needs of some customers. The software system itself is created by some developers themselves. Finally, the full system will be used by end users. Thus, there are three main parties interested in a new system: customers, developers and users. Somehow the requirements of the system that will meet the needs of the customers and the concerns of the users must be communicated to the developer. The problem is that the client generally does not understand the software or software development process, and the developer often does not understand the client's problem and application area. This causes a communication difference between the parties involved in the development project. One basic purpose of specifying the software requirements is to bridge this communication gap. SRS is the medium through which clients and user's needs are accurately assigned to the developer. So one of the main benefits is:
• SRS establishes the basis for the agreement between the customer and the supplier that what the software product will do. This agreement is often formalized in a legal agreement between the customer and the developer for the agreement. Therefore, through SRS, the customer clearly describes what it expects from the supplier, and the developer clearly understands what capabilities to build in the software.
• SRS provides a reference for final product verification. That is, SRS helps the client determine whether the software meets the requirements. Without a proper SRS, there is no way that a customer can determine what was ordered from the software being distributed, and there is no way that the developer could explain to the client that all the requirements have been met. . Providing the basis of agreement and recognition, there must be sufficient reason for both the client and the developer to understand the requirement and the intensive and hard work of specification, but there are other very practical and stressed reasons for having a good SRS.
• High quality SRS is a prerequisite for high quality software. Finally, we show that the quality of the SRS impacts the costs of the project (and schedule). A requirement error, if the system was detected and removed after it was developed, it could cost up to 100 times more during the phase of requirements.
• High quality SRS reduces development cost. The quality of SRS influences the customer (and the developer)'s satisfaction, system verification, quality of the final software, and software development costs. The key role of SRS in the software development project should be clear.
One basic limit for this is that the user should keep changing the environment in which the change works with the system over time. Even accepting that some requirement change requests are inevitable, are still due to the pressures that why the intensive work should be done in the phase of the requirements to produce high-quality and relatively stable SRS.
Requirement of SRS
Most software systems are in the needs of some customers. The software system itself is created by some developers themselves. Finally, the full system will be used by end users. Thus, there are three main parties interested in a new system: customers, developers and users. Somehow the requirements of the system that will meet the needs of the customers and the concerns of the users must be communicated to the developer. The problem is that the client generally does not understand the software or software development process, and the developer often does not understand the client's problem and application area. This causes a communication difference between the parties involved in the development project. One basic purpose of specifying the software requirements is to bridge this communication gap. SRS is the medium through which clients and user's needs are accurately assigned to the developer. So one of the main benefits is:
• SRS establishes the basis for the agreement between the customer and the supplier that what the software product will do. This agreement is often formalized in a legal agreement between the customer and the developer for the agreement. Therefore, through SRS, the customer clearly describes what it expects from the supplier, and the developer clearly understands what capabilities to build in the software.
• SRS provides a reference for final product verification. That is, SRS helps the client determine whether the software meets the requirements. Without a proper SRS, there is no way that a customer can determine what was ordered from the software being distributed, and there is no way that the developer could explain to the client that all the requirements have been met. . Providing the basis of agreement and recognition, there must be sufficient reason for both the client and the developer to understand the requirement and the intensive and hard work of specification, but there are other very practical and stressed reasons for having a good SRS.
• High quality SRS is a prerequisite for high quality software. Finally, we show that the quality of the SRS impacts the costs of the project (and schedule). A requirement error, if the system was detected and removed after it was developed, it could cost up to 100 times more during the phase of requirements.
• High quality SRS reduces development cost. The quality of SRS influences the customer (and the developer)'s satisfaction, system verification, quality of the final software, and software development costs. The key role of SRS in the software development project should be clear.
Software requirements ano
from Technology development http://bit.ly/2VeCTT4
Comments
Post a Comment