Professional Documents
Culture Documents
I. Introduction This document contains the Software Requirements Specification (SRS) of an Video Rental System. The main aim of this project is to provide automation to all operations in a Rental shop.
The SRS contains the complete description of the software requirements for the Video Rental System. It provides insight to the design and information needed for software support.
The Video Rental System is developed for the Video shop to improve the current rental process. Here we are try to develop such type system which is provide the automation on the any type of the rentalshop. That means a shop which has the type system which provides the facility to the customers of the shop to purchase the video from the shop without any complexity. For example any customer want to purchase any video from the shop than first of all customer just choose the stream of the video than he/she can see the more than one type of movies there and then he/she can choose the specific video from
Page 1
VIDEO RENTAL SYSTEM Requirements Documentation there. And then purchase it by paying price on rental shop cash counter and receives its invoice
Definitions
Transaction
Extension
Customer
Acronyms
VRS
Abbreviations
1.4 References
Page 3
In this requirements document, general description, specific requirements, appendices and index are included. Under general description are: product perspective, product functions, user characteristics, general constraints and lastly is the assumption and dependencies. Specific requirements on the other hand will be covering functional, non-functional and interface requirements.
This section describes the general factors that affect the product and its requirements. It does not state specific requirements; it only makes those requirements easier to understand.
Page 4
II.1 Product Perspective This is a new and independent system. It will make the transaction of the company accurate and easy to manage.
This product function provides a summary of the functions that the software will perform. It discusses major functional areas without mentioning any of the large amounts of detail that goes with those areas.
It could ADD, Edit, Delete and View Aliens personal Information. It has Extension transaction. It could compute the remaining days of extensions. It allows to know the due payments of the customer
Page 5
User characteristic describe the general characteristics of the eventual users of the system that will affect the specific requirements.
Computer background Had an experience of manual transaction Complexity with the other works Can work with computers in an average period of time
Page 6
Page 7
General constraintsare descriptions of any other items that will limit the developers options for designing the system.
Rental procedure Hardware/system software resource limitations (i.e. Memory, disk space) External interfaces Marketing purposes Communications protocol Application criticality Safety, security
Page 8
Software malfunction Hardware availability Hardware failure Application Error Resource limitation (storage; memory) Transition from manual to automated Clients must have the username and password to be able to use t he system transaction.
Administrator same with the client must have username and password to be able to access the whole system.
Page 9
This is the common used in a specific business projects software design, implementation, and testing. Video Rental System specific requirements are: System must complete the process. System must identify where the origin and destiny of the customer System must only rent in a specific videos
Page 10
rental personal Information. System must run on windows server 2008, server 2010, server 2003 windows XP or windows 7. System must have SQL server or MS ACCESS databases only. Works stations must have at least 256Ram and 250gig disk drive storage.
IV. Appendices Software requirement Inspection Checklist 1. Does SRS include all user requirements? 2. Are all external interfaces defined? 3. Do the requirements provide an adequate basis for design? 4. Are algorithms intrinsic to the functional requirements defined? 5. Is the expected behavior documented for all anticipated error conditions? 6. Are all the necessary objects in requirement defined? 7. Do any requirements conflict with or duplicate other requirements?
Page 11
8. Are all internal references to other requirements correct? 9. Are all requirements written at an appropriate level of detail? 10. Is each requirement written in standard terminology and definitions? 11. Is each requirement verifiable by testing, demonstration, review, or analysis? 12. Is each requirement free from errors in content? 13. Can all of the requirements be implemented within known constraints? 14. Are all performance objectives properly specified? 15. Are all real time, security and safety considerations specified in sufficient detail? 16. Is the SRS traceable? 17. Are all requirements actually requirements?
V. Index
Page 12
VIDEO RENTAL SYSTEM Requirements Documentation Password(text) User_id(text) Prod_id(text) Quantity(Integer) Transdate(text)
Page 13