Documents

CONTENTS

1. Brief introduction to project
2. Process Model used
3. Software Requirement specification
i. Scope
4. Functional Requirement
ii. Member management
iii. Book management
iv. transcations
5. Context Level diagram
6. Use case Diagrams
7. Activity diagrams


















Introduction To Project:



The Library Management System is an application for
assisting a librarian in managing a book library. 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.



Process Model Used:

In our project we have used WATERFALL model. Because in our project ‘Library Management System’ all the requirements are well defined and reasonably stable.

The waterfall model, sometimes called the classic life cycle, suggests a systematic, sequential approach to software development that begins with customer specification of requirements and progresses through planning, modeling, construction and deployment, culminating in on-going support of the complete software.


Software Requirement specification:

Scope:

Project scope will be contains the following activities:
• User activities
• Books transactions
• Member Management System



FUNCTIONAL REQUIREMENTS

MEMBER MANAGEMENT
Sub-module: member_store()
DESCRIPTION:

This is a master entry screen to add the details of a student.
Each entry have some attributes like student name, student
Age, student roll number, student year and student
registration number, list is as follows,

• 
  
• Each entry has the following attributes:
•  Student Name
•  Student Age
•  Student Roll Number
•  Student Year
•  Registration Number

INPUTS:

This module will take some attributes as input these modules
Includes name of the student, age of the student, roll number of
The student, year in which student is studying and his/her
Registration number.



OUTPUTS:
This module in response to the input will create a record for the user so that user information can be accessed using this record.

ALGORITHM:
The various student details including the name, age, roll
number, year, and Registration number available are taken as
input to create a record.





Sub-module: member_display()

DESCRIPTION:
This module is will show all record related to any member of the
Library related to books transactions. In short we can say that this module will display the member details.

OUTPUT:
When a requested is send to see some information about a user, this
Module will display name of the member, age of the member, roll
Number of the member, year in which the student is studying and
His/her registration number.

•  Name
•  Age
•  Roll number
•  Year
•  Registration

ALGORITHM:

Open the file which contain the record (“student.dat”) the
Record of the requested student. Read the contents of that
file and then display that record.


Sub-module: memb()

DESCRIPTION:
This module is used to check is the student is a valid
member of the library or not.

INPUT:
This module will take roll number as an attribute to
Check whether the provided roll number exist in record
Or not.

OUTPUT:
As an out to the request this module will response that
Whether any user is valid member or not.


ALGORITHM:

•  Open the file “student.dat” from the database.
•  Then take roll number entered as an input.
•  The given roll number is compared with the file contents.
•  If valid, print “Valid member”

Else
Print “Invalid”
Sub-module: member_delete()

DESCRIPTION
This module is used to delete a member from the record.

INPUT:

This module take the roll number of the student whose details are to be
Deleted, as input.
OUTPUT:
The deleted roll number from the database is displayed and the record is deleted.
ALGORITHM:

•  The roll number of the student whose account is to be
•  Deleted is obtained from the user.
•  The details of the student are deleted.
•  The changes in the file are saved.
•  The deleted roll number is displayed.

MODULE: BOOK MANAGEMENT

Sub-module: bk_store()

DESCRIPTION
This module will add the book details. Each entry has the following attributes:

•  Book Name
•  Book Author
•  Book Count

4. Book Edition
INPUT:

Input of this module are the title of the book, author of the book,
Number of books add in the system, edition of the book. The list
Of the input is as follows:

• Title
•  Author
•  Count
•  Edition

OUTPUT:
As an output of this system a record is added to the book database.

Sub-module: bk_display()

DESCRIPTION
This module is used to display the book details.
OUTPUT:


This module will show the book name, author name of the book
Number of Book and the edition of book as an output.
 Name
 Book Author
 Book Count
 Book Edition

ALGORITHM:

•  Open the file “Book.dat”.
•  Read the contents from the file.
•  Display the contents of the file.

MODULE: TRANSACTION

Sub-module 1: issue()

DESCRIPTION
This module is used to issue a book to a student.
INPUT:

• 
  
•  Book Name
•  Student Roll number
•  Data(issue)

OUTPUT:

• Book Issued
•  Change in database

ALGORITHM:
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:

•  To check the validity of the roll number
•  To check the validity of the book name
•  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: bk_return()

DESCRIPTION
This module enables the student to return a book.
INPUT:

• Book name
•  Student Roll number
•  Data (return)

OUTPUT:

•  Book return
•  Change in the databases

ALGORITHM:
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:

•  To check the validity of the student’s roll number
•  To check the validity of the book name

ERROR HANDLING:
Reject the return request on the failure of any of the above
Validation criteria.