SOFTWARE DESIGN

SPECIFICATION
1. Introduction
1.1 Purpose
The purpose of this Design Document is to present the system design at a level that can be
directly traced to the specific system objective along with providing more detailed data,
functional, and behavioral requirements. This Design Document will verify that the current
design meets all of the explicit requirements contained in the system model as well as the
implicit requirements desired by the customer. System design aims is to identify the modules that
should be in the system the specification of these modules and how they interact with each other
to produce the desired result. The goal of the design process is to produce a module or
representation of a system which can be used later to build that system. The produced model is
called design of the system.

1.2 Scope

The project work titled “LIBRARY MANAGEMENT SYSTEM” is helpful for librarian, who
wants to deal many bus books in a day. Library Management System is a windows application
written for 32-bit windows operating systems which focused in the area of issuing books to
members and returning books from members. For the efficient working of library, some features
should be added. Before transactions, some registrations should be done. These registrations are
category, block, language, book, member type and member. In this library system, number of
books issued at a time to staff.
In the existing system most of the functions have been done manually, which have many
drawbacks. Manual processing is tedious and time consuming. The staffs are unable to deal with
number of operations effectively at a time.

Definitions & Acronyms

Administrator - Person who maintains and controls the entire system.

Acronyms Or Abbreviations
DB- Database
SQL- Structured Query Language
API- Application Programming Interface
INFO-Information
IEEE- Institute of Electrical and Electronics Engineers

References
 Patricia A. Hartman ,”Visual Basic 6.0”, IDG Books, Second Edition 2011.
 Elias M..Awad , “System Analysis And Design”, Galgotia publications , Second Edition.
 Pankaj Jalote, “An Integrated Approach To Software Engineering”, Narcosis Publishing
House, Third Edition 2005
 Silberschatz, korth, sudarshan, “Database System Concepts”

3. Decomposition Description

Library Management System

BLOCK CATEGORY BOOK COPY MEMBER BOOK BOOK BOOK

DETAILS DETAILS DETAILS DETAILS DETAILS ISSUE RENEW RETURN

 BLOCK DETAILS
In Block Registration the details of block are stored. Block separated based on different
department. It include block id and block name. These details are stored in the table block. By
using this module, we can add new record

 CATEGORY DETAILS
In Category registration the details of the book based on different department are stored. It
includes category id and category type. These details are stored in the table category. By using
this module, we can add new record

 BOOK DETAILS
In Book registration the all Information of the book are stored. It includes book id, book name,
category, language, author, volume, publisher, version, edition, prize .These details are stored in
the table book. By using this module we can add new routes.

 COPY DETAILS

In Copy registration copies of different books are stored. It includes the details of book. These
details are stored in the table copy. We can add new record.

 MEMBER DETAILS
In Member registration all the details of member are stored. It includes member id, member
name, member type, gender, address, phone number, email are stored. These details are stored in
the table member. We can add new record and update a record.

 BOOK ISSUE
 In Book issue the details about the book and Details about the member are stored. It includes
issue id, date, member details and book details. These details are stored on the database.

 BOOK RENEW
In Book renew the details about the book that renewed by the member and Details about the
member are stored. It includes renew id, issue id, date, member details and book details. These
details are stored on the tables’ issue master and issue details

 BOOK RETURN
In Book return the details of book and details of member are stored. It includes details such as
return id, return date, book name, author, version, price, copy no, member name, and address.
These details are stored in the database.

4. Component Detailed Design Description

4.1 Admin
4.1.1 Structure

ADMIN

BLOCK CATEGORY BOOK COPY MEMBER BOOK BOOK BOOK

DETAILS DETAILS DETAILS DETAILS DETAILS ISSUE RENEW RETURN

4.1.2 Function
This module helps to Registration of block, category, books, copy of books, member and
book issue, book renew and book return.
4.1.3 Sequential Control Feature
The Admin enter into system by login using username and password
4.1.4 Application Data
The data inputted to this module are username, password, details about book, details
about member etc.
4.2 User
4.2.1 Structure

USER

MEMBER BOOK BOOK BOOK

DETAILS ISSUE RETURN RENEW
 4.2.2 Function
This module help collecting member details, issue, renew and return of books that
member want.
4.2.3 Sequential Control Feature
Users first enter the details. Then the store on database
4.2.4 Application Data
The input of the module is enter the details of user such member details, book details of
user wanted books and all book transaction related fields.

5.Major Constraints
User interface is only in English, no other language option is available .For normal operation this
s/w will require minimum of 1 GB RAM in the client machine. The product is system based
application. So it will work at without network connection. Network problem, does not affect the
functioning of the software. No additional hardware components are required other than standard
I/O devices and power supply devices.

6.Data Design

6.1 Data Structure

6.2 Database Description

Table: LOGIN

FIELD NAME DATATYPE LENGTH CONSTRAINS DESCRIPTION

Username Varchar 50 Primary key User name

Password Varchar 50 Password

Table: BLOCK_REG

FIELD NAME DATA TYPE LENGTH CONSTRAINS DESCRIPTION

block_id Int 4 Primary key Block id
block_name Varchar 50 Block name

Table: CATEGORY

FIELD NAME DATA TYPE LENGTH CONSTARINS DESCRIPTION

cat_id Int 4 Primary key Category id
Cat_name Varchar 50 Category name
block_id Int 4 Foreign key Block ID

Table: BOOK_REG

FIELD NAME DATATYPE SIZE CONSTRAINS DESCRIPTION

buk_id Int 4 Primary key Book id
Buk_name Varchar 50 Book Name
cat_id Int 4 Foreign key Category ID
buk_vol Int 4 Book Volume
buk_lang Varchar 50 Language
buk_auth Varchar 50 Author
buk_publi Varchar 50 Publication
buk_ver Int 4 Version
buk_price Money 8 Price
buk_date Int 4 Date

Table: COPY_REG

FIELD NAME DATATYPE LENGTH CONSTRAINTS DESCRIPTION

Copyno Int 4 Primary key Copy no
Bookid Int 4 Foreign key Book id
Status Int 4

Table: STUDENT_REG

FIELD NAME DATATYPE LENGTH CONSTRAINS DESCRIPTION

Stu_id Int 4 Primary key Student ID
Stu_name Varchar 50 Student Name
Stu_course Varchar 50 Course
Stu_add Varchar 50 Address
Stu_gend Varchar 50 Gender
Stu_ph Bigint 8 Phone Number
Stu_email Varchar 50 Email ID
Stu_status Int 4 Status
Stu_date Datetime 8 Date
Table: BOOK ISSUE

FIELD NAME DATATYPE LENGTH CONSTRAINTS DESCRIPTION

Issue_id Int 4 Primary key Issue id
Stu_id Int 4 Foreign key Student ID
Isu_date Datetime 8 Issue date
Status Int 4 Status

Table: ISSUE DETAILS

FIELD NAME DATATYP LENGTH CONSTRAINTS DESCRIPTION

E
Issued_id Int 4 Primary key Details id
Issue_id Int 4 Foreign key Issue id
Copy_id Int 4 Foreign key Copy ID
Rtn_date Datetime 8 Return Date

Table: RENEW MASTER

FIELD NAME DATATYPE LENGTH CONSTRAINT DESCRIPTION

ren_id Int 4 Primary key Renew ID
Issue_id Int 4 Foreign key Issue ID
Ren_date Datetime 8 Date

Table: RENEW DETAIL

FIELD NAME DATATYPE LENGTH CONSTRAINT DESCRIPTION

Rend_id Int 4 Primary key Detail ID
Ren_id Int 4 Foreign key Renew ID
Copy_id Int 4 Foreign key Copy ID

Table: RETURN MASTER

FIELD NAME DATATYPE LENGT CONSTRAINT DESCRIPTION

H
Rtn_id Int 4 Primary key Return id
Issue_id Int 4 Foreign key Issue id
Rtrn_date Datetime 8 Return date
fine Money 4 Fine
Table: RETURN DETAILS

FIELD NAME DATATYPE LENGTH CONSTRAINT DESCRIPTION

Rtnd_id Int 4 Primary key Return details id
Rtn_id Int 4 Foreign key Return id
Copy_id Int 4 Foreign key Copy ID

7. Software Interface Description

The project is done by using Visual Basic 6.0. Where Visual Basic as front end language and
Microsoft SQL Server 2000 as the back end.

8. Appendices
8.1 Architecture Diagrams

8.1.1 Use case Diagram

 Block Registration

Book Registration

Copy Registration

Student Registration
LIBRARIAN STUDENTS

Book Issue

Book Return

Book Renew