Final Doc't For Group 999999

ASSOSA UNIVERSITY
FACULITY OF ENGINEERING AND

TECHNOLOGY
DEPARTMENT OF INFORMATION SCIENCE
Title: Digital Library System for Faculty of

Engineering and Technology, Assosa University
Prepared by:
Student Name Student ID
1. Birhanu Kirosse ETR/ 804 /06

2. Lidya Daniel ETR/ 916 /06
3. Semira Abdella ETR/1089/06
4. Yared Girma ETR/843/06
5. Yeshimebet Degu ETR/1030/06
This Project is submitted to the Faculty of Engineering and Technology, Department of

information science, in partial fulfillment for the award of degree of Bachelor of Science
in Information Science.
June, 2016
Assosa, Ethiopia
Approval Sheet
This project entitled “Digital Library System for Faculty of

Engineering and Technology, Assosa University” has been read and approved as the
requirements of the department of information science in partial fulfillment for the award of
Degree of Bachelor in Information Science, Assosa University and Assosa, Ethiopia.
Principal -Advisor
Name Signature Date
Hambisa.M _____________ _____________
Co-Advisor
Name Signature Date
Zebene.H _____________ _____________
I
Acknowledgement
First of all our deep heartfelt thanks and praise goes to God, who has been with us, shared our
burden and rose as in his abundance. The team wishes to express our sincere and deepest thanks
to our advisors Mr. Hambisa M. for his guidance and valuable corrective advice to complete
this project. The team wants to thanks Mr. Zebene H. for his great contribution and guidance in
this project. The investigators are also extremely grateful and remain indebted to our group
members who have helped in successful completion of the project.
II
Table of Contents Pages
Approval Sheet.................................................................................................................................I
Acknowledgement..........................................................................................................................II
List of Table...................................................................................................................................III
List of Figures ...............................................................................................................................VI
Abstract........................................................................................................................................v
SECTION ONE...............................................................................................................................1
Introduction..................................................................................................................................1
1.1. Background...........................................................................................................................1
1.2. Statement of the problem......................................................................................................2
1.3. Objectives of the study..........................................................................................................3
1.3.1. General objectives..........................................................................................................3
1.3.2. Specific objectives..........................................................................................................3
1.4. The scope of the project........................................................................................................3
1.5. Significant of the study.........................................................................................................4
1.6. Definition of terms................................................................................................................5
SECTION TWO..............................................................................................................................6
Literature review..........................................................................................................................6
2.1. Library...................................................................................................................................6
2.2. Types of Library....................................................................................................................6
2.2.1. Digital Library................................................................................................................6
2.2.2. Public libraries................................................................................................................8
2.2.3. Special Libraries.............................................................................................................8
2.2.4. Electronic Library...........................................................................................................8
2.3. Related works........................................................................................................................8
2.3.1. Secure the materials........................................................................................................8
2.3.2. Better arrangement of books and modules...................................................................9
2.3.3. Reduces wastage of the Users time................................................................................9
III
2.3.4. Increasing the accessibility of the book in the library....................................................9
SECTION THREE.........................................................................................................................10
Project Design and Methodology...............................................................................................10

3.1. Description of Study Area...................................................................................................10
3.2. Data Collection Methods....................................................................................................10
A. Observation.....................................................................................................................10
B. Interview................................................................................................................................11
3.3. Types of Data......................................................................................................................12
3.3.1. Primary Data.................................................................................................................12
3.3.2. Secondary Data.............................................................................................................12
3.4. Analysis...............................................................................................................................12
3.4.1. Existing system.............................................................................................................12
3.4.2. Proposed System..........................................................................................................13
3.4.3. Functional Requirements...........................................................................................14
3.4.4. Non Functional Requirement.......................................................................................14
3.5. Requirement Analysis.....................................................................................................15
3.5 .1. Hardware requirements..............................................................................................15
3.5.1.2. Software requirements...............................................................................................16
3.6. Feasibility study..............................................................................................................18
3.6.1. Technical Feasibility....................................................................................................19
3.6.2. Operational Feasibility.................................................................................................19
3.6.3. Economic Feasibility....................................................................................................19
3.7. System Modeling................................................................................................................19
3.10. Conceptual data modeling(ER-diagram).......................................................................30
3.11. Logic Modeling.............................................................................................................31
3.14. Implementing tools...........................................................................................................48
3.15. Testing...............................................................................................................................51
3.15.1. Unit Testing................................................................................................................52
3.15.2. Integrated Testing.......................................................................................................53
3.15.3. System Testing...........................................................................................................54
3.16. Evaluation.........................................................................................................................55
IV
3.17. Documentation..................................................................................................................56
SECTION FOUR...........................................................................................................................57
4.1. Conclusion..........................................................................................................................57
4.2. RECOMMENDATION......................................................................................................59
REFERENCES..............................................................................................................................61
AppendixI.....................................................................................................................................62
SAMPLE CODES.............................................................................................................................63
V
Abbreviations/Acronyms
ARPA: Advanced Research Projects Agency.
ALA: American Library Association.
ASU: Assosa University.
CSS: Cascading Style Sheet.
CCTA: Central Computer Telecommunications.
DFD: Data Flow Diagram.
DL: Digital Library.
ERM: Entity Relation Model.
FETASU: Faculty of Engineering and Technology Assosa University.
Html: Hyper Text Markup Language.
NASA: National Aeronautics and Space Administration.
NGO: Non-Governmental Organization.
NSF: National Science Foundation.
OPAC: Online Public Access Catalogue.
RDBMS: Relational Database Management System.
SQL: Structural Query Language.
T-SQL: Transact Structural Query Language.
UNESCO: United Nations Educational, Scientific and Cultural.
US: United States.
VI
List of Table
Table pages
Table 3. 1. Hardware requirements.......................................................................................................14
Table 3. 2. Software requirements........................................................................................................14
Table 3. 3. Software requirements..........................................................................................................39
VII
List of Figures pages
Figure 3.1. Major DFD components...........................................................................................21

Figure 3.2. Context Diagram......................................................................................................22
Figure 3.3. Level 0 DFD admin and intructor............................................................................23
Figure 3.4. Level 0 DFD admin and student..............................................................................24
Figure 3.5. Level 0 DFD admin registration...............................................................................25
Figure 3.6. Level 0 DFD admin request of instructor.................................................................26
Figure 3.7. Level 0 DFD admin request of student....................................................................27
Figure 3.8. Level 0 DFD admin request of instructor.................................................................28
Figure 3.9. Level 0 DFD admin request of student....................................................................29
Figure 3.10. Decisition Tree …...................................................................................................30
Figure 3.11. Entity Relationship diagram ...................................................................................41
VIII
Abstract
In the current world, an organization, agencies, and individuals can receive and access a vast
amount of information from the libraries, such from the manual library. But this manual system
is very tedious and boring in matter of cost, time and manpower. In Assosa University, the
library gives its service in manual system. This manual system is coasty, delay the time of
accessing. The main objective of this paper is Developing Digital Library System for Faculty of
Engineering and Technology Assosa University. This project has feasible, achievable and
practicable in technical, operational and economical benefit to solve the problems that face in
the library.By this students, library workers and lectures are beneficiary from the system. The
project is developed from December to June/ 2016. In order to design the system, structured
modeling like process modeling, logical modeling and conceptual data modeling was used. The
students, staff workers and managers were the population of the study and selected as the
respondents by using purposive sampling techniques to get relevant data by using interview and
observation data collection techniques. The project has the functional requirements such as
login, update, delete and view and non-functional requirements such as performance, security
and availability. To implement the system, c# programming language was applied.
IX
SECTION ONE
Introduction
1.1. Background
The word library derived from the Latin word ‘liber’ a source. The Latinized word ‘bibliotheca’
is the origin of the word for ‘library’ in the Greek, Russian and Roman languages. Today’s
library and information center has passed a long evolutionary sequence. Now the concept and
the very name ‘library ‘has changed to “virtual library”, “information nerve center”,
“information management”, and lastly “digital library” . Document delivery is an essential
service in a library and information center. It involves many components like request for
document, document type, document sources and function or process which again include
function like document selection, request procedure, document retrieval and document transfer.
In the case of electronic document or in the case of digital document, delivery of document takes
place in the digitalized form. Both print and electronic document deliveries are very important
but there are some agencies that deliver both types of document .It are complex processes
involving user, suppliers and time. Document delivery can involve author, publisher,
subscription agents, document delivery services providers, and supplier, library and information
professionals. Generally " I have argued, elsewhere, that the four core characteristics of a public
library are: that it is a physical place, that is, a focus spot for continuous educational
development, that it has a mission to serve the underserved, and that it is a guarantor of public
access to information (Besser, 1998).
A library is a collection of information resources and services, organized for use, and maintained
by a public body, institution, or private individual. In the more traditional sense, it means a
collection of books. In modern sense definition of library is a place in which literary and artistic
materials, such as books, periodicals, newspapers, pamphlets, prints, records, and tapes, are kept
for reading, reference, or lending. Digital library (also referred to as electrical library) is
a library in which collections are stored in electronic media formats (as opposed to
print, microform, or other media) and accessible via computers. The electronic content may be
stored locally, or accessed remotely via computer networks. An electronic library is a type of
1
service that allows users, without actually stepping into the library, to read library books and
conduct research at home, in the office, or at school, using the Internet. Service which enables
users to effectively employ electronic data by using library network is also referred to as a digital
library service. These six well-funded projects helped set in motion the popular definition of a
"digital library." These projects were computer science experiments, primarily in the areas of
architecture and information retrieval. According to an editorial in D-Lib Magazine," Rightly or
wrongly, the DLI-1 grants were frequently criticized as exercises in pure research, with few
practical applications" (Hirtle, 1999).
Though these projects were exciting attempts to experiment with digital collections, in no sense
of the word did they resemble libraries They had little or no service components, no
custodianship over collections, no sustainability, no base of users, and no ethical traditions. We
will call this the "experimental" stage of digital library development. Because efforts during this
experimental stage were the first to receive such widespread acknowledgment under the term
"digital library", they established a popular understanding of that term that has persisted for
many years.
1.2. Statement of the problem
According to the study done by (Vamshi et al, 2003) on the Digital Library of Indian Project, the
following are the listed problems if the library uses manual systems. Some of the problems are
the manual library system contains different types of information sources but the users can
access only printed format materials. They cannot access digitalized or electronic based
documents. File security is also one problem. That means in manual library the file is not secured
sometimes most library user take different books without permission and also some user’s cutoff
a paper from the book. The other problem manual library takes a lot of time that means when the
user wants to search and identify the books take a lot of time. Accessing problem is also another
problem simply in manual library the books are not arranged or not classified, by this reason the
users not access remotely. The other problem is the reader or user waste a lot of many to get
other sources of information for example modules. Manual library waste too much paper and
storage space. The above listed problems are similar with titles for Digital Library System for
Faculty of Engineering and Technology Assosa University Library problems, as a result of these
2
problems and because of the FETASU use manual library systems, the investigators are initiated
to do on the developing Digital library System for FETASU.
1.3. Objectives of the study

1.3.1. General objectives
The general objective of this project is to develop a digital library system for Faculty of
Engineering and Technology Assosa University.
1.3.2. Specific objectives
The specific objective of this project is:
To design a system that security the materials.

To design the system that creates better arrangement of books and modules.
To design the system that reduces wastage of the student time.
To build a system that increases the accessibilities of book.
To build a system that reduces the cost of student and their families they expends for
buying modules and books.
To design the system that upload, download, update & delete materials and also register
users and delete them.
1.4. The scope of the project
The new system which is limited to design Digital Library System for FETASU; the project is
done from December to June, 2016.
Limitations
To develop a real digital library system all the needed requirements need to be fulfilled.
In the context of this project there are restrictions and drawbacks which can be considered as
limitations of the project. In general the limitations are:
1. Shortage of time will be one of the influential factors.

2. Lack of adequate recourses like Analysis tools will be another drawback.
3
3. Absence of reviewing reference materials in the libraries.
4. Lack of experiences in such a big project which needs experience in structured system
analysis and design methodology and inefficiency in organizing large digital collection.
5. Shortage of labor potential to organize the overwhelming dispersed information and

electronic information materials in the different branches of the library.
Delimitations
Because of time, material and financial constraint, the system includes only the development of
digital library system, website of the digital library system with some sample resources.
1.5. Significant of the study
The project has a great significant on performing different information in various settings
working in the faculty of engineering and technology,Assosa University, Assosa University. The
system provides a fast and reliable access for faculty of engineering and technology library users.
This project gives updated information to technology students, instructors.
This project also saves the time of library workers and reduce the disagreement between the
students and the librarian. Student are beneficiary in order to saving time, simply getting books
and other information materials, increase the culture of using library when the library is more
attractive at the time the user of the library also increase ,the system supports to do different
exercise. The instructors also are beneficiary on getting additional references, saving time, to
prepare a module. The system benefits researchers, in order to create knowledgeable person by
accessing different information source.
4
1.6. Definition of terms
Library: - a building or room containing collections of books, periodicals, and sometimes films
and recorded music for people to read, borrow, or refer to.
Digital Library: - Refers to all the library resources that are available online through computers
and all materials are putted digitally or the materials are digital format.
System:-A set of detailed methods, procedures, and routines established or formulated to carry

out a specific activity, perform a duty, or solve a problem.
Database:-Collection or files are put on electronically stored data or unit records with software
for the retrieval and manipulation of the data.
Computerized: -Refers to control, perform, processor and store (system, operation or

information) by means of computers or in an electronic devices to equip with or automate by
computers
Digital Library Service: -Refers to service which is either supplied from local servers or
accessible via networks.
E-Library: - Refers to all the library resources that are available online through computers and
data.
5
SECTION TWO
Literature review
2.1. Library
A library is an organized collection of information resources made accessible to a defined

community for reference or borrowing. It provides physical or digital access to material, and may
be a physical building or room, or a virtual space, or both. A library's collection can include
books, periodicals, newspapers, manuscripts, films, maps, prints, documents, microform, CDs,
cassettes, videotapes, DVDs, e-books, audio books, databases, and other formats (Schrettinger,
1803).
2.2. Types of Library

2.2.1. Digital Library
Digital libraries are systems that combine the machinery of digital computing, storage and
communication, the content, and software needed to reproduce, emulate, and extend the services
of collecting, cataloging, finding and disseminating information offered by traditional libraries
based on paper and other materials (Kenney, A., 2000). A full service digital library must not
only fulfill all essential services provided by traditional libraries but also make good use of the
advantages of digital technology. Digital libraries are viewed as systems providing a community
of users with coherent access to a large, organized repository of information and knowledge.
This organization of information is characterized by the absence of prior detailed knowledge of
the uses of the information. The ability of the user to access, reorganize, and utilize this
repository is enriched by the capabilities of digital technologies (C. Lynch, 1995).
The concept of a “digital library” is not merely equivalent to a digitized collection with
information management tools. It is rather an environment to bring together collections, services,
and people in support of the full life cycle of creation, dissemination, use, and preservation of
data, information, and knowledge (S. M. Griffin, 1998)
6
According to A. Paepcke, (1996) the purposes of digital libraries are identified as:
To speed up the systematic development of the means to collect, store, and organize information
and knowledge in digital form, and of digital library collections, To promote the economical and
efficient delivery of information to all parts of society, To encourage co-operative efforts which
leverage the considerable investment in research, resources, computing and communications
network, To strengthen communication and collaboration between and among the research,
business, government and educational communities and also to contribute to the lifelong learning
opportunities of all people.
The digital libraries offer significant and unparalleled improvement and value addition to library
services. While providing workable solutions to problems traditionally associated with the
management of print based collections in traditional libraries, improved information retrieval and
enhanced document delivery capability is widely accepted. The cost of creating, storing
manipulating and transmitting digital information has decreased considerably providing
necessary urge to the digital library initiates worldwide. Rise in acquisition and subscription fees
have forced the libraries to find other means to make information available to their users and
content aggregators and electronic publishers are providing the means to do so. It is commonly
thought that a digital library enables anyone, at any time or place, to access a library's enormous
book collection by using the Internet. It is even believed that one can use all the books in a
library's collection without actually going to the library. But these notions are only half-truths.
It is true that a digital library is aimed at making it possible for anyone, at any time or place, to
access digitized resources over the Internet. It is only natural, however, that the contents which
can be used over a digital library are limited to those contents which have been digitized at the
library so they can be relayed through a network. The process of digitization is a major one,
involving much labor and expense. Libraries have huge book collections and it is not possible to
digitize all these resources. It is a huge misconception, therefore, to think that anyone, at any
time or place, can access any book in a library. What is more, most of the books in a library's
collection are protected by copyright. Digital libraries must honor copyright and in digitizing and
providing information, ample attention must be given to this copyright (Masaru, 1998).
7
2.2.2. Public libraries
A public library provides services to the general public and usually makes at least some of its
books available for borrowing. Typically, libraries issue library cards to community members
wishing to borrow books. Many to the public libraries also serve as community organizations
that provide free services and events public (ALA 1995).
2.2.3. Special Libraries
Special libraries offer unique opportunities to work in places such as corporations, hospitals, the
military, museums, law firms, advertising agencies, professional associations, private businesses,
and the government. Many special librarians/information specialists now work outside the
typical library setting and have a no library job title. Special libraries can serve particular
populations, such as the blind and physically handicapped, while others are dedicated to special
collections, such as the Library of Congress or a presidential library (Lizz, 2011).
2.2.4. Electronic Library
An electronic library is a type of service that allows users, without actually stepping into the
library, to read library books and conduct research at home, in the office, or at school, using the
Internet. Service which enables users to effectively employ electronic data by using an in-library
network is also referred to as an "electronic library service"(Masaru, 1998).
2.3. Related works
2.3.1. Secure the materials

A Security refers to protection of the information included in library. Security is important in
order to secure the materials. It gives a protection for the materials that is putted in the library
from disasters or from disappears (Saffady, 2005). Security encompasses a holistic approach at
protecting resources against un-authorized removal or loss and disasters (Ajegbomogun, 2004).
The project team understands from this that is important to create better security for the library
materials.
8
2.3.2. Better arrangement of books and modules
Arrangement means ordering of books. By using cataloguing system can order, arrange and
group of books in to the similar subject area. The project team will create a system that
arranging the books by using title, author name and subject. In manual library which is building
digital collections is a good candidate for coordinated activity. First, acquiring digital works and
doing in-house digitization are expensive, especially to undertake alone. By working together,
institutions with common goals can gain greater efficiencies and reduce the overall costs and
time involved in these activities, as was the case with retrospective conversion of bibliographic
records. Second, it also reduces the redundancy and waste of acquiring or converting materials
more than once. Third, coordinated digital collection building enhances resource sharing and
increases the richness of collections to which users have access (Lynch and Garcia, 1995).
2.3.3. Reduces wastage of the Users time

The libraries are to use the resources are not arranged and classification notation does not even
need to be displayed on the screen so an inexperienced user can have the advantage of using a
hierarchical scheme with the distraction of the notation itself after that the library uses
classification system (McKiernan, 1996).
2.3.4. Increasing the accessibility of the book in the library

Circulation and distribution of books and the management of digital assets as achieved through
the functionality of a traditional integrated library system. The ability to record items issued
returned and items overdue and items requested. Also included is the recording of user data
reading and service preferences, and automatic selection of material for them (Hague, IFLA
Headquarters, 2005). When the material or the books is arranged or ordered at that time the
accessibility of the book is increase.
9
SECTION THREE
Project Design and Methodology
3.1. Description of Study Area
The governmental higher educational institutions of Ethiopia were very limited some years ago.
But nowadays, the government has given due attention for the expansion of public higher
learning institutions. As a result, the numbers of universities are increased .Among these Assosa
University is one of them.
The study was conducted in Assosa University. Assosa University began its works in 2004 E.C.
by having all faculties which is served for all faculty and departments and includes other the
night, evening and extension students are accesses the library materials. So, as the basic hearts of
all university, Assosa University library system is developed and located at the ground near to
the registration block. It has very wide with smart design and beautiful colors. The workers
(patrons) those perform in cataloguing and circulation and manager. The library has three places
which students were to study and each reference book is placed depend on the department and
faculties. The library is works throughout 24 hours.
3.2. Data Collection Methods

The following are this project’s data collection methods those are used by the project team to
investigate the study.
A. Observation
Since developers of the system are also users of the library its simple to observe activities in the
library like service provision, accessibility of information materials, positive and negative side of
activities in the library and others. So this method of data collection will be used extensively by
the project group.
The project team is used observation to know the existing system. Project team is observed
activities in the library like service provision, accessibility of information materials, positive and
negative side of activities in the library, how the students brow and lending materials in the
library and others.In order to get relevant information the team is directly observes the activity
and function of Faculty of Engineering and Technology, Assosa University.
10
B. Interview
An interview is formal discussion between an investigator and an applicant or candidate or
Interviews and communication with librarian manager, staff to get information on existing
system, to identify special features and also problems with existing system, to identify barriers
with the current service provision.
typically in person, in which information is exchanged, with the intention of establishing the
applicant’s suitability for a position (Clara, 2009).
In order to get relevant information about the existing system the project team used the following
population of FETASU for interview: - manager, students that are a member of library club and
staff workers or librarian. This used to identify special features and also problems with existing
system.by using interview the team collected different relevant information for the new system.
By interviewing the manager the team gets background of the existing system and stastiscal
data’s, by interviewing the students the team gets the problems that exists in the existing system
and also the team interviews the librarian form the librarian the team gets more information
about FETASU library.
Generally the following advantages that the team gets from interview:-
 Investigate sensitive issues.

 getting primary data’s
 Getting statically data.
 Getting detailed information on a specific topic.
 Knowing the existing system.
 To know the problems that seen in FET ASU library
11
3.3. Types of Data
3.3.1. Primary Data
Primary source is a source of information. It is unorganized form. For the purposes of this,
observation, interview have been used to collect data as primary data sources from the librarians,
students that are a members of library club, director, staff workers to gather the necessary
information.
3.3.2. Secondary Data
These include all types of published and unpublished, public or private documents and other
such types of information. Such as books, documents, journals, articles, different past researches,
reports of the department and online material.
3.4. Analysis
3.4.1. Existing system
Assosa university 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. In case of digital library services the library is at the zero level. And there
is no digitalized services currently provided to the users of the library.
The existing system is draft a manual system likes any educational or university library that is
why we need to provide a digital system for FETASU library.
So the system analysis is full study of the system with internal and external resources or
materials of the system.
In existing system all the transaction of books or modules are done manually, so taking more
time for a transaction like borrowing a book and for searching of members and books. There is
no way for students and lecturers to use the digitized library service in FET ASU.When we see
the existing system the lecturers are difficult to teach because there is no full information about
the course and the students are don`t get the module where ever they want, and also they don`t
get the same types of modules.
12
3.4.1.1. Major functions of existing system
The existing library system of Assosa University has its own function.It gives an access for the
user and it works 24 hours. The library contains different kinds of book and modules, a few of
them has catalogue.
3.4.1.2. Problems in the existing system
In the existing system there are a lot of problems. All material that exist in the existing system is
paper based and they are difficult to use, take a lot of time, there is no better arrangement of
book and modules,the materials are not secured, take a lot of paper and so on.
3.4.2. Proposed System
The proposed system is makes available to the full accessibilities of e-books or e-modules in the
Faculty of Engineering and Technology for ASU library to each and every student, where
students can easily find the e-books and minimize time, secure the material that stored in the
library, reduce wastage of money and also the information from the system have been reliable,
Easy to search e-books, Just need a little knowledge to operate the system, User (students) can
access the information easily, Through system user (admin, instructor, user) the admin can add
members, add modules, add/upload books, search members, search books, update information,
edit information, delete modules, delete books and delete comment. Especially for students by
saving the time required to go from their Dorm to the library. In addition to this it also save the
costs needed to buy different modules that are given from the instructors . For the instructors it
reduces the effort (labor) for preparing or arranging teaching material.
The new system has lower loads from the library staff and also there is faster retrieval of
information about the desired book.
13
Advantages of the proposed system:
The new Investigated systems have the following advantages:
 Search facility
 User friendly interface
 Fast access to database
 Less error
 More storage capacity
 More storage capacity, search facility, less error
 Look and feel env’t and quick transaction.
 Students can read the books online at anywhere and anytime.
 A maximum number of books or Modules are made available to each and every student.
 Reduce the workload of employee.
 The user can access different information sources.
 Provide facility for proper monitoring reduces paper work.
3.4.3. Functional Requirements

Functional requirements describes what a system describes should do and the behavior of the
system that relates to the system's functionality so interactions between the system and its
environment independent of its implementation. The fundamental action that must take place in
developing system in accepting and it is a statement of exactly what the system must do
According, the proposed system has the functional requirements of accept and store library
materials (Books and Modules) in digital format.uploaded the material, delete and update the
information’s entered ,insert book information ,register user. The user can download book and it
organize and make searchable documents.
3.4.4. Non Functional Requirement

Nonfunctional requirement describes the place of constraints on how the system has done so.
invisible aspects of the system. Unlike functional requirement, non-functional requirement deals
with additional quality of the system. Non-functional requirements show the technical aspect that
the system must fulfill the non-functional requirement explains a performance characteristic of
the system.
14
Security: means about the safety of materials (books and modules) because it is other additional
function of the system, availability: the system have been available all time, efficiency: the
system should be complete most tasks instantly, flexibility: the system should be developed on
open architecture to allow modification as & when the need arise, usability: the system have
been easy to learn, operate, prepare input, & interpret output, capacity: the system have been
support much user at a time, user-interface: the user-interface screen shall response quickly, easy
& simple to communicate with, maintainability:the system should be easily extensible to modify
the in later development stage, add new functionality, portable to different platforms and should
be easily mapped to specific requirements.
 The system that contain user account, enable users to log into the system.
 Every user ,for example Admin, Student and staff should be log into the system only by their
appropriate user type.
 User should be able to retrieve library material by entering their password and user name.
3.5. Requirement Analysis
Most software defines two sets of system requirements: minimum and recommended. With
increasing demand for higher processing power and resources in newer versions of software,
system requirements tend to increase over time. Here the requirements can be viewed in two
directions the user side and the librarian or the organizational side.
The project team have been used using different requirement analysis to complete the overall
system. Those requirements are listed below:-
3.5 .1. Hardware requirements

All the physical part of computer is hardware. This form is given to all electrical devices
attached to the computer for the purpose of input, process.
Memory & Secondary storage

1. RAM: 512 MB and above
2.50 GB Hard-disk: and swap space (if RAM is insufficient).
15
Peripherals
1. CD-ROM drives,
2. Network devices, etc.
Table: 3. 4. Hardware requirements
No Types of hard ware Description and Usage
1. Hard disk Used for move, capture and store data.
2. Flash disk Used for move, capture and store data.
3. Printer Used for print documentation.
4. Computer Is a programmable machine carry out a set of arithmetic

or logical operations Automatically
5. RW –CD A storage used for burning the document.
3.5.1.2. Software requirements

Software is an internal part of a computer. It is used to process data.
The project teams have been used using this different language to complete the overall system.
 Platform
Typical platforms include a computer's
 architecture,
 Operating system: Microsoft Windows XP
 programming languages and their
 Runtime libraries.
Web browser
 It support all Internet browser application but MS window Internet Explorer is
recommended.
 Other requirements
16
 Desk top /lap top computers having minimum of 128MB of RAM and a typical storage
capacity and processing speed.
 Un interrupted power supply
 Internet connection and
 Database server computers and web server computers having more than 256MB of RAM and
high storage capacity and processing speed.
Microsoft visual studio
Microsoft Visual Studio is an integrated development environment (IDE) from Microsoft. It

is used to develop computer programs for Microsoft Windows, as well as web sites, web
applications and web services. Visual Studio supports different programming languages and
allows the code editor and debugger to support (to varying degrees) nearly any programming
language, provided a language-specific service exists. Built-in languages include C, C++ and C+
+/CLI (via Visual C++), VB.NET (via Visual Basic .NET), C# (via Visual C#), and F# (as of
Visual Studio 2010). Support for other languages such as M, Python, and Ruby among others is
available via language services installed separately. It also supports XML/XSLT,
HTML/XHTML, JavaScript and CSS. Java (and J#) was supported in the past.
MySQL-2012
MySQL is a popular choice of database for use in web applications, and is a central
component of the widely used LAMP open-source web application software stack (and other
"AMP" stacks). LAMP is an acronym for "Linux, Apache, and MySQL.It is easy to use. A few
simple statements in the SQL language are needed to build and interact with a MySQL
database.It can run on many operating systems. MySQL runs on a wide variety of operating
systems - Windows, Linux, Mac OS, most varieties of UNIX and others.Strong Data Protection:
MySQL oﬀers exceptional security features that ensure absolute data protection. In terms of
database authentication, MySQL provides powerful mechanisms for ensuring only authorized
users have entry to the database server, with the ability to block users down to the client machine
level being possible.
Table: 3. 4. Software requirements
17
No Types of software Description and Usage
1. Microsoft office Software used for presentation of the documentation.

2013
2. SQL database Used for mange database in SQL.
3. Visual studio 2012 Used to develop computerprograms for MicrosoftWindows, as

or 2010 well as websites, webapplications and webservices.
4. Text editor Is a type of program used for editing plain text files (e.g. Text
pad )
5. Adobe reader 9 Used to view PDF (Portable Document Format) files. Allows
you to only read PDF files.
6. C# It is a multi-purpose computer programming language suitable
for a wide variety of development needs.
7. Adobe Photoshop Is a raster graphics editor developed and published by Adobe
Systems for Windows and OS X.
3.6. Feasibility study

To bring the successful completion of this project goals and objectives the feasibilities issues
listed below has determined the project viability or the discipline of planning, organizing, and
managing resources.
 Problems that lend themselves to systems solutions
 Opportunities for improving through: (a) upgrading systems (b) altering systems (c)
installing new systems.
3.6.1. Technical Feasibility
In this feasibility study project team test whether the system can be developed using existing
technology or not. This System can be this system provides help description to the user about
how to use the system and other technical modification on the system is done by the developers.
3.6.2. Operational Feasibility
Currently there is no existing system in the case of digital library so this system will be
implemented in Assosa University as a pioneer of digital library project. The system will provide
18
adequate through put at desired time to the user and also give the needed information in a timely
usefully formatted way. The system also has security to gives access privilege providing account
for an authorized person. There is a place that doesn’t need security or privilege to access for all
uses like general information.
3.6.3. Economic Feasibility
As cost/benefit analysis, show the new system is developed using a very minimum coast and it
give a lot of benefits such as advancing the services of the library, decreasing the work load of
the libraries, students or users of the collection will access the material they want at any time and
etc.
3.7. System Modeling
System modeling or design is the process of defining the architecture, components, modules,
interface and data for a system to satisfy specified requirements. This section deal how the
system is designed. To design the system, there are structured and unstructured system designs.
From the two, structured modeling have been used for this project. Structured systems analysis
and design methodology is a set of standards for systems analysis and application design. It uses
a formal methodical approach to the analysis and design of information systems (CCTA, 1980-
1981).
 To design the new system that the investigators are going to use structured modeling that
means Process modeling (DFD, context diagram, level O-diagram.
 Logical modeling .
 Conceptual data modeling (ER-diagram).
3.8. Data Flow Diagram (DFD)
The project team used DFD to represent the processes in their information system from the
viewpoint of data. The DFD lets project team visualize how the system operates, what the system
accomplishes and how it have been used implemented, when it is refined with further
specification.
Data flow diagrams (DFDs) reveal relationships among and between the various components in a
program or new system. DFDs are an important technique for modeling a system’s high-level
detail by showing how input data is transformed to output results through a sequence of
19
functional transformations and where the data is come from and go to, and where the data is
stored. DFDs consist of four major components the components has its own symbols: entities,
processes, data stores, and data flows.To indicate the process the team used the above
components of DFD and the symbols. The symbols used to show how these components interact
in a system are simple and easy to understand; however, there are several DFD models to work
from, each having its own symbology.When it comes to conveying how information data flows
through systems (and how that data is transformed in the process), data flow diagrams (DFDs)
are the method of choice over technical descriptions for three principal reasons.
 DFDs are easier to understand by technical and non-technical audiences.
 DFDs can provide a high level system overview, complete with boundaries and connections
to other systems.
 DFDs can provide a detailed representation of system components.
In the figure below the investigator understands that how information is flow. It illustrates flow
of information in structural order in the new system from input and what is the output. Data can
browse from the database in what they want.
3.9. Defining DFD Components
DFDs consist of four basic components that illustrate how data flows in a system: entity, process,
data store, and data flow.
3.9.1. Entity
An entity is the source or destination of data. The source in a DFD represents these entities that
are outside the context of the system. Entities either provide data to the system (referred to as a
source) or receive data from it (referred to as a sink). Entities are often represented as rectangles
(a diagonal line across the right-hand corner means that this entity is represented somewhere else
inthe DFD). Entities are also referred to as agents,terminators,or source/sink.
3.9.2. Process
The process is the manipulation or work that transforms data, performing computations, making
decisions (logicflow), or directing data flows based on business rules. Inother words, a process
receives input and generatessome output. Process names (simple verbs and dataflownames, such
as “Submit Payment” or “Get Invoice”) usually describe the transformation, which can
20
beperformed by people or machines. Processes can be drawn as circles or a segmented rectangle
on a DFD, andinclude a process name and process number.
3.9.3. Data Store
A data storeis where a process stores data betweenprocesses for later retrieval by that same
process oranother one. Files and tables are considered data stores.Data store names (plural) are
simple but meaningful, such as “customers,” “orders,” and “products.” Datastores are usually
drawn as a rectangle with the right- hand side missing and labeled by the name of the data
storage area it represents, though different notations do exist.
3.9.4. Data Flow
Data flowis the movement of data between the entity,the process, and the data store. Data flow
portrays theinterface between the components of the DFD. The flowof data in a DFD is named to
reflect the nature of thedata used (these names should also be unique within aspecific DFD).
Data flow is represented by an arrow,where the arrow is annotated with the data name.These
DFD components are illustrated in Figure 10.
Entity
Data flow
Process
Data store
Figure1. The Four major DFD Components.
21
Figure 2.Context data flow diagram shows information flow in the new system.
22
Figure 3. Level 0 DFD shows clear information flow in the new system for
administrator and instructor.
In figure below illustrates the 0 level of administrator & instructors function when the
administrator logs into his/her account and register the users, update, search, delete their
information and when the instructors he/she can upload modules.
23
Figure4. Level 0 data flow diagram shows clear information flow in the proposed system for
administrator and student.
In figure below illustrates the 0 level of administrator function when it logs into his/her account
and register the users/instructor, update, search, delete their information.
24
Figure 5.Shows administrator register instructor and edit their information after logging.
The following three successive figures indicate how the administrator add, update, search, delete
book and module information with respect to the student and instructor permission/request.
Because, without the request of instructor and student he/she did not edit and delete the items
information.
25
Figure 6.Shows how administrator adds, and edits book information with the request of
instructor.
26
Figure 7.Shows how administrator adds, and edits book information with the request of student.
27
Figure 8.Shows how administrator adds, and edits module information with the request of
instructor.
28
Figure 9.Shows how administrator adds, and edits module information with the request of
student.
29
3.10. Conceptual data modeling(ER-diagram)
An entity-relationship (ERD) diagram, a graphical representation of entities and their
relationships to each other, typically used in computing in regard to the organization of data
within databases or information systems. An entity is a piece of data-an object or concept about
which data is stored. Supports different diagram types like flowcharts, network diagrams,
database models and objects help to draw professional diagrams.
There are basically three(3) things which the project team consider while making ERD.
3.10.1 Entity
An entity is something, real or abstract, about which the project team store information. For this
system there are basically these three entities:
 Administrator
 Instructor
 User/student
3.10.2. Relationship
A relationship is an association that exists among entities. That indicates the relation between all
functions with perspective actors and users. Like an admin can register many instructors and one
user can download many bibliographic items.
3.10.3 Attributes
A property of an entity or a relationship type, for this system the project team have following
attributes of two specified entities:
 Instructor: user name, password, instructor ID, instructor name, Email, instructor
Department …
 Administrator: username and password.
30
3.11. Logic Modeling
Focuses on the logic of the decisions, steps, choices, etc. those are made, or need to be made,
within the organization to carry out the objectives of the business. DFDs do not show the logic
inside the process (function) thus logic modeling involves representing internal structure and
functionality of processes depicted on a DFD.
Investigator uses DFD in process modeling and also have the following most common
techniques in logic modeling (decision analysis).
 Structured English (pseudo code)
 Decision tables
 Decision trees
Structured English (pseudo code)
Appropriate technique to use when the process logic involves formulas or iterations or when the
decisions are not complex (simple)
It is a modified form of English and has no standard version.
Any analyst can use his / her own dialect of English, by using verbs, i.e. names of processes (to
describe processes) and noun phrases to describe data structures and no usage of adjectives or
adverbs.
It can be used to represent the 3 basic types of programming logic:
Pseudo code for logion:
Step 1. Actor: administrator, instructor.
Step 2. Precondition: the administrator and the instructor open the system.
Step 3. Post condition: after the opening of the system the administrator and the instructor can
perform their activity.
3. Description: Administrators and instructor open the system.
4. Login form displayed.
5. Administrators and the instructor fill login details/user name and password.
6. Administrator and instructor click the button.
7. The system validate the login details/user and password.
8. System displays successfully login message.
Alternative course of action
31
If the system validates the login details is incorrect return back to step 6.
Pseudo code for manage book.
Actors: Administrator.
Precondition: the administrator opens the system.
Post condition: the administrator manages the book details
Description:
Step1. The administrator opens the system
Step 2. The administrator log in the system by filling their own user name and password.
Step 3. The book manage detail form is displayed
Step 4. The administrator fills details of books
Step 5. The administrator click the update link (button)
Step 6. The system validates the details of books
Step 7. If the details of books are correct
Step 8. You have successfully updated message is displayed
If the book details are incorrect not success full message is displayed and the administrator fills
the book details by return back to step 4.
Pseudo code description for manage module
Precondition: the Instructor opens the system
Post condition: The instructor manages the details of module
Description:
Step 1. The instructor log in to the system by submitting the correct user name and password
Step 2. Manage module form is displayed
Step 3. The instructor fills the module details on the form
Step 4. The instructor clicks the update link (button)
Step 5. The system validates the details of module
Step 6. If the details are correct successful message is displayed
Alternative course of action:
If the details are incorrect not successful message is displayed and the instructor fill the correct
logion details by returning back to step 3.
32
Pseudo for Register instructor detail
Precondition: the administrator opens the system
Post condition: the administrator registers the instructor to the database
Description:
Step 1. The administrator log in to the system
Step 2. Register instructor detail form is displayed
Step 3. The administrator fills the details of instructor information
Step 4. The administrator click the register button
Step 5. The system validates the details of instructor
Step 6. The system displays successful message when the information are correct
Alternative course action
If the information is not correct not successful message is displayed and he/she must fill the
correct information by returning back to step3.
Pseudo code for delete instructor details
Description:
Step 2. The delete instructor detail form is displayed
Step 3. The administrator fills the id of instructor
Step 4. The instructor clicks the delete button
Step 5. The system validate the ID number of instructor
Step 6. If the ID is correct you have successfully deleted message is displayed
If the ID is incorrect please enter the correct Id is displayed and the administrator enters the
correct Id by returning back to step3.
Pseudo code for Instructor details
Description:
33
Step 1. The administration log in to the system
Step 2. The update instructor detail form is displayed
Step 3. The administrator enters the instructor id and new instructor information
Step 4. The administrator clicks the update button
Step 5. The system validates the instructor’s detail (information)
Step 6. If the information is correct you have successfully updated message is displayed
If the instructor details are incorrect the administrator return back to step3 and 4
Pseudo for save book detail
Post condition: the administrator save the book to the database
Description:
Step 2. Save book detail form is displayed
Step 3. The administrator fills the details of save book information
Step 4. The administrator click the save button
Step 5. The system validates the details of save book
Pseudo code for delete book details
Post condition: the administrator deletes the book from the database
Description:
Step 2. The delete book detail form is displayed
Step 3. The administrator fills the id of book to be deleted
Step 4. The instructor clicks the delete button
Step 5. The system validate the ID number of delete book
34
Step 6. If the ID is correct you have successfully deleted message is displayed
If the Id is incorrect please enter the correct Id is displayed and the administrator enters the
correct Id by returning back to step3.
Pseudo code for search book details
Post condition: the administrator the search book from the database
Description:
Step 2. The search book detail form is displayed
Step 3. The administrator enters the search book code and new search book information
Step 5. The system validates the search book detail (information)
Step 6. If the information is correct you have successfully searched message is displayed
If the search book details are incorrect the administrator return back to step3 and 4
Pseudo code for update book details
Post condition: the administrator registers the update book to the database
Description:
Step 2. The update book detail form is displayed
Step 3. The administrator enters the update book code and new search book information
Step 5. The system validates the update book detail (information)
Step 6. If the information is correct you have successfully updated information message is
displayed
If the update book details are incorrect the administrator return back to step3 and 4
Pseudo for Register student/user detail
35
Precondition: the student/user opens the system
Post condition: the student/user registers the student to the database
Description:
Step 1. The student log in to the system
Step 2. Register student detail form is displayed
Step 3. The student fills the details of student information
Step 4. The student click the register button
Step 5. The system validates the details of student
Pseudo code for search book details
Precondition: the student/user opens the system
Post condition: the student search book from the database
Description:
Step 1. The student log in to the system
Step 2. The search book detail form is displayed
Step 3. The student enters the search book code and new search book information display and
search request will be displayed
Step 4. The system validates the search book detail (information)
Step 5. If the information is correct you have get the book for use
If the search book details are incorrect the student return back to step3 and 4
Pseudo code for save module details
Precondition: the administrator/instructor opens the system
Post condition: the administrator/instructor book details to the database
Description:
Step 1. The administrator/instructor log in to the system
Step 2. The save module administrator/ instructor detail form is displayed
36
Step 3. The administrator/instructor clicks the save module button
Step 4. The system validate the module administrator/ instructor
Step 5. If the module is correct you have successfully save message is displayed
If the module is incorrect please enter the correct module is displayed and the administrator
/instructor enters the correct module by returning back
Pseudo code for delete administrator/instructor details
Precondition: the administrator/instructor opens the system
Post condition: the administrator/instructor registers the administrator /instructor to the database
Description:
Step 2. The delete module administrator/ instructor detail form is displayed
Step 3. The administrator /instructor fill the id of delete module
Step 4. The administrator /instructor clicks the delete button
Step 5. The system validate the ID number of administrator /instructor
Step 6. If the book ID no is correct you have successfully deleted module information message is
displayed
If the book Id no is incorrect please enter the correct Id is displayed and the administrator
/instructors enters the correct Id by returning back to step3.
Pseudo code for search module administrator/instructor details
Precondition: the administrator /instructor open the system
Post condition: the administrator/instructor search the module from the database
Description:
Step 2. The search module detail form is displayed
Step 3. The administrator/instructor enters the search module code and new search module
information display and search request will be displayed
Step 4. The system validates the search module detail (information)
Step 5. If the information is correct you have successfully updated message is displayed
37
If the search module details are incorrect the administrator/instructor returns back to step3 and 4
Pseudo for upload module detail
Post condition: the administrator in to upload module to the database
Description:
Step 2. Register upload module detail form is displayed
Step 3. The administrator uploads the module information
Step 4. The administrator click the upload module button
Step 5. The system validates the details of updated module
If the input data has errors the system display error message & allow the Administrator to try
again.
3.12. Decision tables
 A matrix representation of the logic
 It specifies the possible conditions and the resulting actions.
 Best used for complicated decision logic
 Consists of 3 parts.
Condition stubs; list of conditions relevant to decision
Action stubs: list of actions that result from a given set of conditions
Rules: links conditions to actions and specify which actions to be followed for a given set of
conditions.
 Standard procedure for creating decision tables:
 Name the condition and values each condition can assume
 Name all possible actions that can occur
 List all rules
 Define the actions for each rule
 Simplify the table (by removing unnecessary rules)
38
 Consult users.
Actor type: A=add /upload book,
Table 3.3. Decision Table
Rules
Conditions/Action of 1 2 3
manager
instructor manager User/students
Actor type
Condition stubs
Open the system

Action stubs yes yes yes
logion yes yes no

Upload book/module yes yes no
Delete book/module yes yes no
Write news no yes no
register no yes no
Download book/module yes yes yes
 In order to logion in to the system manager and the instructor must be known their own user
name and password.
3.13. Decision trees

 A graphical representation of a decision situation
 Decision situation points are connected together by arcs and terminate in ovals.
 It has two main components
 Decision points: represented by nodes
39
 Actions: represented by ovals.
How to do
 It is read form left to right
 Each node has a number corresponding to a numbered choice on a legend.
 All possible actions are listed on the far right
 Identify all conditions and actions and their order and timing
 Begin building the tree from left to right while making sure you are complete in listing all
possible alternatives before moving over to the right.
Figure 10. Decision trees for the manager, instructor and users their activities.
Legend
40
1. Manager
2. Instructor
3. Students
Figure 11. Shows entity relation-ship of the proposed system.
41
The user Interface design
User Interface Identifier DLSFETASU 1
User Interface Name DLSFETASU home page
User Interface Description It serves as index to user home
Relationship Search form
Type(Major/Minor) Major
Steps to followed to use the interface
1.Type DLSFETASU URL in address bar of web browser
2.The page will be displayed because it is default page
3.Select search type
4.Search library books or modules/search web
5.Type your query
6.Click search command button
7.Result will be displayed
42
User Interface Name DLSFETASU Book /modules downloads
User Interface Description Available Book / modules downloads are
displayed here
Relationship list
43
1.Open home page of DLSFETASU
2.Click the link select the file upload the Book/ modules downloads
3.Available Book/ modules downloads will be displayed
4.Fill it properly
4.Download the materials
44
User Interface Name Comment
User Interface Description User comment library
Relationship Comment form
1.Open library home
2.Click the comment link
3.Form will be displayed
4.Fill it properly
4.Submit the information’s
45
User Interface Description Librarians log in by this page
Relationship forms
1. Type your User name and password
2. Click login

User Interface Name Administrator Create account
User Interface Description Sets settings
Relationship Form/wizard
46
1.Type administrator URL on browses address bar
2.Click create account
3.Wizard with form is displayed
4.Filling the information
5. Sign up
3.14. Implementing tools
In this part implementation of pages of each module is done. Pages are divided in to librarian
interface and user interface. That is for security measurement. Rather than using same interface
its better using independent one is better.
47
 Database Implementing
We have used relational database management system. It supports different activities like
deleting, updating, retrieving, creating, uploading, downloading, displaying and other
functionalities. The data base used for database implementation is Microsoft SQL 2012.
Database allows access to materials stored on the server to accessible to users, enables to post
comments, upload resource, and download and others activities. It follows client-server
topology.
 Server side functionality

Displaying resource available on the server depending on request, retrieval of uploaded information is
completed server side.
 Client side functionalities

User can search the library database based on different search criteria. Other user side applications like
comment are depend up on client side database application and also have an Implementation Tools
It is meant to prove quick overviews of concepts of implementing programming languages using

a number example including an arithmetic evaluator and a simple java script interpreter
(Christopher, 2001). Implementation is a way of System Implementation can be summarized as
follows: making the new system available to a prepared set of users (the deployment), and
positioning on-going support and maintenance of the system within the Performing Organization
(the transition). Implementation is the carrying out, execution, or practice of a plan, a method, or
any design for doing something. As such, implementation is the action that must follow any
preliminary thinking in order for something to actually happen. To design the project the project
team have uses C# language and SQL server database this article introduces the basic concepts
of programming language implementation for C# programmers. So the investigators use this
language because it is easy to use and easy to implement. And also C# is it is a language and it is
used to develop different applications and it is also used to design system. SQL server it is a
structural query language.
There are several ways to implement the system. From those types the team have been using the
parallel run implementing system one. Because it better to look up and compare up to the final
48
product with the current system. A system can be implemented after it has been tested. It is also
known as system conversion. It can be performed in any of the following ways:
 Parallel Conversion
A type of conversion in which both new and old systems operate together for a period of time is
called parallel conversion. It is the safest type of conversion. The systems that means existing
and new systems are compared. In the existing system there are so many problems but in the new
system the problems are removed. Parallel running is one of the ways to change from an existing
system to a new one.
 Pilot Conversion
In this type of conversion, one part of the organization uses the new system and the rest of the
organization uses the old system. When one part of the organization is satisfied with the new
system, the rest of the organization can start using it. Once the test implementation feedback has
been evaluated and selected changes have been made to the repository, it’s time to launch the
Pilot Implementation to the group identified during planning. The pilot group can vary
significantly in size. It could range from one department to an entire institution or multiple
institutions. Ideally, your pilot launch should be introduced by individual/s with prestige in the
educational community.
Confirm that your support and help services have been updated based on user feedback from the
test implementation and help staff are ready to assist your users with any problems.
 Phased conversion
A type of conversion in which individual components of new system are implemented one by
one is called phased conversion.
 Direct conversion
In this type of conversion, the old system is directly replaced by the new system. It is the most
risky conversion. It may be necessary when time is very short. It is also called crash conversion.
It describes the importance of user training to use a system.
The training of users is very important to run the new system successfully. The users must be
trained properly to use the new system effectively.
49
The design methodology used in the proposed system is parallel as a result of the fact that
parallel methods support the use of the proposed system side by side with the existing system in
order to test for the system efficiency. Top down approach is used as well in the design because
it allows the analysis of the system to be carried out one after the other.
To apply this parallel system the following should be done.

 Install IIS server with visual studio 2012 to the administrator client PC.
 Making the administrator PC as a web server by installing server software.
 Insert the project to this server particularly insert codes into C# and database into MySQL
folder and then into data folder) and then check the project correctly run.
 Giving a specific address for this project for the sake of user access.
3.15. Testing
Any system needs to be tested before being introduced or revealed to the public or before being
introduced to the public firstly before using the system, the system must be test is it work correct
or not. Secondly the system is tested with what kinds of data are contains. Thirdly the system is
tested with very large amounts of data to see how it can cope or handle or manage.
The main testing mechanisms are:-

 Checked the new system with the correct existing system
 Tested each functional component (for addition, updating, deletion etc.)
 Tested each interface for instance, check the administrator login.
 Tasted the system for redundancy of data registration.
 Tasted the system flow of information.
Sample data for tasting
For the sample the researchers use add form, and login form
 Add form: Example:-
In ‘name’ text filed try to insert number
In ‘email’ text filed try to insert number only and check the result
In ‘id’ text field try to add or upload books which have the same value of id from the previous
 Take Administrator login, staff login.
Example: try to login without inserting something.
50
Project team have been use the following system testing methods:
3.15.1. Unit Testing
This testing model is each and individual model has been tested against the requirement with
some test data. Testing the components is tested individually. For Example:-To check unit test
investigator for instance uses admin login page as follows:-
 Acquisition librarian module
 Search module
Admin login page
Functionality: the form accepts information looks for any field that left by the admin that has left
without being felt. Investigator tested this by repeatedly filling information to the database. If the
investigator left the form without filling and click login button the following message is
displayed:
“You are inserted incorrect password or user name.”That displays in the following manners.
51
3.15.2. Integrated Testing
This type of testing in which the system is almost not all integrated or test. I.e. Two or more web
forms are integrated each other.For instance two or more consecutive pages are tasted, if the
investigator take examples: when admin log from home page and go to admin interface then do
its function.
52
3.15.3. System Testing
This testing method is done by a professional testing agent on the overall completed software
product before it is introduced to the market. For general testing the project team have browse
our home page ones and navigate through its entire link and from the other pages to the rest
pages. Since the links are well structured to perform what they are intended for we do not came
across any error while testing them.
All the links are linked to each other, which move it easily to navigate through the entire size and
most of their independent of one another.
For example: - when the home page is link the overall of the system activities.
53
3.16. Evaluation
To evaluate the system is must be evaluated by different techniques. The following mechanisms
may be used:
 Examine the system by professionals and Check its user friendly (check the system
whether it is easy for the user).
 By using requesting the user to give comment about the system and to evaluate the
system. If the users give positive feedback like: - excellence, appreciation. The project
team can know our system how much it is effective. Unless otherwise the system is
revised again.
 Compare the new system with the existing system (Suitability of information distribution,
Readability and accuracy of information).
 Checked the system is far from political influence and contradiction with the existing on
the political system of the country
 Examined the system for its effectiveness (e.g. by registering huge amount record,
updating those records and deleting it. If it is we can say the system is effective.) and
Efficiency.
54
3.17. Documentation
Documentations are Manuals, instructions, tutorials, procedures, specifications,etc., that
accompany a piece of equipment or software, and provide guidance for its proper use
and maintenance.
Any system should have documentation that helps the user of the system by preparing the
methodology how the system was done and prepare manual how to use code to be tasted and
manipulated. It also provides documentation how to solve the problem when it occurs. The
researchers prepare this section both in printed as a module and electronic as online help on the
system. Researcher’s documentation includes the following main points:-
 How to recover if the software fails (visual studio 2012 server and SQL server 2012 fail)
the system.
 How to recover if the browser fails (e.g. if opera don’t call visual studio 2012server).
Here the researcher put brief description of system documentation
If visual studio 2012 sever is fails (if it doesn’t open the database), the administrator can enable it
the following procedure:-
1st click start on the desktop
2nd click all program
3rd click visual studio 2012
4th click visual studio 2012 and then control visual studio server panel
Finally you can get tools control panel application dialog box, then click setting.
On the other hand if the browser unable to open the database, the responsible body can recover it
by installing the new version or install again.
If the default browser unable to open the program, you can use other browser like chrome, opera
spark and UC browser,so on.
55
SECTION FOUR
Conclusion and Recommendations

4.1. Conclusion
The Digital library system developed can facilitates user information retrieval system if it is
fully applicable for:
1. The Digital library system developed can facilitates user information retrieval system if
it is fully applicable.
2. It saves time consumed by traditional library service.
3. It gives access to resource available in limited number of copies.
4. The number of workers/employees needed in traditional system is reduce.
5. Need of going library physically is already overcome.
In summing up the proposed system have arias problems that face in manual library and fix them
by developing digital library system especially for library workers,students and instructors in the
university community. It addresses the cost benefits and time consuming. When Assosa
University is starting its own function, it gives many operations and utilities from those services
library are one that operates the services to its users. Library is the place in which printed and
non printed materials are available to the readers that are access via on internet or in manual
system. In assosa university FET library is operates its function by manual system, but the
project team are going to solve this manual system by making it digital library system in order to
solve the problem like time consuming, consuming money, difficulties to access and in saving
man power.
The new system that the researchers have been developed; in some instance can reduce the
problem that is found in FET library. Some of the solutions that proposed system brings are:
unlike manual system users can get library material (e.g. Module) easily with low cost, it saves
the time and effort needed to go from home to the library, it also reduce space requirement, etc.
To develop this proposed system the researcher have use the two types of data source; primary
data source and secondary data source, and the very familiar data diagram: ERD and DFD.
Finally the expected output is the admin be maintained the system and users can use this system
based on the rule and regulations.
56
4.2. RECOMMENDATION
In order to take the advantage of the proposed digital library system and to improve the service
of the library we recommend devising this system into implementation. This system will advance
the library operation to the better and reliable service provision and it allow access to
information materials even if there is failure in the internet connection and the system is
accessible because it’s applicable on the intranet connection.
The Digital library system developed can facilitates user information retrieval system if its full
applicable for Many organizations and individuals were use information in their day to day
activities; in case of this they get into library to browse the information need. When they use
manual library there is difficulties, so project team is go to solve those problems.
The only solution for the problem is to adapt the computerized or digitalized support system to
support their transaction system which has been helping them with the accurate and faster
management to produce:
 The system should allow user to search for books and module and downloads them.
 The system should allow the administrator to check for the updates to the database.
 The system allow guest only to main page.
 Upon incorrect login, an error message is displayed and the users have been log again
with correct user name and password.
 Since the user name is unique the system must given a message if the entered user name
is not available.
 The system should allow administrator to register, update, and delete users, books and
module.
Generally Recommendations of Digital Library system group members is listed in following few
lines
1. Firstly the team recommends Assosa university library systems to apply this to their library
usage
2. Since the system is more users friendly every user can access it without any trouble. So the
team recommend library to make use of this system.
57
3. The system is developed currently for the first time. And it may have some limitations should
be take in considerations. So the team are willing to welcome every interested person’s idea and
the team need support of programmers to make the best.
4. Maintenance is needed for the new system , so concerned body should take in consideration
for maintaining the system
5. System should be made up to date. To make this collaboration of concerned is needed.
6. The user can search modules by using module code so the team recommends the next
generation develop the system that can search by using module name.
7. The user can search books by using title code so the team recommends the next
generation develop the system that can search by using book name, authors name, serial
number, note, publication date, ISBN, by publication area, by physical description.
58
REFERENCES
Abifarin, A. library stock security: the experiance of the University of Agriculture Abeokuta,
Nigeria. library & Archival Security, Vol.14, No. 1: 11-19.
Ajegbomogun, F. (2004). Users' assessment of library security: ANigerian university case study.
. Retrieved from Library Management,25 (8/9), 386-390.
Alexander, C. (1979). a timeliness way of building. New york, NY:: Oxford University press.
Ambati, V.; Sankar, p.; Pratha, l.; and Jawahar, C. (2005). Quality management in digital
Libraries. In the preceedings of 1st ICUDL.
American Library Association . (1995). Types of library . Retrieved from Public Libraries.
Coombs,K. A. . (2007). Building a library web site on the pillars of web 2.0. Retrieved from
Computers in libraries, 27(1).
Griffin, S. (1998). The concept of Digital Library.
Jump up and Edward A.Fox. (1999, October/November). The Digital Libraries Initiatives.
Retrieved from Update and Discussion, Bulletion of the america society of Information Science,
Vol. 26, No 1,.
Kenney, A. (2000). Digital Library.
N.D. (2010, July 26). Guidelines for University library Service to Undergraduate Students.
Retrieved from ACRL:http://www.ala.org/ala/mgrps/divs/acrl/standards/ulsundergraduate.cfm
Schirettinger, M. (1803). Defination of Library.
59
AppendixI
ASSOSA UNIVERSITY
FACULTY OF ENGINEERING AND TECHNOLOGY
DEPARTMENT OF INFORMATION SCIENCE
Interview Questions:
This interview questions are developed to interview Manager of librarian of Assosa University
Library.
Interview questions on the background FET ASU of the digital library
1. When and how was Assosa university library established?
2. Currently how many users are in FET ASU library?
3. What is the main problem that seen in FET ASU library?
4. How many students use the library at a time?
5. How many books are found in the ASU FET library?
6. Who are the users of the library?
7. is there something planned in the future to improve library service?

8. How do you express service currently provided at the libraries in the terms of users
information access, that means does user got information on his subject need, at time he need it
most, in format he can handle and in language he can understand it more?
9. What is service time per a day?
60
APPENDIX II
SAMPLE CODES
Visual C# Code for book search page
using System;
using System.Collections.Generic;
using System.Linq;
using System.Web;
using System.Web.UI;
using System.Web.UI.WebControls;
using System.Data;
using System.Data.SqlClient;
using System.Configuration;
public partial class Web_page_Searchbook : System.Web.UI.Page
{
protected void Page_Load(object sender, EventArgs e)
{
}
protected void Button1_Click(object sender, EventArgs e)
{
{
//if (ddlsect_keywrd.SelectedValue=="Author" && TextBox2.Text == "Author2")
{
string FileName = TextBox3.Text;
Response.ContentType = "application/octet.stream";
Response.AppendHeader("Content.disposition", "attachiment;FileName=" +
FileName);
Response.TransmitFile(Server.MapPath("~/Material/" + FileName));
Response.End();
}
//else
//{
// lblMessage.ForeColor = System.Drawing.Color.Red;
// lblMessage.Text = "No data found Try again";
//}
}
}
{
{
//if (ddlsect_keywrd.SelectedValue == "Author")
//{
string CS = ConfigurationManager.ConnectionStrings["ASUCS"].ConnectionString;
using (SqlConnection con = new SqlConnection(CS))
{
string Command = "Select * from book_upload where Title like @Title";
SqlCommand cmd = new SqlCommand(Command, con);
//Provide the value for the parameter_
61
cmd.Parameters.AddWithValue("@Title", TextBox2.Text + "%");
con.Open();
GridView1.DataSource = cmd.ExecuteReader();
GridView1.DataBind();
}
//}
//else
//{
//}
}
//////
}
}
Code for module search page
using System.Linq;
using System.Web;
using System.Data;
public partial class Web_page_Search : System.Web.UI.Page
{
{
}
{
string CS = ConfigurationManager.ConnectionStrings["ASUCS"].ConnectionString;
using (SqlConnection con = new SqlConnection(CS))
{
string Command = "Select * from Upload_module where Module_Code like
@Module_Code";
SqlCommand cmd = new SqlCommand(Command, con);
//Provide the value for the parameter_
cmd.Parameters.AddWithValue("@Module_Code", TextBox2.Text + "%");
con.Open();
GridView1.DataSource = cmd.ExecuteReader();
GridView1.DataBind();
}
}
{
//try
//{
//if (ddlselec_key.SelectedValue=="Author")
//if (ddlselct_dept.SelectedValue == "IS" && ddlselct_year.SelectedValue == "I")
{
string FileName = TextBox1.Text;
Response.ContentType = "application/octet.stream";
Response.AppendHeader("Content.disposition", "attachiment;FileName=" +
FileName);
62
Response.TransmitFile(Server.MapPath("~/Material/" + FileName));
Response.End();
}
//else
//{
// if (ddlselct_dept.SelectedValue == "IS" && ddlselct_year.SelectedValue ==
"II")
// {
// string FileName = TextBox1.Text;
// Response.ContentType = "application/octet.stream";
// Response.AppendHeader("Content.disposition", "attachiment;FileName=" +
FileName);
// Response.TransmitFile(Server.MapPath("~/Material/" + FileName));
// Response.End();
// }
// //else
// //{
// if (ddlselct_dept.SelectedValue == "IS" && ddlselct_year.SelectedValue ==
"III")
// {
FileName);
// Response.End();
// }
// // else
// // {
// if (ddlselct_dept.SelectedValue == "CS" && ddlselct_year.SelectedValue ==
"I")
// {
FileName);
// Response.End();
// }
//else
//{
FileName);
// Response.TransmitFile(Server.MapPath("~/Resource/CS/II/" + FileName));
// Response.End();
//}
//// }
////}
//else
{
lblMessage.ForeColor = System.Drawing.Color.Red;
lblMessage.Text = "No data found Try again";
}
}
}
//}
63
//catch (Exception)
//{
//}
Code for submitting comments using System;
using System;
using System.Linq;
using System.Web;
using System.Data;
public partial class Web_page_Comment_Us : System.Web.UI.Page
{
{
//lblDatetime.Text = DateTime.Now.ToString();
}
{
TextBox1.Text = "";
TextBox2.Text = "";
TextBox4.Text = "";
TextBox5.Text = "";
TextBox6.Text = "";
}
{
try
{
string CSS =
ConfigurationManager.ConnectionStrings["ASUCS"].ConnectionString;
using (SqlConnection con = new SqlConnection(CSS))
{
SqlCommand cmd = new SqlCommand("spAddComment", con);
cmd.CommandType = System.Data.CommandType.StoredProcedure;
cmd.Parameters.AddWithValue("@First_Name", TextBox1.Text);
cmd.Parameters.AddWithValue("@Last_Name", TextBox2.Text);
cmd.Parameters.AddWithValue("@Subject", TextBox4.Text);
cmd.Parameters.AddWithValue("@Date", TextBox6.Text);
cmd.Parameters.AddWithValue("@Comment", TextBox5.Text);
con.Open();
cmd.ExecuteNonQuery();
Response.Redirect("~/Web page/Admin Login Page/comment warning.aspx");
//lblMessage.ForeColor = System.Drawing.Color.Blue;
//lblMessage.Text = "Comment were sent Succesfully with Name " +
txtName.Text;
}
}
catch (Exception)
{
lblMessage.ForeColor = System.Drawing.Color.Red;
64
lblMessage.Text = "there is unknown problem please try later";
}
}
//protected void Timer2_Tick(object sender, EventArgs e)
//{
// DateTime Datetime = DateTime.Now;
// this.lblDatetime.Text = Datetime.ToString();
//}
}
Code for login System;

using System;
using System.Linq;
using System.Web;
using System.Data;
public partial class Web_page_Login : System.Web.UI.Page
{
SqlConnection con = new SqlConnection(@"Data Source=MULER-PC\\SQLEXPRESS;Initial
Catalog=ASU;Integrated Security=True");
string constr = "Data Source=MULER-PC\\SQLEXPRESS;Initial Catalog=ASU;Integrated

Security=True";
SqlConnection c;
DataRow dr;
SqlDataAdapter da;
DataSet ds;
DataTable t;
DataTable dt;
{
}
{
txtUserName.Text = "" ;
txtPassword.Text = "";
}
{
{
c = new SqlConnection(constr);
c.Open();
da = new SqlDataAdapter("select * from account_admin where User_Name='" +
txtUserName.Text + "' AND Password='" + txtPassword.Text + "'", c);
ds = new DataSet();
da.Fill(ds, "ASU");
dt = ds.Tables[0];
if (dt.Rows.Count > 0)
{
Session["un"] = txtUserName.Text;
65
Response.Redirect("~/Web page/Admin Login Page/admin page.aspx");
}
else
{
Response.Redirect("~/Web Page/Admin Login Page/warning.aspx");

//lblMessage.Text = "Invalid User Name and/or Passord is inputed.";
//lblMessage.ForeColor = System.Drawing.Color.Red;
}
c.Close();
}
}
}
Code for Admin create account page

using System;
using System.Linq;
using System.Web;
using System.Data;
public partial class Web_page_Admin_Login_Page_Create_Account : System.Web.UI.Page
{
{
//if (!IsPostBack)
//{
// Panel10.Visible = false;
// //GridView2.Visible = false;
// //GridView6.Visible = false;
//}
}
protected void ImageButton7_Click(object sender, ImageClickEventArgs e)
{
//if (GridView6.Visible)
//{
// GridView6.Visible = false;
//}
//else
//{
// GridView6.Visible = true;
//}
}
{
//if (GridView2.Visible)
//{
// GridView2.Visible = false;
//}
//else
//{
66
// GridView2.Visible = true;
//}
}
//protected void ImageButton8_Click(object sender, ImageClickEventArgs e)
//{
// if (Panel10.Visible)
// {
// Panel10.Visible = false;
// }
// else
// {
// Panel10.Visible = true;
// }
//}
{
try
{
string CSS =
ConfigurationManager.ConnectionStrings["ASUCS"].ConnectionString;
using (SqlConnection con = new SqlConnection(CSS))
{
SqlCommand cmd = new SqlCommand("spAddcreate_account", con);
cmd.CommandType = System.Data.CommandType.StoredProcedure;
cmd.Parameters.AddWithValue("@Fname", TextBox1.Text);
cmd.Parameters.AddWithValue("@Lname", TextBox2.Text);
cmd.Parameters.AddWithValue("@UserName", txtUserName.Text);
cmd.Parameters.AddWithValue("@Password", txtPassword.Text);
cmd.Parameters.AddWithValue("@Confirm_Password", txtRetype.Text);
cmd.Parameters.AddWithValue("@Sex", DropDownList1.SelectedValue);
con.Open();
cmd.ExecuteNonQuery();
Response.Redirect("~/Web Page/Admin Login Page/Account warning.aspx");
//lblResult.ForeColor = System.Drawing.Color.Blue;
//lblResult.Text = "Instructor account Created Succesfully with User
First Name " + TextBox1.Text;
}
}
catch (Exception)
{
lblResult.ForeColor = System.Drawing.Color.Red;
lblResult.Text = "there is unknown problem please try later";
}
}
{
TextBox1.Text = "";
TextBox2.Text = "";
txtUserName.Text = "";
txtPassword.Text = "";
txtRetype.Text = "";
DropDownList1.SelectedValue = "Select Sex";
}
{
67
}
68

Final Doc't For Group 999999

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Final Doc't For Group 999999

Uploaded by

Copyright:

Available Formats

ASSOSA UNIVERSITY

FACULITY OF ENGINEERING AND

DEPARTMENT OF INFORMATION SCIENCE

Title: Digital Library System for Faculty of

Student Name Student ID

1. Birhanu Kirosse ETR/ 804 /06

This Project is submitted to the Faculty of Engineering and Technology, Department of

This project entitled “Digital Library System for Faculty of

Hambisa.M _____________ _____________

Name Signature Date

Zebene.H _____________ _____________

List of Figures ...............................................................................................................................VI

Project Design and Methodology...............................................................................................10

ARPA: Advanced Research Projects Agency.

ALA: American Library Association.

ASU: Assosa University.

CSS: Cascading Style Sheet.

CCTA: Central Computer Telecommunications.

DFD: Data Flow Diagram.

DL: Digital Library.

ERM: Entity Relation Model.

FETASU: Faculty of Engineering and Technology Assosa University.

Html: Hyper Text Markup Language.

NASA: National Aeronautics and Space Administration.

NGO: Non-Governmental Organization.

NSF: National Science Foundation.

OPAC: Online Public Access Catalogue.

RDBMS: Relational Database Management System.

SQL: Structural Query Language.

T-SQL: Transact Structural Query Language.

UNESCO: United Nations Educational, Scientific and Cultural.

US: United States.

Figure 3.1. Major DFD components...........................................................................................21

1.2. Statement of the problem

1.3. Objectives of the study

1.3.2. Specific objectives

The specific objective of this project is:

To design a system that security the materials.

1.4. The scope of the project

1. Shortage of time will be one of the influential factors.

5. Shortage of labor potential to organize the overwhelming dispersed information and

1.5. Significant of the study

System:-A set of detailed methods, procedures, and routines established or formulated to carry

Computerized: -Refers to control, perform, processor and store (system, operation or

A library is an organized collection of information resources made accessible to a defined

2.2. Types of Library

2.2.3. Special Libraries

2.2.4. Electronic Library

2.3. Related works

2.3.1. Secure the materials

2.3.3. Reduces wastage of the Users time

2.3.4. Increasing the accessibility of the book in the library

Project Design and Methodology

3.1. Description of Study Area

3.2. Data Collection Methods

 Investigate sensitive issues.

3.3.2. Secondary Data

3.4.1. Existing system

3.4.1.2. Problems in the existing system

3.4.2. Proposed System

The new Investigated systems have the following advantages:

3.4.3. Functional Requirements

3.4.4. Non Functional Requirement

Hambisa.M _ _

Zebene.H _ _