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 Online Point of sale management system and hereby given all
necessary privileges and authorities by Horseed International University with full
support to fulfil their degree requirements under the supervision of Mr.Abdikarim
Mohamed Mohamud (Lecturer) and with the approval of IT Department.

Names of students:

Suldan Hussein Ibrahim

Salaad Abdulle Huurshe

Mohamed Nor Raage

Farhan Mohamed Ismail

NB: Any alteration renders this certificate invalid.

Dean, Faculty Of CS&IT Project Supervisor

_______________ _________________

Date: May , 2021

Website: www.hiu.edu.so Mogadishu - Somalia

i
 POINT OF SALE MANAGEMENT SYSTEM

SULDAAN HUSSIEN IBRAHIM ID CARD: 8093

MOHAMED NOR RAGE ID CARD: 8147

Farxan Mohamed Ismacil ID CARD: 7971

Salad Abdulle Hurshe ID CARD: 8647

A GRADUATION THESIS SUBMITTED IN PARTIAL FULFILMENTS

OF THE REQUIREMENTS FOR THE AWARD OF

THE DEGREEOF BACHELOR OF COMPUTER SCIENCE AND TECHNOLOGY

HORSEED INTERNATIONAL

UNIVERSITY

(HIU)

MAY, 2021

ii
 DECLARATION A

"This project is our original work and has not been presented for a Degree or any other academic
award in any University or Institution of Learning".

SULDAN HUSSEIN IBRAHIM

MOHAMED NUUR RAAGE

SALAD ABDULLE HURSHE

FARHAN MOHAMED ISMACIL

Names and Signature of the Candidates

Date

iii
 DECLARATION B

"I confirm that the work presented in this project was carried out by the candidate under my
supervision".

Name and Signature of Supervisor

Date

iv
 APPROVAL SHEET

This Project entitled “Online supermarked management system" prepared and submitted by suldan
Hussein ibrahim, Mohamed nuur raage, salad abdulle hurshe and farhan Mohamed ismacil in
partial fulfillment of the requirements for the degree of Bachelor of computer Science in Information
Technology has been examined and approved by the panel on oral examination.

Name and Sig. of Chairman Name and Sig. of Panelist

Name and Sig of Supervisor Name and Sig. of H.O.D

Name and Sig. of the Dean

v
 DEDICATION

We dedicate this project to our parents. Without their patience, understanding, support and most
of all love, the completion of this work would not have been possible.

vi
 ACKNOWLEDGEMENT

We thank to Allah the Creator of this world who gave us the opportunity to complete this project
successfully. You won't find a successful person made his way to the top, without a support. Each
one of us is debt to known or unknown people. Those who gave us hands when darkness was
everywhere around. Show us the way, surrounded us, and smiled to us… gave us hope. We would
like to thank our family and parents for supporting us emotionally and financially.

We would like to thank the administration of HORSEED UNIVERSITY, especially Dean of

Faculty of Computer Science and Technology, Mr. IBRAHIM FARAH HILOWLE for his
guidance, training, supervision and encouragement during our study at the university especially
ComputerScience (CS).

We would like to extend our warmest gratitude to our supervisor, ENG ABDKARIIM AB for his
immense amount of support, advice, and guidance throughout the process. We couldn’t have done
any of this without their support.

vii
 ABSTRACT

Abstract and Figures Point of Sales (POS) is a computerized system manages sales and performs
simple day to day operations in the retail stores. POS terminal building involves interfacing printer,
bar code scanner, computer, Debit/Credit Card Reader, keyboard, touch screen input, weighing
machine and software on a CPU to run operations in a store

viii
 Table of contents

CHAPTERS TITLE PAGE

Cover i

DECLARATION A ii

DECLARATION B iii

APROVAL SHEET iv

DEDICTION v

ACNOWLADGEMENT vi

ABSTRACT vii

TAPLE OF CONTENTS viii

LIST OF TAPLE xi

LIST OF FIGURES xii

CHAPTER I: Introduction

1.0 Introduction 1

1.1 Background Problem 1

1.2 Problem Statement 3

1.3 Purpose of the Project 4

1.4 Project objectives 4

1.5 Project Scope 4

1.6 Significance Of The Project 5

ix
1.7 Project Organization 5

2.0 CHAPTER II: LITERATURE REVIEW

2.1 Introduction 7

2.2 Theoretical and Conceptual Development 10

2.3 Case Study of the Research 11

2.4 Compare between Existing Systems 12

2.5 Chapter Summary 13

CHAPTER III: SOFTWARE PLANNING

AND ANALYZING

3.0 Introduction 14

3.1 Operational Framework 15

3.2 Work Breakdown Structure 16

3.3 System Requirement 17

3.3.1 Software Requirement 18

3.3.2 User Requirements 19

3.4 Problem Analyses Identification 20

3.5 Requirement Gathering Techniques 21

3.5.1 Interview 21

3.5.2 Observation 22

x
3.6 Process Modeling 23

3.6.1 Data Flow Diagram 23

3.6.2 UML 25

3.6.2.1 Use Case Diagram 26

3.7 Data Modelling 28

3.7.1 Entity Relationship Diagram 28

3.7.1.1 ERD Symbols 29

3.7.1.2 Types of Relationships 29

3.7.1.3 ERD of the Proposed System 31

3.8 Suitable Solution Strategies of proposed System 31

3.9 System Feasibility 31

3.9.1 Technical Feasibility 32

3.9.2 Operational Feasibility 33

3.9.3 Economical Feasibility 34

3.9.4 Schedule feasibility 34

3.10 Chapter Summary 35

CHAPTER IV: SOFTWARE DESIGN

4.0 Introduction 36

4.1 Architectural Design 36

4.2 User Interface 37

xi
4.3 Database Storage Design 37

4.4 Database Design 38

4.4.1 Database Normalisation 38

4.4.2 First Normal Form (1NF) 38

4.4.3 Second Normal Form (2NF) 39

4.4.4 Third Normal Form (3NF) 39

4.4.5 Normalized Tables of the Proposed System 41

4.4.6 Transforming E-R Diagrams into Relations 42

4.4.7 Data Dictionaries 42

4.5 Designing Forms And Reports 45

4.6 Chapter Summary 46

CHAPTER V: SYSTEM
IMPLEMENTATION AND OPERATION

5.0 Introduction 47

5.1 Coding Phase 47

5.2 Sample Code 48

5.3 Test system implementation 49

5.4 Development Testing 49

5.4.1 Release testing 50

5.42 User testing 51

5.4.3 Developing User Manuals 52

xii
5.5 Chapter Summary 52

CHAPTER VI: CONCLUSION AND

ENHANCEMENT

6.0 Introduction 53

6.1 Objectives Achievements 53

6.2 Weakness And Problem Of The System 55

6.3 Future Work and Recommendations 55

6.4 Chapter Summary 55

References 56

Appendices A 57

Appendices B 58

Appendices C 59

xiii
LIST OF TABLES

Table Reference no Description PAGE

Table 1 22

Table 2 Software requirements 23

Table 3 Economic Feasibility 24

Table 4 Organization Feasibility 24

Table 5 Schedule feasibility 25

Table 6 Users table 33

Table 7 Employees table 33

Table 8 Detergents table 34

Table 9 Invoice table 34

Table 10 PAYMENT table 35

Table 11 Users table 35

Table 12 finance table 35

Table 13 Employees table 35

Table 14 Invoice table 35

Table 15 Wash table 35

xiv
LIST OF FIGURES

FIGURE NO DESCRIPTION PAGE

Figure 1 context diagram 17

Figure 2 level one 18

Figure 3 level two 18

Figure 4 ERD symbols 20

Figure 5 Entity relationship diagram 20

Figure 6 architectural design 27

Figure 7 ERD relation ship 32

Figure 8 Login Form 36

Figure 9 Admin home 37

Figure 10 Payroll 37

Figure 11 Create User Form 38

Figure 12 Payment 38

Figure 13 payment Report 39

Figure 14 employee Report 40

Figure 15 Create User 45

Figure 16 Change Password 45

Figure 17 New Employee 46

Figure 18 Detergent 46

xv
 CHAPTER ONE

INTRODUCTION

1.0 INTRODUCTION
The Point-of-Sale system is designed to control all areas of activity within Parts,
Service and Bodyshop environments. It monitors all aspects of Work-in-Progress
and records all sales transactions for parts and labour.
There is also a full customer backorder system that controls all orders for parts all
the way through from time of request, to ordering on your supplier, to eventually
clearing your customer backorder when the goods are received.
The system allows the printing of various documents such as:

 Point-of-Sale Invoices (Parts and Service)

 Credit Notes (Goods Returned to Stock or Invoice Reversal to be Recharged)
 Job Cards
 Estimates
 Picking slips
 Requisitions
 Notifications for deposits received

. BACKGROIND OF THE SYSTEM

Point of Sale and Inventory System is a process wherein the business could monitor
the movements of the products as well as the sales transactions. It is important for
the company to take account inventory of the products as well as the sales. Inventory
refers total amount of goods and/or materials contained in a store at any or factory
at any given time (Inventory, 2011)
Even though technology is available, still many companies use manual system.
Operating manual inventory is a time-consuming task, lots of paper works and slow
date processing (Hamlet, 2011).
It also problematic in terms of communication streams. Each update or removal
from the inventory must be updated daily (Cruz, 2010).
Manual sales and inventory process was prone to errors that required time to rectify
discrepancies (“Inventory”, nd.). Since manual inventory consumes a lot of time and

1
is susceptible to errors, it would be helpful to build a system that will automate the
transactions from acquisition of the product description to updating the inventory
database. Work efficiency of employees is defined as how productive they are in
their work (“Inventory”, nd.). The causes of the discrepancies in the records are
many, and some of the commonly observed ones are: stock loss; transaction error,
inaccessible inventory, and incorrect product identification. Stock loss, also known
as shrinkage in industry, includes all forms of loss of the products available for sale.
One common example is theft, which can be committed by both shoppers (external
theft) and employees (internal theft). With these problems of manual inventory
system, businesses emerged with computerized Point of Sales and Inventory System.
It tracks purchases and sale transactions thought an organization. Point of Sale and
Inventory System is a tool used by retail businesses such as stores, supermarkets,
and restaurants. It can register the purchase and keep track of inventory. It also
records information on the purchase including time and store location. It also
manages the sales of retail goods. It makes a business much more efficient, lowering
the costs of running the business while improving customer service and making the
business more pleasant to work in (Smith & Harris, 2011)
According to Hendeson (2011),
that effective tracking of inventory is an imperative component to a small business
successful operation. By having up-to-date data regarding all needed stocks for sale,
the organization will drastically increase its bottom line. The amount of time that
can be saved by the company is the biggest benefits of using a computerized point
of sale and inventory system. Another benefit of a computerized point of sale and
inventory system is the accuracy it ensures. The companies operation will be more
effectively. The business owner or the manager can ensure that the reports,
purchased order and other documents related to sales and inventory are uniform
regardless of two created the reports (What are the benefits of Computerized Sales
and Inventory, n.d.). According to ruffling (2009), senior director of retail services
for BBK Ltd., the trends in Sales and Inventory System are not just inventory
accuracy but the use of pricing models to allow for markdown management. Based
from the problems encountered in a manual point of sales and inventory system,
developers come up with this computerized point of sales and inventory system.
Developers have chosen Thirsty Teddy Refilling Station and The Sierra Spa started
its operations in the year 2012 by Mr. Randy S. Quiniones. It is located at Sierra

2
Heights Place, Sierra Madre St. Highway Hills, Mandaluyong City. The company is
currently using a manual inventory system but aims for improvement to be
competitive. In small businesses, inventory system is still applicable because of the
advantages it provides the management.
.1.2 PROBLEM STATEMENT
Point of sale systems, commonly found in retail establishments and known as
POS, often feature a complex arrangement of hardware, software and network
connections. POS systems rely on predictable operation, and any number of
problems can appear when hardware, software or users do not perform as
expected.So, I'm doing a project book point of sale management System and
information system that solves all of that needs.

3
 1.3 PURPOSE OF THE PROJECT
A purpose of point of sale is, the place where the sales-transaction (the exchange
of goods/services for money, etc) occurs. can be virtually anywhere but depends
on goods/services being offered. here a some good point of sale software in market
like hdpos and many more they provide.

1.4 project objectives

Here are the most three objectives:
 Managing your inventory pos management system
 Automation accounting pos management system
 Collection of customer data pos management information system

1.5 PROJECT SCOPE

Like any other project this project has both geographical scope and time scope the
geographical scope of this project will be around the capital city of Somalia Mogadishu
particularly this project will take place in pos which is the case study for my project
so that I am going to develop this project for them the time scope for this project will
be between 3 november (as a start date) and may 2020(as an end date).

1.6 SIGNIFICANCE OF THE PROJECT

Points of sale (POSs) are an important focus for marketers because consumers tend
to make purchasing decisions on high-margin products or services at these strategic
locations. Traditionally, businesses set up POSs near store exits to increase the rate of
impulse purchases as customers leave.

1.7 REPORT ORGANIZATION

The organization of this thesis of point of sale management Information System will
Contain 6 chapters. The following paragraphs will show

The contents of those chapters

Chapter one will discuss the Project Introduction that will provides an overview of the
project and introduces issues in which the projects is considered such as background
of the project problem Statement Purpose of the projects project

4
Objectives Scope and significant of the project
Chapter two will discuss Literature Review that will provide the reviews of the
effective evo1ulion of selected document on computing topics and this chapter will
contain. Theoretical and conceptual development Inter organization case study and
comparing and contrasting between current systems
Chapter three will deeply converse Software development methodology and the
chapter will illustrate the framework that is used to structure, plan and control the
Process of developing an information system and requirement gathering process
Which is intensified and focused specially on software and this chapter will contain
Preliminary system study System requirements software requirements specification
User requirement definition problem analysis identification requirement gathering

Chapter Four: Proposes the design of the online project for based Design and Develop
of a Web-based parent record keeping 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 based Design and Develop of a Web-based parent record keeping
information System and its future enhancements.

5
 CHAPTER TWO

LITERATURE REWIEW

2.0 INTRODUCTION

A literature review is a search and evaluation of the available literature in your

given subject or chosen topic area. It documents the state of the art with respect to the
subject or topic you are writing about. A literature review shows your readers that you
have an in-depth grasp of your subject; and that you understand where your own
research fits into and adds to an existing body of agreed knowledge. (what-is-a-
literature-review, 2012)
A literature review is a critical and in-depth evaluation of previous research. It is a
summary and synopsis of a particular area of research, allowing anybody reading the
paper to establish why you are pursuing this particular research. A good literature
review expands on the reasons behind selecting a particular research
question.(Shuttleworth, 2009)

Litereture
Review

2.1 2.3 Compare

2.0 Theoretical 2.2 Case Between 2.4 Case 2.5 Chapter
Introduction And Study Exiting Study Summary
Conceptual System

Figure 2.1: Literature Review Map

6
2.1 THEORETICAL ANDCONCEPTUAL DEVELOPMENT

This section will discuss the concepts of Design and Implementation point of sale
management system.
The point of sale (POS) or point of purchase (POP) is the time and place where a
retail transaction is completed. At the point of sale, the merchant calculates the amount
owed by the customer, indicates that amount, may prepare an invoice for the customer
(which may be a cash register printout), and indicates the options for the customer to
make payment. It is also the point at which a customer makes a payment to the
merchant in exchange for goods or after provision of a service. After receiving
payment, the merchant may issue a receipt for the transaction, which is usually printed
but can also be dispensed with or sent electronically.

To calculate the amount owed by a customer, the merchant may use various devices
such as weighing scales, barcode scanners, and cash registers (or the more advanced
"POS cash registers", which are sometimes also called "POS systems"). To make a
payment, payment terminals, touch screens, and other hardware and software options
are available.

The point of sale is often referred to as the point of service because it is not just a point
of sale but also a point of return or customer order. POS terminal software may also
include features for additional functionality, such as point of sale management.

Businesses are increasingly adopting POS systems, and one of the most obvious and
compelling reasons is that a POS system does away with the need for price tags. Selling
prices are linked to the product code of an item when adding stock, so the cashier
merely needs to scan this code to process a sale. If there is a price change, this can also
be easily done through the inventory window. Other advantages include the ability to
implement various types of discounts, a loyalty scheme for customers, and more
efficient stock control, and these features are typical of almost all modern ePOS
systems

7
SYSTEM
The “System” concept 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")(yolex, 2010).
System is a set of things working together as parts of a mechanism or an
interconnecting network; a complex whole. System is group of related hardware units
or programs or both, especially when dedicated to a single application. System is a set
of organs in the body with a common structure or function. System is a set of principles
or procedures according to which something is done; an organized scheme or
method.(liolerin, 2014)

A set of detailed methods, procedures and routines created to carry out a specific
activity, perform a duty, or solve a problem.
INFORMATION SYSTEM
Information system, an integrated set of components for collecting, storing, and
processing data and for providing information, knowledge, and digital products.
Business firms and other organizations rely on information systems to carry out and
manage their operations, interact with their customers and suppliers, and compete in
the marketplace. Information systems are used to run inter organizational supply
chains and electronic markets. For instance, corporations use information systems to
process financial accounts, to manage their human resources, and to reach their
potential customers with online promotions. Many major companies are built entirely
around information systems. These include eBay, a largely auction
marketplace; Amazon, an expanding electronic mall and provider of cloud
computing services; Alibaba, a business-to-business e-marketplace; and Google,
a search engine company that derives most of its revenue from keyword advertising
on Internet searches. Governments deploy information systems to provide services
cost-effectively to citizens. Digital goods—such as electronic books, video products,
and software—and online services, such as gaming and social networking, are
delivered with information systems. Individuals rely on information systems, generally
Internet-based, for conducting much of their personal lives: for socializing, study,
shopping, banking, and entertainment (Vladimir Zwass, 2016).

8
As information systems enabled more diverse human activities, they exerted a
profound influence over society. These systems quickened the pace of daily activities,
enabled people to develop and maintain new and often more-rewarding relationships,
affected the structure and mix of organizations, changed the type of products bought,
and influenced the nature of work. Information and knowledge became vital economic
resources. Yet, along with new opportunities, the dependence on information systems
brought new threats. Intensive industry innovation and academic research continually
develop new opportunities while aiming to contain the threats (Vladimir Zwass, 2016).
The level of complexity of the system will depend on each organization’s specific
context. For some organizations, especially smaller ones, it may simply mean having
strong leadership from the business owner, providing a clear definition of what is
expected from each individual employee and how they contribute to the organization’s
overall objectives, without the need for extensive documentation. More complex
businesses operating, for example, in highly regulated sectors, may need extensive
documentation and controls in order to fulfill their legal obligations and meet their
organizational objectives.(soxil, 2016).

JAVA

Java is a general-purpose programming language that is class-based, object-oriented,

and designed to have as few implementation dependencies as possible. It is intended
to let application developers write once, run anywhere (WORA), meaning that
compiled Java code can run on all platforms that support Java without the need for
recompilation. Java applications are typically compiled to bytecode that can run on
any Java virtual machine (JVM) regardless of the underlying computer architecture.
The syntax of Java is similar to C and C++, but it has fewer low-level facilities than
either of them. As of 2019, Java was one of the most popular programming languages
in use according to GitHub, particularly for client-serverweb applications, with a
reported 9 million developers.

Java was originally developed by James Gosling at Sun Microsystems (which has since
been acquired by Oracle) and released in 1995 as a core component of Sun
Microsystems' Java platform. The original and reference implementation Java
compilers, virtual machines, and class libraries were originally released by Sun under
proprietary licenses. As of May 2007, in compliance with the specifications of the Java

9
Community Process, Sun had relicensed most of its Java technologies under the GNU
General Public License. Meanwhile, others have developed
alternativeimplementations of these Sun technologies, such as the GNU Compiler for
Java (bytecode compiler), GNU Class path (standard libraries), and Iced Tea-Web
(browser plugin for applets).

MySQL

MySQL is an open source relational database management system (RDBMS) based

on Structured Query Language (SQL).
MySQL runs on virtually all platforms, including Linux, UNIX, and Windows.
Although it can be used in a wide range of applications, MySQL is most often
associated with web-based applications and online publishing and is an important
component of an open source enterprise stack called LAMP. LAMP is a Web
development platform that uses Linux as the operating system, Apache as the Web
server, MySQL as the relational database management system and PHP as the object-
oriented scripting language. (Sometimes Perl or Python is used instead of PHP.)
MySQL, which was originally conceived by the Swedish company MySQL AB, was
acquired by Sun Microsystems in 2008 and then by Oracle when it bought Sun in 2010.
Developers can still use MySQL under the GNU General Public License (GPL), but
enterprises must obtain a commercial license from Oracle. (Margaret , MySQL, 2013)
2.2 CASE STUDY OF THE RESEARCH
Retail Point of Sale Software Case Study: Harold’s Lighting - Wasp Barcode. Wasp
QuickStore™ Point-of-Sale lights the way to a Brighter Future Harold’s Fine Home
Lighting is a company based on tradition. Harvey Hanson started the business during
the depression when he used his artistic skills to create lamps and then sell them door-
to-door..

10
MISSION –

 Points of sale (POSs) are an important focus for marketers because

consumers tend to make purchasing decisions on high-margin products
or services at these strategic locations.

VISION – Welcome to DataMax Services Let us help you find your next point of sale
system, pos product or bar code scanner! Many companies supply point of sale
systems and POS products to support today's retailer.

2.3 COMPARATIVE BETWEEN EXISTING SYSTEMS

There are a lot of systems that are similar to (pos Parent Record keeping
Information System) so they have some differences when compared with this system.

LEGAL pos

Point-of-sale systems (POS) represent the computerization of the cash register—and

their linking to data-bases—thus providing businesses with more digital data and the
ability to know themselves. POS systems give businesses the ability to retain and
analyze a wide variety of inventory and transaction data on a continuous basis. They
have been touted as valuable tools for a wide variety of business purposes, including
refining target marketing strategies; tracking supplier purchases; determining
customer purchasing patterns; analyzing sales (on a daily, monthly, or annual basis) of
each inventory item, department, or supplier; and creating reports for use in making
purchases, reorders, etc. Basic point-of-sale systems currently in use include stand
alone electronic cash registers, also known as ECRs; ECR-based network systems; and
controller-based systems. All of these function essentially as sales and cash
management tools, but each has unique features.

11
2.4 Compare Exiting System.

12
2.5 CHAPTER SUMMARY

This chapter has discussed many topics starting with the definition of book point of
sale and its history: also it has explained the conceptual and the theoretical
development of appointment management system and the future of this chapter also
included the comparison of the current existing pos record keeping information
systems finally the chapter has concluded with mentioning the features and advantages
of the new system over the system.

13
 CHAPTER THREE
SOFTWARE PLANNING AND ANALYZING
3.0 Introduction
This chapter will talk about the software development methodology which

Illustrates more points like the operational framework preliminary system study,
system requirements, problem analysis identification, requirement gathering
techniques, use case analysis, process modeling, data modeling, new proposed system,
solution strategy and system feasibility and affordability, finally the chapter will be
concluded with summary.
Planning: A basic management function involving formulation of one or more
detailed plans to achieve optimum balance of needs or demands with the available
resources. (definition/planning.html, n.d.)
Software Analyses is Software analysis patterns or analysis patterns
in software engineering are conceptual models, which capture an abstraction of a
situation that can often be encountered in modelling.(Software_analysis_pattern, n.d.)
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.

14
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

Initialization and planning

Phase one
Literature Review

Data gathering

Intervie Observatio
Phase Two w n

Analyzing

DESIGNING PROTOTYPE

NO
System
Phase Three Accept
ance

YES

Test the Prototype

Report writing

Figure 3. 1 Operation Frame Work

15
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 are measured against the project plan.(Tausworthe,
1984)

WBS is categorized into:

A) WBS product

Owner

Online notary management

Documentation
system
Records Reports

Registration

Figure 3. 2 WBS Product

16
 B) WBS process

Figure 3. 3 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. the 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.

17
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.

18
Software Requirements

Table 3. 1 Software Requirements

Operating System : Windows 7,8,10

Front End : Java

Back End : j.query, bootstrap

Hardware Requirement

Table 3. 2 Hardware Requirements

1 Computer HB

2 Corei3 or Corei5

3 2GB 4GB 8GB RAM

4 500 or 1 TB hard disk

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 solution-oriented
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).

A customer cannot demand features not in the user requirement document (URD)
while the software developer cannot claim the product is complete and ready if it does
not meet even one item of the user requirement document (URD).
Although the current system is no sufficient to fulfill the needs of the family head or
family administrator, it will become very hard to apply after the development of this

19
system because the new System will be expected to handle all tasks automatically in
registering customers appointments and experts the new Online point of sale
management system will offer user friendly flexibility, efficient environment, user
respondent, error tolerant, ready for and some security features.

3.4 Problem Analysis Identification

Researcher is going to develop this project for Parent the system is very important to
keep the records of the activities of all family members, now the head of the family
uses manual system to record of the family, The key problem involved with the current
system so now it is very difficult to estimate the expenses of the family daily, monthly
or even yearly after. Investigated working system process carefully, it has been
discovered that the current system has the following limitations such as:

 The performance of the current system is slow.

 Difficult to handle data accurately and security because of the data lost.
 Losing of papers,
 Day to day current system is very weak.
 So, security wise is not guarantee to all information and data’s.
 If the family head wants search their details it very difficult.
 Processing delay,
 Not easy to handle family details.
 . storage problems,
 . Unable to analyze past data,
 . {Update search, delete edit} these types of methods are not accessible
 Not carry with the manual method.
 Correction data or information is difficult

20
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, 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.

The interview is a specific form of meeting or conference, and is usually limited to

two persons, the interviewer and the interviewee. In special situations there may be
more than one interviewer or more than one interviewee in attendance (martymodel,
2017).

21
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
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. By reading the facial expression of the respondent the
interviewer can easily understand what the respondent want to tell them about anything
(answers-yahoo, 2017)

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

22
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).
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 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;

23
  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 Data flow diagram (DFD) contains 15 data flow diagram symbols for drawing
both context-level data flow diagram and Level 1 DFD.

The design elements library DFD, Gane-Sarson notation contains 12 data flow diagram
symbols of Gane-Sarson DFD notation.

The design elements library DFD, Yourdon and Coad notation contains 22 data flow
diagram symbols of Yourdon/DeMarco DFD notation(conceptdraw, 2017)

Process

Data Storage

External Entity

Data Flow
Figure 3. 4 UCD

24
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 Booch, James Rumbaugh, 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(smartdraw, 2017)

The key to making a UML diagram is connecting shapes that represent an object or
class with other shapes to illustrate relationships and the flow of information and data.
To learn more about creating UML diagrams:

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.

These diagrams are organized into two distinct groups: structural diagrams and
behavioral or interaction diagrams.

Structural UML diagrams

 Class diagram
 Package diagram
 Object diagram
 Component diagram
 Composite structure diagram
 Deployment diagram
Behavioral UML diagrams

 Activity diagram
 Sequence diagram
 Use case diagram
 State diagram

25
  Communication diagram
 Interaction overview diagram
 Timing diagram
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).

A use case diagram shows you some of the use cases in your system, some of the actors
in your system, and the relationships between them. A use case is a high – level piece
of functionality that the system will provide. An actor is anyone or anything that
interacts with the system being built.

Use case diagram is done in an early phase of a software development project. The use
case diagram describes the use case (functions of the system), Actors (users) and the
relationship between the actors and the use case is connective

Here are the Symbols of UCD:-

Actor Connector Use case System

Figure 3. 5 UCD

26
 Log in

Register member

Records

Create
institution

Staff

Manage other
expensive

Reports

User
Admin

Figure 3. 6 Use Case Diagram

27
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 object-oriented
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(webo, 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
3.7.1 EntityRelationship 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 describes this.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(lucidchart, 2017). 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)

28
3.7.1.1ERD 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.

Entity Relationship Attribute Line

Figure 3. 7 ERD

3.7.1.2 TYPES OF RELATIONSHIPS

Relationship is an association among one or more entities. J his relationship can be

broadly classified into one-to-one relation, one-to-many relation many-to-many
relation

 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 relationship

 One to one Relationship Type: Abbreviated 1:1, one to one relationships is a

special case of one to many relationships True one to one relationship is rare
the relationship between the president and country is Example is one to one
1ationship
.
 Many to Many Relationship Type: Abbreviated M: M, the relationship

29
MPLOYEE entity and PROJECT entity is an example of many
Relationships many employees will be working in many projects hence
Re1ationship between employee and project is many to many relationships.

 Many to One Relationship Type: Abbreviated M: 1, the relationship between

MPLOYEE and DEPARTMENT is an example of many to one relationship,
Three may be EMPLOYEE working in one DEPARTMENT hence relationship
And DEPARTMENT is many to one relationship. (s.sumathi.2007)

Table 3. 3 ERD

Relation Type Representation

One-to-one

One-to-many

Many-to-many

Many-to-one

30
3.7.1.3 ERD of the Proposed System

Login Home Records

1 * 1

*
Online Parent Parents
Record Keeping

Information System

Location School * 1 Parent

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 Android. 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.

31
Feasibility study is divided into four types:-

1. Technical Feasibility.
2. Operational Feasibility.
3. Economic Feasibility.
4. Schedule Feasibility.

3.9.1 Technical Feasibility

Technical Feasibility is defines as the feasibility that is concerned with specifying

equipment and software that will successfully satisfy the requirement. It compasses
the technical needs of the system Configuration of the system is given a huge
importance than the actual make of hardware while examining technical
feasibility(quora, 2017).

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.

32
Table 3. 4 Technical Feasibility

No Item Description Quantity Cost Per Amount

Unit

1. Laptop Corei3 1 $360.00 $360.00

2. Hp laserjet1563 MFP 1 $40.00 $40.00

Total $400.00

Table 3. 5 Items

No Item Description Quantity Cost Per Unit Amount

1. JSP& MYSQL 1 Free

Total Free

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.

Table 3. 6 Operational Feasibilit

Activities Duration Expected Cost

Training Current 1 Week $300.00

Employee

Training New Employee 2 Week $600.00

Total $900.00

33
3.9.3 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. 7 Economic Feasibility

Types of feasibility Description Expect Cost

Technical Hardware & software $400.00

feasibility

Operational Training with best option $900.00

feasibility

Total $1300.00

3.9.4 Schedule Feasibility

Typically this means estimating how long the system will take to develop, and if it can
be completed 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.

34
Table 3. 8 Schedule Feasibility

Level Phase Name Duration

1 Analysis phase 8 week

2 Design phase 7 week

3 Coding 6 week

4 Implementation and Testing 5 week

5 Operation and maintenance phase 2 week

Total 28 week

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

35
 CHAPTER FOUR

SOFTWARE DESIGN

4.0 Introduction
This chapter will discuss about the software design of the Design & Develop of web-based
cash receipt generation system for notary. Designing is the most significant phase of software
development it requires a careful planning and philosophy on the part of the system designer.
The design phase involves converting the System Requirement Specification (SRS) identified
during the initiation and planning phases in to a logical Design and then into Physical Design
that the technical programmer can follow to develop the project during the development phase.
Design will play a bigger role in every project, therefore; developing a good design is needed
and related to have enough information.

4.1 Architectural Design

The Design & Develop of web-based parent record keeping information system will have the
following features:

Login Dashboard Login User Reg

4.2 Figure 4.1 architecture designs

Registration Owner Report

36
 4.2 User Interface Design
Interface design is the process of defining how the web will interact with the external entities
“web apps or other web browsers”. It describes the layout of the pages and the flow of events
and is also concerned with where and how data are represented on the pages. However, in a
User Interface Design, the needs, experience, and capabilities of the web users must be taken
into account. In addition, the designers should be aware of users‟ physical and mental
limitations. The user of this digital system doesn’t need any software to install, but only
requires a browser interface to access it. To access the web, users will be required to have
login through the web login page, which can be accessed via homepage.

Figure 4.2 User Interface

4.3 Database Storage Design

Design for database for using MYSQL with relational database system Provides minimum
search times when locating specific records. That will provide Stores data in the most efficient
manner possible to keep the database from growing too large, makes data updates as easy as
possible and creating more flexible enough to allow inclusion of new functions required of
the Web apps.

37
 4.4 Database Design
Database design process integrates relevant data in such a manner that is can be processed
through a mechanism for recording the facts. A database of an organization is an information
repository that represents facts about the organization. The database design is a complex
process. The complexity arises mainly because of the identification of relationships among
individual components and their representation for maintaining correct functionality are
highly involved. The complexity increases if there are many-to-many relationships among
individual components. This section discusses about the database created for this project. The
database is created using MYSQL.

4.4.1 Database Normalization

Normalization is the process of organizing data in a database. This includes creating tables
and establishing relationships between those tables according to rules designed both to protect
the data and to make the database more flexible by eliminating two factors: redundancy and
inconsistent dependency. Redundant data wastes disk space and creates maintenance
problems. Most popular Normalization stages include.
First Normal Form(1NF), Second Normal Form(2NF) and Third Normal Form(3NF)

4.4.2 First Normal Form (1NF)

A relation is in first normal form (1NF) if the following two constraints both apply: There
are no repeating groups in the relation (thus, there is a single fact at the intersection of each
row and column of the table) and A primary key has been defined, which uniquely
identifies each row in the relation.
A database is in first normal form if it satisfies the following conditions:
• Contains only atomic values
• There are no repeating groups

38
4.4.3 Second Normal Form (2NF)

A relation is in second normal form (2NF) if it is in first normal form and contains no
partial functional dependencies. A partial functional dependency exists when a non-
key attribute is functionally dependent on part (but not all) of the primary key. To
convert a relation with partial dependencies to second normal form, the following steps
are required: Create a new relation for each primary key attribute (or combination of
attributes) that is a determinant in a partial dependency. That attribute is the primary
key in the new relation. Move the non-key attributes that are dependent on this primary
key attribute (or attributes) from the old relation to the new relation.
A database is in second normal form if it satisfies the following conditions:
 It is in first normal form
 All non-key attributes are fully functional dependent on the primary key

OID Name Phone User Password Reg_Date

1 Mohamed 615386886 Deeq 1231 2020-01-10
2 Ali Omar 613203050 Mustaf 1412 2020-01-10

Table 4.3 Second Normal form

Loc Location Reg_Date

1 Wadajir – suuqa weyn 2021-01-15
2 zoope – Km5 2021-01-15

4.4.4 Third Normal Form (3NF)

A relation is in third normal form (3NF) if it is in second normal form and no transitive
dependencies exist. A transitive dependency in a relation is a functional dependency
between the primary key and one or more non-key attributes that are dependent on the
primary key via another non-key attribute. You can easily remove transitive dependencies
from a relation by means of a three-step procedure: 1) For each non-key attribute (or set of
attributes) that is a determinant in a relation, create a new relation. That attribute (or set of

39
 attributes) becomes the primary key of the new relation. 2) Move all of the attributes that
are functionally dependent on the primary key of the new relation from the old to the new
relation. 3) Leave the attribute that serves as a primary key in the new relation in the old
relation to serve as a foreign key that allows you to associate the two relations. table and
stays as foreign key in the old table.
A database is in third normal form if it satisfies the following conditions:
 It is in second normal form
 There is no transitive functional dependency

Table 4.3 Third Normal Form

CID Name Phone User Password Reg_Date

1 Cali cabdi 615169538 Cadde 7890 2021-05-2020

2 Suldan xusen 618044375 yarre 4375 2021-05-2020

Table 4.4 Third Normal Form

CID Name Phone Address Email Reg_Date

1 Cali cabdi 615169538 Waberi Cade1234@gmail.com 2021-05-2020

2 Suldan xus 618044375 shangaani Suldanxusen475@ 2021-05-2020

40
Table 4.5 Third Normal Form

Loc Children Location Reg_Date

1 Cali cabdi Waberi 2021-05-2020
2 Suldan xusen shangaani 2021-05-2020

4.4.5 Normalized Tables of the proposed system

Normalization of Database can decrease redundancy, increase efficiency and reduce
anomalies by implementing three of seven different levels of normalization called
Normal Forms. The first three NF’s are usually sufficient for most small to medium
size applications.
Table 4.4 Normalized Tables

CIDName Phone Address Email Sex Reg_Date

1 Cali cabdi 615169538 Cadde Cadde1234@gmail Male 2021-05-2020
2 Suldan xus 618044375 yarre Suldanxusen475@ Male 2021-05-2020

Table 4.5 Normalized Tables

CID Name Phone User Password Reg_Date

1 Cali cabdi 615169538 Cadde 7890 2020-01-10
2 Suldan xus 618044375 yarre 4375 2020-01-10

Loc Location Reg_Date

1 Waberi 2021-05-2020
2 Shangaani 2021-05-2020

41
Table 4.6 Normalized Tables

Loc Children Location Reg_Date

1 Cali cabdi Waberi 2021-05-2020
2 Suldan xusen Shangaani 2021-05-2020

4.4.6 Transforming E-R Diagrams into Relations

Documents, and organize specific facts about system include the data flows, data stores,
external entities, and processes. The data dictionary also defines and describes all data
elements and meaningful combinations of relations.

4.4.7 Data Dictionaries

Data dictionary, or data repository, is central store house of information about System’s data.
I will use it to collect, document, and organize specific facts about system include the data
flows, data stores, external entities, and processes. The data dictionary also defines and
describes all data elements and meaningful combinations of data elements.

42
Table 4. 1Children Table

Column Type

ID (Primary) int(11)

Name varchar(50)

MotherName varchar(50)

Gender varchar(20)

Age varchar(10)

ClassID int(11)

Description varchar(100)

RegDate varchar(20)

Table 4. 2Class Table

Column Type

ID (Primary) int(11)

ClassName varchar(100)

SchoolID

43
Table 4. 3Discipline Table

Column Type

ID (Primary) int(11)

StudentID int(11)

Description varchar(100)

Date date

Table 4. 4Location Table

Column Type

ID (Primary) int(11)

LocationName varchar(100)

Table 4. 5School Table

Column Type

ID (Primary) int(11)

SchoolName varchar(100)

LocationID int(11)

Phone1 varchar(20)

Phone2 varchar(20)

44
 Table 4. 6 Users Table

Column Type

ID (Primary) int(11)

Username varchar(50)

Password varchar(50)

RecoveryPin varchar(20)

4.5 Designing Forms and Reports

The most effective method of online data entry is a form filling, in which a blank form that
duplicates or resembles the source document is completed on the screen. The user enters the
data and then moves to the next field. The form can have many control features such as menu
bars, toolbars, dialog boxes, text boxes, command buttons, list boxes, scrollbars, drop-down,
group boxes, check boxes, and more others. The design of data entry screens shall consist of
the following forms is used to o register the locations or addresses of the users of the system.

Figure 4. 1 form rejistration

Figure 4. 4 login form

45
This Login form is used to check other users

Figure 4. 2 User Form Design

Above form design is used to register and modify users of the system, a system without
user management isn’t a good.

Figure 4. 4 employee Form Design

Figure 4. 3 develper

4.6 Chapter Summary

Design, Data storage design, database design, Normalization, Transforming E-R diagram
into relations, data dictionaries, design forms and finally chapter summary.

46
 CHAPTER FIVE

SYSTEM IMPLEMENTATION
5.0 INTRODUCTION
System implementation is a process of ensuring that the information system is
operational. Implementation allows the users to take over its operation for use and
evaluation. It involves training the users to handle the system and plan for a smooth
conversion.(implementation, 2018)

This chapter will include Coding phase, Test system implementation, development
testing, release testing, user testing, developing user manuals and chapter summary.

5.1 Coding Phase

The coding phase of the software life-cycle is concerned with the development of code
that will implement the design. This code is written is a formal language called a
programming language. Programming languages have evolved over time from
sequences of ones and zeros directly interpretable by a computer, through symbolic
machine code, assembly languages, and finally to higher-level languages that are more
understandable to humans. (INN, 2009)

This Phase is devoted to providing access to most of the computer programs that the
researcher used to prepare the data and apply the programming is techniques,
instructions on how to construct this application project using the software available
on the attached compact disk (CD).

47
5.2 Sample Code

<!DOCTYPE html>

<%@ taglib uri="http://java.sun.com/jsp/jstl/core" prefix="c" %>

<%@ taglib uri="http://java.sun.com/jsp/jstl/functions" prefix="fn" %>

<%@ taglib uri="http://java.sun.com/jsp/jstl/sql" prefix="sql" %>

<html>

<head>

<title></title>

</head>

<body>

<sql:setDataSource var="uniso" driver="com.mysql.jdbc.Driver"

url="jdbc:mysql://localhost/parentkeeping" user="root" password=""/>

<sql:update dataSource="${uniso}" var="ok">

INSERT INTO address VALUES(null, '${param.b}')

</sql:update>

<c:if test="${ok==1}">

<p>Inserted Successfully</p>

</c:if>

</body>

</html>

48
5.3 Test system implementation

The testing phase involves some modification to the pervious design phase and system
testing has been done to minimize the programming errors.

Testing the system is a very important stage to ensure that all system requirements
have been developed without errors. System testing can be done through some stages.
These include.

1. Developing test

2. Release test

3. User test

5.4 Development testing

Development testing is a software development process that involves synchronized

application of a broad spectrum of defect prevention and detection strategies in order
to reduce software development risks, time, and costs. Development testing is always
done by the developer who is responsible programming stage.

This testing shows as if wrong username and password is entered can’t allowed to
access the system.

Figure 5. 1 Login Failed

49
5.4.1 Release testing

Prior to making a software system available for public consumption, a series of tests
should be conducted to ensure the software runs as intended. Flaws are fixed and
inefficiencies removed to come up with a program that runs seamlessly. A battery of
tests is conducted with a view towards identifying and fixing bugs, which are a
precursor for system failure. It is an essential part of the Software Development Life
Cycle (SDLC), and may perhaps be considered the most important aspect, aside from
design and coding. Indeed, the quality of the product plays a huge part in setting the
stage for the acceptance and success of subsequent ones in the market. With this in
mind testing hitherto release of software should not be taken for granted. (Brown,
2016)

The ability to evaluate and ensure the quality of in-process and/or final product based
on process data, which typically include a valid combination of measured material
attributes and process controls. A release is the distribution of the final version of an
application. A software release may be either public or private and generally
constitutes the initial generation of a new or upgraded application.

Figure 5. 2 Location Release Testing

50
5.4.2 User testing

User testing refers to a technique used in the design process to evaluate a product,
feature or prototype with real users. There are several reasons why you might want to
undergo usability testing, the most common is that it allows the design team to identify
friction in a user experience they are designing, so that it can be addressed before being
built or deployed. Identifying any issues early reduces the long-term cost. (user-testing,
2018)

This system has been tested by the user (alpha testing), the developer and the user (beta
testing), and the user only in his work location (Acceptance testing).

Alpha Test: An alpha test is a preliminary software field test carried out by a team of
users in order to find bugs that were not found previously through other tests. The main
purpose of alpha testing is to refine the software product by finding (and fixing) the
bugs that were not discovered through previous tests.(alpha-test, 2017)

Beta Test: Beta testing is also sometimes referred to as user acceptance testing (UAT)
or end user testing. In this phase of software development, applications are subjected
to real world testing by the intended audience for the software. The experiences of the
early users are forwarded back to the developers who make final changes before
releasing the software commercially.(Rouse, 2015)

Figure 5. 3Dashboard

51
5.4.3 Developing User manuals

In computer software product development, documentation is the information that

describes the product to its users. It consists of the product technical manuals and
online information (including online versions of the technical manuals and help facility
descriptions).

The term is also sometimes used to mean the source information about the product
contained in design documents, detailed code comments, white papers, and blackboard
session notes. The term is derived from the idea that engineers and programmers.

Also, is a general term for a multiplicity of documents in a chosen mix of media and
with a certain collection. Purpose of documentation is the use to support a tool or a
process. Classical documentation is a set of documents printed on paper

5.5 Chapter Summary

This chapter discusses about the implementation and testing of the system. Developing
the system requires a server, host to access the portal. The purpose of the Testing is to
check the errors and analyze the problem in order to develop a successful System that
meets the users’ requirements. In this I have discussed important points on the system
Development starting form introduction of the chapter then the Coding step of system,
Types of testing, User Documentation, and the last Implementation although I have
covered majority of the project now I am going to Conclude and Summarize this
research and for recommendations of the project.

52
 CHAPTER SIX

CONCLUSION & ENHANCEMENT

6.0 INTRODUCTION

This chapter covers the achieved objectives of the project and demonstrates how the works of
this project is implemented. Also, it debates the experiences that have been gained during
development of this project and it also includes the future recommendation which will
facilitate how to improve the functionality and features of this system in the future.

6.1 OBJECTIVE ACHIEVEMENT

The key objective for developing this project is to develop point of sale management
information system; the project will be applicable to the other universities. Furthermore, here
are the details of the project objectives that have been accomplished.

1. The researcher designed the point of sale management system using modeling tools such
as unified modeling language (UML) diagrams including use cases diagram and class
diagram.

53
2. The research coded the proposed system and tested it; during implementation
phase of the project using with JSP for end and MYSQL for back end, and eventually
achieve this objective properly.

Generally, all the objectives above mentioned have been attained and the constraint
of the users has been met through the project.

Constraints and Challenges

Through the process of developing this project, I have faced some complications and
constraints. Some of these difficulties related to the study of the project and its
related topics and others are related to the implementation and design of the project.
The most important challenges faced are underlined as follows:

 Designing of the project was the difficult challenge that I have faced since
more alternatives are considered.

 Challenges to learn how java server page function, and their technologies

 Difficulties were faced during design the project of the project, such as
normalization processes and etc.

 Following and keeping malaria app thesis format and guidelines was one of
the most difficult tasks to encounter during the certification of the report.

 Other challenges include lack of time which also was one of the challenges
confronted during the implementation of the system.

54
6.2 WEEKNESSES AND PROBLEMS OF THE SYSTEM

A lot of experiences have been gained during this project such that the literature
review provided knowledge of existing system of Java systems for universities, and
also it helps in identifying the weaknesses and the strengths of the developing system
by comparing the features of the system that is going to be developed with three
existing systems which are related to it.

During the methodology study, it identifies the software engineering methodology

for any software engineering system. Moreover, one of the most experiences gained
during this project was the methods used to get the requirements from the user and
doing the practice in analyzing the collected requirement to achieve the objectives of
the system.

6.3 FUTURE WORK & RECOMMENDATIONS

The future enhancements of the system are as follows:

1. To improve the security and privacy of this system for organization.

2. To add helpdesk for the sake of solving the problems may be faced by the new
user of the system.

3. To extend scope of the project and include extra modules and functions.

6.4 CHAPTER SUMMARY

This chapter discussed Introduction, Objectives Achieved, Weaknesses and problems

of the system, Future Work and Chapter Summary.

55
 REFERENCES

Point of sale (POS) systems are electronic systems that provide businesses with the
capability to retain and analyze a wide variety of inventory and transaction data on a
continuous basis. POS systems have been touted as valuable tools for a wide variety
of business purposes, including refining target marketing strategies; tracking supplier
purchases; determining customer purchasing patterns; analyzing sales (on a daily,
monthly, or annual basis) of each inventory item, department, or supplier; and
creating reports for use in making purchases, reorders, etc. Basic point of sale
systems currently in use include standalone electronic cash registers, also known as
ECRs; ECR-based network systems; and controller-based systems. All function
essentially as sales and cash management tools, but each has features that are unique.

Standalone ECRs. These electronic registers operate independently of one another,

and are thus the most limited of the three POS system types. They cannot provide
their owners with storewide reporting or file sharing; they can merely report the
business activity at that particular register. Given its limitations, ECRs are usually
used by small independent retailers that feature a limited number of register sites.
Indeed, these systems are often well suited for small businesses because they are the
least expensive of the POS system options, they nonetheless provide many helpful
features, including automatic sales and tax calculation ability; calculation of change
owed to the customer; sales report generation capability; capacity to sort food stamps
and trading stamps (through programming of function keys); and scanning.

Network Systems . Network or ECR-based point-of-sale systems feature multiple

terminals arranged into a primary/secondary configuration. One ECR in the store,
equipped with extra memory capacity, serves as the primary terminal and receives
data from the secondary terminals. These systems give businesses the added capacity
to manage storewide data and transmit data to mainframe systems.

Controller-Based POS Systems . The top POS systems are controller-based systems
in which each terminal is connected to a computer—the "controller" of the system—
which receives and stores all sales, merchandise, and credit data. "The controller
checks all data from the terminals for transmission errors and reformats the data for
use by the headquarters computer," explained Chain Store Age Executive. "It may
also perform sales analysis and price look-up. By having a dual-controller
arrangement in which the computers back each other up, the chance for a total

73
system failure can be reduced. Because of the importance of accurate data capture in
sophisticated point-of-sale systems, retailers are increasingly turning to scanning as
an alternative to error-prone keypunch entry." Indeed, scanning became a ubiquitous
feature in many of the nation's most modestly-sized retail outlets during the 1990s.

Point of sale systems, like many other computer based innovations, continue to
change and develop at a rapid pace. In addition, the demand for POS systems has
spawned many new manufacturers, each of which offer a dizzying array of standard
and optional POS features to their customers. For example, some electronic POS
systems now cover hand-held scanning devices, customer promotions, credit-card
confirmations, counterfeit money checks, and staff scheduling. Given the expense
involved and the proliferating number of POS software packages, small business
owners should make sure that they adequately research both their current and future
needs before making a purchase, so that they are able to acquire a customized POS
system that best fills their current operating requirements and can accommodate
future changes in the business. "Consider value—don't make your decision on price
alone," counseled National Petroleum News. "Look for a high level of connectivity
and compatibility with a multitude of peripherals. Demand customization
capabilities. Don't accept a system that's almost what you want when today's
technology makes it possible to customize one to exactly what you need."
Blair, Adam. "POS Data to Power Efficient Distribution." Supermarket News. March
22, 1999.

Durocher, Joseph. "Point of Departure: Don't Think of Your POS System as Merely
a Cashbox but Rather as a Management Tool." Restaurant Business. September 1,
1994.

Field, Christopher. "POS Man Always Rings Twice." Computing. October 22, 1998.

Murphy, Patricia A. "Cash Management Issues Foster Electronic Payments at Point

of Sale." Stores. July 1999.

"Systems to Keep the Checkout Counter Humming." Chain Store Age

Executive. October 1990.

74
APPENDICES

Appendix A – Budget

Items Unit Cost Units Total

Printing Costs

Drafts 0.5 Approx. 77 $7

Final 0.5 74 $10

Grand Total $17

75
 Appendix B – Time Frame of the Development of the proposed system

Nov Dec Jan Feb Marc April May

h

1 2 3 4 1 2 3 4 N/A
Task

N/A N/A 1 2 3 4 1 2 3 4

Research Proposal

Introduction

Literature Review

Software

Planning

Software Design

Software Development

Implementation
&testing

Conclusion
 APPENDIX C

BUDGET OF THE PROJECT

NO DESCRIPTION AMOUNTS

1 Communication Cost $20

2 Internet Cost $14

4 Transportation Cost $37

5 Stationery and Materials $19

6 Printing and Photocopy $11

7 Electric charge $116

Total Cost $217