Download - Library management system

Library management systemAnalysis and design using UML

1/12/2009

Rabha said Mansur ID 11091

Supervised by: Dr. Adal asmeda

Library Management System

2


Introduction.

001.1 Problem statement.1.2 System objectives1.3 Project scope .1.4 Project approach1.5 Context Diagram

Notation about DFD.

2.1Data flow diagrams.2.2Decomposed DFDs.

2.2.1 Process Create bills [3].2.2.2 Process Create reports and queries [4]2.2.3 Process Maintain Books Information [1]2.2.4 Process Make book search [2]

3.1 State transaction diagram STD3.2 Screen hierarchy. Appendix:

A.1 Conclusion A.2 References

3


figures Figure 2.1 Context diagram Figure 3.1 DFD level 0 Figure 3.2 DFD level 1 Maintain Books Information Figure 3.3 DFD level 2 Maintain author Figure 3.4 DFD level 2 Maintain subject Figure 3.5 DFD level 2 Maintain sub subject Figure 3.6 DFD level 2 Maintain publisher Figure 3.7 DFD level 2 Maintain book author Figure 3.8 DFD level 2 Maintain book Figure 3.9 DFD level 1 Make book search Figure 3.10 DFD level 1 Create billsFigure 4.1 use case diagramFigure 4.2 class diagramfigure sequence diagramfigure State transaction diagram (STD)

4


1.1 Introduction.

The aim of this project is to design and implement an online library, which will enable users to search for books and browse information about these books as the abstract, publisher information, cost, table of contents, etc.

The database of the library based on one of the standardized systems for cataloging and classifying the books. We follow the standardization rules to assign subjects and sub-subjects codes, and to classify books under subjects and sub-subjects.

5


1.2The curnt system

it is manually system where librarian have to process every thing manually from organizing the books and place them in the right place write shelf to retrieve them for the library visitors and that is overwhelming consuming process

1.3 Problem for the current system.

Retrieving books from a library is very important for many peoples. The main problem is to define whether this book is exactly what the user wants and where this book resides in the library (to go and pick).

And that with be source of some of these hinders in books searching in library

1- Wasting a lot of time looking for the book in the wrong location in the library

2- Use the wrong search item and ending up with the same title for more than author

3- Misallocate books in the wrong section the wrong shelf

6


4- Search process consume allot of the librarian time as well as the visitor and it could be overwhelming for the librarian specially if they have to deal with more than one visitor at the time

There is a need for designing an advanced search engine that searches a library database and returns a complete book record, including the shelf number on which the book resides

1.3 System Objectives.

Design and implement a library database based on a standard library classification system.

Build an advanced search that can help for the best handling of user queries, this search should handle different search types like searching by author, title, subject, format or any combination of them, or searching by ISBN, or Publisher and Publication date. The search result should contain information about the exact location of the book.

Build the interface between the online screens and the library database system.

7


1.4 Project Scope.

Project scope will be contains the following activities:

- Reception activities.- Sales transactions.- Accounting system.- Book store follow up.- Using internet facilities to connect all branches

together.

Activities to be covered in our project

The following is the activities that will be covered in our project scope:-

Maintain book information. Maintain publisher information. Maintain author information. Handel search request. Handel retrieval operations like:-.

- List all books with specific title.- List all books with specific author name.- List all books classified under specific sub-

subject.

8


- List all books with any combination of title, subject and author.

- List all books published by a certain publisher.- List all books published in a certain date.- Retrieve a book with a given ISBN.- List all books belong to a certain series.

1.5 Project approach.

To solve our problems in this system, we will use the following structured approach to achieve the system goals using the next steps in analysis and design phases:-

Analysis phase: In this phase we want to analyses the system and

tray to explain the moving data between different components of the system.

* Prepare the context diagram, which it is the highest level view of the system, it contains only one process and a number of data flows and also a number of sources. It is an overview of an organizational system that shows the system boundaries, external entities that interact with the system, and the major information flows between the entities and the system.

* Data flow diagram (DFD). It is a logical model of the system. These

diagrams have a notification for each of the

9


components of the system, they also have a notification for representing different level in a hierarchy of detail used to describe the system.

*use case diagramuse case in a use case diagram is a visual representation of a distinct business function in a system. For example, In a banking application, a deposit function represents a use case

*Class diagramIt’s the conceptual model ; and it’s use conceptual ion to visuals the basic concept of the system in the analysis stage

Design phase: * Prepare the (ER) entity relationship diagram,

which it is a data model that determines the relationships between several entities in the system.

* ER to relational data model mapping. * Normalization. The normalization process takes a relation

schema through a series of tests to certify weather it satisfies a certain normal form.

*Sequences diagramIt call interaction diagram too ;in it the transformation for the analysis requirements to the it’s final functionality in the destine stage

10


2.3 Context Diagram:

The context diagram is the highest level view of the system, it contains only one process, no data stores, and a number of data flows and also a number of source/sinks. The single process represents the entire system and its labeled “o”. The source/sinks represent its environmental boundaries. Since the data stores conceptually inside the one process, no data stores appear on a context diagram.

It is an overview of an organizational system that shows the system boundaries, external entities that interact with the system, and the major information flows between the entities and the system.

In the figure, the context diagram of the System is shown. It consists of the following entities and the following data flows.

Reception: This source represents the first step to start functions of our system that this section meet the customer to give him the answers of different questions he needs.

Administration: This source represents the main department in library which responsible for managing all the information which the system needs.

11


Cashier: This section responsible for customer’s payment and issue the bills.

Data flow:

Customer request: this request from user to reception to inquiry about certain book with little information about this book, reception clerk will search and replay to customer about his needs in suitable time.

Bill: prepared by cashier for all items purchased by customer using the information system which contains information about all items in the library like item description, quantity, item price and total value for bill.

Statistical reports: prepared by computer department to help the mangers in the library to take a suitable decisions in the suitable time.

Process Library Management System

Connected via Connected to Src Dst

Bills issuing Cashier (External Entity) X

Maintain books information

Administration (External Entity) X

make search Reception (External Entity) X

Queries and Reports Reception (External Entity) X

Queries and invoices Cashier (External Entity) X

Queries and reports Administration (External Entity) X

12


13


3.2 Notation about DFD.

First, Data Flow Diagram is a logical model of the system, the model does not depend on hardware, software, data structure or file organization. It is a graphical picture of the logical system. It is an excellent tool for communication with user to explain the system for him. Data Flow diagram describes what happen not how is happens.

Data Flow diagrams have a notation for each of the components of a system. They also have a notation for representing different level in a hierarchy of detail used to describe the system. This notation makes it possible to represent an overall view of a large complex system and a detailed view of a part of a system using the same notation. Parts of a system can be isolated into independent subsystems. These work together as a unit to perform a set of processes that must be done together at one time. There is a standard process that an analyst can follow to make sure that all components of a system are identified.

Data Flow Diagrams are constructed from four basic building blocks:

Terminators Data stores , Data Flows, and Process.

14



enter sub subject data Administration (External Entity) X

Read author data Author (Data Store) X

Read book authors Book_author (Data Store) X

Read book information Book (Data Store) X

read publisher data Publisher (Data Store) X

read sub subject data Sub_subject (Data Store) X

read subject data Subject (Data Store) X

Subject data updating Subject (Data Store) X

Updating author data Author (Data Store) X

Write Book author data Book_author (Data Store) X

Write book data Book (Data Store) X

Write Publisher data Publisher (Data Store) X

Write sub subject data Sub_subject (Data Store) X

DFD level 0

15


Sub process Maintain book

16

Sub subject reading

Subject reading

Reading publisher data

Reading author data

Reading book dataReading subject data

Reading sub subject data

issue reports

Queries and invoices

Write bill data

Subject data updatingWrite sub subject data

Read book information

Books result

Write Book author data

Write Publisher data

Updating author data

author reading

Read bill data

data reading of books

create bill

Books Query

books data readingWrite book data

publisher data reading

book author_data_reading

Read book authors

read publisher data

read sub subject data

read subject data

Read author data

enter sub subject data

Administration

Cashier

Reception

1Maintain Books

Information +

2

Make book search

+

3Create

bills +

1 Author

2 Subject

3 Sub_subject

4 Publisher 5 Book_author

6 Book

Data Flow Diagram Level 0

7 Billing

4Create

reports and queries

D

D D

D

D

D

D



Enter book data Administration (External Entity) X

Read book information Book (Data Store) X

Readin book author Book_author (Data Store) X

Reading puplisher information Publisher (Data Store) X

Reading sub subject information Sub_subject (Data Store) X

Reading subject information Subject (Data Store) X

Write book data Book (Data Store) X

17

book reading

Reading book author

Reading sub subject

book read

read book

Reading subject

Readin book author

Reading puplisher information

Reading sub subject information

Reading subject information

Reading author

[Read book information]

[Write book data]

[Write Book author data]

[Read book authors]

[Write Publisher data]

[read publisher data]

[Write sub subject data]

[read sub subject data]

[Subject data updating]

[read subject data]

[Updating author data]

[Read author data]

Enter book data

Enter book author

Enter publisher data

[enter sub subject data]

Enter subject data

Enter author data

Administration

1 Author

2 Subject

3 Sub_subject

4 Publisher

5 Book_author

6 Book

1.1

Maintain author

+

1.2

Miantain subject

+

1.3Maintain

sub subject +

1.4

Maintain publisher

+

1.5Maintain

book author +

1.6

Maintain book

+

DFD Level 1 for Process #1

D

D

D

D

D

D


Sub process Maintain book author


18


Enter author data Administration (External Entity) X

Read author data Author (Data Store) X

Reading book author Book_author (Data Store) X

Updating author data Author (Data Store) X

data updating

[Reading book author]

author data

Maintenance data

Data adding

[Updating author data]

[Read author data]

[Enter author data]

1 Author

Administration

1.1.1Add new author no

1.1.2

Update author data

1.1.3Delete

author data

DFD Level 2 process 1.1

5 Book_author

D

D

Sub process Miantain subject


book reading Book (Data Store) X

19


Enter subject data Administration (External Entity) X

read subject data Subject (Data Store) X

Reading sub subject Sub_subject (Data Store) X

Subject data updating Subject (Data Store) X

data subject updating

[book reading]

[Reading sub subject]

Reading sub subject

Enter subject code

Flow of subject data

Adding new subject data

[Subject data updating]

[read subject data]

[Enter subject data]

2 SubjectAdministration

1.2.1Add new subject

code

1.2.2

Update specific subject

1.2.3

delete subject

code

DFD Level 2 for process 1.2

3 Sub_subject

6 Book

D

D

D

Sub process Maintain sub subject


enter sub subject data Administration (External Entity) X

20


read sub subject data Sub_subject (Data Store) X

Reading subject Subject (Data Store) X

Write sub subject data Sub_subject (Data Store) X

Sub process Maintain publisher


Enter publisher data Administration (External Entity) X

read book Book (Data Store) X

read publisher data Publisher (Data Store) X

Write Publisher data Publisher (Data Store) X

21

updating data

Reading book data

Enter data

Data enter

[enter sub subject data]

Reading subject

[Reading subject]

data sub subject updating

[read sub subject data]

[Write sub subject data]

Administration3 Sub_subject

2 Subject


6 Book

1.3.1Add new

sub subject

1.3.2

Update sub subject data

1.3.3

Delete sub subject

D

D

D


Publisher data updating

Updating publisher data

[read publisher data]Maintenance data

Publisher data

[read book]

[Write Publisher data][Enter publisher data]

4 PublisherAdministration

1.4.1Add new publisher


6 Book

1.4.2Update

publisher data

1.4.3Delete

publisher data

D

D

Sub process Make book search Sub process Search by authorConnected via Connected to Src Dst

author reading Author (Data Store) X

book author_data_reading Book_author (Data Store) X

books data reading Book (Data Store) X

22


Books Query Reception (External Entity) X

Books result Reception (External Entity) X

Sub process Search by book


Book query Reception (External Entity) X

Book result Reception (External Entity) X

Reading book Book (Data Store) X

Sub process Search by publisher


publisher data reading Publisher (Data Store) X

Publisher query Reception (External Entity) X

Puplisher result Reception (External Entity) X

Reading book information Book (Data Store) X

Sub process Search by subject and sub subject


Book reading data Book (Data Store) X

Sub subject reading Sub_subject (Data Store) X

Subject query Reception (External Entity) X

Subject reading Subject (Data Store) X

Subject result Reception (External Entity) X

23


Book result

Book query

Reading book

Reading book information

Puplisher result

Publisher query

Book reading data

Subject result

Subject query

[Books result]

[Sub subject reading]

[publisher data reading]

[Subject reading]

[Books Query]

[books data reading][book author_data_reading]

[author reading]

5 Book_author

4 Publisher

6 Book

Reception

1 Author

2 Subject

3 Sub_subject

2.1

Search by author

2.2Search by

subject and sub subject

2.3Search by publisher

2.4Search by

book

DVD Level 1 for process #2

D

D

D

D

D

D

Sub process Create bills


create bill Cashier (External Entity) X

data reading of books Book (Data Store) X

Queries and invoices Cashier (External Entity) X

Read bill data Billing (Data Store) X

Write bill data Billing (Data Store) X

24


Reading books

Updating bill dataenter bill data

Updating data

[Write bill data]

bill data

[Queries and invoices]invoice and report

[Read bill data]

[data reading of books]

[create bill]

Cashier

6 Book

7 Billing

3.1Add new

bill

3.2

Update bill data

3.4

Issue invoice

DFD Level 1 process #3

3.3Delete

bill data

D

D

Use case diagram

1-In this use case diagram administrate the

2-requirement with simple symbols; easy for the use to understand

3-It covers the whole system and how it works and any thing out of the system borders that means it’s not in the system

25


4-It make it easier to communicant between the client and the system developers

26


Class diagram

in this conceptual model we descript the basic concepts of the system and it’s relationships with each other ; in this point we do not pay much attention to the system behavior

in this conceptual model we determent the basic concepts of the for the library system we analysis

1-Administrative

2-Reception

3-Cashier

4-Book

27


Designe stage

28


Entity-Relationship Data Model (E-R Model):It is detailed Logical representation of the entities, association, and data elements for an organization or business area.

* Entity-Relationship Diagram (E-R Diagram):It is graphical representation of ER Model.

* Entity Type:A collection of entities shared common properties or characteristics.

* Attribute: A named property or characteristic of an entity that is of interest to the organization.Relationship:it is association between the instances of one or more entity types that is of interest to the organization.

29


CONTAINES

Includes

Published by

Belongs to

Related_to

Written by

Auther information

BOOK_AUTHERauthorauthoridauth_firstauth_lastauth_fullnameauth_emailauth_countryauth_phone_no

bookisbntitlenumberofvolumespublisheryearmontheditionpricenoteformatnumberofpagedimentioncallnumbertableofcontant

PUBLISHERpublisheridpublishernamepublisherplace

SUB_SUBJECTsubsubjectidsubsubjectname

SUBJECTsubjectidsubjectname

billingbill_nobooks_countvaluediscountnotes

ER Diagram for

Online library

30

User entrance

User number, user password written

Order form

Db accessing Search result

Order booked Result pages

Getting confirmed message

[if form not fill]/ display form

[if the form is fill] / go to db

Order searched

[if not there ]/display message

[if there ]/ display result

Book button is pressed

Confirmation message is displayed

Order clicked

State Transition Diagram


3.5 State transaction diagram STD

It is represent dynamic models of how objects change their states in response to events. It is a model of the states of an object and the events that cause the object to change from one state to another.

A state is shown as a rectangle with rounded corners.

In figure we have shown different states of Book order object such as user entrance, order form, database accessing , searching result and getting results.

The state diagram shows how the object transactions from an initial state to other states, when certain events occur or when certain conditions are satisfied.

31


A.1 Conclusion.

After prepared analysis and design for this system, we try to replace the manual system by automated one. In our analysis we used high techniques to prepare a good design to be easy for implementation phase, so we hope that this system will appear in a good case. This new system is required to match new fast technology age for helping libraries requirement. The new system can be integrated with other library’s systems to get full benefit.

A.2 References.

1- Elmasri, R. and Navathe,Fundamentals of Database Systems. Benjamin / Cummings publishing company, California, USA

32


2- Jeffrey A. Hoffer & Joey F. George & Joseph S. Valacich. Modern System Analysis & design.

33