POS SYSTEM Diploma in information technology Jomo Kenyatta University of agriculture and technology POS system Submitted in for the diploma In Information Technology in the Jomo Kenyatta University of Agriculture and Technology 2882265600710002018 DECLARATIONThis research project is my original work and has not been presented for any Academic award in any University

POS SYSTEM
Diploma in information technology
Jomo Kenyatta University of agriculture and technology
POS system
Submitted in for the diploma In Information Technology in the Jomo Kenyatta University of Agriculture and Technology 2882265600710002018
DECLARATIONThis research project is my original work and has not been presented for any Academic award in any University. No part of it should be reproduced without prior written permission of the author.

Name of candidate :
Registration Number:
Signature: ……………………… Date: …….…………………….

Declaration by the Supervisor
This thesis has been submitted for examination with my approval as University Supervisor.

Supervisor: Mr.
Signature: ……………………… Date: …….…………………….

ACKNOWLEDGEMENTS I would like to take this opportunity to thank all those who have in various ways helped me in writing my project proposal. I also thank Mr. Vincent Omwoma, my supervisor, for his constant source of inspiration in project proposal preparations.

TABLE OF CONTENTS
TOC o “1-3” h z u DECLARATION PAGEREF _Toc503771580 h iiACKNOWLEDGEMENTS PAGEREF _Toc503771581 h iiiABSTRACT PAGEREF _Toc503771582 h viiiCHAPTER ONE PAGEREF _Toc503771583 h 11.0 Introduction PAGEREF _Toc503771584 h 11.1 Background PAGEREF _Toc503771585 h 11.2 Problem Statement PAGEREF _Toc503771586 h 11.3 Objectives PAGEREF _Toc503771588 h 11 .4 Justification PAGEREF _Toc503771589 h 21.5 Scope and Limitation PAGEREF _Toc503771590 h 21.6 Schedule PAGEREF _Toc503771591 h 31.7 Budget PAGEREF _Toc503771592 h 3CHAPTER TWO PAGEREF _Toc503771593 h 4Literature Review PAGEREF _Toc503771594 h 42.0 Introduction PAGEREF _Toc503771595 h 42.1 Acquisition PAGEREF _Toc503771596 h 42.2 Redeployment PAGEREF _Toc503771597 h 42.3 Functions PAGEREF _Toc503771598 h 42.4 Types of POS systems PAGEREF _Toc503771599 h 42.5 Three-Tier Design PAGEREF _Toc503771600 h 52.6 Machine Repository-Based Design PAGEREF _Toc503771601 h 62.7 Components of an POS system PAGEREF _Toc503771602 h 62.7.1 Reorder Point PAGEREF _Toc503771603 h 62.7.2 Asset tracking PAGEREF _Toc503771604 h 62.7.3 Service management PAGEREF _Toc503771605 h 62.7.5 Competitors in POS system PAGEREF _Toc503771606 h 72.7.6Use of radio frequency identification. PAGEREF _Toc503771607 h 72.7.7Data on the cloud. PAGEREF _Toc503771608 h 72.7.8 Analytic to drive efficiency. PAGEREF _Toc503771609 h 72.7.9 Challenges in acquisition PAGEREF _Toc503771610 h 72.8 Purchasing PAGEREF _Toc503771611 h 72.8.1 Development PAGEREF _Toc503771612 h 82.8.2 How much are you willing to pay PAGEREF _Toc503771613 h 82.8.3How long will it take to learn PAGEREF _Toc503771614 h 82.8.4Threads in the system PAGEREF _Toc503771615 h 82.8.5 Related work PAGEREF _Toc503771616 h 8Reviews PAGEREF _Toc503771617 h 8CHAPTER THREE PAGEREF _Toc503771618 h 103.0 System Analysis PAGEREF _Toc503771619 h 10Table 3.0 PAGEREF _Toc503771620 h 113.1.0 Feasibility Study PAGEREF _Toc503771621 h 113.1.1 Technical Feasibility PAGEREF _Toc503771622 h 113.1.2 Social Feasibility PAGEREF _Toc503771623 h 123.1.3 Economical Feasibility PAGEREF _Toc503771624 h 123.1.4Feasibility Study Report PAGEREF _Toc503771625 h 133.1.5 Introduction PAGEREF _Toc503771626 h 133.1.6 Recommendation PAGEREF _Toc503771627 h 133.1.7 Software Requirement Specification PAGEREF _Toc503771628 h 143.1.8 Introduction PAGEREF _Toc503771629 h 143.1.9 Purpose PAGEREF _Toc503771630 h 143.1.10 Scope PAGEREF _Toc503771631 h 143.1.11 Product functional and non-functional requirements PAGEREF _Toc503771632 h 143.2.5.8 Functional Requirements PAGEREF _Toc503771633 h 143.2.5.9 Non-Functional Requirements PAGEREF _Toc503771634 h 153.2.5.10Specific Requirements PAGEREF _Toc503771635 h 163.2.5.11Technology used: PAGEREF _Toc503771636 h 16CHAPTER FOUR PAGEREF _Toc503771637 h 174.0 System Design PAGEREF _Toc503771638 h 174.1 System Architecture PAGEREF _Toc503771639 h 174.2 System overview PAGEREF _Toc503771640 h 174.3 The figure below shows system overview. PAGEREF _Toc503771641 h 184.4 The figure below shows the architecture of the proposed system PAGEREF _Toc503771642 h 194.5 Use Case Diagram PAGEREF _Toc503771643 h 204.6 Context Diagram PAGEREF _Toc503771644 h 214.7 Diagram Zero PAGEREF _Toc503771645 h 22Figure 4.8 Diagram 1 (a) Submit Form PAGEREF _Toc503771646 h 23Fig 4.9 Diagram 1(b) Authenticate User PAGEREF _Toc503771647 h 24Fig 4.10: Diagram 1(c) Define access Rights PAGEREF _Toc503771648 h 25Fig 4.11: Diagram 2 (c) Manage System PAGEREF _Toc503771649 h 26Fig 4.12: Diagram 2 (c) (ii) Access channels PAGEREF _Toc503771650 h 274.13Data Dictionaries PAGEREF _Toc503771651 h 284.14 Data Structure PAGEREF _Toc503771652 h 294.7.1 Data Structure Description PAGEREF _Toc503771653 h 294.15 Database Design PAGEREF _Toc503771654 h 304.16 Entity Relationship Modeling PAGEREF _Toc503771655 h 30Figure 4.17 ER Diagram PAGEREF _Toc503771656 h 31CHAPTER FIVE PAGEREF _Toc503771657 h 32System Implementation PAGEREF _Toc503771658 h 325.0 Tools used PAGEREF _Toc503771659 h 325.2 Wamp server PAGEREF _Toc503771660 h 325.3 Mozilla Firefox PAGEREF _Toc503771661 h 32System testing PAGEREF _Toc503771662 h 325.4Test results PAGEREF _Toc503771663 h 32Fig 5.1 staff sign up page/login page PAGEREF _Toc503771664 h 33Fig 5.2 unregistered user Error Message PAGEREF _Toc503771665 h 34Fig 5.3. System interface whenever one has login in successfully PAGEREF _Toc503771666 h 34Fig 5.4 adding inventory into the system PAGEREF _Toc503771667 h 35Fig 5.5 removing inventory from the system PAGEREF _Toc503771668 h 36Fig 5.6 when one has successfully searched equipment PAGEREF _Toc503771669 h 365.7 SYSTEM TESTING. PAGEREF _Toc503771670 h 375.8 IMPORTANCE OF SYSTEM TESTING PAGEREF _Toc503771671 h 375.9 DIFFERENT HIERARCHICAL LEVELS OF TESTING PAGEREF _Toc503771672 h 37CHAPTER SIX PAGEREF _Toc503771673 h 396.0 Summary, Recommendation and Conclusion PAGEREF _Toc503771674 h 396.1 Summary PAGEREF _Toc503771675 h 396.2 Conclusion PAGEREF _Toc503771676 h 396.3 Recommendation PAGEREF _Toc503771677 h 396.4 Appendices PAGEREF _Toc503771678 h 39References PAGEREF _Toc503771679 h 43
ABSTRACTPoint of sale systems have changed how people buy products in multiple stores for a long time. Prior to the digital age, vendors would use multiple types of books to keep records of their sales and stock. The system worked for a long time until the world human population could no longer be managed by books and written documents. Human errors became the number on loss stimulant making the biggest losses ever recorded in history.
Ushering in the digital era, Point of Sale systems have all been computerized minimizing the scale of error. Taking of stock is way easier. The computerized systems have add-ons that ensure security of goods for instance the barcodes. POS systems weren’t enough for many people. Businesses wanted more. Most businesses are way bigger than most point of sale systems can handle.
This document fully describes the new point of sale built on the basis of ubiquity. The new system will run on distributed server technology making work easier for businesses around the world. Integration of digital and mobile money payment methods makes it even more interesting
CHAPTER ONE1.0 Introduction1.1 BackgroundPOS system is a software system for managing and tracking inventory levels, orders, sales and deliveries. Lesonskey, Rivera (1998). States that an POS system can also be used in the manufacturing industry to create a work order, bill of materials and other production-related documents. Companies use POS software to avoid product overstock and outages. It is a tool for organizing inventory data that before was generally stored in hard-copy form or in spreadsheets. Was adopted by the grocery industry in April 1973 as the standard barcode for all grocers, though it was not introduced at retailing locations until 1974. Markowitz, Robert (August17, 2010). States that starting in the early 2000s, POS software progressed to the point where businesspeople no longer needed to input data by hand but could instantly update their database with barcode readers. Also, the existence of cloud based business software and their increasing adoption by businesses mark a new era for POS software
1.2 Problem StatementThe main aim for coming up with the proposed system is replace the manual one that will be more secure and more efficient to use while storing data and retrieving data. The old POS software has the following features; The system does not provide a single function via a page.

Data is only kept in record books which can be stolen or get lost
The system has difficult to view since books are hard to view data has to search Page per page
1.3 ObjectivesThis is going to replace the manual and traditional way of keeping company records at large this are some of the way it is going to replace the existing ways it is going to be secure data in the database where only registered users can access it;
The proposed system will help tracking on how inventory will enter in the warehouse, how they are distributed and the condition of the already distributed in several offices.

Monitor the inventory that is either purchased or acquired legally.

How the inventory is being distributed across all the offices for utilization.

Show the remaining inventory for one to make decision on to increase the stock.

1 .4 JustificationThis proposed system is intended to replace the manual way of keeping data in the organization therefore to help modernize the way of data entry in records for organizational purposes. The system is going capture all products that are going to be stored in the warehouse/malls/supermarkets/stores etc., those in use and those that are default but still in work waiting to be replaced with new one. The good thing with the system it is going to be modern since one is able to see all the inventory the company owns there able to what commodities needs to be replaced and what to dispose as faulty.

1.5 Scope and Limitation Time factor will be the greatest barrier to the successful completion of this exercise since it will be done within the semester, since time has proven to be a great factor in completion of work. Skill is also a challenge since the project will need some skills that are more professional and has complex coding. In this case one is required to have knowledge of the various software that will be used in the developing of the project.

1.6 ScheduleThe system will take about three months to do analysis, design, develop, test and implement and train users how to operate.

Duration(weeks)
Project title 1-2 analysis 2-4 Design 5-9 Implementation 9-10 Testing 11-12 Training 13-14
1.7 BudgetThe projected costs for the system are outlined in the table below:
Items Description Cost (KShs.)
Labor Remuneration 15,000
Computer Hard disk, 2GB RAM, 4.6 GHZ
Processor speed DVD R/W 50,000
Printing Project proposal
Project plan
User manual
Project paper 250
250
1200
15,00
Research Traveling cost
Internet (MODEM)
Communication cost 2,500
1,000
800
Stationery Flash disk (2GB) 750
Error tolerance Contingencies 2,000
Total 75,200
CHAPTER TWOLiterature Review2.0 Introduction POS software is a software system for tracking inventory levels, orders, sales and deliveries. The system is an enterprise-wide discipline concerned with the identification and tracking of Information Services hardware and software assets. Its three main
Areas of concern are:
2.1 AcquisitionThe proposed system is going to made by a system developer where they are paid so it is going to remain the company asset once finished
2.2 RedeploymentProcedures are responsible for ensuring that assets are tracked in the organization
2.3 FunctionsThe objective of POS is to manage the physical and logical properties of resources and their relationship, while ensuring that service level commitments are achieved. This process will: To identify and track all data processing assets in an Inventory System Repository. To define the process by which assets are identified and maintained in the
2.4 Types of POS systems This is the view of the software we wanted to build, we set about to actually Design it. Although we considered many possible architectures, there were two Alternatives that our team debated: the Three-tier Client-server Architecture and The Repository-Based Architecture. They both seemed fairly appropriate, so we present them both here:
2.5 Three-Tier DesignThe three-tier model is a type of client server architecture. This model consists of two types of machines, service consumers (clients) and service providers (Servers). What is most important about this architecture is that clients and Servers may or may not be running on dedicated machines. Thus it is possible for a machine to act as both a client and a server depending on the situation. In The case of PRO, the clients will be the individual microcomputers all around the Company and the central server will be the provider.

2.6 Machine Repository-Based DesignRepository based architecture is very similar to the client-server model described above. The system revolves around a central data structure (usually a Database), and a collection of independent components which operate on the Central data structure. One of the only main differences between this and the Three-tier model is that in this case there is a dedicated server and dedicated Clients. Under no circumstances can a client machine become a service Provider, thus the system is very directed and straightforward. In the case opry, the central data structure would be the inventory database, which would be Located on the server. Each client would access the server over the network and Query the data they require. All software procedures would be present.

2.7 Components of an POS system2.7.1 Reorder PointThe POS system should have a point recorder for the products that are received in the warehouse for them to be identified. Should inventory reach a specific threshold, a company’s POS system can be programmed to tell managers to reorder that product. This helps companies avoid running out of products or tying up too much capital in inventory.

2.7.2 Asset trackingWhen a product is in a warehouse or store, it can be tracked via its barcode and/or other tracking criteria, such as serial number, lot number or revision number. Systems. For Business, Encyclopedia of Business, 2nd ed. nowadays, POS software often utilizes barcode, radio-frequency identification (RFID), and/or wireless tracking technology.

2.7.3 Service managementCompanies that are primarily service-oriented rather than product-oriented can use POS software to track the cost of the materials they use to provide services, such as cleaning supplies. This way, they can attach prices to their services that reflect the total cost of performing them.

2.7.4 Product identification
Barcodes are often the means whereby data on products and orders is inputted into POS software. A barcode reader is used to read barcodes and look up information on the products they represent. Radio-frequency identification (RFID) tags and wireless methods of product identification are also growing in popularity. Modern inventory software programs may use QR codes or NFC tags to identify inventory items and smartphones as scanners. This method provides an option for small businesses to track inventory using barcode scanning without a need to purchase expensive scanning hardware.

2.7.5 Competitors in POS system2.7.6Use of radio frequency identification.The use of (RFID) for locating individual products components and their respective quantity/quality monitoring has also been in the play since POS trends since 2015. Employees will carry a handled device which will emit corresponding signals that will connect with the chip to retrieve location, quantity or other related vital.

2.7.7Data on the cloud.Small, medium and big enterprises are moving their POS process to cloud-based systems that offer flexible scalability at affordable pricing.

2.7.8 Analytic to drive efficiency.Inventory optimization and analytic have been like hand in glove since ages. Metrics like stock levels, stock cycles have helped mangers store optimum stock levels.

Combined with cloud technology and ERP reports, analytics will help enterprises to develop deeper into inventory data derive important information.

2.7.9 Challenges in acquisition 2.8 PurchasingOne needs to identify what kind of system he or wants, the stock or the asset management system so that you don’t buy impulsive. Because there are consumed and those that are long term assets
(www.waspbarcode.com)
2.8.1 DevelopmentIt’s good for one to consider what are the features the that the system will be having because it is to be caught up with bells and whistles
2.8.2 How much are you willing to payAs a small business you are likely to have tighter budget, and it’s important to get the most for your money. On the other hand, is to lose more time and money.

2.8.3How long will it take to learn Lengthy software training one has to choose software that several employees can learn relatively easily CITATION asa1 l 1033 (asapsystems, n.d.).

2.8.4Threads in the system
1) Information being hacked by thugs either from inside the company or outside sources
2) The data can be destroyed by viruses inside the computer
Prevention mechanism
1) Ensure that the system is protect thought that no one can access it without the authorization from authorities
2) The system should have cloud backup for safety purposes that is to ensure that even if the data on the computer is lost one is able to retrieve the work again without losing anything
2.8.5 Related workIn the modern ICT trends it’s possible to integrate two or three system to work together for easier functionality and saving time when carrying out daily operations in an enterprise there we should embrace this modern technology to make operations easier and flexible.

ReviewsAn POS system is powerful modern tool for tracking inventory levels, orders, sales and deliveries. The system is an enterprise-wide discipline concerned with the identification and tracking of Information Services hardware and software assets. Therefore, all small, medium and large enterprises should come up with one to monitor their goo ds as they enter and go out of there store for easier tracking. It saves time also because the system can be integrated with other system in the enterprise therefore saving more time than manual way of recording the inventory. During this research I have learned a lot about POS system. I have been able to examine various Examples of POS systems. Out of the various types of all POS systems I have decided to implement a company inventory system as my project, because I think there is need to improve on the way organizational workers and staff need to access information when there is need to I have discovered that developing a system consumes a lot of time as well as resources in terms of money and labor, I want to be sincere by saying that I might not be able to deliver a fully and complete functioning POS system. This of course will be attributed to the lack of enough time. However, to try and at least counter the above problem, I will most of the time rely on the help of open source codes available on the internet example Wikipedia and googleweblight. The key issue I will examine is security, there is need to the POS system to be safe attackers.
CHAPTER THREE3.0 System Analysis
Analysis is an important intermediate stage between investigation and design. It involves Examining all the facts collected or gathered in order to make a proper assessment of both the proposed system
In this system the method which was used to collect data was observation and use of other secondary sources such as literature books to gather enough data I was successful, these were the findings I got to understand the existing system.

For observation I was able observe the following;
The system could not provide a single function via a page.

The system was unfriendly user graphical interface and not interactive as users expected.

The system was difficult for users access the system.

The findings for the investigation were:
The information was accessed only in record books before where book records were kept for references
a) Possible solutions to the organization problem this section shows the comparison of the possible options to the business problems. Possible Solutions are compared to each other with respect to cost, level of application risk and efforts required.

Table 3.0Options Cost of purchase in
Kshs. Level of risk Effort Required
Purchase off the shelf
software Approx. 190,000/= Lowell–designed
solution and industry
Approved. Medium – Simple buy
and install
But can still fail if not
Implemented properly. Build Own Approx. 30000 Medium- well
designed solution,
developer has no much
experience High
3.1.0 Feasibility StudyOne the process of coming up with the system there were some factors we had to consider and it worth decision making to come up with a successful running system to replace the existing in place the areas that we concentrated on was;
3.1.1 Technical FeasibilityThis part deals technical and software that the proposed system must meet over the other one
The specification for hardware and software are as follows;
A total of 10 computers are required. They should have a capacity of 40 GB and above,
Processing speed of 1.0 GHZ and memory of not less than 512 MB.

The operating system preferably windows XP.

Antivirus software to protect against harm to data in the computer.

Microsoft access for the DBMS.

Server with at least 2GB RAM, duo core processor
Training of system administrators is required since the core people of the system. They can be taught through use of a tutor or through reading tutorials that can assist them to know more about operation of the system. A system administrator is needed to install and maintain the operating system and installing IDEs for updates.

3.1.2 Social FeasibilityOn implementing of the proposed system the user will accept and appreciate the user graphical interface we are going to improve on the existing one. It is going to be added more feature over the old one like user login for easier accessing the inventory of the company. It is also going to eliminate manual system which is sometimes used to store information in the company by the end the day the users of the system appreciate the proposed system and learn on how to operate it without much difficulty.
3.1.3 Economical FeasibilityThe estimated amount of money will cover all the costs that will be incurred on the process owing the fact that the system is viable.

a) Costs
The costs of the proposed system include:
Software Two
Software cost- Costs incurred when buying software windows xp
MySQL server
Browsers Mozilla Firefox or Google chrome
Equipment costs – Costs incurred when buying computers,
Development costs – Costs incurred during the development of the system.

Operational costs – costs incurred during the installation of the network devices and
Computer software.

b) Benefits
Reduces operational expenses e.g. printing costs, papers since most information that was
Once being printed can now be posted on the inventory system Workers save time checking in the books for the information required e.g.
The no of computers that are working in the whole building and the no of printers the company owns.
Users are saved from fatigue of filling and following through large chunks of paper as
They look for details.

3.1.4Feasibility Study Report3.1.5 IntroductionThe proposed POS system caters for the overhead costs incurred Through; allowing sharing of data among various departments hence no need to follow up on the Information through making calls, ensuring accuracy and integrity of data hence not susceptible to human errors, does not require much human effort hence saves.
3.1.6 RecommendationEven though there are initial costs or capital costs required for the success of the proposed System, the benefits in terms of availability, accuracy, convenience and currency out do costs.
3.1.7 Software Requirement SpecificationThere’s very little requirements for the system since it has been designed to be used even by kids. Software wise the system needs;
Stable internet connection
Linux server.

Browser: preferably chrome or firefox.

3.1.8 Introduction
The system’s main intended purpose is to manage sales. However, the POS system manages more than just sales. The proposed POS can be used to run ads to potential customers giving them the ads specific to what they purchase regularly.
3.1.9 PurposeThe purpose for the proposed system is monitor sales of products and services. The system automatically updates the database of products making it a stock auto manager too.

3.1.10 ScopeThe POS is the software that is going to track what is being used to show how product enter, how they are distributed and the condition they’re while operating in offices. The system will be used to achieve the following tasks:
Monitor the inventory that is either purchased or acquired legally.

Information integration.

How the inventory is being distributed in office across all the offices for utilization.

Show the remaining inventory for one to make decision on to increase the stock.

The condition of the product is being distributed in the several offices.

3.1.11 Product functional and non-functional requirements3.2.5.8 Functional RequirementsThis section of the requirements states the function of the system i.e. what the system
Should do.

a) User Authentication
All users must identify themselves using an username address and a password in order to gain access without registration one is not able to access the system.

b) Search and Navigation
The system allows one to search anything in the system because it has a database should be able to support search and navigational services to all users the system is not personalized it basically contains what the organization owns.

3.2.5.9 Non-Functional RequirementsThese are requirements that stipulate the performance levels required of the system for various
Kinds of activities to be performed.

a) Performance
The system will be efficient and fast in access of information requested by users.
b) Reliability
The system should have some tolerance to some of the errors that may occur. For example, Entry of invalid values by users should not make the system to halt rather it should provide error Messages trying to inform the admin of the error made.

c) Availability
The user should be able to access the system at the place of work only the admin is able to manipulate the exact details he/she needed.

d) Usability
The system should be easy to use and easy to understand user interface. Also the error
Messages should consist of simple language. This is so as to ease the operability of the system.
3. User Characteristics
The intended users (staff) should possess the following qualities.

They should be computer literate.

Have an understanding of navigations.

3.2.5.10Specific RequirementsThis section of the SRS contains all the requirements to a level of detail sufficient to
Enable designers to design a system to satisfy those requirements. Below is a brief description of entities that participate in the inventory system operation
Users – They include managers, staff. They are identified by email address and name.

System Administrators– They are like the technical staff. They define rights for users,
Manage the system with material and monitor events, add or remove information in the system
Default users –They are group of users who do not need to have registered, and they are
Allowed to access basic information on the inventory system.

3.2.5.11Technology used:Language: php, html, css, js
MySQL for database connection

CHAPTER FOUR4.0 System DesignThis section is going to explain the design issues involved in the system architecture, interface designs of data in web based application and Database modeling. It is going to let us know the relations and how it can be accessed throughout the system.

4.1 System ArchitectureSystem Architecture for the proposed POS system is based on the open source Web based applications. The servlet engine includes the Apache as well as web server.

4.2 System overviewThe proposed system is the third tier is between the user interface (client) and the data management components. This middle tier provides process management where business logic and rules are executed and can accommodate hundreds of users by providing functions such as queuing, application execution, and database staging.

4.3 The figure below shows system overview.23883622054Inventory
Staff
Scanners
Equipment
Printers
Computer categories
Pc model
monitor
Keyboard
Mouse
0Inventory
Staff
Scanners
Equipment
Printers
Computer categories
Pc model
monitor
Keyboard
Mouse

4.4 The figure below shows the architecture of the proposed system-4118936298Level 1
Level 3
Level 2
Database server
Application server
Client
SQL Query
Sending requests
0Level 1
Level 3
Level 2
Database server
Application server
Client
SQL Query
Sending requests

3105665114300016063784438100
4.5 Use Case Diagram114300846211Register
Login
Register new equipment
Monitor system
Update system
User
System admin
00Register
Login
Register new equipment
Monitor system
Update system
User
System admin
4053254254312600
4.6 Context Diagram6063586157218System admin
00System admin

-383545209648staff
00staff
3713441120569003913381202514Login
00Login
22462431111800
000
224624341192
00
2653555117880022462433166700
367407626661400368349851762003700091132918Add or remove staff
00Add or remove staff
369055020103700118364096520User register
00User register
221642527354700
9004395405003858260301625Access inventory
00Access inventory

132715016510Login
00Login
94930196560037692816984600
84709072390Access the inventory
00Access the inventory
access
385000525400Update system
00Update system

4.7 Diagram Zero0-635User
Authenticate User
4
Fill Login
3
Submit form
2
5
Reg form
2
User
Authenticate User
4
Fill Login
3
Submit form
2
5
Reg form
2

Figure 4.8 Diagram 1 (a) Submit Formleft84438staff
2.1
Validate form
2.2
Prepare error notice
2.3
Successful notice
staff
Staff form
Successfully
Filled form
Form errors
Error message
staff record
Response
Successful information message
00staff
2.1
Validate form
2.2
Prepare error notice
2.3
Successful notice
staff
Staff form
Successfully
Filled form
Form errors
Error message
staff record
Response
Successful information message

Fig 4.9 Diagram 1(b) Authenticate User00Registered users
4.2
Prepare login error
User validation
Wrong username/password message
Login error msg
staff
4.1
Validate username, password
4.3
Redirect staff
User redirection
Response
staff
Login error msg
Response
system
System validation
D1
D2
0Registered users
4.2
Prepare login error
User validation
Wrong username/password message
Login error msg
staff
4.1
Validate username, password
4.3
Redirect staff
User redirection
Response
staff
Login error msg
Response
system
System validation
D1
D2

Fig 4.10: Diagram 1(c) Define access Rights02895775.2
Manage system
User login
5.1
Validate username, password
staff
User Pages
D3
5.3
Access channels
staff
5.2
Manage system
User login
5.1
Validate username, password
staff
User Pages
D3
5.3
Access channels
staff

Fig 4.11: Diagram 2 (c) Manage System
005.2.2
Update system
5.2.1
Validate username, password
D3
5.2.3
Manage system
staff
5.2.2
Update system
5.2.1
Validate username, password
D3
5.2.3
Manage system
staff

Fig 4.12: Diagram 2 (c) (ii) Access channels0-6355.3.2
Manage system
User navigation
5.3.1
Navigation through pages
Search engines
5.3
Search engine
Users
005.3.2
Manage system
User navigation
5.3.1
Navigation through pages
Search engines
5.3
Search engine
Users

4.13Data DictionariesDiagram Zero.

User detail= user id + email + name + username + password
Field confirm password= Dialog box + Error field location + Solution
Confirmation status= Dialog box + Confirmation message
Completed form= user id + name + username + password
User record= user + name + username + office name + password
Submitted form= fully completed form
User login information= Username + password
User redirection page= Webpages
Diagram 1(2. submit form)
Form error notice= Error message
Response= Refilled form + corrections
Successful form= dialog box + successful message.
Diagram 2(5.2 manage system)
Manage system= access rights + editing mode
System record=userss’ information + skins +Databases + image library
Secure portal= log events + user management + user parameters + system parameters.
User navigation= pages + sections
Search activities= inventory to be searched
Invalid username= wrong user address + wrong password
Security measures= monitor system usage + granting rights and withdrawing.
4.14 Data Structurestaff page
User id* page name*
Name* description
Username* Password* 4.7.1 Data Structure DescriptionUsers name Page
User id* page name*
Name* description
Username* Password*
4.15 Database DesignIn this section database designing for the proposed system is explained. The methodology for designing database consists of three phases that is conceptual design, logical design, and physical design. These three phases are explained as follows: –
Conceptual Database Design – conceptual database design includes the identification of the entities, relationship between entities and their attributes.
Logical Database Design – this level helps in designing the relations and constraints.
Physical Database Design – this level includes the physical implementation of relations into database management system.
Entity-relationship Diagram helps in describing the entities and relationship. The database designing was done from beginning and during database designing it is ensured that Database model is in the normalized form. The database design for the organization is based on the following ER Diagram showing entities and their relationships.
4.16 Entity Relationship Modeling It is a detailed logical representation of data for an organization. It is expressed in terms of entities, relationship between or among the entities and attributes of both the entities and relationships.
The following is the composition of the entities and attributes used in the system:
Staff= staff_id, full name, username, office, Password
Staff= staff _id, username, password
Inventory Categories= equipment Id, equipment name, Equipment type, office name + condition
computer categories=pc model+monitormodel+keyboard model+mouse model+ printer model+scanners
Figure 4.17 ER Diagramleft17076Staff
System page
user
Inventory categories
Staff
System page
user
Inventory categories

CHAPTER FIVESystem Implementation5.0 Tools used MYSQL, HTML, PHP.

5.1 MySQL
This tool is specifically to design and manage databases. The databases are used for storing logically related data.

5.2 Wamp serverThis tool provides the server side services that enables clients to access applications stored in a server.

5.3 Mozilla FirefoxThe tool enables the application’s pages to be accessed over internet. At least I.E 5.5 and above will do. For this system am using IE 7.0.
System testing5.4Test results

The below windows below shows how system works
Fig 5.1 staff sign up page/login page lefttop
Fig 5.2 unregistered user Error MessageFig 5.3. System interface whenever one has login in successfullyFig 5.4 adding inventory into the system

Fig 5.5 removing inventory from the system4341340114547000
Fig 5.6 when one has successfully searched equipment

5.7 SYSTEM TESTING.System testing is the type of testing to check the behavior of a complete and fully integrated software product based on the software requirements specification (SRS) document. The main focus of this testing is to evaluate Business / Functional / End-user requirements.

This is black box type of testing where external working of the software is evaluated with the help of requirement documents ; it is totally based on Users point of view. For this type of testing do not required knowledge of internal design or structure or code.

This testing is to be carried out only after System Integration Testing is completed where both Functional ; Non-Functional requirements are verified.

In the integration testing, testers are concentrated on finding bugs/defects on integrated modules. But in the Software System Testing testers are concentrated on finding bugs/defects based on software application behavior, software design and expectation of end user.

5.8 IMPORTANCE OF SYSTEM TESTINGa) In Software Development Life Cycle the System Testing is performed as the first level of testing where the System is tested as a whole.

b) In this step of testing check if system meets functional requirement or not.

c) System Testing enables you to test, validate and verify both the Application Architecture and Business requirements.

d) The application/System is tested in an environment that particularly resembles the effective production environment where the application/software will be lastly deployed.

5.9 DIFFERENT HIERARCHICAL LEVELS OF TESTINGUnit testing – Testing is done in the development process while developer completes the unit development. The object of this testing is to verify correctness of the module. The purpose of unit testing is to check that as individual parts are functioning as expected. Basically Unit testing is typically carried out by the developer.

Integration testing – System Integration Testing is started after the individual software modules are integrated as a group. A typical software project consists of multiple modules ; these are developed by different developers. So in integration, testing focuses to check that after integrating modules If two modules are communicating with each other or not. It is critical to test every module’s effect on the entire program model. Most of the issues are observed in this type of testing.

System testing– This is the first time end to end testing of application on the complete and fully integrated software product before its launch to the market.

Acceptance testing – User acceptance is a type of testing performed by the Client to certify the system with respect to the requirements that was agreed upon. This is beta testing of the product & evaluated by the actual end users. The main purpose of this testing is to validate the end to end information flow.

Chapter Six6.0 Summary, Recommendation and Conclusion6.1 SummaryFrom all discussions or ideas that have been considered in this write-up about an POS system, it can be seen that the project is fully digital of capturing inventory that one has in the stores or working.
6.2 ConclusionThe POS System will be developed using php HTML and MySQL in that way it will meet all the required work that it is supposed to meet the objectives of the system for which it will be developed according to the information gathered. The system will be operated at a high level of efficiency and all the users associated with the system will understand its advantage.

6.3 RecommendationThis study is based on the computerization of the POS system. The present system (manual) has been seen to be error prone, ineffective and time consuming which sometimes gives rise to incorrect attendent information then this will at the long run affect decision making of the department of work. I recommend that the new system based on the study should be put in place immediately, when the new system has been fully tested and found reliable. Proper staff training should also be effected so that skilled people will be available to use the computerized system.

6.4 AppendicesThe following is the user login code.

<?php
session_start();
if(isset($_SESSION’back’)){
$returnurl = $_SESSION’back’;
}
else{
$returnurl = ‘../’;
}
$server = mysqli_connect(‘127.0.0.1’, ‘root’, ”);
if(isset($server)){
$database = mysqli_select_db($server, “pos”);
}
if(isset($database)){
if($_SERVER’REQUEST_METHOD’ = ‘POST’ && $_POST > 0){
$lock = ucwords($_POST’username’);
$key = sha1(md5($_POST’password’));

$mail_check = mysqli_query($server, “SELECT `users`.`username` FROM `pos`.`users`”);
while($fetch = mysqli_fetch_assoc($mail_check)){
if($fetch’username’ != $lock){
$error_mess = “<b>” .$lock. “</b> does not exist in the database”;
$_SESSION’error’ = $error_mess;
header(“Location: login.php”);
}
}
}

$details = mysqli_query($server, “SELECT * FROM `pos`.`users` WHERE `users`.`username` = ‘$lock'”);
while($fetch = mysqli_fetch_assoc($details)){
if($key != $fetch’password’){
$error_mess = “The username and password entered do not match”;
$_SESSION’error’ = $error_mess;
header(“Location: login.php”);
}
else{
$_SESSION’name’ = $fetch’username’;
$_SESSION’username’ = $fetch’username’;
$personalized_sessions = mysqli_query($server, “SELECT * FROM `pos`.`users` WHERE `users`.`username` = ‘$lock'”);
while($personalized = mysqli_fetch_assoc($personalized_sessions)){
$_SESSION’dp’ = $personalized’dp’;
$_SESSION’status’ = $personalized’status’;
$_SESSION’location’ = $personalized’location’;
}

header(“Location: index.php”);
}
}
}
mysqli_close($server);
?>

References1. BIBLIOGRAPHY asapsystems. (n.d.). Retrieved from asapsystem.com: www.asapsystems.com
2. asapsystems. (n.d.). Retrieved from asapsystems: www.aspsystems.com
3. donlisky, a. (august 17, 2010). POS history part four. almyta systems.

4. googleweblight. (n.d.). Retrieved from googleweblight: www.googleweblight.com
5. lesonsky, R. (1998). tracking inventory. entrepreneur.

6. moskowitz, r. (august 17, 2010). using your computer for inventory contorol. accvision.

7. waspbarcode. (n.d.). Retrieved from waspbarcode.com: www.waspbarcode .com