Acropolis institute of Technology and Research

Faculty of Computer Application

MCA 406 - Minor Project

Project title - E-Library
Software Requirement Specification (SRS)

By- Submitted to-

Ritika Jain Mr. Gondal Sir
Ayasmita Das
Shivam Jwell
1. Introduction

 A digital library is a type of information retrieval system.

 It maintains a database as a collection of e-materials.
 Digital Library services are information services that are delivered
digitally over computer networks.
 Digital materials are items that are stored, processed and transferred via
digital devices and network.
1.1 Purpose

 The purpose of Software Requirements Specification (SRS) document is

to describe the external behavior of the E-Library System.
 Requirements Specification defines and describes the operations,
interfaces, performance, and quality assurance requirements of the E-
Library System.
1.2 Scope

 The application will provide the C.S. and I.T. students books related their
courseware.
 Initially the scope of application will be limited to the C.S. Branch.
 However, the application will keep on increasing its data and will include
books of another domain too.
2. General Description

 Product Perspective (what is our website for users?)

 Product Function (What we are offering to the users?)
 User Characteristics (Type of Users)
 Constraints (Rules of Website)
 Assumptions and Dependencies
3. Specific requirements
3.1 External Interface Requirements
 User Interface
The user interface shall follow basic Website style and functionality conventions. The
interface has five tabs at top center of the screen, which will allow users to easily switch
between the different pages of website.
 Hardware Interface
This website will run on any web browser with active internet connection device and it
doesn’t depend on type of software and operating system.
 Software Interface
The devices only will require web browser.

 Communication Interface
This network is open and is accessible from the internet.
3. Specific requirements (Cont.)
3.2 Functional Requirement
Feature 1. Administration panel
The books uploaded on the application by the Admin are already pre-approved while
the books uploaded by the users must be approved by admin. Administrator can
disable user account and remove the inappropriate content from the Application. 
Feature 2. User Account
User account are password protected. Password reminder and resets are handled by
the website.
 3. Specific requirements (Cont.)
3.3 Use Cases

Use Case for Registered

User
 3. Specific requirements (Cont.)
3.3 Use Cases

Use Case for

Non Member User
3. Specific requirements (Cont.)
3.4 Non-Functional Requirement
 Performance
 Reliability
 Availability
 Maintainability
4. Analysis models
4.1 ER-diagram
Tables
Table 1. ARTICLE -
ARTICLE_ID TOPIC CONTENT PUBLISED
BY

Table 2. BOOK -
BOOK_ID BOOK_NAME AUTHOR TYPE GENERA FILE STATUS

Table 3. USER -
ID FNAME LNAME EMAIL CONTACT PASSWORD

Table 4. ADMIN -
ADMIN_ID PASSWORD
 Normalized table 1NF
First Normal Form is defined in the definition of relations (tables) itself.
This rule defines that all the attributes in a relation must have atomic domains.

Table for the Entity ARTICLE Table for the Entity

-
ARTICLE_ID TOPIC CONTENT PUBLISED BY ADMIN - PASSWORD
ADMIN_ID

Table for the Entity

BOOK -BOOK_NAME
BOOK_ID AUTHOR TYPE GENERA FILE APPORVED

Table for the Entity

USERFNAME
ID
- LNAME EMAIL CONTACT PASSWORD
 Normalized table 2NF
Be in 1NF
Should not have Partial Dependency

Table for the Entity ARTICLE Table for the Entity

-
ARTICLE_ID TOPIC CONTENT PUBLISED BY ADMIN - PASSWORD
ADMIN_ID

Table for the Entity

BOOK -BOOK_NAME
BOOK_ID AUTHOR TYPE GENERA FILE APPORVED

Table for the Entity

USERFNAME
ID
- LNAME EMAIL CONTACT PASSWORD
 Normalized table 3NF
•Be in 2 NF

•Should not have Transitive Dependencies.

Table for the Entity ARTICLE Table for the Entity

-
ARTICLE_ID TOPIC CONTENT PUBLISED BY ADMIN - PASSWORD
ADMIN_ID

Table for the Entity

BOOK -BOOK_NAME
BOOK_ID AUTHOR TYPE GENERA FILE APPORVED

Table for the Entity

USERFNAME
ID
- LNAME EMAIL CONTACT PASSWORD
4.3 Data Flow Diagrams (DFDs)
DFD 0 – Context Level
4.3 Data Flow Diagrams (DFDs)
DFD 1 – Process 1.0
4.3 Data Flow Diagrams (DFDs)
DFD 1 – Process 2.0
4.3 Data Flow Diagrams (DFDs)
DFD 1 – Process 3.0
Appendices