A Software Requirements Specification
Essay Preview: A Software Requirements Specification
Report this essay
Software Requirements Specification Table of ContentsTable of Contents IIRevision Log IV1. Introduction 11.1 Purpose 11.2 Document Conventions 11.2.1 Abbreviations 11.3 Intended Audience 21.4 Project Scope 21.5 References 22. Overall Description 22.1 Product Features 22.1.1 Secured Login 32.1.2 Inserting new reservations 32.1.3 Confirmations 32.1.4 Updating existing reservations. 32.1.5 Removing existing reservations. 32.1.6 Search capabilities. 32.2 Known Bugs 32.3 Operating Environment 32.4 Assumptions and Dependencies 33. Requirements 43.1 Login 43.1.1 Description 43.1.2 Functional Requirements 43.2 Flight Reservation 63.2.1 Description 63.3 New Order Process 83.3.1 Description 83.3.2 Functional Requirements 83.3.3 Error Messages 83.3.4 Search for an Order 103.3.5 Report generation 113.3.6 Graph generation 123.3.7 Help Menu 123.3.8 About Menu 12IntroductionA Product requirements document is used in product marketing to plan and execute new products. A Software Requirements Specification is a complete description of the behavior of the system to be developed. It includes a set of use cases that describe all of the interactions that users will have with the software.
Use Cases are also known as Functional Requirements. In addition to use cases, the SRS also contains nonfunctional requirements.The software requirements document is a written statement of what the software will do. What the software does is directly perceived by its users. When the user performs some action, the software responds in a particular way.Therefore you must agree on actions the users can perform and response they should expect. This common understanding is captured in the requirements document.PurposeThis document contains the tests requirements for the Automation FR Project.These software requirements were established by Dani Vainstein.This SRS specifies to Mercury Flight Application Version 4a.Intended AudienceProject teamCustomersProject ScopeThis document defines at a functional level the business activities that are encompassed by the system and the rules that apply to them. It also encompasses some of the key high and low level technical requirements of the system.It draws heavily on both proposed Framework and Business Rules and the Technical Architecture documents. The scope of the detailed analysis project phase specifies that this document will include.Classification of requirements according to their functional areas.A description of each process in the system, including their inputs, outputs, and data transformation rules.ReferencesDatabases