PROJECT PLAN

TITLE AND SCOPE OF PROJECT

Title: LIBRARY MANAGAMENT SYSTEM

SCOPE:
The system accepts the General Library Transactions of book issue, return and
renewals for the members

INITIAL ACTIVITY:
Project Plan
1. OUTPUTS OR DELIVERABLES FOR THE PROJECT:
ITEM REQUIREMENT RESPONSIBILTY PLANNED
DATE
ACTUAL
DATE
STATUS
1. Software Turbo C Vidhyalakshmi
R., G. Vidhya,
Roja Sanna
Reddy, Shabnam
Shaik
Completed
2. Documents MS Word Vidhyalakshmi
R., Shabnam
Shaik
Completed


2. RESOURCE REQUIREMENTS


RESOURCE
NAME
WHY WE NEED
A RESOURCE
WHERE WE
GET THE
RESOURCE
FROM
HOW LONG
WE NEED THE
RESOURCE
HOW DO
WE GET
THE
RESOURCE
CURRENT
STATUS
CONTINGENCY
ACTION
1 Hardware For
construction
of the
system
St. Josephs
College Of
Engineering
Throughout
the
construction
phase
Request
the
faculty
Available Work At
Home
2 Software For
construction
of the
system
St. Josephs
College Of
Engineering
Throughout
the
construction
phase
Request
the
faculty
Available Work At
Home


3. RISKS IDENTIFIED IN THE PROJECT
RISKS PROBABILITY
(%)
SEVERITY (%) ACTION PLAN
1. Missed Deadlines 80 100 Regular
Discussion
between the
team and
taking print
outs
2. Defects in the end
product due to problems
during integration
90 100 Discuss the
faculty and
find the info
from books
and help
3. Difference in Standards
followed like naming
convention
80 100 Discuss the
naming
convention
with
members
4. ALLOCATION OF TASKS
TASKS RESPONSIBILITY
1. Writing the source code for Library Management
System
Vidhyalakshmi R., Vidhya G.,
Roja Sanna Reddy, Shabnam
Shaik
2. Creating documents such as SRS, Abstract,
Project plan
Vidhyalakshmi R., Vidhya G.,
Roja Sanna Reddy
3. Designing reports, E-R Diagrams,DFD,STD Vidhya G., Shabnam Shaik





















SOFTWARE REQUIREMENT SPECIFICATION DOCUMENT


1. SCOPE
OVERVIEW:
The Library Management System is an online application for assisting a
librarian in managing a book library in a university. The system would
provide basic set of features to add/update members, add/update books,
and manage check in specifications for the systems based on the clients
statement of need.


2. FUNCTIONAL REQUIREMENTS

MODULE I: MEMBER MANAGEMENT

Sub-module 1: mem_store()
DESCRIPTION:
This is a master entry screen to add the details of a student. Each entry has
the following attributes:
1. Student Name
2. Student Age
3. Student Roll Number
4. Student Year
5. Number of Tokens
INPUTS:
1. Name
2. Age
3. Roll number
4. Year
5. Number of tokens

OUTPUTS:
A record is created in the database
ALGORITHM:
The various student details including the name, age, roll number, year,
and number of tokens available are taken as input to create a record.



Sub-module 2: mem_display()
DESCRIPTION:
This module is used to display the member details.
OUTPUT:
1. Name
2. Age
3. Roll number
4. Year
5. Tokens

ALGORITHM:
1. Open the student.dat file.
2. Read the contents from the file.
3. Display the contents of the file.



Sub-module 3: memb()
DESCRIPTION:
This module is used to check is the student is a valid member or not.
INPUT:
1. Student Roll number
OUTPUT:
Valid Member/Invalid
ALGORITHM:
1. Open the file student.dat.
2. The roll number is entered.
3. The given roll number is compared with the file contents.
4. If valid, print Valid member
Else
Print Invalid



Sub-module 4: mem_delete()
DESCRIPTION
This module is used to delete a member from the record.
INPUT:
Enter the roll number of the student whose details are to be deleted..
OUTPUT:
The deleted roll number is displayed and the record is deleted.
ALGORITHM:
1. The roll number of the student whose account is to be deleted is obtained
from the user.
2. The details of the student are deleted.
3. The changes in the file are saved.
4. The deleted roll number is displayed.

MODULE II: BOOK MANAGEMENT


Sub-module 1: bk_store()
DESCRIPTION
Add the book details. Each entry has the following attributes:
1. Book Name
2. Book Author
3. Book Count
4. Book Edition
INPUT:
1. Title
2. Author
3. Count
4. Edition
OUTPUT:
A record is added to the book database.
ALGORITHM:
The various details of the book such as the Title, Author, Count, Edition are
entered in the book database.



Sub-module 2: bk_display()
DESCRIPTION
This module is used to display the book details.
OUTPUT:
1. Book Name
2. Book Author
3. Book Count
4. Book Edition
ALGORITHM:
1. Open the file Book.dat.
2. Read the contents from the file.
3. Display the contents of the file.

MODULE III: TRANSACTION


Sub-module 1: issue()
DESCRIPTION
This module is used to issue a book to a student.
INPUT:
1. Book Name
2. Student Roll number
3. Data(issue)
OUTPUT:
1. Book Issued
2. Change in database
ALGORITHM:
1. On valid entry of the roll number of the student and the book name, the
book is issued and necessary changes made in the member and book
databases .
VALIDATION:
1. To check the validity of the roll number
2. To check the validity of the book name
3. To check if the number hasnt exceeded the total number of tokens
available for each student.
ERROR HANDLING:
Rejects the issue request on the failure of any one of the above validation
criteria.



Sub-module 2: bk_return()
DESCRIPTION
This module enables the student to return a book.
INPUT:
1. Book name
2. Student Roll number
3. Data (return)
OUTPUT:
1. Book return
2. Change in the databases
ALGORITHM:
1. On valid entry of roll number of the student and the book name, the book
return operation is performed and necessary changes are made in the
member databases and the book database.
VALIDATION
1. To check the validity of the students roll number
2. To check the validity of the book name
ERROR HANDLING
Reject the return request on the failure of any of the above validation criteria.
HARDWARE AND SOFTWARE REQUIREMENTS

HARDWARE:
Pentium Processor
SOFTWARE:
Turbo C (Version 3)
ASSUMPTIONS AND DEPENDENCIES:
The software is effective on a stand-alone system.