A Project Report on NEXAM
| dc.contributor.author | Karthik, P | |
| dc.date.accessioned | 2017-07-25T12:34:08Z | |
| dc.date.available | 2017-07-25T12:34:08Z | |
| dc.date.issued | 2017-07-25T12:34:08Z | |
| dc.description.abstract | A software requirements specification (SRS) is a description of a software system to be developed. It lays out functional and non-functional requirements, and may include a set of use cases that describe user interactions that the software must provide. Software requirements specification establishes the basis for an agreement between customers and contractors or suppliers (in market-driven projects, these roles may be played by the marketing and development divisions) on what the software product is to do as well as what it is not expected to do. Software requirements specification permits a rigorous assessment of requirements before design can begin and reduces later redesign. It should also provide a realistic basis for estimating product costs, risks, and schedules. Used appropriately, software requirements specifications can help prevent software project failure. The software requirements specification document enlists enough and necessary requirements that are required for the project development. To derive the requirements we need to have clear and thorough understanding of the products to be developed or being developed. This is achieved and refined with detailed and continuous communications with the project team and customer till the completion of the software. | en_US |
| dc.identifier.uri | http://hdl.handle.net/123456789/8186 | |
| dc.language.iso | en | en_US |
| dc.subject | Karthik P | en_US |
| dc.subject | A Project Report on NEXAM | en_US |
| dc.subject | 14VFSB7027 | en_US |
| dc.title | A Project Report on NEXAM | en_US |
| dc.type | Other | en_US |