1. A PROJECT REPORT ON
LIBRARY MANAGEMENT
(LIBRARY MASTER & ISSUE AND RETURN DETAILS)
VOCATIONAL TRAINING AT
!
MECON LIMITED, RANCHI
A GOVT OF INDIA ENTERPRISE
UNDER THE GUIDANCE OF
MR. P.K.DUBEY
IT SERVICES,
MECON LTD, RANCHI
SUBMITTED BY:
SUMEDH KUMAR SINGH
B.TECH, COMPUTER SCIENCE AND ENGINEERING
REGISTRATION NO. - 1210312259
IIND YEAR,
GITAM INSTITUTE OF TECHNOLOGY
VISAKHAPATNAM
SESSION: 2012-2016
1
2. ACKNOWLEDGEMENT
I take this opportunity to express my profound gratitude and deep regards to my guide MR.
P.K.DUBEY for his exemplary guidance, monitoring and constant encouragement throughout the
course of this thesis. The blessing, help and guidance given by him time to time shall carry me a
long way in the journey of life on which I am about to embark.
I also take this opportunity to express a deep sense of gratitude to MR. A. BHATTACHARYA,
DGM IN-CHARGE, IT SERVICES, MECON LTD, RANCHI, for his cordial support, valuable
information and guidance, which helped me in completing this task through various stages.
I am also grateful to MR. Rupam Baruah for his day today help and support provided to
complete this project. I am obliged to staff members of MECON LIMITED, for the valuable
information provided by them in their respective fields. I am grateful for their cooperation during
the period of my assignment.
Lastly, I thank almighty, my parents, sister and friends for their constant encouragement without
which this assignment would not be possible.
Sumedh Kumar Singh
1210312259
B.Tech
C.S.E, IIND Year,
Gitam Institute of
Technology,
Visakhapatnam
Session: 2012-2016
Place: Ranchi
Dated: 04-JUNE-2014
2
3. INDEX
SL. No CONTENTS PAGE NO.
1. Synopsis 4-5
2. Feasibility Study 5-6
3. System Architecture 6-7
4. Understanding Oracle Express 7-9
5. Creation and Installation of Database 10-11
6. Data Tables 12-14
7. Data Flow Diagram(DFD) 14
8. Entity Relationship Model 15
9. Creating Initial Application 15-18
10. Snapshots of the Forms 19-22
11. Deployment of the Application for the End Users 23
12. Future Scope 24
13. Conclusion 25
14. Bibliography 26
3
4. SYNOPSIS
1. Introduction:
The main objective of the application is to automate the library management system. This
software application manages the student details, employee details, books details. This system
deals with the books issue, book return operations, and fine calculations. This also takes care for
security options. The main modules of this project are Books information management system
module, issue-return operations module, personal detail management module, book’s supplier
module.
Library Management System is an application refer to other library system and it is suitable to
use by small and medium size library. It is used by librarian and library admin to manage the
library using a computerized system. The system was developed and designed to help librarian
record every book transaction so that the problem such as file missing or record missing will not
happened again.
1.1 Purpose:-
The purpose of this application are as follows:
• The software is for automation of library.
• It provides following facilities to:
a) Operator:
• Can enter details related to a particular book.
• Can provide membership to members.
b) Admin:
• Can read and write information about any Member.
• Can update, create and delete the record of Membership as per requirement and
implementation.
4
5. 1.2 Scope:
The different areas where we can use this application are:
• Any education institute can make use of it for providing information about author, content of
the available books.
• It can be used in offices and modifications can be easily done according to requirements.
1.3 Technology Used:
Front End: Application Express 4.0 (APEX)
Back End: Oracle XE 11G, Apache Tomcat server.
1.4 Assumptions
• This application is used to convert the manual application to the online application.
• Customized data will be used in this application.
• User does not have right to enter information about books.
1.5 Overview:
Project is related to library management which provides reading services to its members. Any
person can become a member of the library by filling a prescribed form. They can get the book
issued, so that they can take the books home and return them after the issued period.
1.6 Functionality:
• Online membership.
• Keeps the track of issues and submission of books.
Feasibility Study:
In feasibility study phase we had undergone through various steps which are describe as under:
1. Identify the origin of the information at different level.
2. Identify the expectation of user from computerized system.
5
6. 3. Analyze the drawbacks of existing system (manual).
WORKING OF PRESENT MANUAL SYSTEM:
The staffs of library are involved in the following tasks.
1. Membership process: person have to fill membership form and they are provided with member
DRAWBACKS OF PRESENT SYSTEM:
Some of the problems being faced in manual system are as follows:
1. Fast report generation is not possible.
2. Tracing a book is difficult.
3. Information about issue/return of the books are not properly maintained.
4. No central database can be created as information is not available in database.
PROPOSED SYSTEM
There will be three major components:
1. Stock maintenance.
2. Transaction entry.
3. Reports.
Proposed system provides with following solutions:
1. It provides "better and efficient" service to members.
2. Reduce the workload of employee.
3. Faster retrieval of information about the desired book.
4. Provide facility for proper monitoring reduce paper work and provide data security.
5. All details will be available on a click.
6
7. System Architecture
The proposed application is developed as two tire application in which workloads are between
the provider of a resource or service, called servers, and services requesters, called clients.
Often clients and servers communicate over a computer network on separate hardware but both
client and server may reside in the same system. A server machine is the host that is running one
or more programs which share their resources with clients. A client does not share any of its
resources. But requests a server’s content or service function. Clients therefore initiate
communication sessions with servers which awaits incoming requests. The following system is
proposed.
Understanding Oracle Application Express Architecture
About Oracle Application Express Listener, Oracle HTTP Server (Apache), and the Embedded
PL/SQL Gateway. The version of Oracle Database you use determines how the URL is
translated:
■ Versions prior to Oracle Database 11g Release 1 require Oracle Application Express Listener
or Oracle HTTP Server (Apache) with mod_plsql. The following graphic illustrates the three-tier
architecture when using Oracle HTTP Server (Apache).
!
7
8. ■ With Oracle Database 11g Release 1 or later or Oracle Database Express Edition, you can use
the embedded PL/SQL gateway. The following graphic illustrates the two-tier architecture using
the embedded PL/SQL gateway
.
!
!
8
9. The following illustration shows multiple users with various roles accessing the oracle
application express environment, Application express administration services, and the published
applications.
!
Application Express Administrator, Workspace Administrator, and Developer. The following
illustration shows an Oracle Application Express instance with a single user.
9
10. !
Creation and installation of Database:-
1. In a web browser , go to : http:// localhost:8080/apex/
2. Under the login button, click sign up for an account.
The Registration Wizard appears. Note the steps included in the wizard. In a flowchart on
the left side of the page. From admin service creating a workspace. A workspace is a shared
work area within the oracle application express development environment that has a unique
ID and name. All users in the workspace can access all its application and scripts.
To create a workspace:
1. Log in to Oracle Application Express Administrative Services. The Homepage of
Administrative Services appears.
2. Click manage workspaces
3. Under manage Workspaces, Click Create Workspace.
10
12. SQL Workshop Snapshot:
Data Tables:
Table: Members
C o l u m n
Name
Data Type Nullabl
e
P r i m a r y
Key
Description
MEMBER_ID NUMBER No 1 Membership Identification
Number
NAME CHAR(70) Yes Name
ADDRESS VARCHAR2(2
00)
Yes Address of the Member
REG_DATE DATE Yes Date of Registration
EXP_DATE DATE Yes Registration expiry Date
MEM_TYPE CHAR(20) Yes Permanent/Temporary
NATIONALITY CHAR(20) Yes Nationality
12
13. Table: Add Books
POST_CODE NUMBER Yes Postal Code
PHONE_NO NUMBER Yes Contact number
NRIC NUMBER Yes Identification Proof Number
DATE_OF_BIR
TH
DATE Yes Date of Birth
EDUCATION CHAR(30) Yes Educational Qualification
STREAM CHAR(20) Yes Stream
PARENT_NAM
E
CHAR(50) Yes Name of Parent
PARENT_NRIC NUMBER Yes Parent's Identification Proof
Number
C o l u m n
Name
Data Type Nulla
ble
Primary
Key
Description
BOOK_CODE NUMBER No 1 Book identification Number
BOOK_NAME VARCHAR2(
100)
Yes Name of the book
AUTHOR CHAR(100) Yes Author of the book
ISBN NUMBER Yes ISBN code of the book
DATE_OF_ARR
IVAL
DATE Yes Date on which book was received
PRICE NUMBER Yes Price of the book
RACK_NO VARCHAR2(
20)
Yes Rack on which the book is kept
13
14. Table: Issue
NO_OF_BOOK
S
NUMBER Yes Number of copies of the book
SUBJECT_COD
E
VARCHAR2(
20)
Yes Unique identification number of
particular subject
BOOK_SUBJEC
T
VARCHAR2(
40)
Yes Subject of the book
BOOK_CATEG
ORY
CHAR(30) Yes Category of the book
COPYRIGHT_Y
EAR
NUMBER Yes Year of copyright
BOOK_CLASS VARCHAR2(
50)
Yes Book Class
BOOK_PUBLIS
HER
VARCHAR2(
5)
Yes Publisher of the book
Column Name Data Type Nullable Primary Key Description
BOOK_ID NUMBER No 1 Unique Identification code of the
book
BOOK_NAME CHAR(30) Yes Name of the book
ISSUE_DATE DATE Yes Date on which the book is issued
DUE_DATE DATE Yes Date on which the book is to be
returned
14
17. Creating the initial Application
This first exercise guides you through creating your initial application. Using the Create
Application Wizard, you create two pages and specify basic application functionality.
The page created in this section include:
Home – This page is the first page displayed when the application is run. This page contains a
link to the Department Report.
Departments- This page is an interactive report of all Departments.
To create your initial application:
1. Log in to Oracle Application Express
2. On the Workspace home page, Click Application Builder
3. Click the Create button
The Create Application Wizard appears,
!
17
18. !
Select from Scratch and click next. Then type the desired application name and click Next
!
18
19. Main Screen:
From this form a user can select the various assets related forms and can perform the data
manipulation as per requirement.
!
Click on Create page and then Select Form and click Next
19
25. Deployment of Application for the End Users
This describes basic information about deploying the Oracle Application Express application. It
also shows us how to create end users and to determine the URL of our Application.
To create end user account:
1. Navigate to the Workspace home page.
2. From the Administration links list on the right, click Manage Application Express Users.
3. Under the Tasks list on the right, click the Create End User link.
4. Under Account Control:
Set Account Availability – Select Unlocked.
Require Change of Password on First Use – Select No if you do not want to force the user
to change his/her password at first login.
5. Under User Identification, Enter the Appropriate Information:
a. User name – Enter a user name for the end user.
b. Password and Confirm Password – Enter a case- sensitive password for this account.
c. Email Address – Enter a valid email address for the end user.
6. Under Developer Privileges:
a. Accessible Schemas (null for all) – Leave this blank to allow the end user to access
all applications in the workspace, or enter a colon-delimited list of schemas to restrict
the end user’s access. If a user does not have access to the schema that an application
is built on, the user cannot access the application.
b. Default Schema – Accept the default value, that is, the schema you set up for this
guide
25
26. c. User is a Developer – Accept the Default- No.
d. User is a Workspace Administrator- Accept the default, No
Selecting No, limits the user to only accessing and using the application, not
modifying the application itself
7. Under User Groups, you can select a user group.
8. Under Additional Attributes, you can select a user group.
9. Click Create User or Create and Create Another.
Future Scope:
Future Scope of the Application:
This application can be easily implemented under various situations. We can add new
features as and when we require. Reusability is possible as and when require in this
application. There is flexibility in all the modules.
Software Scope:
• Extensibility: This software is extendable in ways that its original developers may not
expect. The following principles enhances extensibility like hide data structure, avoid
traversing multiple links or methods, avoid case statements on object type and distinguish
public and private operations.
26
27. • Reusability: Reusability is possible as and when require in this application. We can
update it next version. Reusable software reduces design, coding and testing cost by
amortizing effort over several designs. Reducing the amount of code also simplifies
understanding, which increases the likelihood that the code is correct. We follow up both
types of reusability:
Sharing of newly written code within a project and reuse of previously written code on
new projects.
• Understandability: A method is understandable if someone other than the creator of
the method can understand the code (as well as the creator after a time lapse). We use the
method, which small and coherent helps to accomplish this.
• Cost-effectiveness: Its cost is under the budget and make within given time period. It is
desirable to aim for a system with a minimum cost subject to the condition that it must
satisfy the entire requirement. Scope of this document is to put down the requirements,
clearly identifying the information needed by the user, the source of the information and
outputs expected from the system.
27
28. Conclusion
From a proper analysis of positive points and constraints on the component, it can be
safely concluded that the product is a highly efficient GUI based component. This
application is working properly and meeting to all user requirements. This component can
be easily plugged in many other systems.
28
29. Bibliography
Books:
• Oracle XE Getting Started Guide
• MySQL for Dynamic Websites
• The Oracle Ace
Websites:
• www.oracle.com
• www.stackoverflow.com
29
