Abstract
Software Requirements Engineering (SRE) process define software manuscripts with sustaining Software Requirement Specification (SRS) and its activities. SRE comprises many tasks requirement analysis, elicitation, documentation, conciliation and validation. Natural language is most popular and commonly used to form the SRS document. However, natural language has its own limitations wrt quality approach for SRS. The constraints include incomplete, incorrect, ambiguous, and inconsistency. In software engineering, most applications are object-oriented. So requirements are unlike problem domain need to be developed. So software documentation is completed in such a way that, all authorized users like clients, analysts, managers, and developers can understand it. These are the basis for success of any planned project. Most of the work is still dependent on intensive human (domain expert) work. consequences of the project success still depend on timeliness with tending errors. The fundamental quality intended for each activity is specified during the software development process. This paper concludes critically with best practices in writing SRS. This approach helps to mitigate SRS limitation up to some extent. An initial review highlights capable results for the proposed practices
Highlights
A Software document is a representation of information designed for developing a software product by the analyst
This document consists of all essential requirements required within the Software Development Process (SDP) or Software Development Life Cycle (SDLC)
Even for software engineers who are working in the company to specify a complete, precise, and correct requirement specification for the proposed system
Summary
A Software document is a representation of information designed for developing a software product by the analyst. This document explains all the requirements related to the business process, user experience, product development at different phases...etc. Such documents are persistent, and suitable in the system development life cycle for archival uses, or it may be ephemeral, lasting only for viewings. Requirements Specification (SRS) is a detailed description of a proposed software system. This is widely acknowledged and used by most of the software developers, irrespective whether it’s a service, product or system, even any distinct requirements integrated. To develop a proposed system one should have clear understandings of the system This can be achieved by gathering all necessary requirement with the stakeholders recurrently. What are the main business objectives and functionality of the proposed product, and how core functions are performed
Sign-in/Register to view highlights & summary Sign-in/Register to access full text options 
Free) 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a call
