BAHIR DAR UNIVERSITY

INSTITUTE OF TECHNOLOGY
FACULTY OF COMPUTING
DEPARTMENT OF INFORMATION TECHNOLOGY
Industrial Project on: - Digital library system for
Blue Mark College
By
Name ID
Labena Lemma BDU08017003US
Mesiud Seid BDU08017331US
Biruk Mathewos BDU0801613US
Aweke Aba BDU0801577US
Advisor:-
Bahir Dar , ETHIOPIA
Sep 2021

I
 Acknowledgment
First and for most we would to express our deep thank to our almighty GOD for his unlimited help and
blessing in this project. We would also like to express our deep gratitude to Advisor ______, our project
advisor, for her patient guidance, enthusiastic engorgement and useful critiques of this graduation
project. We would also like to thank all our friends and family for their constant support and advice
throughout this project. Our thanks also extends to the Information Technology department staff who
provided the necessary resources and platforms for the successful accomplishment of each task.

ii | P a g e
 Abstract
This project is aimed to develop a system that handles digital library has been applied to a wide
variety of offerings from collections of electronic journals to software agents that support inquiry-
based education to collections of email to electronic versions of a public library, to personal
information collections, and even to the entire Internet. All of the objects in a digital library,
whether sounds, images, texts, or some other media, can be treated in essentially the same way. So,
libraries needed to treat various media, for example, books, journals, videos, and musical
recordings, mechanism which permits a form of equality among various information resources.
This equality has importance for delivery and integration of information. Thus in this project I will
implement digital Library in Blue Mark college education.

iii | P a g e
 Abbreviation and acronyms
 PHP---------------------------------------------- personal home page
 HTML-------------------------------------------hypertext markup language
 XML---------------------------------------------extensible markup language
 CSS-----------------------------------------------cascading style sheet
 HTTP--------------------------------------------hyper text transfer protocol
 MYSQL-----------------------------------------structured query language
 UML--------------------------------------------unified modeling language
 OOSA --------------------------------------------Object Oriented System Analysis.
 OOSD---------------------------------------------Object Oriented System Design
 CD-------------------------------------------------Compact Disc.
 DVD --------------------------------------------------Digital Versatile Disc
 UC--------------------------------------------------use case
 DLSDBCTE---------------------------------------- digital library system

iv | P a g e
 List of Table
Table 1 Cost analysis.................................................................................................................................13
Table 3 Actor identification.......................................................................................................................22
Table 4 Use case Diagram........................................................................................................................24
Table 5 Register Book use case.................................................................................................................25
Table 6 Search Book Use case..................................................................................................................26
Table 7update Book Use case....................................................................................................................27
Table 8 Delete Book Use Case..................................................................................................................28
Table 9 Print Document Use Case............................................................................................................29
Table 10 Download Document Use Case..................................................................................................30
Table 11 Send comment Use Case.............................................................................................................31

v|Page
 List of Figures
Figure 1 Admin Login to the System........................................................................................................34
Figure 2 Admin register books.................................................................................................................35
Figure 3 Admin Searches for Registered Book.........................................................................................36
Figure 4 Admin Update Registered Book..................................................................................................37
Figure 5 End user Login to the system......................................................................................................38
Figure 6 End user Search resource...........................................................................................................39
Figure 7 End User Material Download....................................................................................................40
Figure 8 Class Diagram............................................................................................................................42
Figure 9 Admin Registration for Book......................................................................................................43
Figure 10 Admin Search Book..................................................................................................................44
Figure 11 Admin update Record (Book)...................................................................................................45
Figure 12 Admin delete books...................................................................................................................46
Figure 13 End user search........................................................................................................................47
Figure 14 State Diagram for Login...........................................................................................................48
Figure 15 State Diagram for Registration...............................................................................................49
Figure 16 State Diagram for Search Information.....................................................................................50
Figure 17 User Interface prototype...........................................................................................................51
Figure 18 overview Software Architecture................................................................................................57
Figure 19 Deployment Diagram...............................................................................................................58
Figure 20 Physical data Base design........................................................................................................59
Figure 21 component diagram..................................................................................................................60
Figure 23 Users login page........................................................................................................................64
Figure 24 Admin creating accounts...........................................................................................................65
Figure 25 Admin uploading books............................................................................................................66
Figure 26 users downloading book............................................................................................................66

vi | P a g e
 Table of Contents
Acknowledgment...............................................................................................................................................................ii
Abstract............................................................................................................................................................................. iii
Abbreviation and acronyms...............................................................................................................................................iv
List of Table........................................................................................................................................................................ v
List of Figures.....................................................................................................................................................................vi
INTRODUCTION..................................................................................................................................................................1
1.1 Introduction.............................................................................................................................................................1
1.2 Background Information of the organization...........................................................................................................1
1.3 Statement of the problem........................................................................................................................................1
1.4 Objective of the project............................................................................................................................................2
1.4.1 General objective..............................................................................................................................................2
1.4.2 Specific objective...............................................................................................................................................2
1.5 Scope of the project.................................................................................................................................................2
1.6 Significance of the Project........................................................................................................................................2
1.7 Limitation of the project.....................................................................................................................................3
1.8 Target Beneficiaries of the system...........................................................................................................................3
1.9 Methodology for the project....................................................................................................................................3
1.9.1 Data collection method.....................................................................................................................................3
1.9.2 System Analysis and Design Methodology........................................................................................................4
1.9.3 Case tools..........................................................................................................................................................4
1.9.4 System development environment...................................................................................................................5
1.9.5 Testing procedures............................................................................................................................................6
1.9.6 Risks and contingencies.....................................................................................................................................6
1.10 Feasibility Studies...................................................................................................................................................7
1.10.1 Economical Feasibility.....................................................................................................................................7
1.10.2 Technical Feasibility.........................................................................................................................................8
1.10.3 Operational Feasibility.....................................................................................................................................8
1.10.4 Legal Feasibility...............................................................................................................................................8
CHAPTER TWO...................................................................................................................................................................9
DESCRIPTION OF THE EXISTING SYSTEM............................................................................................................................9
vii | P a g e
 2.1 Introduction of the existing system..........................................................................................................................9
2.2 Player in the existing system....................................................................................................................................9
2.3 Major Functions/Activities in the Existing................................................................................................................9
2.4 Report Generated in the Existing System...............................................................................................................10
2.5 Business Rules in the Existing System.....................................................................................................................10
2.6 Bottlenecks of the Existing System.........................................................................................................................10
2.7 Practices to be preserved.......................................................................................................................................11
2.8 Proposed Solution for the New System..................................................................................................................11
2.9 Requirements of the proposed system..................................................................................................................12
2.9.1 Functional requirement...................................................................................................................................12
2.9.2 Nonfunctional requirement.............................................................................................................................13
2.10. System Models....................................................................................................................................................15
2.10.1 Actor identification...................................................................................................................................15
2.10.2 Use case Diagram..........................................................................................................................................17
2.10.3. The Descriptions of Use cases...................................................................................................................19
2.10.4. Object Model............................................................................................................................................26
2.10.3. Class Diagram..............................................................................................................................................34
2.10.3. Activity Diagram..........................................................................................................................................36
2.10.5. State Diagram...........................................................................................................................................40
2.11. User Interface prototyping (navigation path and screen mock-ups)........................................................43
2.11.1. Supplementary Specification.......................................................................................................................45
CHAPTER Three................................................................................................................................................................ 46
SYSTEM DESIGN............................................................................................................................................................... 46
3.1. Introduction......................................................................................................................................................46
3.1.1. Purpose of the system..............................................................................................................................46
3.1.2. Design Goals.............................................................................................................................................46
3.2. Current Software Architecture.........................................................................................................................47
3.3. Proposed Software Architecture......................................................................................................................47
3.3.1. Overview..................................................................................................................................................47
3.1.1. Subsystem Decomposition.......................................................................................................................50
3.1.2. Deployment Diagram................................................................................................................................50
3.1.3. Physical data Base design.........................................................................................................................51
viii | P a g e
 3.1.4. Component diagram.................................................................................................................................52
CHAPTER FOUR................................................................................................................................................................54
4. IMPLEMENTATION AND TESTING.............................................................................................................................54
4.1. Introduction.........................................................................................................................................................54
Final Testing of the System...........................................................................................................................................54
4.2. Hardware Software Acquisition........................................................................................................................55
4.3. User Manual Preparation.................................................................................................................................55
4.4. Training.............................................................................................................................................................56
4.5. Startup Strategy...............................................................................................................................................56
4.6. Sample Users Interface.....................................................................................................................................56
4.7. sample code.....................................................................................................................................................60
APPENDIX.........................................................................................................................................................................65
References....................................................................................................................................................................... 66

ix | P a g e
 INTRODUCTION
1.1 Introduction
A digital library is a library in which collection are stored in digital formats and accessible by the
computers. The computer contents may be stored in locally. Digital library is a type of information
retrieval system.
The one property these various entities have in common is their digitization or digital coherence. Digital
coherence means all the objects in a digital library, whether sounds, images, texts, or some other media,
can be treated in essentially the same way. Prior to digital coherence, libraries needed to treat various
media, for example, books, journals, videos, and musical recordings, one could say that digital
coherence is the mechanism which permits a form of equality among various information resources.
This equality has importance for delivery and integration of information. Thus in this project we will
implement digital Library in Blue Mark college.

1.2 Background Information of the organization

Blue Mark College is Located at Bahir Dar City Kebele 3 and it was established in the year 2008 E.C. it
stands with its objectives of; to contribute towards the overall development of the country by
producing competent and skilled high and middle level human resource particularly equipped with
reliable computer, managerial, financial, economical and legal skill which the present era requires. To
provide high and middle level education and training opportunities for the needy citizens of the region in
their areas of residence. To increase the participation of girls and minority through the scholarship
program of the college. To be involved in the capacity building endeavors of the Amhara National
Regional State in particular and the country at large. To contribute towards the enhancement of pure as
well as applied researches and speed up innovation and transfer of technology to the country. To assist
the country by sharing the students enrollment burden of governmental institution of higher learning.
To provide job opportunities for academic and non-academic job seekers

1.3 Statement of the problem

 They use to introduce new books and websites using manual or by posting papers on the wall.
 They do not have website. So, it difficult witches book they have and witch they don’t have.

1|Page
  Incomplete resource sharing among the existing students and the instructors themselves.
 They cannot access new website.
 New research of the, students, lifelong learners, and the general public by developing of digital
libraries are not enabling
1.4 Objective of the project
1.4.1 General objective
The general objective of the project is to develop online digital library system for Blue Mark
College.

1.4.2 Specific objective

Towards achieving this objective some specific objectives can be laid down. These may include:
To gather required information about Blue Mark college library.
 To gather requirement
 To study existing system and the current business process.
 To identify problem in existing system
 Design the system
 develop database for the system
 Implement the system
 To test system
1.5 Scope of the project
The scope of the project is to allow standard and wise sharing of resources based on standard set of
rules on the server located at using Blue Mark College.
Distributing course materials not only modules but also other materials like video, texts, books,
news, and word documents etc… via the internet.
1.6 Significance of the Project
The propose system has the following significances:
 The propose system will be humble effort to prepare a model for a digital library system in Blue
Mark College.
 Increased accessibility for resources without geographic location or organizational affiliation.
 People can gain access to the information at any time

2|Page
  It save space which reserved by shelves.
 Improve the data sharing (uploading and downloading) from one sub system to another sub System.
 The authorized access to information resources files of the system is more advanced. This Means
secured login to the system will be developed.
 Resources and time sharing in the system operation and services provision is one of the major
benefits.
 Enabling students to use today’s ICT technology.
 Decrease errors in information access of the manual system

1.7 Limitation of the project

Our system has also limitations on a place that has not internet accessibility because it is depend on
connection since it is online. Library management system have a very large library that will be
difficult to update. If software is corrupted, whole data is damaged.

1.8 Target Beneficiaries of the system

 Giving digital copies of sites to users.
 Inspiration to students to be member of E-journal and book publishers.
 Giving soft copy books, journal and, research to users.
 The digital librarian also monitors collection budgets and expenditures and is largely responsible
for monitoring relationship with all vendors associated with the digital library.
 They must access new technology and new website.
 Give services for all its members, students, teachers, employees on time who know the website.
 Change the manual system into computerized to share resources.
 Any person downloads resources from the website.
 It solves the shortage of books and other resources.
 The development of the digital library system

1.9 Methodology for the project

1.9.1 Data collection method

The Methods in will be utilizing to collect both qualitative and quantitative data are the following:
Interview
3|Page
 In interview and communication with head librarian, staff and user of the library to get information
on existing system, to identify special features and also problems with existing system, to identify
barriers with current service provision.
Observations
Since developers of the system are available are also users of the library, it is simple to observe
activities in the library like service provision, accessibility of information materials, positive and
negative side of activities in the library another’s. So this method of data collection will be used
extensively by me.
Document analysis: We referred some previously done library projects from different websites as
well as from other bodies like our teachers and our friends. We choose this method to have detailed
awareness about our project.

1.9.2 System Analysis and Design Methodology

The project team plan to use the object oriented design methodology for the development of the
system among the different methodologies. Because it is better way to construct, manage and
assemble objects that are implemented in our system. Object oriented design methodology has
two phases:-
Object Oriented Analysis: During this phase the team will model the functions of the system
(use case modeling), Find and identify the business objects, Organize the objects and identify the
relationship between them and finally model the behavior of the objects.
Object Oriented Design: During this phase the team will refine the use case model to reflect the
implementation environment, model object interactions and behaviors that support the use case
scenario, and finally update object model to reflect the implementation environment.

1.9.3 Case tools

Soft ware tools
 MySQL - to create and design the database which used to store the information
 Edraw Max and visual paradigm: to designs the system analysis part of the project.
 PHP scripting language and its own XAMP server: to implement the system and provide the user
of the system with an interface.
 HTML sand CSS: using for static part of the website and for the style of the website
4|Page
  Notepad ++: to write the client side code.
 Windows Operating system: will be used for the system since it is readily available in
laboratories.
 Browsers:- since our system is web based, it is very necessary requirement.
 Microsoft office Word: - for documenting the corresponding deliverables associated with the
project.
Type of documentation tools used are:-
 Microsoft office word2007:for writing documentation
 Microsoft Power Point 2007: for presentation of the system.
 Microsoft Edraw: for drawing different diagrams.
 Notepad: to write HTML program.
 Snipping tool: to copy image from data base to past in to screen shoot.

Hardware Tools
Different hardware used to develop our project
 Computer: -computer is a machine capable of doing many things. We use it to type on it
and install all software and programming language.
 Flash Disk and CD Hardware: - used for the movement of data from one machine to
another. We use both of them when we move our data from one machine to another.
 Stationery: Stationery like paper, pen and so on that were need. All these are necessary
thing that we need to do and use.
 Network cable: since our system is web based, it is very necessary requirement. It is also
help us to extract relevant information about our project from internet

1.9.4 System development environment

System development environment is the environment that is responsible for operating or applying
the product of software. The operating environment of this product use different hardware
platforms like computer and development language using PHP language.
 PHP programming language:- the implementation or code part of this system is
developed on the area of this language. It is used to develop computer programs for
Microsoft Windows, as well as web sites, web applications and web services.
5|Page
  Microsoft office 2010: The team use Microsoft office word during prepares planning and writing
documentation.
 Microsoft Power Point 2010: We will use it to present our presentation in short and
brief way.
 Notepad++ (editor): Software used to develop server side interface.
 MySQL:- for the Database on the apache server.
 UML Diagramming:- The application design using different UML diagram for the use
of enterprise architecture. The team proposes to use enterprise architecture in order to
support those diagrams. Since enterprise architecture facilitates object-oriented
analysis and design diagram.

1.9.5 Testing procedures

Testing procedures are the testing practices, processes and techniques used to ensure that the
software application is tested and validating before release or deployment.
Testing levels: there are different testing levels for a system. But we will use the following testing
levels. These are:
Unit testing: while coding, the project team performs some tests on that unit of program to know if
it is error free. This testing level helps us to decide that individual units of the program are working
as per requirement and are error free.
System testing: the software is compiled as product and then it is tested as a whole. This can be
accomplished using one or more of the following tests:
Functionality testing: tests all functionalities of the software against the requirement.
Performance testing: this test proves how efficient the software is. It tests the effectiveness and
average time taken by the software to do desired task.

1.9.6 Risks and contingencies

During the development of the project, there may be different problems that we may face.
These are:
 Virus attack: it is difficult to control data from virus but try to scan the data, installing
and updating antivirus software.

6|Page
  Time management problem: we solve this problem by working cooperatively, divide
our time by schedule for each phase of the project and we try to use this schedule
effectively
 Power problem: we tried to use laptops to cover the gap happened to our
project during power failure.

1.10 Feasibility Studies

Feasibility is the measure of how beneficial the development or enhancement of an information
system would be to the business. Feasibility analysis is the process by which feasibility is
measured. It is an ongoing process done frequently during systems development projects in order to
achieve a creeping commitment from the user and to continually assess the current status of the
project

1.10.1 Economical Feasibility

Economically the system is more functional in reducing costs from both students and the
organization as it helps to many personnel need and standard journals producing with the standard
set of guides found in the server of the web site.

Types of Tool name Qua Unit Total

costs ntity price (in price
Birr) (in
Birr)
Hardware Flash(16GB) 1 200 120
costs Pen 6 5 30
Paper 1 100 100
Note book 1 25 25
Software Microsoft 1 Free Free
costs office 2007
Notepad++ 1 Free Free
Notepad 1 Free Free
Snipping 1 Free Free

7|Page
 tool
Edraw max 1 Free Free
Windows 10 1 Free Free
OS
Total cost - - - 275
Table 1 Cost analysis

1.10.2 Technical Feasibility

Technically, the system will be powerful to be applied by low skilled users as much as possible.
There is no need for the developer involvement in almost all implementation of the entire system. It
is easily accessible by the people who can easily understand natural languages.
1.10.3 Operational Feasibility
Operationally the system will become easily operable and quick enough in producing the desired
deliverables. As it is web based, the operational level sometimes based on the internetworking
devices and the number of users at a time. Keep remind that PHP is the latest web based software
that helps to increase the operational level of the system that we are going to develop.

1.10.4 Legal Feasibility

Legally the propose system is fully feasible because it never contradicts with legal and criminal
laws of the country. If the system has contradicted with the governmental rules regulations
automatically rejected. But this system has not contradicted with the governmental rule and
regulations. Therefore the system is legally feasible.

8|Page
 CHAPTER TWO

DESCRIPTION OF THE EXISTING SYSTEM

2.1 Introduction of the existing system
The organization is established to keep quality education in the college. It provides different types
of hardcopies such as different types of books related to different types of departments, magazines,
newspapers and the like for the community in the college. It works together with external
educational organizations in order to make teaching-learning process much suit by sharing different
experiences, habits.
This system tries; to make the interface as simple as possible and at the same time not risking the
security of stored data. This minimizes the time duration in which the user digital library . It aims at
improving efficiency and reducing complexities.

2.2 Player in the existing system

There are different players/actors in the existing system, those are:-
Administrator: -is the responsible person in the library for managing and coordinating the whole
system. This service called backline that means he/she doesn’t contact with members
Manager: - Performs all management related tasks. He creates account for the member, add
member, remove member and search all information about the library
Librarian: - They provide front line serves for the user/members and always have direct contact
with the members.
End user: - Members are registered who are authorized to issue articles from the library
2.3 Major Functions/Activities in the Existing
The existing system is work a paper based system. It has encountered a lot of problems which rises
from the manual undertaking of the various activities. From the findings of the observation,
interview and document review.

 Registration of information about book is mostly done by filling form by hand writing, it’s difficult
in the manual system
 End user searches books from library shelf
9|Page
  It tries to fulfill the Mission and vision of the college.
 Recording library information
 It stores actor files and service items
 Try to reduce the complaint of end users

2.4 Report Generated in the Existing System

The library head generates report daily, weekly and monthly what activities are performed, the
report is manual, it takes time to reach the library Information of Blue Mark College. Reporting the
total number of book in library is manpower intensive, time taking ,difficult to manage or arrange

2.5 Business Rules in the Existing System

In every organizations or institution’s there are rules and policies, which used to govern all
activities in specified work flow, control the work flow, and performed in the work environment
this are business rules. Or business rule are statement about the organization’s way of doing
business. So the digital library system governs and controls the work flow through the following
rules.
 Can only access authorized user.
 Unauthorized user cannot access the system for the reason of system security.
 Users must be registered to access the system to be authorized user by filling the
necessary information in the registration form.
 Users must have username and password to login to the system.
2.6 Bottlenecks of the Existing System
Time: - The existing system operates manually so it takes time.
Resource: - In the existing system there is wastage of resource.
Problems in data backup:-in the current manual system of data collection system backup of data
are difficult because the data are organized in a paper form so to back up such types of data there
must be a room to store papers data. When the papers data are large it is difficult to back up all data
in a room. Due to this reason back upping of data in the current system is difficult.
Problem in information retrieval:- the information retrieval of the current system is
very less this is due to the problem of they have not computerized database to retrieve
information to somebody that wants the data or information.
10 | P a g e
 Performance (response time):- In case of performance of the existing system the condition is
manual so clients can ask their
questions and in order to give response with takes a lot of many and time at this time the clients or
customers and the service provider has conflict.
Problem in data security: - Now a day the most common issues on data management and storage
are the level of security, in the current manual book loan service system, there is no any types of
software security rather it has only physical security. Due to the reason the current system has not
any types of software security it leads sensitive data may be lost. The current system has not any
types of authentication method to identify who is the correct authorized user.
2.7 Practices to be preserved
Even if the existing system is manual and has weakness, there are important activities we should
preserve to the proposed system. These practices are:
 Generate report timely.
 Give respect to end users.
 Provide services to end users.
 Solve problems by their order of request.

2.8 Proposed Solution for the New System

The project aims at solving problems of the existing system. Every college community can Access
it being in intranet of the college. The access time is 24 hours a day allowing access to information
making in the college libraries. The system has feature of collecting request on additional services
from the user. As the requirement, the system needs intranet connection and server computer for
which information materials will be stored for user access in the intranet.
The proposed system, first record materials and classifies them by category depending on their
subject. Materials may be scanned information materials, soft copy, research reports, project
records and essential data files. The proposed systems organize and classify information materials
to be added into the collection. It also locates the materials where they can be retrieved physically
and have a feature of which are free of charge and subscribed by Blue Mark college.

11 | P a g e
 In general the proposed system will be described as follows regarding:-
Performance
 It is easy to use (user friendly)
 Fast and reliable
Speed
 It will let the user to access the information being needed more quickly.
 Give service to many users at any time.
Cost
 It minimizes cost
 Reduces wastage of man power
 Reduces wastage of paper, pen, pencil, rubber
 Reduces consumption of resources to maintain regular communication

2.9 Requirements of the proposed system

2.9.1 Functional requirement

Functional requirements which are observable tasks or processes that must be performed by the
system. For example, functional requirements of my system is must upload and more accessible
digital collections for a user in the intranet. The main purpose of the system is to enable users of the
systems who build digital library collections and to make it accessible using the network connection
and on other storage medias. The necessary tasks of system can be:
 Building the collection which will be the digital collection of the library.
 Enabling the users to take the print format of the document they want using hard copies
 Document the file which is placed on the system to be accessed as digital information sources.
 Enable the library to control its endemic resources just by bringing the digital format online and
preserving the print one.
 Enable the library to share different types of data with other libraries, information Centers, etc.
 Generate the print format of the digital document.
 It organizes and makes searchable documents
12 | P a g e
 Possible functional requirements include:
 Login
 Download documentation
 Search book
 Register book
 Delete book
 Update book
 Print documentation
 Send comment

2.9.2 Nonfunctional requirement

Accessibility
The accessibility degree of this system can be in two directions. First one is for the librarian who
will interact with the system to build digital collections and the users who will search the
collections of the library. After the librarian install this tool in the server or computer he will use it
can be accessed easily and friendly without any kind of difficulty. For the users collections are
accessible anywhere in the intranet of Blue Mark teacher college of education it can also be
accessed on the internet if it is published by having public domain.
Quality Issues
To keep the quality of the system when it functions there are basic considerations determined as
requirements for reliability and user requirement
Requirement for reliability
 Computer with good processing speed, memory and storage capacity for backup.
 Local Area Net work (LAN) and internet connection
User requirement
 Technical issues example user friendly types, layout convention and analysis of the algorithm
Security issues

13 | P a g e
 This issue encompasses measures taken throughout the applications life cycle to prevent exceptions
in the security policy of the system through flows in the design, development, and maintenance of
application. In general to make the system asset safe, the system will follow a role based security
which means the access level and privilege for each builders of the collection is predefined by the
system administrator. The end user of the system most of the time will be asked for authorization
login except if the library or collection developer has set its own criteria to access the collections
Performance characteristics
The system will be accessed by many users or students inside the college. So it should be given
more emphasis for the speed to access the web site or the system database. The constraint
characteristics are also one of the performance characteristics of the system, the constraints can be
user’s computer low RAM, Network or connectivity failure, and others
Error Performance characteristics or handling and Extreme conditions
When the users of the system interact with the system errors may appear. To control these
Inaccuracies the system will generate different messages. Data errors which are entered in to the
system may not be completely avoided but they can be minimized. To do this most of the system
execution buttons will be controlled according to the sequence which the user is expected to follow.
Or this can be done by generating different system responses to the input of the users
System modification
Through time there are always changes when the user’s needs another additional functionality,
when the system administrator identifies the system need to be modified, while the organizations
work style is changed and depending on different reasons. Some of the user interface and basic
modification can be performed by the collection developers but the system developers are the right
persons to update the system

14 | P a g e
 2.10. System Models
The project development team used an object oriented system development methodology. Because
the Object system development approach gives easier and natural way to breakdown problems into
simple, small and manageable components. An important goal of requirement modeling is come to
an understanding of the existing system problem that the new system is to address. This chapter
focuses on developing the requirement and analysis models for the new system using the UML use
case model, sequence diagram, activity diagram and class diagram. And also in this section the
functionalities of the system are described and modeled using UML models and also describe the
interaction between the user and the system. This section also used to identify the actors of the
system and what the actors does on the system.

2.10.1 Actor identification

An actor is a person, organization, or external system that plays a role in one or more interactions
with a system. In Blue Mark college digital Library System, there are about four actors.
As shown in Table

15 | P a g e
 Actor name Description
Administrator Administrator is the responsible person
in the library for managing and
coordinating the whole system. This
service called backline that means he/she
doesn’t contact with members
Manager Performs all management related tasks.
He creates account for the member, add
member, remove member and search all
information about the library
Librarian
They provide front line serves for the
user/members and always have direct
contact with the members.

End user Members are registered who are

authorized to issue articles from the
library

Table 2 Actor identification

16 | P a g e
 2.10.2 Use case Diagram
Use case diagrams are diagrams used for capturing for functional requirements of the system. Each
use case diagram describes a behaviorally related sequence of transaction in a dialogue between the
user and the system.
Accordingly, Blue Mark college Digital library System contains many use cases that are described
as follows.

17 | P a g e
 Table 3 Use case Diagram

18 | P a g e
 2.10.3. The Descriptions of Use cases
Register Book use case
Name of use case Register use case
ID UC#1
Actor Admin
Flow of events: 1. The Librarian logs to Book
Registration form the home page of
the DBTCDLS
2. The Librarian clicks on the
register Book button
3. The system displays Book
registration form
4. The Librarian fills Book
registration data and click register
Book
5. The system displays successfully
saved message
Alternative case 6. If the registered Book exists in the
database, the system displays the file
already exists
Message and if the input data has
errors the system display error
message and allow the
Librarian to try again

Table 4 Register Book use case

19 | P a g e
 Search Book Use case

Name of use case: search Book

ID UC#2
Participating actor Librarian

Entry condition The Librarian logs in to the system

using his account
Flow of events 1. The Librarian logs to his account
from the home of DBCTEDLS
2. The Librarian clicks on the search
new Book button
3. The system displays search
options (Name, author, publisher)
4. The Librarian search using one
search method
5. The system will displays the
searched result
Alternate case 6. if the Book searched doesn’t exist
in the database, the system displays
“the
Book not found” message exit
condition, the result is displayed

Table 5 Search Book Use case

20 | P a g e
 Update Book record Use Case
Name of use case Update Book

ID UC#3
Participating Actor: Admin

Entry condition The admin logs in to the system using his

account
Flow of events 1. The admin logs to his account from the
home page of The DBTCDLS
2. The admin clicks on the Search new
Book button
3. The System displays search options
(name, author, and publisher)
4. The admin search using one search
method
5. The system displays the searched result
6. The admin clicks on the update button to
modify the record

Alternate case 7. If the data there is a mistake in the data

entry the system displays error
Message and allow making correction

Exit condition The Book record is modified successfully

Table 6update Book Use case

21 | P a g e
 Delete Book Use Case
Name of use case Delete Book
ID UC#4
Participating actor Admin

Entry Condition The Librarian logs in to the system

using his account
Flow of events 1. The Librarian logs to his account
from the home page of the
DBTCDLS
2. The Admin clicks on the Search
new Book button
3. The System displays search
options (name, author, and
publisher)
4. The Admin search using one
search method
5. The system displays the searched
result
6. The Admin clicks on the Delete
button to delete the record
Alternate case 7. If the registered record exists in
the database, the system displays the
file Already exist message and if the
input data has errors the system
display error
Exit condition The Librarian record is deleted
successfully

Table 7 Delete Book Use Case

22 | P a g e
 Print Document Use Case
Name of use case: Print Document
ID UC#6
Participating actor: End User (Admen, Librarian,
Students, Staff and others)
Entry condition: The End user login to the system

Flow of events: End user clicks on the Search

Library button or link
1. The System displays search
options (Keyword, Author, Subject,
Title,
Year, and Department) and
Advanced
2. The End user search using search
one method
3. The search result should be
displayed
4. The End user clicks the Ok button
and the system display
Successful message
Alternate Flow: 5. If the computer is not connected
with printer the system will displays
“Please connect your pc with
printer” message
Exit condition The search result is closed and the
system count the usage frequency of
the Document
Table 8 Print Document Use Case

23 | P a g e
 Download Document Use Case
Name of use case Download Document
ID UC#7

Participating actor End User (Administrator, Librarian,

Students, Staff and others)
Entry condition 1. Login
2. Search (Keyword, Author,
Subject, Title, Year, and Department)
And Advanced
3. The End user search using search
one method
4. The system displays the searched
result
5. The End user click one linked
document
6. The system displays the full
document
7. The End user click the download
button
Alternate case If no download display no document
available

Table 9 Download Document Use Case

Send comment Use Case

24 | P a g e
 Name of use case: Send comment

ID UC#8
Participating actor End User (Students, Staff and
others)
Entry condition Login

Flow of events 1 login page

2. The End user click comment
3. The System displays the Leave
comment page
4. The End user leaves his/her
comment and click send button
5. If the text box is empty the system
will displays “Please leaves
comment” message.
Exit condition The system displays comment sent
successful message

Table 10 Send comment Use Case

25 | P a g e
 2.10.4. Object Model
Object model deals with object oriented of the system. An object model is a logical interface,
software or system that is modeled through the use of object-oriented techniques. It enables the
creation of an architectural software or system model prior to development or programming. This
includes class diagram, relationship between these classes, methods in the class and properties.
2.10.5. Sequence diagram
Sequence diagram describe behavior as a sequence of messages exchanged among a set of objects.
Sequence diagram which is also known as interaction diagrams are one of the diagrams used in
UML, for modeling the dynamic aspects of the system. It shows an interaction consisting of a set of
objects and their relationship including message that may be dispatched among them. It emphasizes
the time ordering of messages.
A sequence diagram shows an interaction arranged in time sequence. In particular, it shows the
instances participating in the interaction by their “lifelines” and the stimuli that they exchange
arranged in time sequence. It does not show the associations among the objects. Sequence diagrams
are used to display the interaction between users, screens, objects and entities within the system. It
provides a sequential map of message passing between objects over time. Frequently these
diagrams are placed under Use Cases in the model to illustrate the use case scenario how a user will
interact with the system and what happens internally to get the work done. Often, the objects are
represented using special stereotyped icons. Its participating objects.

26 | P a g e
 Figure 1 Admin Login to the System

27 | P a g e
 Figure 2 Admin register books

28 | P a g e
 Figure 3 Admin Searches for Registered Book

29 | P a g e
 Figure 4 Admin Update Registered Book

30 | P a g e
 Figure 5 End user Login to the system

31 | P a g e
 Figure 6 End user Search resource

32 | P a g e
 Figure 7 End User Material Download

33 | P a g e
 2.10.3. Class Diagram
Class diagram shows the static structure of data and the operations that action the data, i.e. it shows
the static structure of an object-oriented model the object class, their internal structure, and the
relationships in which they participate. Class diagram represents a detailed view of a single use
case, shows the classes that participate in the use case, and documents the relationship among the
classes. It is a logical model, which evolves into a physical model & finally becomes functioning
information system. Class diagram evolve into code modules, data objects, & other system
components Class diagrams describe the structure of the system in terms of classes and objects.
Classes are abstractions that specify the attributes and behavior of a set of objects. Objects are
entities that encapsulate state and behavior.

34 | P a g e
 Figure 8 Class Diagram

35 | P a g e
 2.10.3. Activity Diagram
Activity diagram is another important diagram in UML to describe the dynamic aspects of the
system. Activity diagram is basically a flowchart to represent the flow from one activity to another
activity. The activity can be described as an operation of the system. The control flow is drawn
from one operation to another. This flow can be sequential, branched, or concurrent.

Figure 9 Admin Registration for Book

36 | P a g e
 Start

Home

Click Library link

Login form

Login

Admin page

Click search
End
Registration
Form

Choice
Close Click Cancel
Registration
Form
Click No
Click search

Summary Correct?
msg box

Click close
Click yes

Figure 10 Admin Search Book

37 | P a g e
 Start

Home

Click Library link

Login form

Login
Library page
End
Click update book
Registration
Form

Choice
Close
Registration
Form
Click Cancel
Click search

Registration
Form with page
Click No
Click update book
Summary
msg box
Correct?
Click ok

Click yes
Successful update
Message

Figure 11 Admin update Record (Book)

38 | P a g e
 Start

Home

Click Library link

Login form

Click login

Library page

Click Delete book

Registration
Form

Choice
Close
Registration
form
Click cancel

Click search

Registration
Form with page
Click No
Click Delete book
Summary
msg box
Correct?
End Click close

Click yes
Successful Delete
Message

Figure 12 Admin delete books

39 | P a g e
 Start

Home

Click L End user link

Login form

Click login

End user page

Click search button

Search page

Correct
NO Correction
Message

Yes

Download/view

End

Figure 13 End user search

2.10.5. State Diagram

UML state chart diagrams depict the various states that an object may be in the transition between
those states. In other word, it has initial and final states in addition to transition that is a progression
from one state to another. States are represented as a rounded rectangle with the name of the state
shown in the system. Connecting states together are transitions. These represent the events that
cause the object to change from one state to another. The guard clause of the label is again mutually
exclusive and must resolve itself to be either true or false. Actions represent tasks that run causing
the transitions State chart diagrams show class states and the events that cause them to transition
between states.

40 | P a g e
 Figure 14 State Diagram for Login

41 | P a g e
 Figure 15 State Diagram for Registration

42 | P a g e
 Figure 16 State Diagram for Search Information

2.11. User Interface prototyping (navigation path and screen mock-ups)

Interface designs: There are various types of user-computer interface designs, each of which has a
typical character and ability. The design type is required to be suitable to the system’s duties and to
its users who will interact directly with the system. The design and documentation of the user
interfaces are as follow

43 | P a g e
 NEWS
NEW
S

Searc
h

Figure 17 User Interface prototype

44 | P a g e
 2.11.1. Supplementary Specification
Functionality
✓ Remote Access
All functionality shall be available remotely through an internet connection.
Usability
✓ Design for Ease-of-Use
The user interface of the marketing and service directory web app shall be designed for ease-of use
and shall be appropriate for a computer-literate user community with no additional training on the
System.
Reliability
✓ Availability
The marketing and service directory web app shall be available 24 hours a day, 7 days a week if
users want to use it.
Performance
✓ Simultaneous Users
The web application can be used by too much of users at a time simultaneously.
✓ Database Access Response Time
The application shall provide access to marketing and resource directory database with no more
than a 1second latency

45 | P a g e
 CHAPTER Three

SYSTEM DESIGN
3.1. Introduction
After the determination of the requirements, it is the design that follows. The design is all about
stating the design goals of the system and subdividing the system into smaller parts so as to tackle
the problem in a modular approach. The output of this phase includes description of each
subsystems and the deployment of the subsystems. The use of digital library system is very
important for Blue Mark college digital library system in rendering service for the user. To give
right service for the right user at the right time on subject of his/her need, digital library plays a
great role.
Blue Mark College Digital Library system is currently renders service manually for its users.

3.1.1. Purpose of the system

The proposed system is developed to facilitate and organize best way of accessing Information
resources available in Blue Mark Digital Library system. The other purpose of this system is
developing users information retrieval by developing system that save time, simple to use, user
friend, and accessible every time.
3.1.2. Design Goals
The design goals are derived from the non-functional requirements of the system, which were
stated in chapter two of this document. They describe what the system should focus on. This
includes:
Performance: the part of the system to use for the programming language should have a fast
response time (real time) with maximum throughput. Furthermore, the system should not be
taking up too much space in memory. The user gets fast response time over throughput and hence
the system should try to be more interactive. The system should be more reliable in order to
satisfy the constraints than fast response time. Criteria’s for performance are the response-time,
throughput and space for file storage.
Response time: quickly reacts to a user. Response request to the user at most Three
seconds.

46 | P a g e
 Throughput: system can accomplish high amount of outputs within a specified
amount time.
Availability: The system or component is always operational and accessible when required for
use.
Accuracy: system must display accurate output.
Usability: -The system should have a simple and easy graphical interface that users can understand
quickly.
Security: user’s account is created by the system administrator, so, no one can’t create an account
by themselves and use the system. But person who has an account can login to the system
using his/her username and password and use the system. For example in the grading system,
since each student see their grade value by their own account with unique id, no one can’t see
other’s grade. Generally due to the above reasons, our system is secure.
Error handling: When the users interact with the system errors may appear. In addition to the
operating system error handling mechanism we use exception handler during implementation. To
control these inaccuracies the system will generate different messages.
Extensibility: the system is enabling the addition of new functionality without any restriction.
This constraint enables the system to have the acceptance of users, for it does not restrict the future
expansion of the system.

3.2. Current Software Architecture

Blue Mark college Digital library system is using currently traditional way of rendering service.
There is no considerable activity that related with digitization. It is giving service for users not in
Digital format but in print one.

3.3. Proposed Software Architecture

3.3.1. Overview
The proposed system is expected to replace the existing manual system by an automated system
in all facts. The architecture used for the system is a 3 tier Client/Server Architecture where a
client can use Internet browsers to access the digital library system (DLS) with in the local area
network of the school or anywhere using the Internet.

47 | P a g e
 The presentation tier: the top most level of the application and is responsible for display and
collection of user data. It translates tasks and result to something the user can understand.
The middle tier (web/application server) is responsible for taking requests for the client’s
presentation tier, performing some type of business logic or process, and returning the results
back to the client for presentation. The controller logic processes client requests such as requests
to view placement or to retrieve data from the database. Business rules enforced by the business
logic dictate how clients can and cannot access application data and how applications process
data.
A web server is a program that runs on a network server (computer) to respond to HTTP requests.
The most commonly used web servers are Internet Information Server (IIS) and Apache.
The web server used in this system is IIS. HTTP is used to transfer data across an Intranet or the
Internet. It is the standard protocol for moving data across the internet
The data layer: is responsible to store and retrieve information from database. Only the application
tier should be allowed to request information from this tier. The data tier maintains the applications
data such as user data, placement data etc. It stores these data in a relational database management
system (RDBMS).

48 | P a g e
 Internet
accesses

Digital library DB
Clint browser

Download book
MYSQL Database

Search book

49 | P a g e
 Figure 18 overview Software Architecture

3.1.1. Subsystem Decomposition

From the functional requirements I identified in the system analysis section, the envisaged system
consists of the following subsystems:
 Administrator sub system
 Register book
 Delete book
 Update book
 Search book
 Manager sub system
 View report
 Registration library information
 Update library information
 Delete library information
 End user sub system
 Search book
 Download book
 Print documentation
 Library sub system
 Post news
 Manage news

3.1.2. Deployment Diagram

The deployment diagrams:-
 Describes the relationship of components with that of hardware nodes.
 It gives a high-level view of each component.
 Deployment diagram shows physical components of a new system.show the structure of the run-
time system.

50 | P a g e
  Shows the configuration of run-time processing elements and the software components, processes,
and objects.
 The collection of one or more deployment diagrams with their associated documentation. Showing
relation b/n application and the database shows the deployment.

Librarian Manager

Admin

Database devices
MYSQl

User
Main server
Application server
Digital library DB

Figure 19 Deployment Diagram

3.1.3. Physical data Base design

Database design is the process of producing a detailed data model of a database.
This logical data model contains all the needed logical and physical design choices and physical
storage parameters needed to generate a design in a Data Definition Language, which can then be
used to create a database. A fully attributed data model contains detailed attributes for each entity.
The physical database according to the ER-diagram will look like as the sample below

51 | P a g e
 Figure 20 Physical data Base design

3.1.4. Component diagram

In this Diagram components of the system will be wired showing that there is relation among
components, management of the system, database and operations performed on databases such
security issue. The goal of the component modeling is to distribute the classes of the system into
large scale, cohesive component.
 Component diagrams show the physical placement of the components in the system.
 A type of design diagram that shows overall system architecture and the logical components within
it for how the system will be implemented.

52 | P a g e
  Identifies the logical, reusable, and transportable system components that define the system
architecture

UML Component Diagrams Digital Library

Admin
Security

Manager

IReservation

Digital library

Digital library
User
DB

Librarian’s worker

Figure 21 component diagram

53 | P a g e
 CHAPTER FOUR

4. IMPLEMENTATION AND TESTING

4.1. Introduction
The implementation phase is the most crucial phase in which it transforms the design and analysis of
the system into a tangible system by writing the code to the system to be developed and make it
operational and applicable by testing and debugging the functionalities that are done. This phase
involves the construction of the actual project result. During this phase that the project becomes visible
to outsiders, to whom it may appear that the project has just begun. This makes the implementation
stage more essential step to develop the required system. So, it is the most vital and necessary stage in
achieving a successful system and in giving the users confidence that the new system will work and be
effective by testing the system that is already implemented.
In this phase, the production system is installed, initial user training is completed, user documentation
is delivered, and the post implementation review meeting is held. When this phase is completed, the
application is in steady state production. Once the system is in steady-state production, it is reviewed
to ensure that we met all of the goals in the project plan for a satisfactory result.

Final Testing of the System

The team members test the whole system in the following procedures:-
Unit testing
Unit testing is a way of testing each of the system functionality independently. Accordingly, the
team has tested each one of the major activities and the rest accompanying activities in dependently
using different user input, different login mechanisms and any technique of faultfinding so that an
incorrect functioning of the activities was corrected at the right time.
Integration Testing
All the modules will be combined together and tested it for its fitness with each other and with the
systems functionality. If error occurs in combining them, the module with problem will be
identified and recombined.
Functional Testing

54 | P a g e
 Functional testing is the testing to ensure that the specified functionality required in the system
requirements works.

System testing
It is the final step of testing. In this system tested the entire system as a whole with all forms, code,
modules. In this we tested all the functionalities in the System. All errors in the forms, functions,
modules have been tested. Finally, System testing ensures that the entire integrated software system
meets the desired requirements. It tests a configuration to ensure known and predictable results.

4.2. Hardware Software Acquisition

For the project implementation the Following Software and hardware are used:-
Hardware
Computers
laptop: we use it in dorm to do since it is portable we use it every ware
Printer: To printing the documents
Cables: - For network connection purpose.
Server: To create connection to the client computer(to host the system)
Software
Language: PHP(Notepad++)
XAMMP Server
Google chrome and Baidu spark browser.
Window 10 operating system
MS word 2010
Enterprise Architect
My SQL

4.3. User Manual Preparation

Since the system is web based and easily user friend, everything important for the users will be
explained and implemented while giving short training when the system is after developed. There is
no need of preparing full user manual because it is only run on a single machine that is any

55 | P a g e
 computer. So anyone who can access the internet can also access the system easily with in the given
permission or role.

4.4. Training
During the deployment of the system, the project group members will give short time training. The
team will provide short training term for the admin and registrar how he/she manage and operate
the system. The teams can explain information regarding the operation of the system for the
administrator during deploying the system on server. As the system is user friendly, it is not
complicated for the administrator to manage the system.

4.5. Startup Strategy

The start-up strategy will be:
Buying a domain name
hosting the system
finally available internet connection

4.6. Sample Users Interface

The design of computers, appliances, machines, mobile communication devices, software
applications, and websites with the focus on the user's experience and interaction. The goal of user
interface design is to make the user's interaction as simple and efficient as possible, in terms of
accomplishing user goals what is often called user-centered design. Good user interface design
facilitates finishing the task at hand without drawing unnecessary attention to it.
The following interface design pictures describe the logical characteristics of some interfaces
between the system and the users. So the sample interfaces are shown as follows:

56 | P a g e
 Figure 22 Users login page

57 | P a g e
 Figure 23 Admin creating accounts

58 | P a g e
 Figure 24 Admin uploading books

Figure 25 users downloading book

59 | P a g e
 4.7. sample code

Login.php
<?php
$conn=mysql_connect("localhost","root","");
$db1=mysql_select_db("digital",$conn);
if(isset($_POST['login']))
{
$username=$_POST['username'];
$password =$_POST['password'];
// $position=$_POST['position'];
$query = "SELECT * FROM account WHERE username = '{$username}' AND password =
'{$password}' ";
$result_set=mysql_query($query);
$row=mysql_fetch_array($result_set);
$user=$row['position'];
if(mysql_num_rows($result_set)>0)
{
if($user=='manager')
{
session_start();
$_SESSION['accountid']=$row['accountid'];
echo "<script>window.location='managerpage.php';</script>";
}
else if($user=='user')
{
session_start();
$_SESSION['accountid']=$row['accountid'];
echo "<script>window.location='user.php';</script>";
}
else if($user=='admin')
{
session_start();
$_SESSION['accountid']=$row['accountid'];
echo "<script>window.location='manager.php';</script>";
}
else if($user=='librarian')
{
session_start();
$_SESSION['accountid']=$row['accountid'];
echo "<script>window.location='librarian.php';</script>";
}
}
60 | P a g e
 else
{

echo" <font color='green'><p class='wrong'>User Name and password not

match!</p></font>";
echo' <meta content="3;login1.php" http-equiv="refresh" />';
}
}
mysql_close($conn);
?>

Upload.php
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<link rel="stylesheet" href="css/bootstrap.min.css" />
<style type="text/css">
#wrapper {
margin: 0 auto;
float: none;
width:70%;
}
.header {
padding:10px 0;
border-bottom:1px solid #CCC;
}
.title {
padding: 0 5px 0 0;
float:left;
margin:0;
}
.container form input {
height: 30px;
}
body
{

font-size:12;
font-weight:bold;
}

</style>
61 | P a g e
 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<title>Upload File</title>

<?php
if(!empty($_POST))
{
$con = mysql_connect("localhost","root","");
if (!$con)
echo('Could not connect: ' . mysql_error());
else
{
if (file_exists("download/" . $_FILES["file"]["name"]))
{
echo '<script language="javascript">alert(" Sorry!! Filename Already Exists...")</script>';
}
else
{
move_uploaded_file($_FILES["file"]["tmp_name"],
"download/" . $_FILES["file"]["name"]) ;
mysql_select_db("digital", $con);
$sql = "INSERT INTO book(book,author,file) VALUES ('" . $_POST["sub"] ."','" .
$_POST["pre"] . "','" .
$_FILES["file"]["name"] ."');";
if (!mysql_query($sql,$con))
echo('Error : ' . mysql_error());
else
echo '<script language="javascript">alert("Thank You!! File Uploded")</script>';
}
}
mysql_close($con);
}
?>
</head>
<body>
<div class="container home">
<br>
<h3><center> UPLOAD BOOKS</center></h3></font>

<form id="form3" enctype="multipart/form-data" method="post" action="upload.php">

<table class="table table-bordered">
<tr>
<td> <label for="sub">BOOK NAME</label> </td>
<td> <input type="text" name="sub" id="sub" class="input-medium"
62 | P a g e
 required autofocus placeholder="enter book name"/> </td>
</tr>
<tr>
<td valign="top" align="left">AUTHOR NAME</td>
<td valign="top" align="left"><input type="text" name="pre" cols="50" rows="10" id="pre"
placeholder="enter author name"
class="input-medium" required></textarea></td>
</tr>
<tr>
<td><label for="file">File:</label></td>
<td><input type="file" name="file" id="file"
title="Click here to select file to upload." required /></td>
</tr>
<tr>

<td colspan="2" align="center">

<input type="submit" class="btn btn-primary" name="upload" id="upload"
title="Click here to upload the file." value="Upload File" /></td>
</tr>
</table>
</form>
</div>
<br><center><button onclick="location.href='display.php'" class="btn btn-primary">display
book</button></center>
<br><center><button onclick="location.href='manager.php'" class="btn btn-
primary">back</button></center>
</body>
</html>

Download.php
<?php
$file = './download/'.$_GET['id'];
$title=$_GET['id'];

header("Pragma: public");
header('Content-disposition: attachment; filename='.$title);

header('Content-Transfer-Encoding: binary');
ob_clean();
flush();

$chunksize = 8 * (1024 * 1024); // how many bytes per chunk

63 | P a g e
 if (filesize($file) > $chunksize) {
$handle = fopen($file, 'rb');
$buffer = '';

while (!feof($handle)) {
$buffer = fread($handle, $chunksize);
echo $buffer;
ob_flush();
flush();
}

fclose($handle);
} else {
readfile($file);
}
?>

64 | P a g e
 APPENDIX
Diagram used during development Symbol definition
Symbol definition

------------------------------------------------------------------------------------ Actor

----------------------------------------------------------------------------- Use case

----------------------------------------------------------------------------- Package

---------------------------------------------------------------------- Component

---------------------------------------------------------------------------------- Node

---------------------------------------------------------------------------------- Device

65 | P a g e
 References
1. Stephen, R.(2005) Object Oriented and Classical Software Engineering
2. http://www.youtube.com/watch?v=digital
3. Digital libraries. Types and structures of digital library. Retrieved Aug,
2013, from the free encyclopedia
5. Wikipediawebsite:http://en.wikipedia.org/wiki/Digital_library
4. Software engineering text book and object oriented software engineering book.
6. www.dynamicss.com...how to design interfaces

66 | P a g e