Chapter One

1.0Project Proposal

1.0 INTRODUCTION
Today’s practice of medicine is extremely information-intensive. Health science professionals
depend heavily on access to varied information resources to make intelligent and informed
choices for education, patient care management and research protocols (Davis, 1987).
Libraries and librarians who serve medical clients face a paradox. Health science disciplines are
highly specialized, yet users need a broad, multi-disciplinary approach. Information and know-
ledge continue to grow exponentially, but the purchasing power of resource collections have
decreased. Library collection growth has stabilized, user information demands have escalated.
Library measures to maintain self-sufficiency are laudable, but unrealistic goals (Broer-ing,
1986).
Several authors have addressed these contradictions and have concluded that the solution for
libraries and users lies in building and strengthening networks and engaging in resource sharing
projects. In 1975, de Gennaro suggested that the emphasis for libraries should shift from
holdings (storing) and size to access and services. At that time, he predicted that computer
technology would have its greatest payoff for libraries as a tool to assist librarians in developing
and operating networks and other mechanisms for resource sharing (De Gennaro, 1975).
Similarly, Kronick (1982) reached the conclusion that libraries can no longer afford self-
sufficiency and he suggested that a more attainable goal is "mutual sufficiency" (Kronick, 1982).
The growing resource sharing trend of the 1970s and 1980s, which is even more feasible today
through high performance computers and networks, is bound to become an essential part of
library operations in the 1990s.

1.1 Problem statement

The project implications and significance are profound in potentially changing the library service
paradigm and shaping delivery of information in the future. Unique project features are use of
Internet not only to access other library catalogs, but to have a central menu of LIS databases
with transparent transfer capabilities to whatever data-base a user chooses regardless of

1
geographic location. Automatic online access to document delivery directly from a literature
search is provided from different library systems, Current Contents, Bioethicsline and the
OPACs. An innovative milestone under development is the search and display of images through
the online catalog. Users will navigate easily, unaware of the underlying technical complexities.
Another significant milestone is the development of a Library Management Information System
(LMIS) to allow the FLIS libraries to organize data efficiently, improve their reports and
complete national library association.

1.2 Problem solution

Library Information System (LIS) Resource Sharing Project to provide electronic access and
delivery of information in various print and non-print formats and in varying formats to a
consortium of libraries that all use the LIS and through this advanced system, improve medical
education, research , patient care and the academicians. The project design include a
collaborative network of databases, document delivery, digitized images and an information
management system to extend services to LIS user libraries.

1.3 Specific objectives

There are four project objectives:

 Create Internet Access to Share Databases;

 Accelerate Transmission of Documents to Users;
 Provide OPAC Access to Digitized Images;
 Generate Outcomes and Evaluations by developing a Library Management
Information System (LMIS).

1.4 Significance of the system

To improve medical education, research, patient care and the academic by expanding the Library
Information System (LIS), an integrated system, used by over 40 medical libraries.

To enhance access to and delivery of information by providing LIS member libraries and their
users with access to the collective resources and information formats.

2
1.5 Beneficially of the system

The beneficially of the project are the library users like health institutions, research institutions
,the academic institutions and the academicians and even other government agencies like the law
society of Kenya, Kenya land survey authority, Kenya resource management institutions and
other agencies which need information in their day to day activities.

1.6 Literature review

1.6 Purpose

The purpose of literature review was to establish the potential topics and suggest ideas for
another research, reporting published materials on existing conceptual framework, theories,
techniques, processes, styles and instruments of other researchers related to the topic under
investigation. At the same time to identify why some of the literature was noteworthy and which
literature had made important theoretical contributions to the field being studied (Anderson and
Kanuka, 2003). It helped align our scope of study and in determining the various variables to be
included. As for this research, the main purpose of literature review was to grasp comprehensive
ideas on the extent of library information initiatives and projects that had taken place worldwide
and the factors and conditions that had influenced and contributed to their success.

1.6.1Minimedline

Automatic online access to document delivery directly from a literature search is provided from
minimedline, Current Contents, Bioethics line and the OPACs. An innovative milestone under
development is the search and display of images through the online catalog. Users will navigate
easily, unaware of the underlying technical complexities. Another significant milestone is the
development of a Library Management Information System (LMIS) to allow the LIS libraries to
organize data efficiently, improve their reports and complete national library association.

3
1.6.2The Dahlgren Memorial Library

At Georgetown University, for example, the Dahlgren Memorial Library has undertaken the task
of developing a Knowledge Network that provides access to a family of bibliographic,
information, diagnostic and research databases. The strategy was developed in 1985 as part of a
multi-phasic, ten year project supported by the National Library of Medicine (NLM) to plan,
develop and implement an Integrated Academic Information Management System (IAIMS). It
has further enhanced cooperative endeavors with the medical libraries that use the Georgetown
Library Information System (LIS). Collaborations with these institutions began in the mid-1980s
and have increased rapidly since 1990. Some of the most notable features are the Dahlgren
Library’s ability to design functional models for the integrated LIS, to develop educational
software that integrates print and non-print materials, and to expand the IAIMS Knowledge
Network of health sciences databases. Through the IAIMS network, users at Georgetown are
also linked to other university resources including the collections of all campus libraries (law,
medical and main campus). The two paths of LIS and IAIMS have served to expand the library’s
traditional role in information management and now places it in a position to explore even
further (Broering 1988; Broering, 1985).

1.7 RESEARCH METHODOLOGIES

1.7.1Approach to Literature Review

The approach to literature review was the browse method where print and electronic sources
were looked at, read and digested, looking for some relevancy, appropriateness and usefulness of
the topic at hand. Browsing the printed materials – books, periodicals, journals, conference
papers, annual reports, newsletter, newspapers and theses, would strengthen and reinforce the
researcher’s foundation of the subject matter. The use of information retrieval tools such as
OPAC, abstracts, indexes and bibliographies allowed greater insight of the subject in a more
organized manner. Amongthe online databases and e-journals searched were LISA, Emerald,
Ebsco Host, D-Lib Magazine, Libri, Ariadne and the websites/homepages of many foreign
digital libraries.

4
Predetermined keywords used during the search were digital library, virtual library, e-library,
hybrid library, digital library initiatives, digital library problems, digital library research, digital
services, digital reference, resource sharing, distributed information resources, Intellectual
Property Rights, digitization, online databases, dematerialization, born digital materials,
information surrogates, digital objects, information revolution, library automation, library
systems, hybrid library, cyberian, information professionals, digital librarian, global access,
repositories and interoperability. As the research involved qualitative data as well, the researcher
made a lot of efforts at the initial stage of the research making enquiries to get as much primary
data as possible from as many librarians as possible whenever there were opportunities, to
understand the subject better and helped in the formulation of the research questions.

1.8 General description

1.8 Product perspectives

The library information system will incorporate a platform independent software application
system, an interactive graphical user interface (GUI) and a database to store and enable easier
and faster access to staff and library users for them to get access to the information they want.

1.8.0 Product functions

The LIS aims to assist the library users to effectively get access to different information and
knowledge from their comfort of their own house or office by the use of internet enabled
devices;
 Providing information to all library users without necessarily getting to the library
building.
 To reduce plagiarism and enact the law of patent and copyright.
 To improve security to people’s work and help to pass information to millions of library
users
 To act as an archive for crucial information which may be prone to a lot of risks like fire
and any natural disaster.
5
1.8.1 User characteristics
Due to the presences of input and output process the user of the system will be directly
communicating through the use of keyboard and mouse. This will also provide some help to the
user in case of any problem the system will attempt to provide all the relevant information.
The system will be able to provide various error messages in case of some unrecognized
information fed to the system.

1.8.2Assumptions
The system assumption relate to the requirements here are:
 The system is not supposed to exceed the stated budget since this may lead to omissions
of some necessary requirements that are stated in this project.
 The system will be fully integrated with the database and then the system will be a web
based.

1.9 Specific requirement

1.9 Functional requirements

The system will support various processes and function in library. It will interactwith the userto
facilitate its functionality. The user will be required to log in into the system by providing a
username and user password, once logged in the user will then be in a position to proceed with
whatever they want to do. Hence the system will have a good and friendly interaction with the
user through the interactive graphical user interface

1.9.0 System requirement

The following will be needed in order to complete this project:
1. Software requirements
 Windows Operating System Windows 7/Linux/mac os

6
  Wampserver
 MySQL
 Antivirus
 Browser
2. Minimum Hardware requirements
 Pentium IV 2.0 GHz or compatible.
 4GB RAM (Minimum) 8GB RAM (Recommended).
 500GB Hard disk for storage.
 1TB external hard disk for back up.

1.9.1Non-functional requirement

This describes the non-functional requirements that characterize the function of the software
product:

1.9.2 Security
Security is always an issue with the implementation of the systems. Currently the security of
patent and copyrighted information is enforced by the server administrator on a central sever.
This means that the admin has to be taken through the security feature of the system.
Security of library user’s usernames and passwords will be hashed such that even the system
admin cannot reverse the password to retrieve the user credentials.
The system will provide enhanced security for the library and information through the use of
access code and passwords that will limit access and it will help to curb piracy or plagilism.

1.9.3 Reliability
The system will provide accurate, correct and reliable outputs that will meet the user’s
requirements and enable library user to get access to different information within the same site.
And since the application can help one to make a limited print out of given information which
can either be soft copy or hard copy.

7
1.9.4 Maintainability
New arrivals can be added to the system to update the information, the system can also be
updated and even when errors are encountered the system can be maintainable.

1.9.5 Portability
The system should be the one which is compatible with other machines not the one which is
machine independent and also the system can be run in any platform and can use different
browser soft wares available.

1.9.6 Project schedule

Task Description duration Expected Expected Deliverables
start date finish date
1 Coming up 1week 5/05/15 9/05/15 Approved idea
with the idea
and sharing it

8
 with the
supervisor
2 Write the 1day 10/05/15 10/05/15 Project
project proposal
proposal document
document
3 Prepare slides 1day 11/05/15 11/05/15 Complete
for project proposal
proposal document
presentation
4 Project 1 day 12/05/15 12/05/15 Project
proposal proposal
presentation presentation
5 Correction of 2weeks 13/05/15 26/05/15 Project
the error found proposal
during project
proposal
presentation
6 System 4weeks 27/05/15 24/6/15 System
analysis and requirements
preparation of specification
system document
requirements
specification
document
7 System design 4weeks 25/6/15 22/7/15 System design
1.Logical specification
design document
2.Physical
design
8 Progress 1day 23/7/15 23/7/15 Progress report

9
 presentation
9 Coding 4weeks 24/7/15 20/8/15 Progress
report
10 Testing 2week 21/8/15 3/9/15 system
11 implementatio 4week 4/9/15 1/10/15
n
12 documentation 4week 2/10/15 29/10/15 Project
documentation
13 final project 1day 30/10/15 3/10/15 Complete
presentation functional
project

1.9.7Budget
The estimated cost of the project is as follows;

Quantity Amount Description

1 Computer (pc) 20,000
Miscellaneous 2000
2 Software’s 2500
1 Printer 15,000
4 Stationery 1000
1 Printing/photocopying 1000
Total 46,000

Chapter Two

2.0 System requirement specification

2.0 Introduction
The software requirement specification (SRS) is basically a designers understanding (in
writing) of a customer’s or potential client's system requirements and dependencies at a

10
particular point in time prior to any actual design or development work. It's a two-way insurance
policy that assures that both the client and the software designer understand the other's
requirements from that perspective at a given point in time.

SRS is a document that describes all the data, functions and behavioral requirements of the
software under development. It forms a foundation on which the design and implementation of
the system becomes easy.

The system requirement specification is an abstract description of the services that the system is
intended to provide and the constraints under which it must operate. This document outlines the
specifications such as scope of the document, the designer’s view of the client’s need and
requirements just before the actual system design. It is a landmark to indicate that both the users
and the designers are in agreement

2.0.1Purpose
The main and major purpose of this document is to serve as a guide to the developers of the
library information system on how to develop a system which will meet the needs of the users
and to meet the system objectives. SRS helps developers in the following ways:

 Develop an information system that will enable users to get the information about new
information books, journals from different writers and authors who have done extensive
research on various areas of study.
 The system also provides a platform for updating of information of different users who
have subscribed to the system to get information about new arrivals for the users to
check them in the system and get to know the information; also new users can be
registered to the services offered by LIS.
 The LIS will have portal for e-learning which can enable users to download some
section of the book to curb plagiarism for the copyrighted books and journals and also
can buy an electronic book from author.
 It includes information which sets the scope size and complexity of the final system
 It drives the system architecture testing activities and overall system design
 It creates a flow of events during the development of the system that is to say it lays
down the schedule on how activities will be performed an activity will be fully finished

11
 before moving to next activity.

2.0.2 The intended audience includes:

The audience of this document include the system developers who will use this document to
develop the system that will meet the need for the users and be developed within the stipulated
time, requirements and the budget to ensure that the system is valid and verified within the
requirements the system developer uses this document as the authority on designing and building
system capabilities. The other audience is the users who will review the document to ensure that
their system needs are met and that the system is valid to do what the system is intended to do.
This document is also intended to open the market for the authors therefore they are also the
audience since they can also sell their work to the owners of the system to be used to give
information to the subscribers this can also act as the platform to do marketing to the authors.
This document is therefore supposed to give the clear guidelines to the system developer on what
the system will do and the system functionality.

The other intended audience for this specification is:

 Project manager: analyzes designs and implement the system according to the user’s
specification
 Designer: the designer will translate the requirements to graphical or logical
representation of knowledge.
 System developer: to record the progress in developing the system goals and the steps
taken to develop the system.
 System testers: it will act like a check list once development of the system is completed
and confirm if the user requirements and the functional requirement are achieved.
 System administrator: will use the system to make any required update to the system to
ensure that there is no loss of data.
 Supervisor will use the new system to assess and update record s to repair and mainatain
the system.

12
  Database administrator: monitor and check the system to ensure that it works properly so
as to meet the users’ requirements and also work to ensure that the necessary standards
are enforced

2.0.3PROJECT SCOPE
The project application and significance are profound in potentially changing the library service
paradigm and shaping delivery of information in the future . unique project features are use of
internet not only to access other libraries catalogs, but also to have a central menu of LIS
databases with transparent transfer capabilities to whatever database user chooses regardless of
geographical location. Automatic online access to document delivery directly from a literature
search is provided from different library systems, current contents, Bioethics line and the
OPACs. An innovative milestone under development is the search and display of images through
the online catalog. Users will navigate easily, unaware of the underlying technical complexities.
Another significant milestone is the development of library management information system
(LMIS) to allow the FLIS libraries to organize data efficiently, improve their reports and
complete national library association. This document defines at a functional level the business
activities that are encompassed by the system and the rules that apply to the. It also encompasses
some of the key high level technical requirements of the system required by intended users.

2.0.4 Product features

The system will be made up of two parts client application to allow users access and interact
with the system through a graphical user interface and back end database.

It will be for general purposes such as data capture by data entry, entering data captured on
relevant forms. The captured data will be processed and stored in a database hosted in central
server. Then data will be output in form web pages .the users log in to the system through an
interface. On successful authentication through login username and password this user will get
access to the system and do any transaction privileged to him/her by the system administrator.
The new user to the system will be needed to create a profile with the system to be granted the
privilege to access to the system and for the diverse end users can access, search, analyze and
report various types of integrated data based on access rights.

13
2.0.5 Description and priority
The library information system should be stable and secured, have high performance (in terms of
speed and efficiency/effectiveness), and be easy to maintain .this component is central to the
effort and is thus of highest priority. The other thing is to make the system very first in
displaying information either in soft copy and hardcopy where by printing may be required also
it will enable users to download documents in different formats and also to view the documents
in different formats in different platforms without any compatibility issues.

2.0.6 Use case scenario

The team will elicit user requirements from a cross-section of user class members to accurately
and completely describe the expected users and functionality of the system. To elicit
requirements, the user class members will be asked via, interviews and email to provide a
detailed description of the user actions and system responses the will take place during execution
of the use case under normal ,expected conditions .the summation of responses will lead to an
accurate and complete inventory of user requirements.

Gallery
Library facilities

OPAC
Log in Home page

user About us
Log out

14
A user with the profile or account the system can go directly to log in and enter the valid
username and password to get access to the system and the he/she can access the page she/he
wants to access the use case above has got other sub groups of pages which are directly linked
with other use cases.

If a user is a new user who doesn’t have account with the system then he/she is required to create
an account so as to get full access to the system the use case for creating an account is shown
below.

Gallery
Library facilities

OPAC
Sign up Log in Home page

user
About us

Log out

15
2.0.7 User characteristics:
The user classes of this library information system will be;

a) System administrators: staff responsible for managing the system by creating users,
assigning rights and have full read and write rights to viewing users’ activities .and also
to grant and revoke privileges to different users for security purposes.
b) Database administrator: maintenance with read/write/modify privileges to all data in
the servers to enable him make system backup to make the system hide the fact that it has
encountered the error to make updates to the database that is if there is new arrivals of
books journals and other information books which can be accessed via the internet using
the LIS.
c) Support staff: require technical skills on troubleshooting and assisting users when they
encounter a problem and also to guide users on step by step to overcome the problem
they encountered .this would likely be conversant with the general characteristics of
system, the user should be familiar with the following:
 Working on a graphical user interface.
 Searching the required information.
 Downloading given information.
 Printing a section of a book.
 To help users to troubleshoot their users’ accounts when they get a problem while
logging in.
d) System maintainers: the people in charge of maintaining the system will also need access
to the system. This is because some of the problems that will be encountered won’t
necessary need to be reformatted or the editing of code

2.1 Operating environment

The application will be designed to run on windows and Linux platform. With the following
specs a 2.5GHZ processor speed ,4.0GB RAB the platform where the application will run shall
have browsers the application is not browser dependent therefore it means the application can be

16
executed in any browsers like internet explorer ;Mozilla Firefox; Google chrome; tor browser
and even opera mini for windows .

Note that the application can function on other lower specifications than these but for the
purpose of being in line with the current technology, will have to go with the identified
specifications in the document. The system will be based on network setup and through this; it
will ensure different units to be integrated with the central database without remodeling the
entire database. This therefore implies that there must be a central server that holds this
information and that there can only be update to the server other than creating pieces of
information on different computers. The application will again ensure that there is a simple
interface that allows the users to interact with it without much complexity.

2.2 Hardware requirement:

 2GB Ram
 2.5 GHz processor speed
 500Gb Hard disk

2.3 Software requirements:

 UNIX
 Windows operating system
 Antivirus program to protect the application from virus attack
 Microsoft reporting services to support generation of both pre-defined reports
 WampServer
 Browser
 php

2.4 Hardware requirements

2.4 Storage
The system needs to be able to store hundreds of megabytes of data on demand. The potential
for needing gigabytes of data storage capacity is also in the realm of possibilities. Further

17
requirements gathering is needed to get real-world estimates of such data storage needs. Since it
is a web based application a storage capacity will be needed to store the cookies for more than a
week to get the real number of the application users and also to capture the most visited books
and also the most downloaded book.

2.4.0Networking
Load balancing- database servers must be load balanced at the application level to ensure
maximum stability and availability. Specific scenarios, such as fail-over versus session-managed
load balancing need to be addressed in the functional requirements specification.

2.4.1 Private network

The system requires a “back-end” private network environment in order to ensure that end-user
operations (on the front-end) are not implemented by database. Backups, index propagations, or
other large back-end data transfer

2.5 Software requirements

2.5Backup software
Data and application backups will be through fully supported backup software solutions.

2.5.0Database management system

As the primary data storage mechanisms, SQL anywhere 9 servers will be required to support
system functionality.

2.5.1 Populating data

Available data will be reformatted to be compatible with the system’s schema and modeling
requirements. Data to be used in modeling that does not conform to model requirements will be
processed in for inclusion in the system’s databases

18
2.5.2 Scope and limitations
Analysis methodology will involve business analysis, requirement analysis, data analysis, and
process analysis and application architecture:

 Requirement analysis- system I/O description, user requirement definition, functional and
security
 Data analysis- involves data collection process, data validation, data storage,
manipulation and retrieval.
 Process analysis – data/process flow analysis, process decomposition and system
interfaces
 Application architecture- analyzes application information structure, usability, user
interface design.
 Interaction and application implementation.
The system architecture of the system can be described as a set of integrated applications. The
application architecture consists of a number of application components that, working together
meet the requirements for the system’s application.

The system solution will be built using the PHP and MYSQL in order to create the integrated
platform to a single system.

Integrated platform will be created using the following products:

 Microsoft windows server 2007 operating system

 SQL server
Functional requirements

System analysis and requirements specification perform an analysis of the problem using object
oriented techniques

An external view of the model including records, subscriber information, and class schedules
will be developed. This system requirement specifications document will form part of the
documentation for the project.

Some desired features of the new system include:

19
  The ability to search/view processes as desired
 Provide report generation platform
This section of the SRS specifies the functional requirements of the system in terms of use cases
and their associated use case paths. The use case model is primarily organized in terms of the
externals that benefit from the use cases.

2.6 Operational requirements

2.6 Application services and technical support

Programmers and application developers will have access to source code to address bugs or
system enhancements as deemed necessary. Database administration support is also required to
maintain the system.

2.6.0 Administration features

System security and access levels are provided in the system. There are varying levels of system
access and functional authority. Each user access is limited to their class. Only authorized system
administrator(s) has access to all system resource.

2.6.1 System hardware fails over and routine backup

Computer operations center will handle system hardware tasks such as data tape back-up,
hardware maintenance, fail over, scheduled system patches and maintenance.

2.6.2Process requirements
The following are among the inherent requirements that the system must be able to handle.

i) Transaction –the system must be able to send , receive and trigger transaction to the
database system
ii) Data integrity- commit transactions that are completed and/or rollback unfinished or
time-out transaction

20
 iii) Data validation- data error from the user’s end and from the back-end database
processing end must be gratefully handled.
iv) Performance- must resolve locking issues and handle concurrent use of the system
throughout .send, receive and display user messages to assit the over-all user
experience.

2.7 Non functional requirement

These are the needs the application will have to meet to be able to function properly in its
operational domain of application.

2.7.0 Performance requirements

2.7.1 Response time:

The data system shall show no visible deterioration in response time as the number of users
increases. Response time s seen by end users for querying metadata should be on the order of a
few seconds or less.

2.7.2 Loading speed:

The data system shall load as quickly as comparable productivity tools on whatever environment
it is running in.

2.7.3 Throughput:
Throughput refers to transactions per second (tps). As it is difficult to calculate the throughput in
terms of transaction per sec, it is expected that the system should be able to support maximum
throughput for the booking processes

2.7.4 Reliability and availability requirements

The reliability of the system is directly linked to the level of update of the documents to which it
is corrected. The system must be updated constantly according to the necessities of the users.
Both the database will have to be available on demand.

21
2.7.5 Robustness or fault tolerance requirements
When the system is disconnected or frozen due to over access at the same time, it should save all
the process of the users have made up to the point of abnormal happenings. It should also ensure
that the system continues even after user has encountered an error.

2.7.6 Capacity requirements

The system should be able to manage all the information incoming from the database and the
catalogue.

2.7.7 Safety requirements

Data on the server should be protected from power loss and data in transit from server to
requester should not be lost.

2.7.8 Security requirements

The system will have reasonable controls consistent with best practices. Security requirements
will have four primary components. They are authentication, confidentiality, integrity and
availability.

2.7.9 Authentication
The system will follow industry best practices for authentication, using single –sign-on systems
like. Authentication addresses security requirements to ensure those using system are who they
say they are. This is of greatest concern when data are being changed or updated .this is
primarily done through password.

2.7.0.1 Confidentiality
Confidentiality security requirements describe the need to protect the data appropriately. The
system will use the user classes to define boundaries of information sharing to ensure
confidentiality as appropriate. Any date should be viewed by a restricted audience must be
protected with appropriate security features.

2.7.0.2 Data integrity

The integrity of the system’s data will be critical to its success as a product. Scientific research
and publications will be based on the data obtained through the system. Therefore, extensive data
validation and review will be performed both before data are added to the system and as part of

22
the adding process. The system will need policy and procedures protecting the data from
intentional or unintentional modifications, and to ensure accurate data are made available.

2.7.0.3 Availability
The system must be available to the intended audience on demand, with 99% availability and a
tolerance of -5%(not less than 50% of working hours in any week) .for this system ,availability
will be concerned with the reliability of the software and network components. Intentional
“denial of service attacks “is not foreseen as a significant concern.

2.8 Software quality attribute

2.8Portability
This database will be built for a particular system and may not be portable but results to queries
will be portable between many environments

2.8.0 Adaptability
Implementation of the application software/code and design of database structure should be
flexible enough for the necessary change in the later phase.

2.8.1Availability
Availability is defined here to mean the ability to use the system during its intended period of
operation.

2.8.2 Reliability
 appropriate validations and intimation to users on any abnormal inputs/situations
 Consistency of data to be maintained
 Conformation should be taken from the user before deleting any record.

2.8.3Maintainability
 Administrator manual and user manual to be provided.

23
  The system should be maintainable over a period of time. This implies that proper coding
standards and naming conventions are followed: design should be according to proper
standards.

2.8.4 Usability
Usability includes looking at, capturing and starting requirements based around user interface
issues things such as accessibility, interface aesthetics and consistency within the user interface.

2.8.5 Ease of use

The user should be able to perform operations desired quickly without having to navigate
through multiple forms no operation should require more than 3 to 4 clicks.

2.8.6 Efficient
The system should be efficient. This is measured by the time taken to do an operation fully
through the system.

2.8.7 Familiarity
The system’s interfaces and navigations should be based on other systems that the users are
familiar with and like.

2.9 Design and implementation constraints

Developing the application will not be seen as a walk in the park, but is also associated with
several problems as discussed below:

2.9.0Time
Due to the urgency to bring into completion the proposed system, I as the developer will be
forced to develop and implement the system in a period of six months. This does not only take
the six months to develop the application only but also I will be having other subjects that need
to be covered and examined during the six months period.

2.9.1 Portability
Currently there is a trend of moving towards Linux and open source platforms for security
purposes and also the fact that open source products are free. The proposed system being
implemented in a windows platform may pose a problem in case the company wanted to migrate
to Linux or open source platform.

24
2.9.2 Equipment
More equipment will have to be bought to cater for the development of the system and also
because of the amounts of information that will need to be backed up from the system e.g. flash
disks or external hard disks, printers, CD diskettes to act as a permanent storage space for the
already finished documents e.g. the proposal document.

2.9.3 Implementation constraint

The system is supposed to have a pilot runs on multiple environments but this may not be
applicable since there is a single environment that may not be able to test the system as expected.

2.9.4 Client resistance

Once the proposed system is fully implemented, some clients will try very much to oppose the
application due to the fear of being brought to the lime light as non-product full.

25
Chapter three

System design specification

3.0 Introduction

3.0 Purpose of the Document

This is the Software Design Specification (SDS) for the Library Information System (LIS). The
SDS will break down the project into components to describe in detail what the purpose of each
component is and how it will be implemented. The SDS will also serve as a tool for verification
and validation of the final product.

3.0.1 Scope of the Development Project

The scope of the Library Information System includes its distinct features, its benefits, and its
limitations. The system's distinct features allow it to disseminate information regarding to the
need of the subscriber and also the authors can use the platform to advertise their new books to
different users of the system, registering new system users by signing up with the system .The
system enables the users to open the book they want online and read without downloading and if
the users want the information contained in a book to be stored in his personal computer or smart
phone or tablet they can download the book by just a click of a button.. The users who can wish
to read a book online there is a module which will be linking the users to read the books online
and this can be achieved through the OPAC (online public access catalog) this option can allow
the subscribers to print some sections or pages of a book in different formats and also anybody
who has an important information to share with the rest of the world can share it by uploading it
to the system and different subscribers can access it.

26
3.0.2 Definitions, Acronyms, and Abbreviations
Term Definition

API Application Program Interface. An API is a method by which an

application program (a complete program that performs a specific
function directly for the user) can access the computer's operating
system.

SRS Software Requirements Specification, this document which outlines

the

Requirements that the software must fulfill. Entirely design

independent.

GUI Graphical User Interface. The GUI provides a graphical interface for
users to interact with the system.

Link A link is a means of connection between screens. Note: This is not

short for “Hyperlink.”

PDA Personal Digital Assistant. A PDA is a small, portable, computer-like

device that can run software applications.

SDK Software Development Kit. A set of programs that allows software

developers to create products to run on a particular platform or to
work with an API.

27
Synchronization Synchronization is the act of connecting the Personal Digital
Assistant to a computer, using a special device called a docking
station, whereby the information in both the PDA and the computer
become identical.

Client Any person who uses the system, with the general case being the any
computer device that is requesting for service from the server

Administrator A person who has administrative privilege/access to the system.

Subscriber Any customer who registers with this system to get access to the
information offered by it.

Main Menu Page the initial menu which allow users to register/login

Home Page The initial menu for users who have logged in successfully. It’s also
called the home page.

Registration Page The page that allows the user to create new accounts.

Login Page the page that allows the user to login if they have a valid login

3.0.3 Design consideration and Constraints

The system will allow Processing to be done in line with other MS Office applications. There
must be networking. And the Server will run 2.4GHz, 2GB RAM, 1TB hard-disk space. This
system is designed to run in any internet browsers and also it can run in any operating system
that is to say it can be executed in Linux, windos, mac os, android and even windows phone. The
system needs large storage capacity since it will store books inform of textual, graphical and
audio visual that is what normally called tutorials.

3.0.4 Assumptions and Dependencies

This design of the Library information System makes several assumptions about software and
hardware, and has several software dependencies. All environmental requirements of both the
server and client applications can be found in the Library information System
Requirements.Both the server and client applications make the following assumptions about their
environmental environments;

28
  The system can be described by the environmental requirements associated to this
document.
 The system the application is executing on will have the required resources available
as necessary. This entails sufficient memory and permanent storage space, an
adequate CPU for the necessary application, and a TCP/IP network connection.
The client application makes the following assumptions about its operation environment;

 The client machine will have wamp server installed, , PHP scripting language, CSS
(cascading style sheet) The client application is dependent on this set of component.
These components are required for our implementation of access to the dialog
database.
 The client machine will have the necessary databases setup through Msql database
server embedded on it.
The server application makes the following assumptions about its operation environment;

 The client machine will have wamp server installed, , PHP scripting language, CSS
(cascading style sheet) The client application is dependent on this set of component.
These components are required for our implementation of access to the dialog
database.
 The client machine will have the necessary databases setup through Msql database
server embedded on it.
 Preferably the server machine will have TCP ports free for use of the server
application. This is the default port for the server to listen on, though it is not
required to listen on this port.

3.0.5 Goals and Guidelines

The main goals governing this system software include:-

29
  The Library information server is intended to have a simple interface that is relatively
easy to administer. A minimal yet complete set of options is provided for the server
administrator to have control of resources consumed by the server application. These
options include, but are not limited to; controlling the limit of clients able to connect to
the server for maximum efficiency, ability to configure which port the server listens on,
ability to change the Library information database location, and control how often the
database is updated.
 Another major goal of the application is that the user gets a response in a timely fashion.
Intuition tells that a user will lose interest if they have to wait long times for software to
respond. This is why the design has minimal data transferred between client and server.
In this design, a minimum set of information is transferred to the server in order to
retrieve the necessary information, and the server only returns the requested data that is
then formatted into a readable phrase on the client side.
The other goals include:
 To come up with the Database design
 To run on Supported browsers
 Be Simplicity
 To Speed and memory load
 To be scalable
 To be reliable
 portability

3.1Design methodology
It will be worthwhile to state here that the waterfall approach will be used. I intend to deliver the
first model at the end of the first month from the date when the requirement details shall be
submitted.

In waterfall model

 I want the users to give their opinions about what they want the system to do or behave.

 To give users time to learn and understand the cognitive methods aligned to the system
that is to say how to use and interact with the system.

30
3.2 System Architecture Description

3.2.0 Architectural constraints

Being the system information distribution system, the system will rely on networking structure
whereby client, processor and the server are interconnected together using networking
technologies and the transfer of information will be following a given underlying protocol and
standards so that the system can meet the laid down standards and for the users to get good
quality of services.

3.2.1 Design Specifications

Server

The Library information System sever is an active machine interacting with the system users.
The interface user registration and authentication, selects the client, uploading of information,
updating the system functionality.

Client

The client runs on the user machines. It sends message to the main server and gets feedback
according to the purpose it requires; through this the system is updated. The client starts by
looking for a match of entered subscribers username and password. All this is achieved through
communication between client and the server which is achieved through use of communication
protocols via networking interface.

3.2.2Architectural design
The system consists of three major levels:

1 The application level

2 The processor level
3 The database level

31
 3.2.3The application level
The application level is the client application. Is designed to support the following major
features; a simple and intuitive graphical user interface (GUI), easy to understand dialogs,
flexible dialog structure support, and support of an internet transport for subscribers information
retrieval. Unlike the server application, the client application has been designed completely data
independent. No portion of the client application is implementation dependent (excluding dialog
database access). This provides maximal flexibility for other potential uses for the client
application.

3.2.4The processor level

The processor level deals with the processing of the information requested by the user the
process level will convert the information to the format that the user can understand and in the
way their devices can understand using different device application.

3.2.5The database level

Is also called the server. The server application’s major design considerations include easy book
retrieval, easy database updates, multiple client support, and a minimal set of administrative
features. The server application has been designed to be as flexible as possible, trying not to
design the server for specifically sports score information, but for any type of information.
Given the project’s constraints of human resources, software resources, and time, the server is
not completely “data independent”. Portions of the server application are specific to this Digital
channels management system.

Data Inputs

Processor level
Application level

Data display

Database level

32
3.2.6 System flowchart procedure
The flowchart below shows how the user can login and use the system. It also shows the general
view of the whole system.

33
 Start

Home page

Login

Login successful?

No

Home page
(Login as user)Yes

Select tasks

Library facilities Gallery OPAC Download Upload

34
3.3 Data modeling

3.3Tables Schema
The tables below are under MYSQL platform which ware created using MYSQL commands;

3.3.0Users table (login table)

The users table is the one for storing the users and their passwords. They include users who are
only registered by the administrator.

Data name Data type Data size description

User Id
Int 11 Auto increment(PK)
User name Varchar 255 Client user name
Password Char 64 Client password
Email Varchar 50 Client email address

3.3.1Electrical engineering books and upload Table

Data Name Data Type Data size Description
File Varchar 10 File name
Type Varchar 10 File type
ID Int 8 Identification number(PK)
Size Varchar 100 Size of book in kb/mb/gb

3.3.2 Information technology books and upload Table

Data Name Data Type Data size Description
File Text 20 File name
Type Text 20 File type
ID Text 20 Identification number(PK)
Size Text 20 Size of book in kb/mb/gb

3.3.3 Medical books and upload Table

Data Name Data Type Data size Description
File Text 50 File name
Type Text 50 File type
ID Text 50 Identification number(PK)
Size Text 40 Size of book in kb/mb/gb

35
3.3.4 Online public access catalogs books and upload Table
Data Name Data Type Data size Description
File Text 50 File name
Type Text 50 File type
ID Text 20 Identification
number(PK)
Size Text 10 Size of book in kb/mb/gb

3.4User Interface

3.4 Login and Authentication

For anyone to access the system, he/she must login to the system. He/she must type the correct
User Name and the passwords for him to login to the system. But if the person is not the
subscriber to this system then he/she can sign up to be registered to the system.

If a user tries to login without entering anything in the either fields (password field and the

Username field), he receives the error message shown below telling him that invalid Username;
Username field cannot be left blank.

Fig1.0 The print screen below shows the login form for the users;

36
3.4.0 Home page
The main page is also known as HOME PAGE for the user to navigate/manipulate through the
system. From the main home page, there are links to the various pages i.e. page for the authors
online public access catalog, gallery, about us etc.

37
3.4.1 Library facility
This is the page where the types of facilities available in the Library Information System are
accessed through different categories of books carrying information the system is carrying
different information according to the information the user wants to enrich him/herself with the
different books available can be accessed inform of e-book, and at the same time they can upload
any information they wish to share with the other users and as well they can also download a
book.

38
3.5 System implementation

3.5 System coding

After finishing the designing of the system, I wrote the code of the system though coding is still
in progress. I first developed the database using Mysql. After that, I developed the system
Graphical User Interface (GUI) using php,css and html. First I divided the system GUI into
modules and developed one module after the other. The whole system interface was developed
using Hard Cording process in combination with use of a Rapid Application Development
(RAD) tools.

3.5.0 System Testing

I will carry out system testing to try and uncover errors that might have been made inadvertently
as I was designing it or during its construction. While still developing the system, I will carry out
Formative Testing after completion of every component (Module) to check if the module is
constructed as required. This Unit Testing helped me uncover most of the errors that were
incurred during module development. I will carry out module verification at the end of every
module to check if it is constructed as expected and evaluation to check if the module works as

39
expected. After completely developing the applications modules, I will link the modules and
tested if they can work together without incompatibility issues. During this Integration Testing,
I resolved any inter-module conflicts that were spotted and ensured that the different modules
work well together to achieve the overall goal of the system.Finally I will carry out correctly and
conforms to the user requirements.

The main objective of testing was not only to ensure that the system does what is expected of it
but also to confirm that it does it correctly. This was mainly done to assess the quality of the
system.

3.5.1 System Implementation.

After testing and ensuring that the system is well built and works well, I packaged the whole
application code. The system is verified and validated to check whether the system meets the
required system requirements as stated in the system requirement specification. In the next
chapter which is the system testing and implementation am going to explain more about system
testing and implementation.

3.5.2 System Maintenance.

System maintenance will be carried throughout the use of the system, to ensure that the
application does not get corrupt before being presented. I will ensure the system is secured from
the attack by the computer malwares like viruses or worms.

I will make backup of the system that could be restored or used in case the system got corrupted.

3.6 Sample of implementation code

3.6 Implementation code.

The section presents some of the implementation code for both the database and the Graphical

User Interface of the system. Because system coding is still in progress, below is the only code
for the login form which authenticates the user for accessing the system.

3.6.0Sample code for GUI login

<?php

session_start();

40
include_once 'dbconnect.php';

if(isset($_SESSION['user'])!="")

header("Location: index.php");

if(isset($_POST['btn-login']))

$email = mysql_real_escape_string($_POST['email']);

$upass = mysql_real_escape_string($_POST['pass']);

$res=mysql_query("SELECT * FROM users WHERE

email='$email'");

$row=mysql_fetch_array($res);

if($row['password']==md5($upass))

$_SESSION['user'] = $row['user_id'];

header("Location: index.php");

else

41
 {

?>

<script>alert('wrong details,please enter correct email and password and try

again');</script>

<?php

?>

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"

"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">

<html xmlns="http://www.w3.org/1999/xhtml">

<head>

<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />

<title>Login System</title>

<link rel="stylesheet" href="style.css" type="text/css" />

</head>

<body>

<center>

<div id="login-form">

<form method="post">

<table align="center" width="30%" border="0">

42
<tr>

<td><input type="text" name="email" placeholder="Your Email" required /></td>

</tr>

<tr>

<td><input type="password" name="pass" placeholder="Your Password" required /></td>

</tr>

<tr>

<td><button type="submit" name="btn-login">Sign In</button></td>

</tr>

<tr>

<td><a href="register.php">Sign Up Here</a></td>

</tr>

</table>

</form>

</div>

</center>

</body>

</html>

3.6.1 Homepage codes

<?php

session_start();

43
include_once 'dbconnect.php';

if(!isset($_SESSION['user']))

header("Location: login.php");

$res=mysql_query("SELECT * FROM users WHERE user_id=".$_SESSION['user']);

$userRow=mysql_fetch_array($res);

?>

<html>

<head>

<title>Welcome - <?php echo $userRow['email']; ?></title>

<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />

<link rel="stylesheet" href="layout/styles/layout.css" type="text/css" />

<link rel="stylesheet" type="text/css" href="home_style.css">

<!--

#Layer1 {

position:absolute;

left:3px;

top:157px;

44
 width:975px;

height:504px;

z-index:1;

background-color: #FFFFFF;

#Layer2 {

position:absolute;

left:2px;

top:-3px;

width:975px;

height:119px;

z-index:2;

#Layer3 {

position:absolute;

left:2px;

top:112px;

width:975px;

height:40px;

z-index:3;

45
.style1 {

color: #FFFFFF;

font-weight: bold;

#Layer4 {

position:absolute;

left:170px;

top:-7px;

width:973px;

height:797px;

z-index:4;

#Layer5 {

position:absolute;

left:0px;

top:720px;

width:976px;

height:77px;

z-index:5;

background-color: #0066CC;

46
#Layer6 {

position:absolute;

left:641px;

top:8454px;

width:201px;

height:40px;

z-index:6;

#Layer7 {

position:absolute;

left:169px;

top:664px;

width:974px;

height:42px;

z-index:5;

#Layer8 {

position:absolute;

left:533px;

top:751px;

width:343px;

47
 height:38px;

z-index:6;

.style4 {color: #FFFFFF; font-weight: bold; font-size: 16; }

.style5 {font-family: "Times New Roman", Times, serif}

.style6 {font-family: "Times New Roman", Times, serif; font-style: italic; }

#Layer9 {

position:absolute;

left:177px;

top:146px;

width:772px;

height:325px;

z-index:7;

#Layer10 {

position:absolute;

left:173px;

top:527px;

width:972px;

height:137px;

z-index:8;

48
 background-color: #999999;

.style7 {

font-size: 24px;

font-weight: bold;

font-family: "Times New Roman", Times, serif;

color: #000000;

#Layer11 {

position:absolute;

left:178px;

top:150px;

width:869px;

height:45px;

z-index:9;

.style8 {

color: #0000CC;

font-family: "Brush Script MT";

font-size: 36px;

49
.style9 {

color: #00ff00;

font-size: 55px;

.style9 {color: #FF0000}

-->

</head>

<body id="top">

<div class="wrapper col2">

<div id="header">

<div class="fl_left">

<h1><a href="#"> Library System</a></h1>

<p>Information</p>

</div>

<div id="right">

<div id="content">

Hi' <?php echo $userRow['username']; ?>&nbsp;<a

href="logout.php?logout">Sign Out</a>

</div>

50
</div>

<ul id="topnav">

<li><a href="logout.php?logout">Logout</a></li>

<li class="last"><a href="gallery.php">Gallery</a></li>

<li><a href="#">Authors</a>

<ul>

<li><a href="books.php">Books</a></li>

<li><a href="">Biography</a></li>

</ul>

</li>

<li><a href="#">About US</a>

<ul>

<li><a href="contact.php">Contact Us</a></li>

<li><a href="about.php">About</a></li>

<li><a href="#">FAQ</a></li>

</ul>

</li>

<li><a href="">Library facilities</a>

<ul>

<li><a href="view.php">Medical</a></li>

51
 <li><a href="me.php">Information Technology</a></li>

<li><a href="elect.php">Electric Eng</a></li>

<li><a href="civil.php">Civil Eng</a></li>

<li><a href="opac.php">OPAC</a></li>

</ul>

</li>

</ul>

<br class="clear" />

</div>

</div>

<div id="Layer11"><marquee behavior="down" direction="left" scrollamount="7"

class="style7">

<div align="center" class="style8 style9">Library Information System: Our Pleasure is To

Serve You! </div>

</marquee>

<div class="container">

<div id="content-slider">

<div id="slider"> <!-- Slider container -->

<div id="mask"> <!-- Mask -->

<ul>

<li id="first" class="firstanimation"> <!-- ID for tooltip and class for animation -->

52
 <a href="#"> <img src="photos/slide5.jpg" width="1000" height="1000 class="img-
thumbnail" alt="decoder"/> </a>

<div class="tooltip"> <h1>Cougar</h1> </div>

</li>

<li id="second" class="secondanimation">

<a href="#"> <img src="photos/slide1.jpg" width="1000" height="1000 class="img-

circle" alt="Lions"/> </a>

<div class="tooltip"> <h1>Lions</h1> </div>

</li>

<li id="third" class="thirdanimation">

<a href="#"> <img src="photos/slide2.jpg" width="800" height="800 class="img-

circle"alt="Snowalker"/> </a>

<div class="tooltip"> <h1>Snowalker</h1> </div>

</li>

<li id="fourth" class="fourthanimation">

<a href="#"> <img src="photos/slide3.jpg" width="800" height="800 class="img-rounded"

alt="Howling"/> </a>

<div class="tooltip"> <h1>Howling</h1> </div>

</li>

53
 <li id="fifth" class="fifthanimation">

<a href="#"> <img src="photos/slide4.jpg" width="800" height="800 class="img-

responsive" alt="Sunbathing"/> </a>

<div class="tooltip"> <h1>Sunbathing</h1> </div>

</li>

</ul>

</div> <!-- End Mask -->

<div class="progress-bar"></div> <!-- Progress Bar -->

</div> <!-- End Slider Container -->

</div>

</div>

<div class="style4" id="Layer8">

<p class="style5">Designed By Edward nyambane</p>

<p class="style6">Courtesy of KCAU </p>

<marquee color="red">Library Information System </marquee>

</div>

</body>

</html>

54
3.6.2 Uploading codes

<?php

include_once 'dbconfig.php';

if(isset($_POST['btn-upload']))

$file = rand(1000,100000)."-".$_FILES['file']['name'];

$file_loc = $_FILES['file']['tmp_name'];

$file_size = $_FILES['file']['size'];

$file_type = $_FILES['file']['type'];

$folder="uploads/";

// new file size in KB

$new_size = $file_size/1024;

// new file size in KB

// make file name in lower case

$new_file_name = strtolower($file);

// make file name in lower case

$final_file=str_replace(' ','-',$new_file_name);

55
 if(move_uploaded_file($file_loc,$folder.$final_file))

$sql="INSERT INTO it_uploads(file,type,size)

VALUES('$final_file','$file_type','$new_size')";

mysql_query($sql);

?>

<script>

alert('successfully uploaded');

window.location.href='info.php?success';

</script>

<?php

else

?>

<script>

alert('error while uploading file');

window.location.href='info.php?fail';

</script>

<?php

56
 }

?>

Chapter Four

SYSTEM TESTING AND IMPLEMENTATIO

4.0 TESTING AND IMPLEMENTATION

4.0 Introduction
This is the process that checks whether the system developed is the required results under known
conditions. The purpose of testing is to identify and correct the errors of the system.
In system testing, performance and acceptance standards are developed. It can take place when
one is coding the program. One can code a module and run it to see whether it works perfectly.
This does involve the process of inputting real data for testing the suitability of the module and
the system as a whole. The system should work according to the specifications outlined in
previous chapter under the system Requirements Specification document.

4.0.1Objectives of System Testing

 The system test should help to identify errors, faults, bugs and failures of the system so
that it can be described as a successful test.
 It should help to establish test cases for the system and also the test data to enable
efficient and effective system test
 It should also help to establish resources required for performing the tests in the test plan.
These resources include money required for man power.
 The test schedule is also developed for performing the tests which allocates the time
required for each part of testing and the procedures to be followed.
 The system should also ensure consistency in the software that has been developed
ensuring that there are no deviations from the specifications.

57
4.0.2Testing Strategy
The test Strategy consists of various tests that will ensure the system is tested appropriately in
units and as a whole. This will assist to discover the uncovered errors in the system, unit modules
and during their integration and as a whole

58
4.0.3 Test Plan
This does show how the program is to be tested and the procedure. The test data is identified,
what is to be tested, the expected output and the actual results after inputting the test date The
system will be tested in a standalone machine where the database will be hosted locally first .For
the majority of testing, there will be a small test in programs and this will be testing for
compatibility. All test cases will be documented.

4.1 TYPES OF TESTING

4.1.0 Unit Testing

Unit testing is performed to test individual units of an application. Since the application
comprises of various units and module, detecting errors in these unit is simple and consumes less
time, as they are small in size. However, it is possible that the output produced by one unit
becomes the input for another unit, hence if the incorrect output produced by one unit is provided
as input in the second nit then also it shall be incorrect here.If these process is not corrected, the
entire application may produce unexpected outputs. To avoid this all the units in an application
are tested independently using unit testing.
Unit testing is not just performed once during the application development but is repeated
whenever the application is modified or used in new environment. Some other points that should
be kept in mind are:
 Each unit is tested separately regardless of other unit of the application
 The developers themselves perform these testing
 The method of white box testing is done in this testing
In addition
 It ensures that all statements in the unit have been executed at least once.
 It tests data structures that represents relationship among individual elements
 It ensures that the data entered in variables is of the same data type as defined in the unit.
 Unit Input Expected output Obtained status remedies
output
1 Login User name Check with database for Database is pass
and their relevance and Verified and
password redirect to the admin application
homepage redirected to
admin
homepage
2 Library Medical Upload a book, Inserted into pass
facilities Download a book,Open table
a book online

3 Search Start search Check database for the Error due to fail Inserted
criteria book and display book invalid search valid date
keyword
4 Create User name new user Create succes
username and Password s
and password
password

4.1.1ADMINISTRATION MODULE
Fig 1
4.1.2 LIBRARY MODULE
Fig 2

Upload Book Book format Book size Output status remedies

obtained
1 Book title Pdf,doc,txt,jpg Insert into table Inserted success
etc medical the into table
database

4.1.3 Integration testing

This is testing two or more programs that depend on each other. In Integration testing
components of the system are combined and tested in different ways. When you have programs
and components of the network that depend on each other to perform a function then it is
imperative to make sure that they work together correctly. Again in this phase of testing, both
positive testing that simulates your actual conditions and negative testing that simulates incorrect
conditions will be used.
Fig 3

Serial no Unit input Expected Output status remedies

output obtained

1 Administrator User name Create User created success

module and username
password and
password

2 Library medical Upload a View books success

facilities book, available
Download a
book,
Open a
book online.
3 opac Read books Display Open books success
online books in in any
without any format format
downloadin
g

4.1.4 Security testing

System with sensitive information are generally the target of improper or illegal use therefore
protection mechanisms are required to restrict unauthorized access to the system to avoid any
kind of improper usage, security testing is performed which identifies and removes the flaws
from the application that can be exploited by the intruders and thus results in security violation.
Security testing focuses on the following:
To check whether the user can access only those data and functions for which the system
developer or the user of the system has given permission this kind of security is referred to
authorization.

4.1.5 System security:

To check whether only the users who have permission to access the system are accessing
it.These is referred to as authentication.

Security is the main objective of any project. The importance of security testing is to stop
unauthorized usages of data, means to ensure that the users only can access the data that is
permitted by the system developer.

4.2 Beta testing

Application testing is an investigation conducted to provide stakeholders with information about
the quality of the product or service under test.Application testing can also provide an objective,
independent view of the application to allow the business to appreciate and understand the risk of
application implementation. Test techniques include, but are not limited to the process of
executing a program or application with the intent of finding application bugs (errors and
defects)

Application testing can be stated as the process of validating and verifying that a computer
program/application/product:

 Meets the requirements that guided its design and development

 Works as expected
 Can be implemented with the same characteristics
 And satisfies the needs of stakeholders

4.3 Load testing

Load testing is the process of putting demand on a system or device and measuring its
response. Load testing is performed to determine a systems behavior under the normal and
anticipated peak load conditions. It helps to identify the maximum operating capacity of an
 application as well as any bottlenecks and determine which element is causing degradation.
When the load placed on the system is raised beyond normal usage patterns, in order to test
the systems response at unusually high or peak loads, it known as stress testing. The load is
usually so great that errors condition are the expected results although no clear boundary
exists when an activity ceases to be a load test and becomes a stress test.

This term may be used differently and here it’s important to state that our application can
work smoothly in any critical condition. We have to observe that the load testing is
successfully passed by this application.

4.4 Acceptance testing

A test conducted to determine if the requirements of a specification or contract are met.it may
involve physical test or performance test.

In systems engineering it may involve black-box testing performed on a system prior to its
delivery. In these case of application acceptance testing performed by the customer shall be
known as user acceptance testing, end user testing or field testing.

4.5 System Testing

System testing is where the entire system will be tested for functionality.
In this final testing, it will be made sure that it can handle the predicted volumes of data quickly
and efficiently.

4.5 Implementation Strategy

The Implementation Strategy covers the following stages:
1. Hardware and Software Acquisition
2. User Training
3. File creation/Conversion
4. Changeover
Most libraries have the capability of implementing this kind of module except that they do not
give a chance to authors to upload new writings to the system and even download books from the
system
4.6 Hardware and Software acquisition
This process involves hardware selection, installation and acquisition. Software referred here
include operating system loaded in the hardware device drivers.
Proper purchasing procedures should be followed

4.7 File Conversion

This will involve converting of hard copy book to the softcopy books which can be uploaded to
the system. Therefore the data will be fed in to the system database.

4.8 Changeover
This does involve all activities carried out during the switching from the existing system to the
new system. The various approaches are direct changeover, Pilot Changeover, Phased
changeover and parallel changeover. The best approach of implementing the system is the
parallel changeover system
The parallel changeover method involves running both system side by side that is simultaneously
over a period of time until its proved beyond reasonable doubt that the new system is working
appropriately as per the stated specifications and the anticipated benefits are being realized.

4.8.1The changeover will be used because:

 It assists in the comparison of the results from both systems
 It minimizes training efforts or requirements since users familiarize themselves with the
system during the changeover
 It reduces resistance to the new system

4.9 IMPLEMENTATION

4.9 Introduction
This describes the preferred strategy that will be used when taking in the system or rather
implementing the system. It clearly depicts the step by step procedures of activities to be carried
out during implementation by use of almost applicable and preferred strategy.
System Implementation is one of the most important parts in coming up with a system and it
entails processes and steps which should be adhered to systematically as indicated in order to
achieve a successful changeover.
This document therefore describes the selected strategy to perform this function and why it was
chosen or agreed upon by the developer

4.9.0 Strategy for Implementation

Some of the preferred strategies include:-

4.9.1Parallel Changeover
This is the most popular method as it does provide the lowest risk in case a tragedy occurs thus
affecting the system such that the old system can be reverted back to if necessary in order to go
back and make improvements for the new system.

4.9.2 Limitations
 It is expensive and time consuming since both systems will be running at the same time
 Parallel tends to delay the adoption of the new system
 Extra workload in maintaining both systems

4.9.3 Pilot Changeover

This is whereby the system is implemented at selected location of the institution such as only at
the library facilities. The first group to use the system is called the pilot site. The old system is
still running at the pilot site and for the rest of the base.After the system proves successful at the
pilot site, it is implemented to the rest of the base.
4.9.4 Phased Changeover
This is the recommended one over the two other methods of direct and parallel. It is whereby the
system is implemented one module at a time. The various teams working together during
implementation allow the new system to be implemented in stages or modules. The difference
between pilot and phased changeover is that pilot gives one location the entire system at a time,
while phase gives one module of the system to all users at a time

4.9.5 Strategy Justification

The strategy that the developer decided to use is parallel changeover and below is the reasons:
 It allows for comparisons between the two systems used by the force using live data
therefore any mistakes which come up as a result of variation from the old system the
results can be easily noted.
 The user gets to learn the system on how it works way before it is fully implemented thus
reducing the overall tasks of training the users again.
 This method gives the user an opportunity to be able to learn everything about the system
way before it is brought to the station for proper use
 This also provides the user some time to be conversant with the system early enough
before the old system which they have been using for a while is dropped for the new one

4.9.6 Major Tasks in Implementation

4.9.6 Installation
It does involve both hardware and Software installations

4.9.6.0 Training
The user is trained on how to use the new system at times the user may tend not to understand
any of the new things he/she is being taught.

4.9.6.1 Execution
This involves performing actual operation of the system and this is done by person in charge of
the system.
4.9.6.2 File Conversion
Conversion of these activities concerned with the transfer of aspects of the old system to the
new. All existing data will need to be entered manually through input controls

4.9.6.3 Maintenance
Ensuring that the system remains operational and also catering for later versions and addressing
issues that encounter as they are using the system

4.9.6.4 Conclusion
With this documentation the system will be able to accomplish the user’s requirements
established in the system requirements analysis documents The aim of these system is to develop
a system of improved facilities. The proposed system can overcome all the limitations of the
existing system. The system provides proper security and reduces the manual work, which will
lead to fast; efficient way for making order reliability to the user.

However, Maintenance of the system may be expensive due to advance in technology.

4.9.6.5 Developer’s Recommendations

 The program is bound to be improved at future dates
 Better functionality and procedures should be implemented in the later versions of the
program
 The user of the system should be computer literate so as to use the system effectively
Chapter Five

5.0 USER MANUAL

User manual acts as guide to the user of the system. It is aimed at giving the aid to the user of the
system.

This system is designed using PHP,CSS AND JAVA SCRIPT linked with MYSQL to help
relate national libraries to carry out the task of disseminating information to different clients

5.1 The System Installation

This system can run on any window that is compatible with a computer system which has the
internet browsers software that can be used to get access to the database which is hosted by the
internet, an operating system.

Once the system is installed, it should work effectively to efficiently increase speed at which
information is saved and retrieved.

Running the system:

1. Install WampServer to host the database locally.

2. Import the database (MYSQL).
 3. The system is supposed to be hosted by an internet service provider that can make it
accessible remotely by any device which is internet enable.
To run the system open the internet browser and in the uniform resource locater type library
information system but if you are using WampServer just double click the WampServer icon and
wait it to load until it changes its colour to green and then click it and the in the list displayed
click LocalHost to launch web browser software.

5.2 How to Load the System

 Double click on the WampServer
 To run the system open the internet browser and in the uniform resource locater type
library information system but if you are using WampServer just double click the
WampServer icon and wait it to load until it changes its colour to green and then click it
and the in the list displayed click LocalHost to launch web browser software.

5.3 Running the system

5.3 Running the system:

Once the system is set to run the user waits for a few seconds while the system is loading

Here the user keys in his/her credentials that is valid username and password as shown below:
If the user does not have the username and password he/she can go ahead and create a profile
with this system to get access to the system services.

5.3.0 Accessing the system

Once logged in to the system one has the access to the options provided in the homepage as
shown below;
One can navigate through the various pages that are opened after clicking on their links, for
example, opening a page to download a book or upload a book.

3.3.1Accessing a page:
To access a page

 Click on the link on the homepage and select the appropriate page. The page requested
will be displayed.

3.3.2Uploading a book/item:
To Uploading a book/item.

 Click on the browse button the dialog box appears select a file u want to upload and then
click upload.
3.3.3 Closing a page:
To close a page

 Click on the home button and, on clicking it loads and takes you back to homepage.

3.3.4 Error messages:

These are text messages which are displayed when an error is made while entering data or
manipulating the system. To solve such errors, you respond to the dialog box appropriately.
Make sure you are keying in the right username and password and be case sensitive.

3.3.5Troubleshooting
PROBLEM POSSIBLE CAUSE MEASURES

Software not responding Too much system overload, Check memory capacity and may
insufficient memory or run disk cleanup wizard.
corrupt operating system.
Repair the operating system

PC shut down or logoff Power failure which may be Ensure there is power on the main
due to faulty power supply supply

Check your power supply unit

 Check power cable.

Display of funny Attack of virus to your Run anti-virus software or update it

messages on the screen system
or deletion of data
spontaneously.

3.3.6Back Up
This is not necessary since the system will be hosted by the internet service providers but for
preparedness of any eventualities we need to backup this system to allow for tolerance during the
concurrency of faults. This can be achieved through replication and fragmentation of the
databases since the database to be used will be hosted in the network.

Chapter Six

6.0 CODES

6.0 log in page/sign up

<?php

session_start();

include_once 'dbconnect.php';

if(isset($_SESSION['user'])!="")

{
 header("Location: index.php");

if(isset($_POST['btn-login']))

$email = mysql_real_escape_string($_POST['email']);

$upass = mysql_real_escape_string($_POST['pass']);

$res=mysql_query("SELECT * FROM users WHERE email='$email'");

$row=mysql_fetch_array($res);

if($row['password']==md5($upass))

$_SESSION['user'] = $row['user_id'];

header("Location: index.php");

else

?>

<script>alert('wrong details,please enter correct email and password and try

again');</script>

<?php
 }

?>

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"

"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">

<html xmlns="http://www.w3.org/1999/xhtml">

<head>

<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />

<title>Login System</title>

<link rel="stylesheet" href="style.css" type="text/css" />

</head>

<body>

<center>

<div id="login-form">

<form method="post">

<table align="center" width="30%" border="0">

<tr>

<td><input type="text" name="email" placeholder="Your Email" required /></td>

</tr>

<tr>
<td><input type="password" name="pass" placeholder="Your Password" required /></td>

</tr>

<tr>

<td><button type="submit" name="btn-login">Sign In</button></td>

</tr>

<tr>

<td><a href="register.php">Sign Up Here</a></td>

</tr>

</table>

</form>

</div>

</center>

</body>

</html>

6.1 homepage
<?php

session_start();

include_once 'dbconnect.php';

if(!isset($_SESSION['user']))

{
 header("Location: login.php");

$res=mysql_query("SELECT * FROM users WHERE user_id=".$_SESSION['user']);

$userRow=mysql_fetch_array($res);

?>

<html>

<head>

<title>Welcome - <?php echo $userRow['email']; ?></title>

<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />

<link rel="stylesheet" href="layout/styles/layout.css" type="text/css" />

<link rel="stylesheet" type="text/css" href="home_style.css">

<!--

#Layer1 {

position:absolute;

left:3px;

top:157px;

width:975px;

height:504px;

z-index:1;

background-color: #FFFFFF;
}

#Layer2 {

position:absolute;

left:2px;

top:-3px;

width:975px;

height:119px;

z-index:2;

#Layer3 {

position:absolute;

left:2px;

top:112px;

width:975px;

height:40px;

z-index:3;

.style1 {

color: #FFFFFF;

font-weight: bold;

}
#Layer4 {

position:absolute;

left:170px;

top:-7px;

width:973px;

height:797px;

z-index:4;

#Layer5 {

position:absolute;

left:0px;

top:720px;

width:976px;

height:77px;

z-index:5;

background-color: #0066CC;

#Layer6 {

position:absolute;

left:641px;

top:8454px;
 width:201px;

height:40px;

z-index:6;

#Layer7 {

position:absolute;

left:169px;

top:664px;

width:974px;

height:42px;

z-index:5;

#Layer8 {

position:absolute;

left:533px;

top:751px;

width:343px;

height:38px;

z-index:6;

.style4 {color: #FFFFFF; font-weight: bold; font-size: 16; }

.style5 {font-family: "Times New Roman", Times, serif}

.style6 {font-family: "Times New Roman", Times, serif; font-style: italic; }

#Layer9 {

position:absolute;

left:177px;

top:146px;

width:772px;

height:325px;

z-index:7;

#Layer10 {

position:absolute;

left:173px;

top:527px;

width:972px;

height:137px;

z-index:8;

background-color: #999999;

.style7 {

font-size: 24px;
 font-weight: bold;

font-family: "Times New Roman", Times, serif;

color: #000000;

#Layer11 {

position:absolute;

left:178px;

top:150px;

width:869px;

height:45px;

z-index:9;

.style8 {

color: #0000CC;

font-family: "Brush Script MT";

font-size: 36px;

.style9 {

color: #00ff00;

font-size: 55px;

}
.style9 {color: #FF0000}

-->

</head>

<body id="top">

<div class="wrapper col2">

<div id="header">

<div class="fl_left">

<h1><a href="#"> Library System</a></h1>

<p>Information</p>

</div>

<div id="right">

<div id="content">

Hi' <?php echo $userRow['username']; ?>&nbsp;<a href="logout.php?logout">Sign

Out</a>

</div>

</div>

<ul id="topnav">

<li><a href="logout.php?logout">Logout</a></li>
<li class="last"><a href="gallery.php">Gallery</a></li>

<li><a href="#">Authors</a>

<ul>

<li><a href="books.php">Books</a></li>

<li><a href="">Biography</a></li>

</ul>

</li>

<li><a href="#">About US</a>

<ul>

<li><a href="contact.php">Contact Us</a></li>

<li><a href="about.php">About</a></li>

<li><a href="#">FAQ</a></li>

</ul>

</li>

<li><a href="">Library facilities</a>

<ul>

<li><a href="view.php">Medical</a></li>

<li><a href="me.php">Information Technology</a></li>

<li><a href="elect.php">Electric Eng</a></li>

<li><a href="civil.php">Civil Eng</a></li>

<li><a href="opac.php">OPAC</a></li>
 </ul>

</li>

</ul>

<br class="clear" />

</div>

</div>

<div id="Layer11"><marquee behavior="down" direction="left" scrollamount="7"

class="style7">

<div align="center" class="style8 style9">Library Information System: Our Pleasure is To

Serve You! </div>

</marquee>

<div class="container">

<div id="content-slider">

<div id="slider"> <!-- Slider container -->

<div id="mask"> <!-- Mask -->

<ul>

<li id="first" class="firstanimation"> <!-- ID for tooltip and class for animation -->

<a href="#"> <img src="photos/slide5.jpg" width="1000" height="1000 class="img-

thumbnail" alt="decoder"/> </a>

<div class="tooltip"> <h1>Cougar</h1> </div>

</li>
 <li id="second" class="secondanimation">

<a href="#"> <img src="photos/slide1.jpg" width="1000" height="1000 class="img-

circle" alt="Lions"/> </a>

<div class="tooltip"> <h1>Lions</h1> </div>

</li>

<li id="third" class="thirdanimation">

<a href="#"> <img src="photos/slide2.jpg" width="800" height="800 class="img-

circle"alt="Snowalker"/> </a>

<div class="tooltip"> <h1>Snowalker</h1> </div>

</li>

<li id="fourth" class="fourthanimation">

<a href="#"> <img src="photos/slide3.jpg" width="800" height="800 class="img-rounded"

alt="Howling"/> </a>

<div class="tooltip"> <h1>Howling</h1> </div>

</li>

<li id="fifth" class="fifthanimation">

<a href="#"> <img src="photos/slide4.jpg" width="800" height="800 class="img-

responsive" alt="Sunbathing"/> </a>
 <div class="tooltip"> <h1>Sunbathing</h1> </div>

</li>

</ul>

</div> <!-- End Mask -->

<div class="progress-bar"></div> <!-- Progress Bar -->

</div> <!-- End Slider Container -->

</div>

</div>

<div class="style4" id="Layer8">

<p class="style5">Designed By Edward nyambane</p>

<p class="style6">Courtesy of KCAU </p>

<marquee color="red">Library Information System </marquee>

</div>

</body>

</html>

6.2 upload
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">

<html xmlns="http://www.w3.org/1999/xhtml">

<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />

<title>LIBRARY</title>

<style type="text/css">

<!--

#Layer1 {

position:absolute;

left:3px;

top:157px;

width:975px;

height:504px;

z-index:1;

background-color: #FFFFFF;

#Layer2 {

position:absolute;

left:2px;

top:-3px;

width:975px;

height:119px;

z-index:2;

}
#Layer3 {

position:absolute;

left:2px;

top:112px;

width:975px;

height:40px;

z-index:3;

.style1 {

color: #FFFFFF;

font-weight: bold;

#Layer4 {

position:absolute;

left:170px;

top:-7px;

width:973px;

height:797px;

z-index:4;

#Layer5 {
 position:absolute;

left:0px;

top:720px;

width:976px;

height:77px;

z-index:5;

background-color: #0066CC;

#Layer6 {

position:absolute;

left:641px;

top:8454px;

width:201px;

height:40px;

z-index:6;

#Layer7 {

position:absolute;

left:0px;

top:130px;

width:974px;
 height:42px;

z-index:5;

#Layer8 {

position:absolute;

left:205px;

top:182px;

width:343px;

height:38px;

z-index:6;

.style5 {font-family: "Times New Roman", Times, serif}

.style6 {font-family: "Times New Roman", Times, serif; font-style: italic; }

#Layer9 {

position:absolute;

left:175px;

top:152px;

width:967px;

height:497px;

z-index:7;

}
#Layer10 {

position:absolute;

left:771px;

top:325px;

width:0px;

height:2px;

z-index:8;

#Layer11 {

position:absolute;

left:462px;

top:178px;

width:309px;

height:37px;

z-index:9;

#Layer12 {

position:absolute;

left:213px;

top:245px;

width:145px;
 height:26px;

z-index:10;

#Layer13 {

position:absolute;

left:381px;

top:244px;

width:139px;

height:32px;

z-index:11;

#Layer14 {

position:absolute;

left:545px;

top:245px;

width:61px;

height:29px;

z-index:12;
}

#Layer15 {

position:absolute;
 left:657px;

top:245px;

width:204px;

height:35px;

z-index:13;

#Layer16 {

position:absolute;

left:870px;

top:247px;

width:164px;

height:31px;

z-index:14;

#Layer17 {

position:absolute;

left:261px;

top:377px;

width:100px;

height:38px;

z-index:15;
}

#Layer18 {

position:absolute;

left:407px;

top:375px;

width:210px;

height:36px;

z-index:16;

#Layer19 {

position:absolute;

left:261px;

top:420px;

width:122px;

height:33px;

z-index:17;

#Layer20 {

position:absolute;

left:407px;

top:414px;
 width:236px;

height:36px;

z-index:18;

#Layer21 {

position:absolute;

left:262px;

top:460px;

width:117px;

height:27px;

z-index:19;

#Layer22 {

position:absolute;

left:409px;

top:454px;

width:238px;

height:26px;

z-index:20;

#Layer23 {
 position:absolute;

left:264px;

top:332px;

width:111px;

height:31px;

z-index:21;

#Layer24 {

position:absolute;

left:408px;

top:334px;

width:243px;

height:35px;

z-index:22;

#Layer25 {

position:absolute;

left:263px;

top:498px;

width:129px;

height:31px;
 z-index:23;

#Layer26 {

position:absolute;

left:411px;

top:498px;

width:231px;

height:23px;

z-index:24;

#Layer27 {

position:absolute;

left:557px;

top:552px;

width:134px;

height:37px;

z-index:25;

#Layer28 {

position:absolute;

left:1039px;
 top:247px;

width:52px;

height:32px;

z-index:26;

#Layer29 {

position:absolute;

left:216px;

top:190px;

width:874px;

height:424px;

z-index:9;

</style>

<link id="bs-css" href="css/bootstrap-cerulean.css" rel="stylesheet">

<link href="css/bootstrap-responsive.css" rel="stylesheet">

<link href="css/charisma-app.css" rel="stylesheet">

<link href="css/jquery-ui-1.8.21.custom.css" rel="stylesheet">

<link href='css/fullcalendar.css' rel='stylesheet'>

<link href='css/fullcalendar.print.css' rel='stylesheet' media='print'>

<link href='css/chosen.css' rel='stylesheet'>

 <link href='css/uniform.default.css' rel='stylesheet'>

<link href='css/colorbox.css' rel='stylesheet'>

<link href='css/jquery.cleditor.css' rel='stylesheet'>

<link href='css/jquery.noty.css' rel='stylesheet'>

<link href='css/noty_theme_default.css' rel='stylesheet'>

<link href='css/elfinder.min.css' rel='stylesheet'>

<link href='css/elfinder.theme.css' rel='stylesheet'>

<link href='css/jquery.iphone.toggle.css' rel='stylesheet'>

<link href='css/opa-icons.css' rel='stylesheet'>

<link href='css/uploadify.css' rel='stylesheet'>

<link rel="stylesheet" type="text/css" href="css/style.css">

<style type="text/css">

#Layer30 {

position:absolute;

left:129px;

top:44px;

width:1018px;

height:419px;

z-index:9;

.style8 {color: #FFFFFF}

#Layer31 {

position:absolute;

left:210px;

top:382px;

width:875px;

height:70px;

z-index:10;

#Layer32 {

position:absolute;

left:132px;

top:156px;

width:975px;

height:38px;

z-index:10;

background-color: #0000FF;

-->

</style>

</head>

<div id="body">
<label> Upload Your Files Here </label>

<form action="opacupload.php" method="post" enctype="multipart/form-data">

<input type="file" name="file" />

<button type="submit" name="btn-upload">upload</button>

</form>

<br /><br />

<?php

if(isset($_GET['success']))

?>

<label>File Uploaded Successfully </label>

<?php

else if(isset($_GET['fail']))

?>

<label>Problem While File Uploading !</label>

<?php

else
 {

?>

<label>You can upload the following files (PDF, DOC, EXE, VIDEO, MP3,
ZIP)</label><br>

<?php

?>

</div>

<body bgcolor="#00FF00">

<div id="Layer10"></div>

<div id="Layer30">

<div class="container-fluid">

<div id="Layer3"">

<p>&nbsp;</p>

<p>&nbsp;</p>

<div class="alert alert-block span9">

<table class="table table-striped table-bordered bootstrap-datatable datatable">

<thead>

<tr> <th>NO:</th>

<th>ID Number</th>

<th>File</th>
 <th>Size</th>

<th>Type</th>

<th colspan="2" align='center'>Actions</th>

</tr>

</thead>

<tbody>

<?php

$va="pa";

$no=1;

include('dbconfig.php');

$resp=mysql_query("SELECT * FROM opac_uploads");

while($row=mysql_fetch_array($resp)){

echo '<tr>';

echo '<td>'.$no.'</td>';

echo "<td>" . $row['id'] . "</td>";

echo "<td>" . $row['file'] . "</td>";

echo "<td>" . $row['size'] . "</td>";

echo "<td>" . $row['type'] . "</td>";

echo "<td>" ;?>

<a class="btn btn-success" href="uploads/<?php echo $row['file'] ?>" target="_blank""><i

class="icon-zoom-in icon-white"></i>View</a>
<?PHP PRINT "</td>";

echo '<td class="center">';

//echo '<a class="btn btn-success" href="channels.php?id='.$row['ID_NO'].'&jina='.

$row['First_Name'] "><i class="icon-zoom-in icon-white"></i>'."SUBSCRIBE".'</a>';?>

<a class="btn btn-success" href="see.php"><i class="icon-zoom-in icon-

white"></i>DELETE</a>

<?php echo ' </tr>';

$no++;

?>

</body>

</table>

</div>

<div class="alert alert-block span9">

<div id="layer">

<table width="973" height="35" border="0" cellpadding="2" cellspacing="10"

bgcolor="#0099CC">

<tr>

<th scope="col"><a href="index.php"><span class="style1">Home</span></a></th>

 <th scope="col"><a href="login.php"><span class="style1">Logout</span></a></th>

</tr>

</table>

</div>

</div>

<div class="alert alert-block span4" >

<p align="right" class="style5 style8">Designed By Edward Nyambane</p>

<p align="right" class="style6">Courtesy of KCAU </p>

</div>

<p>&nbsp;</p>

<p>&nbsp;</p>

</div>

</div>

</div>

<div id="Layer32">

<table width="973" height="35" border="0" cellpadding="2" cellspacing="10"

bgcolor="#B88483">

<tr bordercolor="#FFFF66">

<th scope="col"><a href="index.php"><span class="style1">Home</span></a></th>

<th scope="col"><a href="login.php"><span class="style1">Logout</span></a></th>

 </tr>

</table>

</div>

<form method="post" action="">

</form>

</body>

</html>