CHAPTER 3

SYSTEM ANALYSIS AND DESIGN

3.1 Introduction to System Analysis
There are three stages in building the new system to create the optimum match for the library.
They are gathering data, designing, implementing, and conducting final testing. Different
strategies will be used within these three areas so that we may develop a system that can
retain high usability and accessibility. Here are some suggestions for the procedure. Prior to
employing software development tools to set up the system, information about the
requirements for users of the system, such as library staff and readers, will be obtained from
the staff by using qualitative data gathering techniques (oral interviews).

Given the size and goals of this study, it is highly recommended to adopt the survey method
of qualitative data collection, which involves conducting oral interviews.

The library serves as both a case study for the suggested system and a significant source of
data. In accordance with this, the primary technique for the system's information collection is
the monitoring the staff and how the library is run is a method for the library and observation.

3.1.1 Analysis of Existing System

There is a ton of paperwork involved with the current library administration system.
According to the system, all library user information will be collected using a white-and-
black technique. Every registered user's borrower information is required when checking out
a book from the library, and that person can sign out the book and return it when finished.

3.1.2 Problems of Existing System

i. Having a general understanding of the current system, the following are its issues.
ii. Data Loss: A lot of paperwork is required to save the information on II. Books
borrowed by a registered user in a safe manner.
iii. Time Wasting: Users waste time looking for books that have already been published.
iv. A user who cannot be identified by their borrowing history on the paper records.
v. Error Prone: The current operating system is prone to mistakes.
vi. It is difficult because it requires a routine.
vii. Processing Speed: There is very little output due to the slow processing speed.
3.1.3 Description of Proposed System

An administrator (Librarian) uses the library management system, a web-based application

system, as an alternative method of keeping track of the books kept in the library. These
characteristics are present.

i. The administrator enters the applicant's first and last names when registering them,
matriculation number, department, etc., as well as a username that the user has
recommended. Alongside a login password that the registered user must use to log in
ii. A candidate is permitted to access the system using his name and a randomly
generated password. which is provided during the registration stage.
iii. The administrator accesses the report to see a specific user's details

3.1.4 Advantages of Proposed System

Certain advantages are related to the projected system which enhances the look of the system.
a number of that are declared below:

i. It eliminates the presence of the audience or fellow colleague who will whisper the
result to their friends.
ii. it's free from biasness (all users are served equally).
iii. It provides a right away an instantaneous response to each user.
iv. It facilitates simple learning.

3.2 Hardware Requirements

The hardware that's needed within the successful completion of this project include;

i. A system running on Pentium 2.

ii. A random access memory (RAM) of 512 MB.
iii. Enhanced Keyboard.
iv. Laptop
v. A 2.0 GB hard disk.
vi. The Intel Core i5 2nd generation is utilized as a processor because it is quick
compared to other CPUs, very dependable, and allows us to run our computer for
extended periods of time. With the help of this processor, we may continue working
on our project without any concerns.
3.3 Software Requirements

The software support for the design of the projected system involves:

i. A windows 8 operating system.

ii. Macromedia Dreamweaver.
iii. XAMPP server.
iv. My SQL database.
v. An internet access in addition as an anti-virus software that prevents the system from
being infected by virus.

The front end and the back end of the project are separated into two sections.

FRONT END: Java script, HTML, PHP, and CSS were used to create the front end.

i. HTML: HTML, often known as Hyper Text Mark-up The primary mark-up language used
to create web pages and other content that can be seen in a web browser is language. Within
the text of a web page, HTML is expressed as HTML elements, which are composed of tags
contained in angle brackets (such as html>).

A web browser's job is to read HTML files and combine them into visually or aurally
appealing online pages. By indicating structural semantics for text elements including
headers, paragraphs, lists, links, quotes, and other objects, it offers a way to produce
structured documents. It has the ability to embed programs that modify the behavior of
HTML web pages and are written in languages like JavaScript.

ii. Cascading Style Sheets (CSS): CSS is a language for creating style sheets that describe
how a document formatted and looked when it was created using a mark-up language. The
language can be used to style any type of XML document, including plain XML, SVG, and
XUL. However, it is most frequently used to style web pages and interfaces written in HTML
and XHTML.

Most web pages utilize CSS style sheets to describe how they are presented since CSS is a
fundamental web specification.

The main purpose of CSS is to make it possible to separate a document's information from its
presentation, which includes things like the layout, colors, and fonts.
This division can increase content accessibility, give the specification of presentation features
greater freedom and control, allow numerous pages to share formatting, and minimize
complexity and duplication in the structural content (for example, by allowing for table-less
web design). The same markup page can be rendered in several styles for different rendering
techniques, including on-screen, in print, via voice (when read aloud by a screen reader or
speech-based browser), and on Braille-based, tactile devices, thanks to CSS. Additionally,
depending on the screen size or viewing device, it can be utilized to enable the web page to
appear differently.

iii JavaScript (JS): JavaScript, a dynamic computer programming language, is the third
option. It is most frequently used as a component of web browsers, whose implementations
enable client-side scripts to interact with users, manage browser settings, communicate
asynchronously, and modify the displayed document content. Additionally, it is employed in
server-side programming, the creation of video games, and the development of desktop and
mobile applications. JavaScript is a dynamically typed, prototype-based programming
language with first-class functions. C had an influence on its syntax. Despite sharing many
names and naming conventions with Java, JavaScript is completely unrelated to Java and has
a significantly different semantic structure. JavaScript's primary architectural tenets were
inspired by the self and Scheme programming languages.t is a multiparadigm language,
supporting object-oriented, imperative, and functional programming styles.

iv. PHP: PHP is a server-side scripting language used for general-purpose programming as
well as web development. More than 244 million websites and 2.1 million web servers
currently use PHP. The PHP Group now produces the reference implementation of PHP,
which was first developed by Rasmus Lerdorf in 1995. PHP is a recursive backronym that
initially stood for Personal Home Page but is now known as PHP: Hypertext Pre-processor. A
web server's PHP processor module interprets the PHP code to produce the final web page:
Instead of contacting an external file to handle data, PHP commands can be directly included
into an HTML source document. It may now be used in independent graphical apps and has
expanded to incorporate a command-line interface capabilities. Free software known as PHP
is distributed under the PHP License. Most web servers support the free deployment of PHP,
which is also available as a standalone shell on practically all platforms and operating
systems.

BACK END: MySQL, which is used to construct databases I is utilized to design the back
end. MYSQL- MySQL, often known as "My S-Q-L" or "My Sequel," is the second-most
popular open-source relational database management system in the world as of July 2013.
(RDBMS).
It is named after My Widenius, the daughter of co-founder Michael Widenius. SQL, or
Structured Query Language, is the abbreviation. The MySQL development project has
released its source code under a number of private agreements as well as the GNU General
Public License. One for-profit corporation, the Swedish company MySQL AB, which is now
owned by Oracle Corporation, was both the owner and sponsor of MySQL.A crucial part of
the widely used LAMP open source web application software stack (and other "AMP"
stacks), MySQL is a well-liked database for usage in online applications. The term "Linux,
Apache, MySQL, Perl/PHP/Python" is referred to as LAMP. MySQL is frequently used in
free-software, open- source projects that need a robust database management system. There
are various paid editions that are available for commercial usage and provide more
capabilities. TYPO3, MODx, Joomla, WordPress, phpBB, MyBB, Drupal, and more
programs all use MySQL databases. Additionally, a lot of well-known, massive websites like
Wikipedia, Google (though not for searches), Facebook, Twitter, Flickr, and YouTube use
MySQL.

3.4 Requirement analysis

By examining the user's needs, the system requirements are gathered (s). Establishing the
functions that the ideal system must have is the focus of this phase. It does not, however,
influence the design or construction of the software. Typically, after interviewing the users, a
document known as the user requirements document is produced.

Figure 3.1: Requirement Analysis

The functional, interface, performance, data, security, and other needs of the system as
anticipated by the user will normally be described in the user requirements document.
Business analysts use it to explain to users how they should utilize the system. The users
carefully read
this document because it will act as the system designers' reference during the system design
process. In this stage, the user acceptance tests are created. There are various ways to obtain
requirements for both soft and hard approaches, including surveys, use cases, throw-away
prototypes, observation, document analysis, interviews, and questionnaires. Throughout the
remainder of the system development process, the requirement document will be consulted to
confirm that the project is evolving in accordance with the needs and requirements.

Systems engineers analyze and comprehend the business of the proposed system throughout
the systems design phase by examining the user requirements document. They come up with
options and methods for carrying out the user requirements. The user is made aware of the
problem if any of the requirements are not practical. Once a solution is identified, the user
requirement document is updated. A document called the software specification is created,
acting as a blueprint for the development stage. The general system organization, menu
structures, data structures, etc. are all contained in this paper. For enhanced understanding, it
might also include sample windows, reports, and business scenario examples. In this phase,
additional technical documentation will also be generated, such as entity diagrams and data
dictionaries. The system testing documentation is ready.

3.5 System Development and System Design

3.5.1 Architectural Design

High-level design is another name for the stage of designing a computer or software's
architecture. The fundamental criterion for choosing an architecture is that it should be able to
accommodate everything, which typically includes a list of modules, a brief description of
each module's functionality, their interface relationships, dependencies, database tables,
architecture diagrams, technology specifics, etc. The specific phase includes the integration
testing design. The necessary specifications for the hardware, software, human, data, and
information resource resources and the information products that will satisfy the functional
requirement of the proposed system can be identified once the requirements have been
established. Before these mistakes or issues are included into the system, the design will act
as a blueprint for it.
3.5.2 Context Flow Diagram

The environment in which the software used is depicted in this picture. The CFD shows the
external entity action on the software is shown here in CFD as a single process.

Figure 3.2: Context Flow Diagram

3.5.3 Data Flow Diagram

1. The DFD is also called as bubble chart. It is a simple graphical formalism that can be used
to represent a system in terms of input data to the system, various processing carried out on
this data, and the output data is generated by this system.

2. The data flow diagram (DFD) is one of the most important modelling tools. It is used to
model the system components. These components are the system process, the data used by
the process, an external entity that interacts with the system and the information flows in the
system.

3. DFD shows how the information moves through the system and how it is modified by a
series of transformations. It is a graphical technique that depicts information flow and the
transformations that are applied as data moves from input to output.

4. DFD is also known as bubble chart. A DFD may be used to represent a system at any level
of abstraction. DFD may be partitioned into levels that represent increasing information flow
and functional detail.
 Figure 3.3: Data Flow Diagram

3.5.3.1 Admin Data Flow Diagram

Figure 3.4: Admin Data Flow

3.5.3.2 User Data Flow Diagram

Figure 3.5: User Data Flow Diagram

3.5.4 ER Diagram

Figure 3.6: E-R Diagram

3.6 Database Design

3.6.1 Admin Table

CREATE TABLE `admin` (

`id` int(11) NOT NULL,
`FullName` varchar (100) DEFAULT NULL,
`AdminEmail` varchar (120) DEFAULT NULL,
`UserName` varchar (100) NOT NULL,
`Password` varchar (100) NOT NULL,
`updationDate` timestamp NOT NULL DEFAULT '0000-00-00 00:00:00' ON UPDATE
current_timestamp()
) ENGINE=InnoDB DEFAULT CHARSET=latin1;

ALTER TABLE `admin`

ADD PRIMARY KEY (`id`);

ALTER TABLE `admin`

MODIFY `id` int(11) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=2;

id Full name Admin email Username Password Updated at Created at

1 Admin [email protected] admin Password 2024-09-17 2024-09-17
m 12:30 9:30

Figure 3.7: Admin Table

3.6.2 Authors Table

CREATE TABLE `tblauthors` (

`id` int(11) NOT NULL,
`AuthorName` varchar(159) DEFAULT NULL,
`creationDate` timestamp NULL DEFAULT current_timestamp(),
`UpdationDate` timestamp NULL DEFAULT NULL ON UPDATE current_timestamp()
) ENGINE=InnoDB DEFAULT CHARSET=latin1;

ALTER TABLE `tblauthors`

ADD PRIMARY KEY (`id`);
ALTER TABLE `tblauthors`
MODIFY `id` int(11) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=16;

id AuthorName Creation Date Updated at

1 Ejike Michael 2024-09-17 12:30 2024-09-17 9:30

2 Mba Paschal 2024-09-17 12:30 2024-09-17 9:30

3 Kelvin John 2024-09-17 12:30 2024-09-17 9:30

4 Bishop Ken 2024-09-17 12:30 2024-09-17 9:30

5 G Godson 2024-09-17 12:30 2024-09-17 9:30

6 Celeb Mike 2024-09-17 12:30 2024-09-17 9:30

Figure 3.8: Author Table

3.6.3 Books Table

CREATE TABLE `tblbooks` (

`id` int(11) NOT NULL,
`BookName` varchar(255) DEFAULT NULL,
`CatId` int(11) DEFAULT NULL,
`AuthorId` int(11) DEFAULT NULL,
`ISBNNumber` varchar(25) DEFAULT NULL,
`BookPrice` decimal(10,2) DEFAULT NULL,
`bookImage` varchar(250) NOT NULL,
`isIssued` int(1) DEFAULT NULL,
`RegDate` timestamp NULL DEFAULT current_timestamp(),
`UpdationDate` timestamp NULL DEFAULT NULL ON UPDATE current_timestamp()
) ENGINE=InnoDB DEFAULT CHARSET=latin1;

ALTER TABLE `tblbooks`

ADD PRIMARY KEY (`id`);
 ALTER TABLE `tblbooks`
MODIFY `id` int(11) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=12;

id Bookname Cat Authorid ISBNumbe BookPrice Bookimage IsIsued Created at Updated

Id r at
1 physics 3 1 1111 1000 1.jpg 0 2024-09- 2024-09-
17 12:30 17 9:30
2 CSC 180 2 3 345688 3000 2.jpg 1 2024-09- 2024-09-
17 12:30 17 9:30
3 CSC 281 1 2 4223 4000 3.jpg NULL 2024-09- 2024-09-
17 12:30 17 9:30
4 CSC 480 1 1 222 6000 4.jpg NULL 2024-09- 2024-09-
17 12:30 17 9:30

Figure 3.9: Books Table

3.6.4 Books Category Table

CREATE TABLE `tblcategory` (

`id` int(11) NOT NULL,
`CategoryName` varchar(150) DEFAULT NULL,
`Status` int(1) DEFAULT NULL,
`CreationDate` timestamp NULL DEFAULT current_timestamp(),
`UpdationDate` timestamp NULL DEFAULT '0000-00-00 00:00:00' ON UPDATE
current_timestamp()
) ENGINE=InnoDB DEFAULT CHARSET=latin1;

ALTER TABLE `tblcategory`

ADD PRIMARY KEY (`id`);

ALTER TABLE `tblcategory`

MODIFY `id` int(11) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=10;
 ID CATEGORYNAME STATUS CREATIONDATE UPDATED AT
4 Finance 1 2024-09-17 12:30 2024-09-17 9:30
5 Science 1 2024-09-17 12:30 2024-09-17 9:30
6 General 1 2024-09-17 12:30 2024-09-17 9:30

Figure 3.10: Books Category Table

3.6.5 Issued Book Details Table

CREATE TABLE `tblissuedbookdetails` (

`id` int(11) NOT NULL,
`BookId` int(11) DEFAULT NULL,
`StudentID` varchar(150) DEFAULT NULL,
`IssuesDate` timestamp NULL DEFAULT current_timestamp(),
`ReturnDate` timestamp NULL DEFAULT NULL ON UPDATE current_timestamp(),
`RetrunStatus` int(1) DEFAULT NULL,
`fine` int(11) DEFAULT NULL
) ENGINE=InnoDB DEFAULT CHARSET=latin1;

ALTER TABLE `tblissuedbookdetails`

ADD PRIMARY KEY (`id`);

ALTER TABLE `tblissuedbookdetails`

MODIFY `id` int(11) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=13;

I BOOKI STUDENTI ISSUESDAT RETURNDAT RETURNSTATU FINE

D D D E E S
1 2 U20219/55 2024-09-17 NULL NULL NUL
12:30
L
2 3 U2019/88 2024-09-17 2024-09-17 9:30 1 0
12:30
3 3 U20219/100 2024-09-17 NULL NULL NUL
12:30
L
4 1 U2019/188 2024-09-17 2024-09-17 9:30 1 0
12:30

Figure 3.11: Issued Book Details Table

3.6.6 Students Table

CREATE TABLE `tblstudents` (

`id` int(11) NOT NULL,
`StudentId` varchar(100) DEFAULT NULL,
`FullName` varchar(120) DEFAULT NULL,
`EmailId` varchar(120) DEFAULT NULL,
`MobileNumber` char(11) DEFAULT NULL,
`Password` varchar(120) DEFAULT NULL,
`Status` int(1) DEFAULT NULL,
`RegDate` timestamp NULL DEFAULT current_timestamp(),
`UpdationDate` timestamp NULL DEFAULT NULL ON UPDATE current_timestamp()
) ENGINE=InnoDB DEFAULT CHARSET=latin1;

ALTER TABLE
`tblstudents` ADD
PRIMARY KEY (`id`),
ADD UNIQUE KEY `StudentId` (`StudentId`);

ALTER TABLE `tblstudents`

MODIFY `id` int(11) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=12;

I STUDENTID FULLNAME EMILID PHONE PASSWORD STATUS REGDATE UPDATED

D AT
1 U20219/55 Nwokeocha [email protected] 232443 12345678 1 2024-09-17 2024-09-17
Pascal 12:30 9:30
2 U2019/88 Kelvin Johan kel@gmail 244343 12345678 1 2024-09-17 2024-09-17
12:30 9:30
3 U20219/100 Peter Pass peter@gmailcom 422422 12345678 1 2024-09-17 2024-09-17
12:30 9:30
4 U2019/188 Ruth Mike [email protected] 53355 12345678 1 2024-09-17 2024-09-17
12:30 9:30

Figure 3.12: Students Table