Certificate

This is to certify that the following group of Name students, from the Information Technology
Department have successfully completed their final three years project titled as Dsign and
implementation of cold storage management system and hereby given all necessary privileges
and authorities by Horseed International University with full support to fulfill their degree
requirements under the supervision of Eng:.Ibraahim Faarah Hilowle (Lecturer) and with the
approval of IT Department.

Names of students:

1.Maxamed Xasan Shiiqeey

2. Abdimalika sayidali mohamud
3.Mukhtar aweys kadar

NB: Any alteration renders this certificate invalid.

Dean, Faculty Of CS&IT Project Supervisor

_______________ _________________

Date: 10/Dec/2023
Website: www.hiu.edu.so Mogadishu - Somalia
 Chapter One

1.0 : INTRODUCTION

Cold Storage Management System plays a crucial role in preserving the quality
and extending the shelf life of perishable goods in various industries, including
agriculture, pharmaceuticals, food processing, and logistics. This chapter serves
as an introduction to the book, providing a comprehensive overview of the
subject and setting the context for the subsequent chapters.
Cold storage refers to the storage of goods at controlled temperature and
humidity conditions to prevent spoilage, maintain product integrity, and ensure
consumer safety. With the increasing demand for perishable goods worldwide,
the efficient management of cold storage facilities has become paramount.
In this introductory section, we will explore the fundamentals of cold storage
management, including the challenges faced and the importance of adopting
effective strategies and technologies. By understanding the key principles and
best practices in this field, businesses can optimize their operations, minimize
wastage, and meet the ever-growing demands of the market.
Throughout this book, we will delve into the intricacies of managing cold storage
facilities, covering topics such as inventory control, temperature monitoring,
equipment selection, quality assurance, and energy efficiency. By acquiring a
comprehensive understanding of these aspects, readers will be equipped to make
informed decisions, streamline their processes, and achieve desired outcomes in
their cold storage operations.
1.1 : BACKGROUND OF THE SYSTEM

The concept of cold storage dates back centuries, with ancient civilizations
employing various techniques to preserve perishable goods. However, the
development of dedicated cold storage facilities and the modernization of cold
storage management systems have significantly evolved over time.
The need for efficient cold storage management arose from the growing demand
for preserving and transporting perishable goods across long distances. In the
mid-19th century, the advent of refrigeration technology revolutionized the cold
storage industry. The invention of mechanical refrigeration systems by pioneers
like Dr. John Gorrie and Carl von Linde paved the way for controlled
temperature storage, enabling food suppliers, pharmaceutical companies, and
other industries to extend the shelf life of their products.
Over the years, cold storage facilities have become more advanced and
specialized. Today, they encompass a range of storage options, including
refrigerated warehouses, cold rooms, blast freezers, and transport containers.
These facilities employ sophisticated technologies to create and maintain precise
temperature and humidity conditions, ensuring optimal storage conditions for
different types of perishable goods.
The growth of the cold storage industry is closely linked to the expansion of
global trade and the increasing demand for fresh produce, frozen food,
pharmaceuticals, and other temperature-sensitive products. Cold storage
facilities now play a vital role in supporting supply chains and enabling the
availability of perishable goods year-round, regardless of geographic limitations.

Moreover, advancements in cold storage management systems have been driven

by the need for improved inventory control, traceability, and quality assurance.
Effective management of cold storage facilities involves considerations such as
proper organization of goods, accurate temperature monitoring, efficient
inventory rotation, and adherence to regulatory standards.
In recent years, the industry has witnessed notable developments in cold storage
technologies and practices. These include the integration of Internet of Things
(IoT) sensors for real-time monitoring, data analytics for predictive maintenance
and inventory optimization, and cloud-based software solutions for seamless
information management.
Understanding the historical background and evolution of cold storage
management systems provides valuable insights into the industry's progress and
sets the foundation for comprehending the complexities and advancements
discussed in this book.
1.2 : PROBLEM OF THE STATEMENT

Generally, all information regarding to the cold storage information of the

Kalkaal Hospital are done manually. It is becoming a challenge for Kalkaal
Hospital to manage that data in an effective way and it is very difficult for
Kalkaal Hospital to manage orders in effective and efficient manner.
Moreover, Kalkaal Hospital do not have any environment to corporate with
their employee in easy manner and all the operations managing are being done
manually, whereas data of every customer stored in different places or papers
and that loses more time to get small information. Moreover, when customers
need to request specific service or information about cold storage they must
come the center of the company, in order to get the information, they need.
However, the exits system do not helps both the company and the customers.
All orders are manage using different papers and all information regarding one
order is stored in different files. Currently in Kalkaal Hospital, the workflow
followed is not very efficient due to lack of Software and digital media usage.

1.3 : PURPOSE OF THE PROJECT

The purpose of this project is to develop a comprehensive understanding of

cold storage management systems and provide practical insights and solutions
to address the challenges in this field. By examining the existing practices,
technologies, and strategies employed in cold storage facilities, this project
aims to contribute to the improvement of overall operational efficiency,
product quality, and sustainability.
 1.4 : PROJECT OBJECTIVES

The objectives of this project are as follows:

1 Explore and analyze the current state of cold storage management systems,
including challenges, trends, and technological advancements.
2 Identify and discuss key factors that impact the efficiency, quality, and
sustainability of cold storage operations.
3 Provide practical insights, strategies, and recommendations to enhance inventory
management, temperature control, quality assurance, and energy efficiency in
cold storage facilities.

1.5 : PROJECT SCOPE

1- Time scope of the project started September 2023 up to August 2024

2- Content of scope will be cold storage management system by

developing system php as front end and MYSQL server as back end.

3- Geographical scope : The study was conduct in wadajir district

mogadishu because our resident and also will be easily conduct
information
 1.6 : SIGNIFICANCE OF THE PROJECT

The project on cold storage management holds significant importance for various
stakeholders in the industry. The following points highlight the significance of this
project:
1. Industry Impact: Cold storage facilities play a critical role in ensuring the
availability of perishable goods year-round. By addressing the challenges and
providing practical solutions, this project can significantly impact the operational
efficiency, product quality, and sustainability of cold storage operations.
Improved management practices can lead to reduced waste, enhanced inventory
control, and optimized energy consumption, thereby benefiting businesses and the
overall industry.
2. Consumer Safety and Satisfaction: Proper cold storage management is crucial to
maintaining the quality and safety of perishable goods. By emphasizing quality
assurance protocols, regulatory compliance, and best practices, this project
contributes to ensuring consumer safety and satisfaction. It helps businesses
uphold their reputation and build trust with consumers by delivering high-quality
products that meet regulatory standards.
3. Cost Reduction and Efficiency: Inefficient cold storage management can result in
increased costs due to product spoilage, energy consumption, and inventory
mismanagement. By providing insights and recommendations for improved
inventory control, temperature monitoring, and energy efficiency, this project can
help businesses reduce costs, streamline operations, and enhance overall
efficiency.
1.7 : Report organization

In this research, it is organized chapters as follows:

Chapter One: describes an introduction and background of online

customer complain information system. Furthermore, this chapter will
cover the objectives, scope as well as significance of the study and how
the project was organized.
Chapter Two: This chapter also discusses the introduction of relevant
literature of design and implementation of an online customer complain
information system with listing concepts and opinions from experts or
authors.
This chapter deals with previous work or existing systems.

Gab analysis will be displayed using tabulated form.

Chapter Three: Defines how the data collected, analyzed, how the
interview has been done and the finding of the analyzed data and also the
chapter will discuss how the system was analyzed using UML (use case
diagram). Chapter Four: Proposes the design and implementation of an
online customer complain information system in details using Entity
Relationship Diagram (ERD), Database design, table design and form
design.
Chapter Five: is the last phase of the project and describes the
implementation of this project and testing it to produce complete
functioning system. Chapter Six: Finally, this chapter provides
conclusion and recommendations by describing the strengths and
achievements of the projects. This chapter also gives the weaknesses of
the design and implementation of an online customer complain
information system and its future enhancements.
 Chapter two

(Literature review)

2.0 : Introduction

This chapter aims to explore existing research, scholarly articles, industry

reports, and best practices related to cold storage management. The literature
review serves as a foundation for understanding the current state of knowledge
in the field, identifying gaps, and examining key trends and advancements.
The detailed literature review covers various topics within cold storage
management. It begins by examining the principles of cold storage, including
temperature control, humidity management, and the cold chain. The review
explores research on the impact of temperature fluctuations, packaging
considerations, and challenges in maintaining optimal storage conditions.
Furthermore, the literature review delves into inventory management, including
tracking systems, rotation strategies, and optimization techniques. It investigates
best practices in inventory management, such as demand forecasting and the use
of technology for real-time monitoring.
Regulatory compliance is another area explored in the literature review,
examining industry standards, certifications, and quality control protocols. The
review also covers energy efficiency and sustainability practices in cold storage,
including energy-saving technologies and renewable energy integration.
Additionally, the literature review investigates technological advancements, such
as the Internet of Things (IoT), data analytics, and cloud computing, which have
the potential to transform cold storage operations.

Figure 2. 1 Literature Review Map

2.1 : Theoretical and Conceptual Development

This section will discuss the concepts of design, implementation,

Cold, storage, management and system.

Design

Software design is a process to transform user requirements into some

suitable form, which helps the programmer in software coding and
implementation. For assessing user requirements, an SRS (Software
Requirement Specification) document is created whereas for coding and
implementation, there is a need of more specific and detailed requirements
in software terms. The output of this process can directly be used into
implementation in programming languages.

Software design is the first step in SDLC (Software Design

Life Cycle), which moves the concentration from problem
domain to solution domain. It tries to specify how to fulfill the
requirements mentioned in SRS.

Implementation

Implementation is the carrying out, execution, or practice of a plan, a

method, or any design, idea, model, specification, standard or policy for
doing something. As such, implementation is the action that must
follow any preliminary thinking in order for something to actually
happen.
 In an information technology (IT) context, software or hardware
implementation encompasses all the post-sale processes involved in
something operating properly in its environment, including analyzing
requirements, installation, configuration, customization, running, testing,
systems integrations, user training, delivery and making necessary
changes. The word "deployment" is sometimes used to mean the same
thing.

Cold

Is the sensation produced by loss of heat from the body, as by contact with
anything having a lower temperature than that of the body.

Storage

Storage is a process through which digital data is saved within a data

storage device by means of computing technology. Storage is a mechanism
that enables a computer to retain data, either temporarily or permanently.
Storage devices such as flash drives and hard disks are a fundamental
component of most digital devices since they allow users to preserve all
kinds of information such as videos, documents, pictures and raw data.
Storage may also be referred to as computer data storage or electronic data
storage.
Management

Management is how businesses organize and direct workflow,

operations, and employees to meet company goals. The primary goal of
management is to create an environment that lets employees work
efficiently and productively. A solid organizational structure serves as a
guide for workers and establishes the tone and focus of their work..

System

The definition of a system is a set of rules, an arrangement of things,

or a group of related things that work toward a common goal. An
example of a system are the laws and procedures of a democratic
government. An example of a system is the way someone organizes
their closet

A system is a collection of elements or components that are

organized for a common purpose. The word sometimes describes the
organization or plan itself (and is similar in meaning to method, as
in "I have my own little system") and sometimes describes the parts
in the system (as in "computer system").
PHP

PHP: Hypertext Preprocessor) an extremely popular scripting language

that is used to create dynamic Web pages. Combining syntax from the
C, Java and Perl languages, PHP code is embedded within HTML pages
for server side execution. It is commonly used to extract data out of a
database on the Web server and present it on the Web page. Originally
known as "Personal
Home Page," PHP is supported by all Web servers and widely used with
the MySQL database

MYSQL

MySQL, is the most popular Open Source SQL database management

system, is developed, distributed, and supported by Oracle Corporation.
A database is a structured collection of data. It may be anything from a
simple shopping list to a picture gallery or the vast amounts of
information in a corporate network. To add, access, and process data
stored in a computer database, you need a database management system
such as
MySQL Server. Since computers are very good at handling large
amounts of data, database management systems play a central role in
computing, as standalone utilities, or as parts of other applications.
2.2 Case study of the research

Kalkaal hospital is Located within the heart of Mogadishu along the Digfeer
Road, Kalkaal Hospital remains one of the most easily and securely accessible
private hospitals within the city. Its location within the KM4 area allows for
quick and safe access by both the corporate class and the general public without
compromising security and the quality of healthcare provided.

Founded in 2015 during an era when Somalia badly needed a healthcare

upgrade, as it rebuilt after the conflict, the hospital's mission is to provide high-
quality yet affordable healthcare to the people living in Somalia.

2.2.1 Vision and Mission

Vision

• To provide quality and affordable medical.

Mission

 Kalkaal Hospital's aim is to demonstrate our concern and commitment to

our patients, corporate partners, and referring specialists
2.3 Compare Between exiting system

COLDMAX

COLDMAX is the leading manufacturer of vacuum cooler, cold room, ice

machine and other modern farm equipment! COLDMAX has a quite strong
focus on quality, innovation, and service. And we adopt in-house developed
evaporator (water catcher, the heart of the vacuum cooler) for optimal cooling
speed with minimal energy consumption.

Figure 2. 2 COLDMAX
Los Angeles Cold Storage

Los Angeles Cold Storage has been providing public frozen food warehouse services
since 1895. Over one hundred thirteen years of modern innovative temperature
controlled warehouse service. With three locations in the center of Los Angeles and
all located within thirty minutes of the two largest ports in America. LA Cold is
surrounded by freeways that lead to the nation. Our locations and services allow LA
Cold to be the warehouse of choice for thousands of frozen food professionals.

Figure 2. 3 Los Angeles Cold Storage

Table 2. 1 Compare between Existing systems and proposed system

COLDMAX Los Angeles Proposed System

Cold
Storage

Storage ✔ ✔ ✔

Online booking ✘ ✘ ✔

Safety ✘ ✔ ✔

Reports ✘ ✔ ✔

Message us ✘ ✔ ✔

2.4 Chapter Summary

This chapter discussed introduction, theoretical and conceptual

development, case study of the research, compare between existing system
and chapter summary
 CHAPTER THREE

SOFTWARE PLANNING AND ANALYZING

3.0 Introduction

Software planning is an objective of each and every activity, where we want

to discover things that belong to the project. An important task in creating
a software program is extracting the requirements or requirements analysis.
Customers typically have an abstract idea of what they want as an end result
but do not know what software should do. Skilled and experienced software
engineers recognize incomplete, ambiguous, or even contradictory
requirements at this point. Frequently demonstrating live code may help
reduce the risk that the requirements are incorrect. Once the general
requirements are gathered from the client, an analysis of the scope of the
development should be determined and clearly stated. This is often called
a scope document. (Ralph & Wand, 2009)

Software analyzing: In computer science, program analysis is the process

of automatically analyzing the behavior of computer programs regarding a
property such as correctness, robustness, safety and liveness. Program
analysis focuses on two major areas: program optimization and program
correctness.
 The first focuses on improving the program’s performance while reducing
the resource usage while the latter focuses on ensuring that the program
does what it is supposed to do. Program analysis can be performed without
executing the program (static program analysis), during runtime (dynamic
program analysis) or in a combination of both. (Agrawal & Horgan, 2020)
This chapter will include the following sections: Introduction, Operational

Framework, Work Break down structure (WBS), System Requirement,

Problem Analysis Identification, Requirements Gathering Techniques,
Process Modeling, Data Modeling, Suitable solution Strategies of the
proposed system, System Feasibility and Chapter Summary.
3.1 Operational Framework

The Operational Framework starts planning, proposal, chapter one

introduction, chapter two literature review, chapter three software planning &
analyzing chapter four software design, chapter five system implementation
and finally chapter six conclusions & enhancement
Figure 3. 1 Operational Framework
3.2 Work Break down structure (WBS)

Work break down structure (WBS) is a vehicle for breaking an engineering

project down into subproject, tasks, subtasks, work packages, and so on. It
is an important planning tool which links objectives with resources and
activities in a logical framework. It becomes an important status monitor
during the actual implementation as the completions of subtasks.

Figure 3. 2
Work Break down Structure (WBS) Process
3.3 System Requirement

System requirement is a characteristic or feature that must be include in any

information system to satisfy users. Since the Administrator and the users
are the main target collection of our software, I will only concern about
some important functions for the admin and the user. the system needs
Applications like web browsers safari, Mozilla Firefox, Google chrome and
internet connection. they include the following interfaces:
a) User Interfaces: The keyboard, mouse, menus of a computer
system. The user interface allows the user to communicate with the
operating system.
b) Software Interfaces: The languages and codes that the applications
use to communicate with each other and with the hardware. c)
Hardware Interfaces: The wires, plugs and sockets that hardware
devices use to communicate with each other, computer systems, or any
other medium of communication. A physical interface is the
interconnection between two items of hardware or machinery.
3.3.1 Software Requirement Specification

One of the critical success factors in the development of high-quality

software product or website is the deep understanding of the user’s real
requirement as opposite to their perceived requirements. This will make the
product very easy to develop, maintain, and to use the software properly by
the end users. User requirement is the process by which user desires, needs,
and expectations are gathered in order to establish what the users will
actually use the software for, and recorded in a way that will be meaningful
both to the users and developments.

Software Requirements
able 3. 1 Software Requirements

Operating System : Macintosh, Linux, Windows Xp,7,8,8.1,10,11

Front End : PHP

Back End : MySQL

3.3.2 User Requirements Definition

A document that defines what a proposed system must be capable of doing

to solve the problems of a defined set of potential users of such a system.
The user requirements specification should be completely independent of
any solutionoriented bias and must use terminology from the problem
domain of the users. It must be understandable by the intended users who
must “buy in” to it. Therefore, it is most unlikely to be created using a
conventional requirements-analysis method, since these introduce solution
bias, representations, and concepts that are rarely understood by (and are
irrelevant to) the users (user-requirements, 2017).
3.4 Problem Analysis Identification

Problem analysis is focused on identifying cause and effect. It can be very

difficult to determine what is cause and what is effect. For example, a
problem that initially looks like a human error may be a latent human error
that is the result of a poorly designed user interface, system or process.
3.5 Requirements Gathering Techniques

Requirements gathering techniques are a process of collecting data from

different sources. Data or (datum in singular) is valuable pieces of
information collected during the research. Data can be divided in to two
categories: primary data and secondary data. In this research, the primary
data comes from observation to the respondents. First, the observation will
be carefully evaluated and to ensure its validity and reliability by pilot test.
There are various methodologies for gathering data as the following:

 Interviews

 Observations
3.5.1 Interview

An interview is a formal face-to-face meeting, especially, one arranged for

the assessment of the qualifications of an applicant, as for employment or
admission. A conversation, as one conducted by a reporter, in which facts
or statements are elicited from another, the interview is the primary
technique for information gathering during the systems analysis phases of
a development project. It is a skill which must be mastered by every analyst.
The interviewing skills of the analyst determine what information is
gathered, and the quality and depth of that information. Interviewing,
observation, and research are the primary tools of the analyst.
Advantages of interview
The main advantage of interviews is that the researcher (interviewer) can
adapt the questions as necessary, clarify doubt and ensure that the responses
are properly understood, by repeating or rephrasing the questions. The
researcher/interviewer can also pick up nonverbal cues from the
respondent. Any discomfort, stress and problems that the respondent
experiences can be detected through frowns, nervous taping and other body
language, unconsciously exhibited by any person. This would be
impossible to detect in a telephone interview. So face-to-face helps the
interviewee to get the desired results and help them the expression of the
person to whom they are interviewing.
Disadvantages of interview
The main disadvantages of face-to-face interviews are the geographically
limitations they may impose on the surveys and the vast resources needed
if such surveys need to be done nationally or internationally. The costs of
training interviewers to minimize interviewer's biases for example
differences in questioning methods, interpretation of response are also high.
Another drawback is that respondents might feel uneasy about the
anonymity of their responses when they interact face to face interviews.

3.5.2 Observation

An observation is a data collection method used to gather detailed

information about a situation or event. Observation data is used to
describe the setting, activities, participants, and the meaning of the
observations from the observer's perspective. Observation in this project
will be based on facts which are both accurate and detailed, but left any
irrelevant or slight information that makes the description difficult to
understand. This data allows the reader to fully understand the situation.
Advantages of observation
a) Allows you to directly see what people do practically rather than relying
on what people say they did.

b) Observer’s document program activity takes time and cost gathering

providing documentation, rather than relying on recollections of the
events.
Disadvantages of observations
a) Observer bias may occur. (Observer may only notice what interests
him or her).

b) With participant’s observation, a skilled facilitator is needed to help

participants present a critical evaluation.

3.6 Process Modeling

A process model is a formal way of representing how a computer system

operates. It illustrates the processes or activities that are per-formed and
how data move among them. A process model can be used to document the
current system (i.e. as-is system) or the new system being developed (i.e.
to-be system). Whether computerized. Process modeling is the process and
analysis of data and objects that are used in business or other context and
identification of the relationship among these data objects. Data modeling
is a first step in doing object-oriented Programming and involves
professional data modelers working closely with business stakeholders, as
well as potential users of information system.

3.6.1 Data flow Diagram (DFD)

Data Flow Diagrams show information transfers and process steps of a

system. The general concept is an approach of a depicting how occurs input
in a system, further processes and what runs out. The aim of DFD is in
accomplishing of understanding between developers and users. Data flow
diagrams are maintained with other methods of structured systems analysis.

A data flow diagram (DFD) illustrates how data is processed by a system in

terms of inputs and outputs. As its name indicates its focus is on the flow of
information, where data comes from, where it goes and how it gets stored.

• Graphical representation of the "flow" of data through an

information system;
• Modeling process aspects;

• An overview of the system;

• For the visualization of data processing (structured design);

• What kinds of information will be input to and output from

the system;
• Where the data will come from and go to;

• Where the data will be stored.(conceptdraw, 2017).

 Data Flow Diagrams notations:

The Data Flow Diagrams solution from the Software Development area of

Concept Draw Solution Park provides three vector stencils libraries for
drawing

DFD using the Concept Draw PRO diagramming and vector drawing
software. The design elements library DFD, Yourdon and Coad notation
contains 22 data flow diagram symbols of Yourdon/DeMarco DFD
notation(conceptdraw, 2017)

Figure 3. 3 UCD

3.6.2 Unified Modeling Language (UML)

UML stands for Unified Modeling Language; UML is a way of visualizing

a software program using a collection of diagrams. The notation has
evolved from the work of Grady Brooch, James Rum Baugh, Ivar Jacobson,
and the Rational Software Corporation to be used for object-oriented
design, but it has since been extended to cover a wider variety of software
engineering projects. Today, UML is accepted by the Object Management
Group
(OMG) as the standard for modeling software development (smart draw,

2017)

Types of UML Diagrams

The current UML standards call for 13 different types of diagrams: class, activity, object,
use case, sequence, package, state, component, communication, composite structure,
interaction overview, timing, and deployment.
3.6.2.1 Use Case Diagram (UCD)

A use case is a methodology used in system analysis to identify, clarify, and

organize system requirements. The use case is made up of a set of possible
sequences of interactions between systems and users in a particular
environment and related to a particular goal. It consists of a group of
elements (for example, classes and interfaces) that can be used together in
a way that will have an effect larger than the sum of the separate elements
combined(techtarget, 2017).

Here are the symbols of UCD:-

Figure 3. 4 UCD
Figure 3. 5 Use Case Diagram
3.7 Data Modeling

Data modeling is the analysis of data objects and their relationships to other
data objects. Data modeling is often the first step in database design and
objectoriented programming as the designers first create a conceptual
model of how data items relate to each other. Data modeling involves a
progression from conceptual model to logical model to physical
schema(web, 2017).

Data modeling is the process and analysis of data and objects that are used
in business or other context and identification of the relationship among
these data objects. Data modeling is a first step in doing object-oriented
programming and involves professional data modelers working closely
with business stakeholders, as well as potential users of information system.

3.7.1 Entity Relationship Diagram

An entity-relationship (ER) diagram is a specialized graphic that illustrates

the interrelationships between entities in a database. ERD show entities in
a database and relationships between tables within that database. It is

essential to have one of these if you want to create a good database design.
The patterns help focus on how the database actually works with all of the
interactions and data flows, although another useful tool is a Data Flow
Diagram (DFD) which more directly described ERD is a detailed, logical
representation of the entities, associations and data elements for an
organization or business. ERD is a graphical modeling tool to standardize
ER modeling; the modeling can be carried out with the help of pictorial
representation of entities, attributes and relationships(lucid chart, 2107).

The basic building blocks of ERD are Entity, Attributes, Relationship and
lines entity is an object that exists and is distinguishable from other object
in other words Entity types or Entity set is a collection of similar entities;
an entity may belong to more than one entity type. A relationship is an
association of entities where the association includes one entity from other
particular types is meaningful association before entity types. Attributes are
properties of entity types in other words; entities are described in a data
base by a set of attributes (Peter Pin-Shan Chen, 1976)
3.7.1.1 ERD SYMBOLS

The ERD is used to represent database schema, here are some symbols used
to represent ERD Symbols:

A rectangle represents an Entity, An Ellipse represents an attribute, A

diamond represents a relationship Lines represent linking of attributes to
entity sets & of entity sets to relationship sets.
3.7.1.2 TYPES OF RELATIONSHIP

Relationship is an association among one or more entities. This relationship

can be broadly classified into one-to-one relation, one-to-many relation,
many-to many relation.
o One to many Relationship Type: Abbreviated 1:M, the
relationship that associate one entity to more than one entity is
called one to many relationships: - Example is country having states
for one country there can be more than one states hence is an
example one to many relationships. o One to one Relationship
Type: Abbreviated 1:1, one to one relationship is a special case of
one to many relationships. True one to one relationship is rare. The
relationship between the president and Country is an example is
one to one relationship.
o Many to Many Relationship Type: Abbreviated M: M, the
relationship between EMPLOYEE entity and PROJECT entity is
an example of many to many relationships. Many employees will
be working in many projects hence the relationship between
employee and project is many to many relationships.
 o Many to One Relationship Type: Abbreviated M: 1, the
relationship between EMPLOYEE and DEPARTMENT is an
example of many to one relationship, there may be EMPLOYEE
working in one DEPARTMENT. Hence relationship between
EMPLOYEE and

DEPARTMENT is many to one relationship (Aplim, 2010).

Table 3. 3 ERD Proposed System

3.8 Suitable Solution Strategies of the Proposed System

As we are reaching the development phase, this section would contemplate

on other ways project’s objectives can be achieved. As you may know, the
system will be developed in programming language and it is the most used
or popular.
3.9 System Feasibility
A feasibility study for an information system project is an in-depth look at
the project in order to determine whether or not an organization should
proceed with its implementation. Feasibility studies provide project
managers with an overview of the primary issues related to the project, as
well as insights about the outcomes of the project, before the company
invests too much time and money(reference, 2017).

A feasibility study could be used to test a new working system, which could
be used because the Feasibility study is an analysis of possible alternative
solutions to a problem and a recommendation on the best alternative. It can
decide whether a process be carried out by a new system more efficiently
than the existing one.
 Feasibility study is divided into four types: - .
 Technical Feasibility
 Operational Feasibility
 Economic Feasibility.
 Schedule Feasibility.

3.9.1 Technical Feasibility

Technical feasibility is the measure of the practically of a specific technical information

system solution and the availability of technical resource to develop, purchase, install and
operate the system often new technologies are solutions looking for a problem to solve.
The assessment is based on an outline design of system requirements in terms of input,
process, output, fields, programs, and procedures. This can be counted in terms of volumes
of data, trends, frequency of updating, etc. in order to estimate whether the new system
will perform sufficiently or not. Technological feasibility is carried out to determine
whether the company has the capability, in terms of software, hardware, personal and
expertise, to handle the completion of the project. A Hardware feasibility is shown in the
below table
Table 3. 4 Technical Feasibility

No Item Quantity Cost Amount

1 Laptop 1 $500.00 $500.00
Table 3. 5
Corei5
Items
2 USP 1 $50.00 $50.00

Mercury

2000
Total $550.0
 No Item Description Quantity Cost Per Unit Amount

1. PHP and MYSQL 1 Free

Total Free

Table 3. 6 Operational Feasibility

Activities Duration Expected cost

Training Current 1 Week $300.00

Employee
Training new Employee 1 Week $500.00

Total $800.00

3.9.2 Operational Feasibility

Operational feasibility is the ability to utilize, support and perform the

necessary tasks of a system or program. It includes everyone who creates,
operates or uses the system. To be operationally feasible, the system must
fulfill a need required by the business. The following table will show the
training cost of the user of the system.
Economic Feasibility
Economic analysis is the most frequently used evaluating the effectiveness
of proposed system, more commonly known as benefit analysis. The
benefit analysis is to determine benefits and saving which are expected
from candidate system and compare them with cost. If the benefits are more
than the cost, the decision is made to design and implement the system. The
cost and benefits may be direct or indirect and tangible or intangible.
table 3. 6 Economical feasibility

Types of feasibility Description Expect Cost

Technical feasibility Hardware & software 600

Operational feasibility Training with best option 660

total 1260
3.9.4 Schedule Feasibility

Typically, this means estimating how long the system will take to develop,
and if it can recomplete in a given time period using some methods like
payback period. Schedule feasibility is a measure of how reasonable the
project timetable is.
This involves questions such as how much time is available to build the
new system, when it can be built, whether it interferes with normal business
operation, number of resources required, dependencies, can the system be
developed in time etc. The project duration schedule is explained in the
following.

Table 3. 8 Schedule Feasibility

Level Phase Name Duration

1 Analysis phase 4 weeks

2 Design phase 2 weeks

3 Coding 6 weeks

4 Implementation and Testing 2 weeks

 5 Operation and maintenance phase 2 week

Total 16 weeks

3.10 Chapter Summary

This chapter presented the following sections: Introduction, Operational

Framework, Work Break down structure (WBS), System Requirement,
Problem Analysis Identification, Requirements Gathering Techniques,
Process Modeling, Data Modeling, Suitable solution Strategies of the
proposed system, System Feasibility and Chapter Summary.