University of San Carlos Technological Center

Department of Computer Science

Capstone Project:
Meribah Water Refilling System

Initial Project Implementation Plan

Lyndon T. Jugalbot
Cheril Ann G. Capadngan
INTRODUCTION

1.1 Project Description

In today’s modern production, water refilling establishments’ daily sales and inventory on the odd
occasion seen to become accustomed the modern world of technology. Small and Medium Enterprises were now
so needy and dependable towards technologies. In order to help some Water Refilling establishments and help
them out on their manual process of transactions and inventory, we proposed a system which will not just
eliminate hassle but an essential system for them for the success and productivity of their business with the help
of technology.
We, Bachelor of Science in Information and Communications Technology 4 th year students in cooperation
with Meribah Water Refilling Station as our main company partner in making this system. We have decided to
make a system which is Water Refilling System that can be very useful for them providing all the necessary
things they want to make their business hassle-free, time saving transactions and more productive.

1.2 Background of the Project

Meribah Water Refilling Station is one of the most valued water refilling establishments in Liloan, Cebu.
They started last December 8, 2004. This station was owned by Mr. Ricardo Anoos and Ms. Annie
AnoosAlponso. They first targeted water dealers as their customers and sold their water by volume and the price
was lesser compared to retailer buyers. They charged for every delivery. If the customer would not return their
bottle, they gave sanctions it was either they will replace it a new bottle or pay for it. For ordering, the customer
will call for them and take its order. Since then, they process every transaction manually recorded, tracked, and
inventory.
They have complete facilities and amenities in the production of their service. They have their own
refilling station beside their house but for now they don’t have any branch. Since they process their transactions
manually, they don’t have computers in their station but the management is very interested of the said system
because they really believe that it could helped them.
The current project is designed to improve the process of transactions of Meribah Water Refilling Station
with the help of technology, this must be implemented. This system is proposed to improve their daily sales,
easier tracking, updating their bottles and customers or for easier inventory.
1.3 Project Objective
In this modern generation, to adapt the changes of technology in answering the company’s needs and
improving the production of services, we aim to develop a system that is unique and will help Meriba Water
Refilling Station make their business safe and convenient.
 1.3.1 General Objective
Water Refilling System generally developed for water refilling establishments for them to
conveniently monitor their daily sales and especially their inventory. The system can eliminate inconvenience
on their daily monitoring of their equipments like tracking the bottles and especially their customers.

1.3.2 Specific Objectives

In making this system possible, this will exist as a great solution to the company:

 Create a unique system that will easily monitor water refilling establishments’ daily sales and
inventory
 Design a system that is user-friendly, realistic and helpful, upgrade faster to water refilling
establishments
 Evaluate that the system answers all the users concerns and must be finished on the date required
 Test that the system is reachable and helpful to the users
 Implement that all the objectives to this project/system really works and surely reduce the users’
tasks.
1.4 Scope and Limitations of the Project

The study will determine the various challenges of the Meriba Water Refilling Station. The
implementation of the system that directed by these challenges will be tested and analyzed. Challenges and
problems of the water refilling establishment particularly on their daily sales, tracking out their equipments and
monitoring or updating their transactions to various customers made easy. However, every study has its own
limitations, since Meriba is a Small and Medium Enterprise, so we focused only on the improvement of its
manual transactions such as tracking of their bottles, records and orders of all customers transactions and the
inventory. The system cannot accommodate the payment of every customer since they should pay their orders
over the counter.
1.5 Significance of the Project/Importance of the Project
This study will be a significant endeavour in promoting good service environment to Meriba Water
Refilling establishment and convenience of its users. This study will also be beneficial to the company and
students in strategic management, corporate strategies and information technology when they employ effective
learning in classroom and workplace setting particularly in different concepts related to the use of web-based
system. By understanding the needs of the users and benefits of quality service, the company and the students will
be assured of a competitive advantage. Moreover, this project will provide recommendations on how to evaluate
the performance of a certain system in accordance to Meribah.
 1.6 Review of Related Works and Studies/ Review of Related Literature
The review of related study for this project focuses on inventory, different functions needed and related
studies will be analyzed and reviewed as an essential factor to consider accomplishing this project.

Water Refilling System

An old age says ''if companies had instincts, its first instinct is to survive''. Based on this saying and also
from deeper studies on the water refilling business, we have to develop a software product that enables owners to
detect critical loopholes in its operations that could lead to substantial losses, if not total closure.

Bottle inventory tracking is a major issue in the water refilling business while water systems loss is
another component of potential problems not to mention pilferage and undocumented sales. Our new software
product handles all of these issues.

WATER REFILLING SYSTEM is a result of long interviews to experienced water station owners,
water refillers, delivery boys, and our own experience in the business. It is also a result of or diligent search for
solutions to water station problems.

Functional Features

Some modules that is very essential in having this system. This includes the admin that monitors
everything and everyone. As the users demand this depends on like the list of their transactions,
backgrounds/history, and list of their bottles, daily sales, supplier database, daily inventory, etc.

Ease of Use

A system should have a user friendly functions that even a grade school or a high school graduates can
operate. It is a water station owner friendly software since it was designed to protect the hundreds of thousands
peso investment in the water station equipment, vehicles, chemicals, workers, etc

1.6 Assumptions and Constraints

This describes the assumptions made regarding the development and execution of this system as well as the
applicable constraints. Some items to consider when identifying the assumptions and constraints are:

i. Schedule
- The system is expected to be complete by the end of February with all the necessary improvements
and additional functionalities to be considered. However, if there are unwanted incidences of delays
such as scheduling of appointments with the company, the schedule will be adjusted. There may be
a lot of revisions to be made for the system. It may not all be considered since there is only limited
time fixed for the system to be developed.
 ii. Budget
- The system that is being developed has less cost since it will be free of charge for the company. The
initial system installation will be utilizing a free web hosting domain. However, maintenance and
post installation requirements will be counted since there is a necessary procedure for maintaining
the system.

iii. Resource Availability

- The system will be launched in Meribah Water Refilling Station as the official Water Refilling System
of the company. However, the company does not have adequate advanced computer equipments
for the future improvements of the system.

iv. Software and other technology to be reused or purchased

- The system does not require costly software and other technologies in its launching and installation.
However, if the company wishes to expand and improve their business and production, the system
may need budget for the hosting of the site.

v. Constraints associated with Product Interfaces

- The system will be tested and evaluated before its launching. Thus, there will be a room for elimination
of errors and improvement for additional functionalities. However, there are post implementation
procedures to be done which is beyond the developer’s concern. There might be incidences of outdated
standard compliance within the system’s functionalities and processes.

SYSTEM PROCESS

2.1 Project Methodology

In order to achieve this system, a model used to show the

project development. This model describes the phases of the Software
Development Life Cycle.
This is an Iterative Waterfall Model. This figure represents the process from the beginning to the end of the project.

 Requirements
 PrintingSoft Solutions Inc. has introduced the system with its detailed requirements.
 The researchers/developers conducted an interview to the management for the necessary information
about the system
 The researchers/developers have decided and listed the specifications for the system to develop.
 Every feature will be documented as an aid in developing the system.
 Design
 The company described the possible design of the system.
 The researchers had able to make the layout of the system with its functionalities.
 Construction (Coding)
 High-level programming languages will be used by the developers/researchers in developing the
system such as PHP and HTML.
 The user interface and functionalities must be designed according to the user’s requirements and
standards.
 Developers must have a coding standard to follow.
 Integration
 Developers will integrate all the components or modules ensuring that it works as a system.
 Testing and Debugging
 Software testing like test case and use case will be applied in order to identify the system
development especially on its functionalities.
 Every function must be tested in order to detect the errors.
 The system must run and ready to be used by the users.
 Every test, there is a software testing failure and debugging is very important in developing a system.
 Debugging the system ensuring that the system will be ready to serve the user.
 The documentation of the whole system must be achieved and ready for documentation testing and
approval.
  Installation
 Once the project is done and ready to be used by the user, installation stage will go all the way
through.
 The whole system must be installed and tested.
 Recommendations are open in this stage, for every functions work.
 Maintenance
 The developers must correct all the errors of the system.
 The developers will implement the necessary enhancement of the system.
 Functions or Details that are not included must be deleted and possible things to be added must be
done.

2.2 System Modules

Modules:

1. REGISTRATION - The function of this module is to REGISTER employee/s. The admin will provide
basic information that is necessary. This module is important since the employee will be the one to
monitor every customer transactions and will help this system useful. The admin will provide the details
to the employee it order to access the system.

2. ADD/DELETE BOTTLES - The function of this module is to ADD or DELETE bottles.

 3. CHECK BOTTLES - The function of this module is to check how many bottles they have. This will
keep track of the number of their bottles time to time.

4. TRANSACTIONS - the function of this module is to view all the transactions done by the employee/s.

5. SEARCH - the function of this module is to search employee to be able to EDIT or DELETE
employee/s.

6. LOGOUT

MODULES:

1. TRANSACT - the function of this module is to do transactions with the customer and at the same time
register the customer on the process.
2. SEARCH - The function of this module is to search whether the customer is already registered in the
database.
IF the customer is not registered, go back to transaction page to register the customer at the same time
transact.
IF the customer is already registered to the database, you can either proceed with TRANSACTION,
EDIT customer
information or DELETE customer. Links are provided for the user to click on the action they want to do.
3. CHANGE PASSWORD - The function of this module is to let the employee/s change their password to
any password they are comfortable with.
4. CHECK BOTTLES - The function of this module is to let the employee/s check how many bottles left
to them and to their customer/s.
5. LOGOUT
2.3 Process Flow Diagram

2.4 Calendar of Activities

SYSTEM DESIGN

3.1 Database Design

 IMPLEMENTATION

4.1 Technology

4.1.1 XAMPP

XAMPP is a free and open source cross-platform web server solution stack package, consisting

mainly of the Apache HTTP Server, MySQL database, and interpreters for scripts written in
thePHP and Perl programming languages.

XAMPP LOGO

Features

XAMPP requires only one zip, tar, 7z, or exe file to be downloaded and run, and little or no
configuration of the various components that make up the web server is required. XAMPP is regularly updated
to incorporate the latest releases of Apache/MySQL/PHP and Perl. It also comes with a number of other
modules including OpenSSL and phpMyAdmin.
Self-contained, multiple instances of XAMPP can exist on a single computer, and any given instance
can be copied from one computer to another.
It is offered in both a full, standard version and a smaller version.

Use

Officially, XAMPP's designers intended it for use only as a development tool, to allow website
designers and programmers to test their work on their own computers without any access to the Internet. To
make this as easy as possible, many important security features are disabled by default. In practice, however,
XAMPP is sometimes used to actually serve web pages on the World Wide Web. A special tool is provided to
password-protect the most important parts of the package.

4.1.2 NOTEPAD++

Notepad++ is a text editor and source code editor for Windows. It aims to be a lightweight and robust editor for
a variety of programming and scripting languages. One advantage of Notepad++ over the built-in Windows text
editor Notepad, is that Notepad++ supports tabbed editing, which allows working with multiple open files.

NOTEPAD++ Logo

Features

General features include:[5]

 Tabbed document interface[6]

 Drag-and-drop
 Multiple clipboards (plugin required)
 Split screen editing and synchronized scrolling
 Spell checker (requires Aspell) (Spell checker does not distinguish between text and code)
 Supports text encoding formats such as Unicode, for international writing systems
 Find and replace: with regular expressions (including multi-line); over multiple documents; and
marking/summary of occurrences
 File comparison
 Zooming
Source code editing features include:[5]

 Auto-completion
 Bookmarks
 Syntax highlighting and syntax folding
 Brace and indent highlighting
 Smart highlighting
 Regular expression find and replace (in perl compatible extent)
 Speech synthesis
 FTP Browser (plug-in included in standard installation)
 Macro recording and execution.
 Various tools such as line sorting, text encoding conversion, text folding
 File status auto-detection

1.4 Meribah Water Refilling System – System’s GUI

1.4.1 Login

Pre-Condition:

o System on.
o User must have an account (Administrator or User) to be able to access the system.

Post-Condition:

o Admin/User is logged in and redirected to the Main Page.

Exceptions:

o If a user enters a not valid Username or Password he/she will get an error message.
1.4.2 Create User/Employee

Pre-Condition:

o System on.
o User is logged in as Administrator.

Post-Condition:

o A new User/Employee will be created.

Exceptions:

o If a user leaves any blank field he/she will get an error message.
o If a user enters a not valid username/password he/she will get an error message.

1.4.3 Delete Admin/User

Pre-Condition:

o System on.
o User is logged in as Administrator/Employee
o The system must have at least one Administrator or one User.

Post-Condition:

o The selected Administrator or User will be deleted.

1.4.4 Update Admin/User

Pre-Condition:

o System on.
o User is logged in as Administrator.
o The system must have at least one Admin.

Post-Condition

o The selected Employee will be updated.

Exceptions:

o If a user leaves any blank field he/she will get an error message.
o If a user enters a not valid username he/she will get an error message.

TRAINING MODULE
 The developers will conduct a training to one of the employees of the water refilling establishment, so
that that the trainee will be the one to endorse or train the rest of the employees. This training will take a day to
completely introduce how the system will work or what the system all about.
TECHNICAL MANUAL
In order to achieve this system, the establishment should have a computer to enable to install the system may it
be in their station.
To deploy Water Refilling System you have first to install XAMPP on your system and do the following steps:
1. Start your Xampp (Apache, MySql).
2. Go to your browser and type localhost/phpmyadmin
3. Run/Import SQL Script “smoutcht.sql”
4. Copy the folder “smoutcht” to “Computer/C:/xampp/htdocs” folder
5. Start your web server
6. Open http://localhost/smoutcht/adminlog.php in your browser if you are the admin.
7. Open http://localhost/smoutcht/index.php in your browser if you are the assigned user/employee.
8. You will be directed to the system’s GUI.
USER MANUAL
Once you are already directed to the System’s GUI.
 ADMIN MANUAL

1. To login, tyoe username and password (a default account will be provide for the admin
only), then click Submit.
2. If you want to change your information as admin (username and password). Click
“Admin” and fill uo all the fields and click Submit.
3. To register an employee, Click “Register”. Fill up all fields and Click Submit.
4. To check and/or delete bottles. Click “Bottles”.
5. To add bottles, type how many and click Submit.
6. To view transactions, click “Transactions”.
7. To search/edit employee, Click “Search”, type the name of the employee and hit Enter.
8. To logout, Click “Logout”.

 USER/EMPLOYEE MANUAL

1. To Login, type username and password(as provided by the admin), Click Submit.
2. To do a transaction with a customer, Click “Search” and check if the customer is already
registered in the database. If yes, below the customer information click “Transact”. If No,
Go back to the HomePage and Click “Transact”.
3. You will be able to register the customer in the database at the same time do a
transaction.
4. To view/edit/delete customer information, Click “Search”. Type the name of the
customer and hit Enter.
5. To change your password, Click “ChangePass”. Fill in the fields and click Submit.
6. To check how many bottles left, Click “CheckBottles”.
7. To logout, Click Logout.

EVALUATION INSTRUMENT
 Filling out this checklist will allow developers to systematically determine whether specific system requirements
are being met. In determining substantial compliance, developers should assess the results of the completed checklist
on the inventory system taken as a whole.

In the checklist, 5 columns follow each criterion. Every column is indicated with numbers that corresponds the
rating of each criterion. For “1” - POOR or the system is really need improvements and below the requirement
expectations. “2” – FAIR or the system is already acceptable but needs to revise to a higher level of specifications. “3” –
GOOD or the system requirements and performance were met, goals and objectives were achieved. “4” – VERY GOOD
or the system design, performance and functionalities expectations were met. “5” – EXCELLENT or the system is highly
impressive to be considered as a Capstone Project and consistently met expectations in all areas of the system.

Inventory System Requirements

Functionality:

Suitability – This is the essential Functionality characteristic and refers to the appropriateness (to

specification) of the functions of the software.

Accurateness – This refers to the correctness of the functions, an ATM may provide a cash dispensing

function but is the amount correct?

Interoperability – A given software component or system does not typically function in isolation. This

subcharacteristic concerns the ability of a software component to interact with other components or systems.

Compliance – Where appropriate certain industry (or government) laws and guidelines need to be

complied with, i.e. SOX. This subcharacteristic addresses the compliant capability of software.

Security – This subcharacteristic relates unauthorized access to the software functions.

Realibility
 Maturity – This concerns frequency of failure of the software.

Fault Tolerance – The ability of software to withstand (and recover) from component, or environmental,

failure.

Recoverability – Ability to bring back a failed system to full operation, including data and network

connections.

Usability

Understandability – Determines the ease of which the systems functions can be understood, relates to

the user mental models in Human Computer Interaction methods.

Learnability – Learning effort for different users, i.e. novice, expert, casual etc.

Operability – Ability of the software to be easily operated by a given user in a given environment.

Efficiency

Time Behavior – Characterizes response times for a given thru put, i.e. transaction rate.

Resource Behavior – Characterizes resources used i.e. memory, cpu, disk and network usage.

Maintainability

Analyzability – Characterizes the ability to identify the root cause of a failure within the software.

Changeability – Characterizes the amount of effort to change a system.

Stability – Characterizes the sensitivity to change of a given system that is the negative impact that may

be caused by system changes.

Testability – Characterizes the effort needed to verify (test) a system change.

Portability
 Adaptability – Characterizes the ability of the system to change to new specifications or operating

environment.

Installability – Characterizes the effort required to install the software.

Conformance – Similar to compliance for functionality, but this characteristic relates to portability. One

example would be Open SQL conformance which relates to portability of database used.

Replaceability – Characterizes the plug and play aspect of software components, that is how easy is it to

exchange a given software component within a specified environment.

CRITERIA RATING
System Performance 1 2 3 4 5

1. FUNCTIONALITY

 Suitability

 Accurateness
 Interoperability
 Compliance
 Security
2. RELIABILITY
 Maturity
 Fault Tolerance
 Recoverability
3. USABILITY
 Understandability
 Learnability
 Operability
4. EFFICIENCY
 Time Behavior
 Resource Behavior

5. MAINTAINABILITY
 Analyzability
 Changeability
 Stability
 Testability

6. PORTABILITY
 Adaptability

 Installability
 Conformance
 Replaceability

INVENTORY

A.
B.

C.
 The Water Refilling System Maintenance Plan has been developed to assure that the Water refilling
System of Meribah Water Refilling Station is adequately inspected and maintained to assure that the system still
meet their design functions. Outlined below are the various inspection and maintenance activities the developers
intend to undertake in regard to achieving these goals:

1. Meribah Water Refilling Station’s Water Refilling System shall be inspected every year to
determine if the system’s technical and software performances are adequate to meet its
design functions. Based on this inspection, errors and possible improvements that are identified for
maintenance will be prioritized.

2. System’s performance will be periodically inspected. During these inspections, unnecessary

functions/modules will be removed and necessary information/modules that to be added so as to provide
reasonable assurances that the system will operate in an unobstructed manner during software or events
errors.