Software Requirements Specification ( Srs ) Essay

1283 WordsNov 22, 20166 Pages
Software Requirements Specification The introduction of the Software Requirements Specification (SRS) provides an overview of the entire SRS Purpose, Scope, Definitions, Acronyms, Abbreviations, References and Overview of SRS. A requirements specification for a software system is a complete description of the behavior of a system to be developed. It includes a set of Use cases that describe all the interactions the users will have with the software. Use cases are also known as Functional Requirements. In addition to use cases, the SRS also contains Non-Functional (or Supplementary) Requirements. Non-functional requirements are requirements which impose constraints on the design or implementation such as performance, engineering requirements, quality standards, or design constraints. In this chapter we will discuss our project’s Purpose, Scope, Definitions, Acronyms, Abbreviations, References and Overview of our project. We will make Use Cases of our project and also discuss the Functional Requirements and Non-Functional Requirements of our project. 1. INTRODUCTION 1.1 Purpose The purpose of the Software Requirements Specification document is to clearly define the system under development, namely “Code for Pak” (CP). The intended audience of the document includes the Supervisor of the project, Coordinators of the project and the University. The other intended audience includes the End Users and the Development Team. 1.2 Scope There are many computer programming
Open Document