ABSTRACT

Wildlife Park Management System is platform that is based on monitoring and controlling
activities of the Park in terms of tourism and travel. Before this time, people used to go to the
park before checking on the park, they often don’t find the chance to check and evaluate the park
they were going to visit before then. Even if they find chances to do so, they face many
difficulties such as: making bookings, communication issues and difficulties in determining
different information about that park so to put an end to this issue we thought of developing a
website that would attract a certain number of users based on their interests. The website was
developed to showcase various tour in the wildlife park. To make a superior stage for tourists, we
chose to make a visit site that associates them with the objective they're searching for. For this
site it's basically worked for visitors and tourists who needs to visit and travel in the park. The
main objective is to develop the web application system that will help Nyandungu Urban
Wetland Eco-Tourism Park to make business scheduling in safe and secured organization system
that allow them to be online and enables the visitor to access the portal anywhere and anytime.
The front-end will be assembled utilizing JavaScript, HTML and CSS while the back-end will be
kept up with by both PHP and MySQL.
 INTRODUCTION AND BACKGROUND TO THE STUDY

 1.1 Introduction

Wildlife animal’s park management system is very important in our digital world. Because as
days are coming everything is turning digital, so we must learn from everything and switch from
Analog to digital world.

Wildlife animal’s park management system is a web-based technology which manages people,
animal’s details and provides ticket to the person who come to visit in park with his/her family.
This web application provides a way to effectively control record and track the people who visit
Wildlife Park (Anuj, 2015).

The software system can store the data of people tickets that came to visit in the Park. The
system also maintains and calculates the price of ticket. The system needs administrator to input
the detail of ticket like how many are adult and how many are child and print ticket and give it to
visitor (Anuj, 2015).

Wildlife animal’s park management system is published online where the visitor will see Wildlife
park details like available animals in park and see price of ticket to visit Wildlife Animal Park.

 1.2 Background to the study

Europe is a continent consisting several countries, each with its own language and culture, so
there is no singular national animal. Instead, individual countries have chosen their own nation
animals. For example, the lion, the official national animal of the Netherland, Norway, and
England, represents bravery and courage (a-z, 2008).

While there is no specific national animal for Europe, itself, there are several species considered
as “the big 5,” seemingly the most impressive animals on the continent. The big 5 animals are the
European Bison, the lynx, the wolverine, the brown bear and the wolf (a-z, 2008).

Rwanda continues to be one of the fastest growing African countries in ICT and there are several
avenues for growth but many institutions are still serving as they did many years ago. Same
techniques are still being used whereas other sectors are migrating from manual to computerized
systems that are able to handle a big number of information and process them (Merriam, 2022).

Therefore, I have decided to design and implement “Wildlife Animal’s Management System”,
a system that digitalize and simplify the way tourism will book online and make trip to visit
Animals.

Wildlife Animals Park was actually started in ancient Egypt around 3000 years ago. Back then,
animals were used to show the wealth and power of a ruler, with Pharaohs demanding wild
animals be captured on their behalf (noahsarkzoofarm, 2014).

Nyandungu Urban Wetland Eco-Tourism Park is 134 hectares Rwandan Tourism Park located
between Gasabo and Kicukiro Districts which allows sustainable travel of people to enjoy
natural areas and wild animals in Nyandungu Valley (RDB, 2022).

 1.3 Statement of the problem

Nyandungu Urban Wetland Eco-Tourism Park has manual scheduling system and manual
reporting system which requires large physical space and not secure, no available contact
information online in order any visitor can contact them, not specific business hours are available
online, lack of easy way of sharing data among other facilities, it too hard to know

Animals details which are available for tourists who came abroad (news platform), to visit for
getting information at Nyandungu Urban Wetland Eco-Tourism Park physical place is time
consuming and finance unpredictable consumption. According to those problem an electronic
solution is needed to gather, validate, process, store, secure and scheduling online platform.

 1.4 Objectives of the study

The objectives of the study can be either general or specific. The general objectives talk about
what the system is generally here to do and. Specific objectives talk about details of them.

1.4.1 General Objectives

The General objectives is to develop the web application system that will help Nyandungu Park
to make business scheduling in safe and secured organization system that allow them to be
online.

1.4.2 Specific Objectives

1. To design a system that will increase the impact of tourist’s profitability of using digital
animal parks system
2. To create a system that will promote tourism sector in Rwanda
3. To develop a system that will help the park in terms of accessing their data and online
feed.
4. To generate reports.

 1.5 Scope of the study

1.5.1 Geographical Scope

Geographically the project research was conducted at Nyandungu Urban Wetland Eco-tourism
located between Gasabo and Kicukiro Districts, Address: 24VW+Q4, Kigali.

 1.5.2 Content Scope

Nyandungu Urban Wetland Eco-Tourism Park had a lot of research has been made in tourism
sector.it is very know field and needs comprehensive study and time to explore the difference
issues regarding implementation of web application. Limited time and resources has bound us to
focus on only one issue

that is exploration of problem and their solution before implementation of web application by
understanding their current working culture.
The result of this research contributed to the consideration that needs to be made, regarding
implementation of web application in Nyandungu Urban Wetland Eco-Tourism Park.

This research will be effective in understanding the web application implementation in

Nyandungu Urban Wetland Eco-Tourism Park because we have relied on social-technical model
for identifying the problems and their solutions before starting the web application
implementation. Social-technical model has helped us in identification of problems by keeping
social and technological issues because these issues can influence the success or failure of web
application implementation.

1.5.3 Time Scope

This project took approximately 6 months from December 2022 to May 2023 covering all the
stages of the development.

 1.6 Project methodology

In creation of this system we have used a waterfall model as the methodology that highly
emphasis on risk analysis. It allows incremental releases of the product or incremental
refinement through each iteration around the spiral.

Each of these Waterfall Model phases is corrected before finishing it if there is an error; this
enables the correction of that error before moving to the next phase.

Data collection can be gathered from the sources, such as the documents, the workplace and the
questionnaires.

We have used these data collection techniques because they are the ones that gave us an easier
approach to the correspondent and these techniques were more understandable and provided the
best accurate answers from the correspondents. These techniques are explained before with the
unique role and reason why they have been used.

The followings are techniques used in the analysis of the system:

Documentation
Documentation is the evidence provided for information and ideas borrowed from others. That
evidence includes both primary sources and secondary sources. We used documentation because
it is an easier way to know what people think with enough time to think about it and choose
according to their opinion of how they feel.

Interview

Is defined as a systematic conversation between an investigator (interviewer) and an informant

(interviewee), initiated for obtaining information relevant to a specific study. The interview is, in
a sense, an oral questionnaire. Instead of writing the response, the interviewee or subject gives
the needed information verbally in a face-to-face relationship. The interview method as a verbal
method is quite significant in securing data about all these aspects. This was used because we
wanted to get direct responses from the interviewee and become able to know how they
understand the question via face-to-face conversation.

 1.7. Interest in the project

1.7.1 Personal interest

This study will help the researcher to improve his knowledge in the IT and business fields, apply
the knowledge gained during the academic studies in real scenarios, and take part in solving 1

1.7.2 Institutional interest

The university will be proud to have students who are specialized in IT skills so that they can
contribute to the development of their home country by solving technical problems using skills

acquired from the university. The report of this study will be available in the university library
and will serve as a basis and guide future researchers and other academic references.

1.7.3 Public Interest

This book will be used by other students and other researchers in order to know how to write
their own books.
1.8 Limitations of the project

During research period, the researcher met different problems like lack of financial resources.
This problem delayed the start of data collection, which caused the extension of the period of
working on this project.

1.9 Organization of the project

Chapter One describes the origin of the idea of developing the system as the introduction.
Chapter Two refers to the project by defining its components according to the literature of
previous research works. Chapter Three focuses on the system analysis and design by describing
the methodology used in the development of the system. Chapter Four illustrates the
implementation of the system by describing different steps used to test the system. Therefore,
chapter five focuses on the conclusion made by the researcher referring to the new system and
recommendations to Nyandungu Park and future researchers.
 LITERATURE REVIEW

 2.0 Introduction

Before developing the information system, basic concepts must be illustrated for used. The
purpose of this chapter is to deal with theoretical concepts and fundamentals that support this
project. It provides an overview, which is clearly precise and concise main concept, as the
guideline for the selected technologies that will support the conception and development of this
project. It also expounds on technologies to be used with a view of providing an overview for the
concept of the system’s design, definition of technologies used and the comparative study
(Patrick, 2021).

 2.1 Definition of key concepts

2.1.1 Wildlife

Living things and especially mammals, birds, and fishes that are neither human nor domesticated
(Merriam, 2022).

2.1.2 Animal

A living thing that can move and eat and react to the world through its senses, esp. of sight and
hearing:

Mammals, insects, reptiles, and birds are all animals (Collins, 2022).

2.1.3 Park

Park is a public area of land with grass and trees, usually in a town, where people go in order to
relax and enjoy themselves (Collins, 2022).

2.1.4 System

A set of computer equipment and program used together for a particular purpose (Webopedia,
2021).
2.1.5 Tourism

Tourism is a social, cultural and economic phenomenon which entails the movement of people to
countries or places outside their usual environment for personal or business/professional
purposes (UNWTO, 2008).

2.1.6 Zoo

A zoo (short for zoological garden; also called an animal park or menagerie) is a facility in which
animals are housed within enclosures, cared for, displayed to the public, and in some cases bred
for conservation purposes (encyclopedia, 2020).

2.1.7 Database Concepts

2.1.7.1 Data

In computing, data is information that has been translated into a form that is efficient for
movement or processing. Relative to today's computers and transmission media, data is
information converted into binary digital form. It is acceptable for data to be used as a singular
subject or a plural subject. Raw data is a term used to describe data in its most basic digital
format. The concept of data in the context of computing has its roots in the work of Claude
Shannon, an American mathematician known as the father of information theory.

2.1.7.2 Database

A database is information that is set up for easy access, management and updating. Computer
databases typically store aggregations of data records or files that contain information, such as
sales transactions, customer data, financials and product information.

Databases are used for storing, maintaining and accessing any sort of data. They collect
information on people, places or things. That information is gathered in one place so that it can
be observed and analyzed. Databases can be thought of as an organized collection of
information. (Ben, 2015)
2.1.7.3 Relational database

A relational database is a (most commonly digital) database based on the relational model of
data. System used to maintain relational databases is a relational database management system
(RDBMS). Many relational database systems are equipped with the option of using the SQL
(Structured Query Language) for querying and maintaining the database. (Cood, 2012)

2.1.7.4 Database Management System

A database management system (DBMS) is system software for creating and managing
databases. A DBMS makes it possible for end users to create, protect, read, update and delete
data in a database. The most prevalent type of data management platform, the DBMS essentially
serves as an interface between databases and users or application programs, ensuring that data is
consistently organized and remains easily accessible. (Craig, 2018)

2.1.7.5 Database Security

Database security concerns the use of a broad range of information security controls to protect
databases (potentially including the data, the database applications or stored functions, the
database systems, the database servers, and the associated network links) against compromises of
their confidentiality, integrity, and availability. It involves various types or categories of controls,
(Stephens, 2018).

2.1.7.6 Review on Database design

Database Design is a collection of processes that facilitate the designing, development,

implementation, and maintenance of enterprise data management systems. Properly designed
databases are easy to maintain, improve data consistency, and are cost-effective in terms of disk
storage space. The database designer decides how the data elements correlate and what data must
be stored. The main objectives of database designing are to produce logical and physical designs
models of the proposed database system.
The logical model concentrates on the data requirements and the data to be stored independent of
physical considerations. It does not concern itself with how the data will be stored or where it
will be stored physically. The physical data design model involves translating the logical design
of the database onto physical media using hardware resources and software systems such as
database management systems (DBMS) (Cood, 2010)

2.1.7.8 Fast and reliable interface

A user-friendly interface is simply a program that the user considers a friend instead of an enemy.
As programmers, we encounter a large number of tools, utilities, and other programs. Some are a
joy to use, others are a nightmare, with obscure and complex command sets (Amj, 2009)

2.1.7.9 Characteristics of Successful User Interfaces

Dickson (1998) said that the successful user interface should have the following characteristics:

Clear: Clarity is the most important element of user interface design. Indeed, the whole purpose
of user interface design is to enable people to interact with the system by communicating
meaningfully and function.

Concise: Keep things clear, but also keep things concise, when you can explain a feature in one
valuable time of your users by keeping things concise. Keeping things clear and concise at the
same time isn’t easy and takes time and effort to achieve, but the rewards are great.

Familiar: Many designers strive to make their interfaces ‘intuitive’. But what does intuitive
mean? It means something that can be naturally and instinctively understood and comprehended.
But how can you make something intuitive? You do it by making it ‘familiar’. Identify things
that are familiar to your users and integrate them into your user interface.

Responsive: Responsive means a couple of things. First, responsive means fast. Seeing things
load quickly, or at the very least, an interface that loads quickly improves the user experience.

Consistent: Consistent interfaces allow users to develop usage patterns, they’ll learn what the
different buttons, tabs, icons, and other interface elements look like and will recognize them and
realize what they do in different contexts. They will also learn how certain things work and will
be able to work out how to operate new features quicker, extrapolating from those previous
experiences.

Attractive: This one may be a little controversial, but I believe a good interface should be
attractive. Attractive in the sense that it makes the use of that interface enjoyably. Yes, you can
make your UI simple, easy to use, efficient and responsive, and it will do its job well

Efficient: A good interface should allow you to perform those functions faster and with less
effort. Now, ‘efficient’ sounds like a vague attribute.

Forgiving: A forgiving interface can save your users from costly mistakes. For example, if
someone deletes an important piece of information, can he easily retrieve it or undo this action?

2.1.8 Report

A report is a document that presents information in an organized format for a specific audience
and purpose. Although summaries of reports may be delivered orally, complete reports are
almost always in the form of written documents. In modern business scenario, reports play a
major role in the progress of business. Reports are the backbone to the thinking process of the
establishment and they are responsible, to a great extent, in evolving an efficient or inefficient
work environment. (Ponam, 2016)

 2.2 Related work

The Animal Adventure Park

Animal Adventure is designed to promote up close and hands-on animal encounters! Hand feed
many domestic and exotic animal ambassadors and get within feet of our cute, but less cuddly,
carnivores. Bring your camera, but keep one hand open, to feed and make friends, with animals
from around the world. Be sure to visit our EVENTS page on our site to learn about special
offerings, and consider following us on Facebook and our other social media platforms to stay
current with park happenings and announcements. We cannot wait to reopen and welcome you
back for many adventures and memory making in 2023! (Animaladventurepark, 2023)

The Yorkshire Wildlife Park

Yorkshire Wildlife Park was officially opened by Justin Fletcher, MBE on 4 April 2009.
In February 2010, the park rescued 13 lions from living in very poor conditions in a dilapidated
Romanian zoo and released them into the newly built 10-acre Lion Country enclosure.
In 2011, Land of the Tigers was opened, with pools and waterfall built next to a vast wetland
reserve.
In March 2012, Leopard Heights opened as one of the largest leopard reserves in the world.
July 2014 saw the opening of Project Polar, with the first bear being 500 kg male Victor; a
second arrived in March 2015 called Pixel; Victor's grandson.
In 2018 the park rescued four Brown Bears from some Japanese museums. Riku and his brother
Kai, along with Amu and Hanako, were rescued from a tourist attraction on the island of
Hokkaido. Yorkshire Wildlife Park took them from tiny cages, concrete floors and school dinner
scraps to a huge grassy reserve, lakes, toys, hay beds and shelters. (YWP, 2023)

In 2018, Yorkshire Wildlife Park also saw planning permission granted for the development of a
new 150-acre site at YWP. 3 years later in 2021 the development was complete and opened to
the public, bringing more ground-breaking animal reserves and new species to the park. The
brand-new Sea Lion reserve opened featuring two naturalistic lakes, with one holding an
incredible 1.9 million liters of filtered water making it the largest purpose-built habitat of its kind
in the world! (YWP, 2023)

The Woburn Safari Park

Woburn Safari Park is a wild animal park, set in over 300 acres of beautiful parkland. Home to
around 1,000 wild and exotic animals, and the perfect day out for animal encounters and visiting
wonderful wildlife. As a multi award-winning visitor attraction, Woburn makes a valuable
contribution to conservation, and is a place where families can enjoy being together, seeing
animals in a beautiful natural environment. Your admission ticket includes unlimited repeat
circuits of the Road Safari drive through reserves, followed by adventures in the Foot Safari.
Most of the leisure activities at Woburn Safari Park are included in your great value ticket price.
(Woburnsafari, 2023)
 SYSTEM ANALYSIS AND DESIGN

3.1. Introduction
According to (Dr. Jawahar, 2012) in business context, System Analysis and Design refers to the
process of examining a business situation with the intent of improving it through better
procedures and methods in business. System analysis and design relates to shaping organizations,
improving performance and achieving objectives for profitability and growth. The emphasis is
on systems in action, the relationships among subsystems and their contribution to meeting a
common goal.
System design in software development is the process of defining the architecture, components,
modules, interfaces, and data for a system to satisfy specific requirement. System design is done
from the study of the existing system in order to determine what changes will be needed to
incorporate the user needs that were not met by the existing one. The output of this phase will
consist of the specifications, which must describe both what the proposed system will do and
how it will work actually defining the solutions. (Douglas, 2015)
3.2. Analysis of the current system
The existing Nyandungu Park has no automation. All the work is done manually. Existing
system has many flaws such as in existing system, the tourists came to physical office and get
detail also pay by hand money without any technology existing system takes a lot of time. Also
the time taken is very much for tourists.

3.2.1. Problem of the current system

 Time consuming to make reports.
 Use of classic payment system: cash payment.
 It can result to the falsification of history transactions.
 Untrustworthy reports.
 Loss of data.
 Difficult for tourists to find the park and visit it.
3.3. Analysis of the new system
3.3.1. Introduction
Wildlife park management system effectively manages and handles all the functioning of a park.
The software system can store the data of people tickets that came to visit in the park. The
system also maintains and calculates the price of ticket. The system needs an administrator to
input the detail of ticket like how many are adult and how many are child and print the ticket and
give it to person.

3.3.2. System requirement

Functional requirements
Function requirement define the capabilities and function that a system must be able to perform
successfully.
The functional requirements of this system include.

 The system allows tourists to make booking

 The system allows the admin to register animal detail.
 The system allows admin to schedule work
 The system allow admin to make report
 The system allow admin view the booking
Administrative requirements:
System provides daily report of recorded members, transactions and payments.
System provides also monthly report and annual report.
System requirements:
Recommended browser: Chrome browser 55 or higher, Internet explorer 9 or higher, Microsoft
edge 40 or higher, Safari 10 or higher, Firefox 49 or higher
OS: Windows 7 or higher, MacOS 10.6 or higher, 64 bit Ubuntu 14.04+, Debian 8+, Fedora
Linux 24+
Processor: Intel Pentium 4 or later and Intel for macOS
Memory: 2GB minimum, 4GB (recommended)
Screen resolution: 1280x680 or larger
Application windows: 1024x680 or larger
Internet connection: Required
Non-functional requirement
“Non-functional requirement is any requirement that specifies how the system performs a certain
function. It is a requirement that specifies criteria that can be used to judge the operation of a
system, rather than specific behaviors. They are contrasted with functional requirements that
define specific behavior or functions. The plan for implementing functional requirements is
detailed in the system design. The plan for implementing non-functional requirements is detailed
in the system architecture, because they are usually architecturally significant requirements.”
(Warden.M, 2012)
The non-functional requirements for OMCIMS are:
Maintainability:
The system should be maintainable when needed
Security
The system will encrypt the user’s information in transit or at rest
Operational:
The system will run on any OS.
The system will be responsive.
Maintainability:
The system should be maintainable when needed
User friendly:
The System will have user friendly interface
The system will be easy to use for any user.
Privacy:
The system should be able to protect the user’s privacy
Availability:
The system will have high availability of 99.999%
The system will not have unexpected downtime
The system should have downtime at most 1 hour per year
Performance:
The system will work well under a fast internet and system requirements
The function diagram describes all activities that can be executed by each user. It gives us a
snapshot of all functions of the system and the user who can perform these tasks.

A functional block diagram, in systems engineering and software engineering, is a block

diagram. It describes the functions and interrelationships of a system

Hardware requirements

i. Hard disk (HD): This system will be installed in a computer that has at least 10GB of
free space before installation and 100 GB on hard disk after installation.
ii. Processor: Inter(R) Core (TM) Intel Pentium CPU G4400 @ 3.30GHz (4CPUs), -
3.31GHz.
iii. Memory (RAM): This system will be installed in a computer that has at least 2GB of
RAM.
iv. External hard disk: This system will be carried on a flash disk that has at least 4GB of
free space.

Software requirements

I. Operating system: Windows 7, 8 and10.

II. Language: Html, Bootstrap 4, PHP, MySQL and JavaScript
III. In order to achieve our objective, several functions need to be realized. Some are required
for the tourist other for the admin.

Software user requirement analysis

Serial Function type Function name Function description

number
1 tourist management Registered tourist Add a new tourist

Edit tourist info Modify tourist information

Login Log into the system using

username and password
Booking Reservation of the place or animal
you want to visit
 Logout Logout, close the tourist session

2 Admin management register animal detail Animals available, animals name,

animals type, etc…
schedule work Organize the day work

make report Summarize the work done

view the booking Check the reservations done

Table 1 Software requirement analysis

3.3.4. Methodological Approach

3.3.4.1 Data collection techniques

Interview

An interview is a procedure designed to obtain information from a person through oral responses
to oral inquiries. An interview is the way of face to face conversation between the interviewer
and the interviewee, where the interviewer seeks replies from the interviewee for choosing
potential human resources (Garly, 2019)

The researcher used the interview to collect the information of the current system in use
Nyandungu Eco Tourism Urban Park and get their suggestion for the new system that can be
used by the park.

Observation

A way to gather data by watching people, events, or noting physical characteristics in their
natural setting. Observations can be overt (subjects know they are being observed) or covert (do
not know they are being watched). Observation as a data collection method can be structured or
unstructured. In structured or systematic observation, data collection is conducted using specific
variables and according to a pre-defined schedule. Unstructured observation, on the other hand,
is conducted in an open and free manner in the sense that there would be no pre-determined
variables or objectives.

The researcher observed the way the data is treated, managed and stored by the staff of
Nyandungu Park and how they make different reports. We also observed the payment process.

Documentation

In a report or research paper, documentation is the evidence provided for information and ideas
borrowed from others. That evidence includes both primary sources and secondary sources. It is
conducted in order to study issues that have developed over a specific period of time and retrieve
comprehensive information. (Dudovskiy, 2014)

The researcher visited different websites, read books and other previous works related to this
study to get an understanding of this research and get a view of the proposed system. This tool
helped him to conceptualize and structure the communication of components of the new system.

3.3.4.2 Software Development Methodology

A software development methodology is a way of managing a software development project.

This typically addresses issues like selecting features for inclusion in the current version, when
the software will be released, who works on what, and what testing is done. No one methodology
is best for all situations. Even the much-maligned waterfall method is appropriate for some
organizations. In practice, every organization implements its software development project
management in a different way, which is often slightly different from one project to the next.
(Sam, 2017)

Nonetheless, nearly all are using some subset or combination of the ones discussed here.
Choosing an appropriate management structure can make a big difference in achieving a
successful end result when measured in terms of cost, meeting deadlines, client happiness, the
robustness of the software, or minimizing expenditures on failed projects. As such, it is worth
your time to learn about a number of these and make your best effort to choose wisely.
SPIRAL MODEL

The spiral model combines the idea of iterative development with the systematic, controlled
aspects of the waterfall model. This Spiral model is a combination of the iterative development
process model and sequential linear development model i.e. the waterfall model with a very high
emphasis on risk analysis. It allows incremental releases of the product or incremental
refinement through each iteration around the spiral. (Barry.B. & Peter.M., 2013)

Spiral Model – Design: The spiral model has four phases. A software project repeatedly passes
through these phases in iterations called Spirals.

Identify Objectives: This phase starts with gathering the business requirements in the baseline
spiral. In the subsequent spirals as the product matures, identification of system requirements,
subsystem requirements, and unit requirements are all done in this phase. This phase also
includes understanding the system requirements by continuous communication between the
customer and the system analyst. At the end of the spiral, the product is deployed in the
identified market.

Perform risk analysis: perform and risk analysis phase starts with the conceptual design in the
baseline spiral and involves the architectural design, logical design of modules, physical product
design, and the final design in the subsequent spirals.

Develop and test: Develop and tests phase refers to the production of the actual software
product at every spiral. In the baseline spiral, when the product is just thought of and the design
is being developed a POC (Proof of Concept) is developed in this phase to get customer
feedback. Then in the subsequent spirals with higher clarity on requirements and design details a
working model of the software called to build is produced with a version number. These builds
are sent to the customer for feedback.

Review and evaluate: Review and evaluate includes identifying, estimating, and monitoring the
technical feasibility and management risks, such as schedule slippage and cost overrun. After
testing the build, at the end of the first iteration, the customer evaluates the software and provides
feedback. The following illustration is a representation of the Spiral Model, listing the activities
in each phase.
Figure 1: Spiral Model

 Changing requirements can be accommodated;

 Allows extensive use of prototypes;

 Requirements can be captured more accurately;
 Users see the system early;
 Development can be divided into smaller parts and the risky parts can be developed earlier
which helps in better risk management.

The disadvantages of the Spiral SDLC Model are as follows −

 Management is more complex.

 The end of the project may not be known early.
 Not suitable for small or low-risk projects and could be expensive for small projects.
 The process is complex.
 Spiral may go on indefinitely.
 A large number of intermediate stages requires excessive documentation

3.3.4.3 System Analysis and Design Methodology

Structured Systems Analysis and Design Method (SSADM) is a set of standards developed in
the early 1980s for systems analysis and application design widely used for government
computing projects in the United Kingdom. SSADM uses a combination of text and diagrams
throughout the whole life cycle of a system design, from the initial design idea to the actual
physical design of the application. (Simon, 2020)

SSADM uses a combination of three techniques:

Logical Data Modeling: the process of identifying, modeling and documenting the data
requirements of the system being designed. The data is separated into entities (things about
which a business needs to record information) and relationships (the associations between the
entities. (Black, 2013)

Data Flow Modeling: the process of identifying, modeling and documenting how data moves
around an information system. Data Flow Modeling examines processes (activities that
transform data from one form to another), data stores (the holding areas for data), external
entities (what sends data into a system or receives data from a system, and data flows (routes by
which data can flow). (Ginapalao.C&Peter.M, 2012)

Entity Behavior Modeling: the process of identifying, modeling and documenting the events
that affects each entity and the sequence in which these events occur. (Shannon, 2022)

 Dataflow Diagram

A Data Flow Diagram (DFD) is a graphical representation of the "flow" of data through an
information system. A data flow diagram can also be used for the visualization of data
processing (structured design). It is common practice for a designer to draw a context-level

DFD first, which shows the interaction between the system and outside entities. This context-
level DFD is then explored to show more details of the system that is being modeled.

The DFD has the following four components:

Entities - Entities are source and destination of information data. Entities are represented by a
rectangle with their respective names.
Process - Activities and action taken on the data are represented by Circle or Round-edged
rectangles.

Data Storage - There are two variants of data storage - it can either be represented as a
rectangle with absence of both smaller sides or as an open-sided rectangle with only one side
missing.

Data Flow - Pointed arrows show Movement of data. Data movement is shown from the base
of arrow as its source towards head of the arrow as destination.

Context diagram / Data Flow Diagram Level 0

The context diagram provides the overview of the data entering and movement out in the system.
It shows graphic representation of entities and system where entities are people that are
interacting with the system. The diagram in shape of ellipse is external entities and rectangle
represents system.

This sample shows the Data Flow Model Diagram of the Wildlife Park management system and
interactions of

Figure 2 Data Flow Diagram Level 0

This figure defines the boundary between the system, or part of a system, and its environment,
by showing the entities that interact with it, this diagram is a high level view of a system.

Data Flow Diagram Level 1

Level 1 is the child diagram of the context diagram or level 0. In this level input are shown and
outputs also and external entities with the corresponding process boxes and also the data stored
describe the main functional areas that represent the boundary of system.

This is the level 1 data flow diagram showing the processes without their description in details
and it shows also arrows representing the flow of data and their corresponding data store and
external entities. i.e. the child representation of the system to be developed without entering in
details of what are its constitutional sub processes inside a process.

Figure 3: Data Flow Diagram Level 1

This figure shows the whole system represented as a single process. A level 1 DFD notates each
of the main sub-processes that form together the complete system

This figure also it shows how different users are recording information in system and it shows
where that information’s are being stored in database

 Entity Relationship Diagram (ERD)

An entity relationship model, also called an entity-relationship (ER) diagram, is a graphical

representation of entities and their relationships to each other, typically used in computing about
the organization of data within databases or information systems.

According to Chen, Peter (2002), An Entity –Relationship model (ER model for short) is an
abstract way to describe a database. It usually starts with a relational database, which stores data
in tables. Some of the data in these tables point to data in other tables - for instance, your entry in
the database could point to several entries for each of the phone numbers that are yours.

The ER model would say that you are an entity, and each phone number is an entity, and the
relationship between you and the phone numbers is 'having a phone number'. Diagrams created
to design these entities and relationships are called entity-relationship diagrams or ER diagrams
Figure 4Entity Relationship Diagram
 Use Case Diagram

Use case diagram: A Use case is a description of set of sequence of actions. Graphically it is
rendered as an ellipse with solid line including only its name. Use case diagram is a behavioral
diagram that shows a set of use cases and actors and their relationship. It is an association
between the use cases and actors. An actor represents a real-world object. Primary Actor –
Sender, Secondary Actor Receiver.
Figure 5 Use case diagram

 Data dictionary

A data dictionary contains metadata i.e. data about the database. The data dictionary is very
important as it contains information such as what is in the database, who is allowed to access it,
where is the database physically stored etc. The customers of the database normally don't
interact with the data dictionary; it is only handled by the database administrators.

Table 2: Admin detail

Field Name Data type Constraints Description

ID int(30) Not null Table for ID number

AdminName varchar(120) Not null Table admin name field

UserName varchar(120) Not null Table username name field

Email varchar(120) Not null Table email field

Password varchar(120) Not null Table admin password field

Table 3 Booking detail

Field Name Data type Constraints Description

Booking_id int(12) Not null Table booking identification field

firstname varchar(255) Not null Table user first name field

lastname varchar(255) Not null Table user last name field

Email varchar(255) Not null Table user email field

Nationality Varchar(255) Not null Table user nationality field

N0 adult Varchar(255) Not null Table adult number field

N0 child Varchar(255) Not null Table child number field

date Date Not null Table booking date created field

Table 4: Animal detail

Field Name Data type Constraints Description

Id int(10) Not null Table animal identification field

Animal_name varchar(200) Not null Table animal name field

Cage_number Int(10) Not null Table cage number field

Feed_number varchar(200) Not null Table feed number field

Breed Varchar(200) Not null Table breed field

Animal_image Varchar(200) Not null Table animal image field

Description mediumtext Not null Table description field

CreationDate timestamp Not null Table user date created field

Table 5: Ticket type

Field Name Data type Constraints Description

Id int(10) Not null Table ticket identification field

Ticket_type varchar(200) Not null Table ticket type field

Price varchar(50) Not null Table price field

Creationdate timestamp Not null Table date field

Table 6 Page table

Field Name Data type Constraints Description

Id int(10) Not null Table page identification field

page_type varchar(200) Not null Table page type field

page_description varchar(200) Not null Table page description field

Email varchar(70) Not null Table Email field

MobileNumber Number Not null Table mNumber field

updatedate timestamp Not null Table date field

Table 7 Table Local

Field Name Data type Constraints Description

Id int(10) Not null Table local identification field

ticketid varchar(200) Not null Table page type field

Visitor name varchar(200) Not null Table page description field

Numberadults varchar(70) Not null Table Email field

NumberChildren Varchar(30) Not null Table nchild field

MobileNumber Number Not null Table mNumber field

Adultunitprice Varchar(50) Not Null Table Price field

Childunitprice Varchar(50) Not Null Table Price field

visitdate timestamp Not null Table date field

Table 8 Foreigner Table

Field Name Data type Constraints Description

Id int(10) Not null Table Foreigner identification field

ticketid varchar(200) Not null Table page type field

Visitor name varchar(200) Not null Table page description field

Numberadults varchar(70) Not null Table Email field

NumberChildren Varchar(30) Not null Table nchild field

MobileNumber Number Not null Table mNumber field

Adultunitprice Varchar(50) Not Null Table Price field

Childunitprice Varchar(50) Not Null Table Price field

visitdate timestamp Not null Table date field

 SYSTEM IMPLEMENTATION

 4.1Testing

4.2 Introduction