Library Management System

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 REQUIREM RESPONSIB PLANN ACTU ENT ILTY ED AL DATE DATE 1 Software Turbo C Vidhyalaksh . mi R., G. Vidhya, Roja Sanna Reddy, Shabnam Shaik 2 Documen MS Word Vidhyalaksh . ts mi R., Shabnam Shaik

STATUS

Complet ed

Complet ed

2. RESOURCE REQUIREMENTS RESOUR CE NAME

WHY WE NEED A RESOURCE

WHERE WE GET THE RESOURC E FROM

HOW LONG WE NEED THE RESOURCE

HOW DO WE GET THE RESOUR CE

CURRE NT STATUS

CONTINGE NCY

1 Hardwa re

For constructi on of the system

St. Joseph’s College Of Engineeri ng

Througho ut the constructi on phase

Reques t the faculty

Availab Work At le Home

ACTION

2 Softwar e

For constructi on of the system

St. Joseph’s College Of Engineeri ng

Througho ut the constructi on phase

Reques t the faculty

Availab Work At le Home

3. RISKS IDENTIFIED IN THE PROJECT 4. ALLOCATION OF TASKS RISKS PROBABILIT SEVERITY Y (%) (%) 1 Missed Deadlines 80 100 .

2 Defects in the end . product due to problems during integration

90

100

3 Difference in . Standards followed like naming convention

80

100

5. ALLOCATION OF TASKS TASKS

ACTION PLAN Regular Discussion between the team and taking print outs Discuss the faculty and find the info from books and help Discuss the naming convention with members

RESPONSIBILITY

1 Writing the source code for Library . Management System 2 Creating documents such as SRS, . Abstract, Project plan 3 Designing reports, E-R . Diagrams,DFD,STD

Vidhyalakshmi R., Vidhya G., Roja Sanna Reddy, Shabnam Shaik Vidhyalakshmi R., Vidhya G., Roja Sanna Reddy 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 client’s 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. 2. 3. 4. 5.

Name Age Roll number Year 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. 2. 3. 4. 5.

Name Age Roll number Year Tokens

ALGORITHM: Open the “student.dat” file. 2. Read the contents from the file. 1.

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. 2. 3. 4.

Open the file “student.dat”. The roll number is entered. The given roll number is compared with the file contents. 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. 2. 3. 4.

Book Book Book Book

Name Author Count Edition

INPUT: 1. 2. 3. 4.

Title Author Count 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. 2. 3. 4.

Book Book Book Book

Name Author Count 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 hasn’t 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 student’s 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.