Library Management System

Share Embed Donate


Short Description

Download Library Management System...

Description

LIBRARY MANAGEMENT SYSTEM

2

TABLE OF CONTENTS - II

CHAPTER

CONTENT

PAGE NO.

ABSTRACT

27

ANALYSIS

28

1.1 Schedule of Project

29

DESIGN

30

2.1 Level 0 DFD Diagram

31

2.2 Level 1 DFD Diagram

31

2.3 Level 2 DFD Diagram

33

2.4 Database Design

35

3

CODING

37

4

OUTPUT WINDOWS

57

5

CONCLUSION

62

6

REFERENCE

63

1

2

3

ABSTRACT The project focuses on the development skills of the user. The knowledge acquired proves to be helpful and effective, only if it is implemented. The implementation of the knowledge acquired is trough project and case studies based on real time scenarios. The “LIBRARY MANAGEMENT SYSTEM” undertaken as a project is based on relevant technologies .The projects are done in groups where the student learn to work in a team, manage project schedules ,follow the best coding standards and conventions and adhere to project documentation standards. Here in this project we use front end as VC++ and backend as ms-access. We store information about the books and the students who have taken the books. All these details are stored in the database by entering into VC++ and the details can be displayed from the database by writing the query in VC ++. This project involves several modules to carry out each action. We created database for storing the details in tables .We created table for MEMBER DETAILS, a table for storing BOOK DETAILS and another table for storing the details of the students who have taken the books namely MEMBER BOOK DETAILS. We can also store the details at run time ,that is we can enter the student details by entering the details of the student separately at run time. Likewise the transaction details can also be entered at run time. We can either store in a database and see the details when required or see the details at run time by selecting the option display.

4

Hence in the existing system for LIBRARY MANAGEMENT SYSTEM ,the performance evaluation system and the maintenance are done manually. The proposed system will maintain all the information in a standard database and will be able to generate reports as and when necessary.Accessing and the user has the right to search based on the above mentioned criterias.

1. ANALYSIS PHASE In this Analysis phase we are analyzing the requirements what we want to do project. We have to collect the requirements needed to develop the project. For that we have to refer the books and websites for gathering the requirements. In this analysis phase, we have to design the project in mind how it has to be and what are all the operations that has to carry in the project and how it has to be interactive with the users and how it has to attract the customer. The project has to contain all the details about the members in the library and books in the library and the details the members who taken the books and this details has to store in the database for this type we have to analyze the problem and we have to develop the project.

In this analysis phase we have to collect the details about the

project such as what are all operations that will make interactive and what are all the fields that has to be present n the database and the database must store the details of all the members and the book details and the members who taken the books. In this analysis phase only we will collect the information about the project. This is the first stage of the project. After this only we will start doing project that is the design of the project will carry after this stage. After that we will write the project coding and we will test the project.

5

This phase will take the duration up to 1 to 2 weeks for completion of this analysis stage that is for collecting the requirements and it has to contain all the details about the project. In some projects it will take more time for completion of the analysis stage because it has to collect more requirements, it has to be depend upon the project it will take duration, hence for small type of projects we can easily complete the project within the short duration, for large projects it will take more duration for analysis stage and also for completion of the project. But for this project we can easily complete the project within the short duration because it is like a mini project and also we can easily complete the stage of analysis. If we completed the stage of analysis then it appears like we completed the 25% of the project within short duration.

1.1 SCHEDULE OF THE PROJECT

ACTIVITY

DURATION

Design Phase Implementation Coding Phase View Result Execution & Demo Report Generation

2 Weeks 2 Weeks 3 Weeks 2 Weeks 1 Week 1 Week

6

2. DESIGN PHASE In this design stage we are designing our project according to customer satisfaction or user satisfaction. In this design phase the user must understand the whole project by seeing the design of the project. After the completion of the analysis stage the user must design the project according to the collected requirements in the analysis stage. After the completion of the analysis stage the user must continue with the design stage. In this project the user must create the database to store the details of members, books, and reports tables based upon collection of table requirements collected in the design stage. In this tables, one field has been given as primary key in the design of tables because it won’t allow the duplicate values of members or it won’t accept the same id number for different members. For Book Details table also one primary key has been allocated for neglecting the same values for the field Book number and another table was created that is for storing the details of transaction that has been carried out, in that database it doesn’t have any

7

keys in that because it can contain the details many users can take the book with same account number. After creation of tables the user must design the project that is it can also represent the design in the form of Data Flow Diagrams. In the Data Flow diagrams it contains the levels that is it has to be represented in Level 0 DFD, Level 1 DFD, Level 2 DFD,… so that we can represent the Data flow diagrams in that format up to number of DFD’s required in the project. The user must design or draw the DFD diagrams based upon the project what it will do, what are the operations that was carrying in the project it will represent the DFD diagrams in the one by one operation that was carrying in the project. The user must understand the project what are all the operations in the project that was going to do or carrying out by seeing the DFD Diagrams. In that format the user must draw the DFD diagram. The DFD diagram that must contain all the details of the project.

2.1 LEVEL 0 DFD DIAGRAM: In Level 0 DFD diagram, it will display the menus of the project that is what are all we can do in the project. From that we can select the option what we are going to do. Based upon the condition it display the next screen for the selected operation. LEVEL O DFD DIAGRAM

SEARCHING THE BOOK STUDENTBOOK ENTERING ENTERING SEARCHING ENTRY THE STUDENT STUDENT BOOK DETAILS DETAIL

DISPLAYING THE BOOK DETAILS 8

DISPLAYING STORING THE THE STUDENTS BOOK STUDENT STUDENTBOOK DETAILS

2.2 LEVEL 1 DFD DIAGRAM: In Level 1 DFD diagram it takes the input details and store the details in the database. It takes the details separately for each table and store details separately in each table.

2.2.1 TO STORE THE DETAILS OF MEMBERS:

NAME

MEM NO STORING THE DETAILS IN THE DATABASE

TAKING INPUT DETAILS OF MEMBER

ADDRESS

DOB

2.2.2 TO STORE THE DETAILS OF BOOKS:

9

STOCK

BOOK

BOOK NO TAKING INPUT DETAIL S OF BOOKS

STORING THE DETAILS IN THE

AUTHOR

EDITION PUBLISHER

2.2.3 TO STORE THE DETAILS OF TRANSACTIONS

MEMNO

DATE OF RETURN

BOOK

BOOK NO TAKING DETAIL S OF TRANSA CTIONS

STORES THE DETAILS IN THE DATABASE

AUTHOR

EDITION MEMBER NAME

DATE OF ISSUE

10

2.3 LEVEL 2 DFD DIAGRAM: In Level 2 DFD diagram it displays the selected details or the details of all books present in the library and the details of selected members or all the members who are having the membership in the library and the transaction details of members who have taken books. 2.3.1 TO DISPLAY THE MEMBER DETAILS:

NAME

MEM NO DISPLAY ING OUTPUT DETAILS OF MEMBER

DISPLAYING THE DETAILS FROM THE DATABASE

ADDRESS

DOB

2.3.2

STOCK

BOOK NAME BOOK NO

DISPLAYING THE DETAILS FROM THE DATABASE

DISPLA YING DETAIL S OF BOOKS

AUTHOR

EDITION PUBLISHER

DISPLAY THE DETAILS OF BOOKS:

11

TO

2.3.3 TO DISPLAY THE DETAILS OF TRANSACTIONS

MEMNO

BOOK

DATE OF RETURN

NAME BOOK NO

DISPLAY ING DETAILS OF REPORTS

DISPLAYING THE DETAILS FROM THE DATABASE

AUTHOR

EDITION MEMBER NAME

DATE OF ISSUE

2.4 DATABASE DESIGN: 12

MS-ACCESS DATABASE : LIBRARY . MDB 2.4.1 BOOKDETAILS TABLE

FIELD NAME

DATATYPE

SIZE

BOOKNO

Text

50

BOOKNAME

Text

50

AUTHOR

Text

50

EDITION

Text

50

PUBLISHER

Text

50

STOCK

Text

50

2.4.2 MEMBER DETAILS TABLE

FIELD NAME

DATATYPE

SIZE

MEMNO

Text

50

NAME

Text

50

ADRESS

Text

50

DOB

Date/Time

8

13

2.4.3 TRANSACTION DETAILS TABLE

FIELD NAME

DATATYPE

SIZE

MEMNO

Text

50

BOOKNO

Text

50

BOOKNAME

Text

50

NAME

Text

50

AUTHOR

Text

50

DATEOFBOOKISSUE

Date/Time

8

DATEOFBOOKRETURN

Date/Time

8

EDITION

Text

50

14

3. CODING: #include # include # include # include # include # include #import "c:\Program Files\Common Files\System\ADO\msado15.dll" \ no_namespace rename("EOF", "EndOfFile") char name[50],aname[50]; int accno; int ed; int rk; int rw; int stock; void selectcase(); void memdetails(); void bookdetails(); void transactiondetails(); void addnewbook();

15

void issuebook(); void menu(); void memmenu(); void bookmenu(); void reportmenu(); void exit(); void back();

void addnewmember(); void deletemember(); //TO ADD NEW MEMBER DETAILS TO THE DATABASE void addnewmember() { //clrscr(); char name[20]; char temp[60]=" "; char memno[10]; char address[10]; char dob[10]; coutmemno; coutname;

16

coutaddress; coutdob; CoInitialize(NULL); try { strcat(temp,"INSERT INTO MEMDETAILS VALUES(' "); strcat(temp,memno); strcat(temp,"','"); strcat(temp,name); strcat(temp,"','"); strcat(temp,address);

strcat(temp,"','"); strcat(temp,dob); strcat(temp,"');"); _RecordsetPtr pRst("ADODB.Recordset"); _bstr_t strCnn("DRIVER={Microsoft Access Driver (*.mdb)};UID=admin;DBQ=LIBRARY.mdb"); pRst->Open(temp,strCnn,adOpenKeyset,adLockOptimistic,adCmdText); pRst->MoveFirst(); while (!pRst->EndOfFile) {

17

pRst->MoveNext(); } pRst->Close(); } catch (_com_error &e) { cout
View more...

Comments

Copyright ©2017 KUPDF Inc.
SUPPORT KUPDF