Software Requirement Specification (SRS) for

Video Library Management System (VLMS)

1.Introduction

1.1 Purpose

In this project, we have designed a 3-tier system that implements the functions of Video
Library Management System. Our system keeps track of all the movies in a database as well as
members and rents out the movies to the members as needed.

This is intended to make the system efficient and have designed to make it more scalable
and reliable.

1.2 Scope

The Scope of the application is wide and can be used with Video selling stores and can also
be used in other media streams with the necessary modifications done. Developing a website
which make it accessible to all the customers at the same time without delay.

Developing a website is not a challenge but making it accessible to all the customers at the
same time without delay is a real big challenge. Thus a website has to be scalable and should
manage the increase in customer traffic very well without delays. In such cases, system's
performance is put to test. We have tried overcoming the challenge by making the system
efficient and have designed to make it more scalable and reliable.

1.3 Definitions, Acronyms, and Abbreviations:

Acronyms and Abbreviations:

a. VLMS: Video library management system

b. SRS: Software Requirement Specifications.

Definitions:

1.Effiecient: Working or Operating in a way that gets the Results you want without any waste.

2.Scalable: A software that is described as scalable has an advantage because it is more adaptable
to the changing needs or demands of its users or clients.

3.Reliable: The ability of an apparatus, machine, or system to consistently perform its intended
or required function or mission, on demand and without degradation or failure.

1.5 Overview:

The rest of this SRS is organized as follows: Section 2 gives an overall description of the
software. It gives what level of proficiency is expected of the user, some general constraints while
making the software and some assumptions and dependencies that are assumed. Section 3 gives
specific requirements which the software is expected to deliver. Some performance
requirements and design constraints are also given.

2.Overall Description:

2.1 Product Perspective:

VLMS is aimed to keeps track of all the movies in a database as well as members and rents
out the movies to the members as needed. The aim of this project is to analyze the information
needs and the business processes regarding video rentals and implement a system that will
computerize this process and help the user manage the business.

2.2 Product Functions:

The high level summary of functions in VLM System is described in the following concept
map. Detail functional requirements will be described in section 3.

2.3 User Characteristics:

The Two types of user for the VLM System are:

1.Customer or Members
2.Admin

The following table describe general users characteristics that will affect the functionality of
the software product.

Type of User User Characteristics User Technical Expertise How the user characteristic
and technical expertise affect
VLM System functionality
Customer or Customer tends to find Customer has a lot of GUI interface may be easier
Member videos in their exposure to Windows to learn than text interface.
specification. type application Provide system help
Will not have any formal Provide appropriate error
training to use the system messages for invalid user
inputs.
Admin Good understanding to Average in technical User interface with less input
Video library operation proficiency steps.
Responsible for Easy to learn.
video library operation as
a whole.

2.4 General Constraints

This system is Web based, there will be a need to provide PC Server hardware connected to
the internet.
VLMS System can potentially have more than hundreds of users. It is unrealistic to provide
training for everyone. Therefore, the system should be designed for easy to use, providing help
instructions, and appropriate error messages for invalid user inputs.
 Security is important to Video library operation. Video library user is allowed to use the VLM
SYSTEM only for searching Videos. User should never be able to break into the system and to
perform any modification.

Readability plays a vital role in this operation.The text and the fonts used on the website should
be such that it enhances readability. Thus the website users focus on making it more readable
for users regardless of age groups and background. Thus we have designed our website keeping
in mind the above points and security concerns and worked more on improving the performance
so that it can handle more number of customer.

2.5 Assumptions and Dependencies

The following is a list of assumptions and dependencies that would affect the software
requirements if they turned out to be false:

 Users have basic understanding to PC and Windows and internet.

 The coding should be error free.
 The system should be user-friendly so that it is easy to use for the users.
 The information of all users, Movies must be stored in a database that is accessible by
the website.
 The system should have more storage capacity and provide fast access to the database.
 The system should provide search facility and support quick transactions.
 The Video library System is running 24 hours a day.
 Users may access from any computer that has Internet browsing capabilities and an
Internet Connection.

The dependencies are:-

 The specific hardware and software due to which the product will be run.
 On the basis of listing requirements and specification the project will be developed and
run.
 The end users (admin) should have proper understanding of the product.
 The system should have the general report stored.
  The information of all the users must be stored in a database that is accessible by the
Video Library System.
 Any update regarding the movie from the library is to be recorded to the database and
the data entered should be correct.

3.Detailed Requirements

3.1 External Interface Requirements

3.1.1 User Interfaces

 The design or layout of every form will be very clear and very interactive to the user.
 When the user open the software the welcome window will appear.
 In the login window the user can easily entered the desired password and login name.
 Then it will give the successfully login message.
 From each and every window the user can easily go to any desired window that is there
is will be a absolute and relative linking.
 There will be a proper collection of GUI interface, which will provide better look and feel.
 In the screen layout the background color is very light and the graphics and font style will
be in proper manner and well organized.
 If the user will print any error statement then it will give the proper error message display.
 In each and every window there will be alert, confirm etc message box for displaying
message.
 In the opening of the software there will be a menu window where the overall table
contents of the software will be present through which the user can move to any desired
window & Mac.
 This will provide the better security data because the menu window will be displaying
according to the login (admin or normal user).
 User can easily save its data in to the database and keep track of the records of purchase,
vendor and inventory etc.
 This software will be easily understandable and operable by the user.

3.1.2 Hardware Interfaces

The existing Local Area Network (LAN) will be used for collecting data from the users and
also for updating the Video Library Catalogue.
3.1.3 Software Interfaces
Mysql Server is used to store the data in Database.

3.1.4 Communications Interfaces

The Online Library System will be connected to the Particular Website

3.2 Functional Requirements

3.2.1 User account manage system

The system shall display the user account information including user number,Membership
Id,Member name, Email.

The system shall use a graphic user interface which allows Members to choice actions
including removing, changing and adding user account and account information.

3.2.2 Logging

Within the system, logging will be used to provide a trail of transactions that have taken
place. This might either be for developer debugging purposes, administrative checks on usage,
or research on the usability of interfaces.

 Transaction logs MUST be kept for each service provided.

 Sufficiently detailed client session logs MUST be generated to support analysis of user
activities. Security and Privacy.The user’s password MUST never be exposed to
compromise.
 User session logs stored for usability and other research MUST be anonymous.

3.2.3 Sign Up

When a customer wants to buy movies on a Video Library Management System, he has to
SignUp first. Customer will be having two types of memberships to choose from:

1. Simple Members
2. Premium Members.

Simple Members are allowed to rent maximum 2 movies while Premium customers have liberty
to ch oose 10 movies at a time. As soon as a Simple Member buys a movie online, he has to pay
for the movie rented while the Premium Member pays for the subscription fees. This payment
for the subscription fees could be done monthly, quarterly or annually.

3.2.4 Buy a movie

When Buying a movie, the system shall show all movie information and check particular user
including:

 Member name
 Member Id
 Issued Movies
 Movie name
 Banner
 Release Date
 Category
 Rent($)
 No of copies available

Simpler Members:

After choosing a movie then the user can add movie to the Cart and Cart window contain
the list of movies added to the particular user. After adding movie the user can click on the
checkout button ,where checkout window has the credit card number option and the total
amount.After verifying the Credit card number and total amount,the user can place the
order.And the movies are added to user account successfully.

Premium Members:

After choosing a movie then the user can add movie to the Cart and Cart window contain
the list of movies added to the particular user. .After adding movie the user can click on the
checkout button ,New window opens and it has the credit card number option and Subscription
Fee(Due amount).After this Checkout window shows list of movies that are added and it has place
order button where it places the movies to account successfully.

3.2.5 Search Movies

The system shall display a list of Movies which are matching the search criteria sorted by movie
titles including:

 the category
 release date
 No of copies available

3.2.6 Data Entry

 The data entry requirements are concerned with how data is entered and validated.
 The system shall allow a user to enter his/her data via a keyboard
 The system shall allow a user to enter his/her data via choose an item via a mouse.
 The system shall allow the user to enter Credit card number.
 The system shall allow the user to add or change information in an account including: last
name, first name, memebership ID,Address,Password.
 the system shall allow the user to logout from the account.

3.2.7 Update Movie database

The system shall allow the user to add or change the record information including:
 Movie name
 Release Date
 Movie category
 Movie Banner
 Available Copies
 Rent Amount
3.2.8 Report Generation
the report generation requirements are concerned with the report generation capabilities of the
Video Library system.
 The system shall have a report feature that will allow the user to generate a report
showing the information of a particular Customer.
 The system shall have a report feature that will allow the user to generate a report
showing the information of movie purchase information in a period including the movie
name, category, release date,the price. It also shall give statistic data about the total
number of movies purchased, the money paid by category.

3.3 Performance Requirements:

Apart from implementing technical details, one should always take care about web site’s
performance, scalability and robustness. As mentioned in a project description, we should take
care of the real time scenarios of huge number of clients and movie data. In case of such bulky
scenarios, database as well as website should work without any kind of problem and web site
crash. Also in case of multiple queries or requests at the same time, it should work faster as much
as possible. Below are the techniques those we have used in our project to improve the
performance.
1.Connection Pooling:
Main purpose of the connection pooling is performance enhancement. In connection
pooling, we can open multiple number of connections (have to specify this number in java file)
based on number of clients. This open connections assign to the client request when arrives and
once client done with his task, he returns this connection to the pool back which will be available
for the next client request. This way less time is spent in opening and closing of connections and
heavy weight resources can be managed.
2.Caching:
Caching is technique of storing the previously fetched data temporarily on server side and
eliminates the costly trip to database. In our project we use HashMap technique in which we use
(key, values) pairs. When any customer signs in to our website whole customer detail is stored
as value and key for the same is his membership ID. So whenever customer signs in again and if
key for customer is already there in HashMap then there is no costly trip to database for fetching
its details and directly returns the value from HashMap. Again, which increase the overall
performance and reduce latency time.
3.4 Design Constraints:
The system shall be installed in a windows network.
3.5 Attributes
Our software has many quality attribute that are given below-
 Adaptability-This software is adaptable by any organization.
 Availability- The availability of the software is easy and for everyone.
 Correctness- The results of the function are pure and accurate.
 Flexibility- The operation may be flexible and reports can be presented in many ways.
 Maintainability- After the deployment of the project if any error occurs then it can be
 easily maintain by the software developer.
 Portability-The software can be deployed at any machine.
 Reliability-The performance of the software is better which will increase the reliability
 of the software.
 Reusability-The data and record that are saved in the database can be reused if needed.

3.6 Other Requirements:

3.6.1 Security Requirements
 The account management system shall only be used by admin or users with defined
privileges.
 The Movie purchase report shall only be generated by Admins or users with defined
privileges.
 Database update data shall be committed to the database only after the Admins have
approved.