H20 Agent

Session: 2016 – 2020

Project Advisor: Ms. Iqra Tariq

Submitted By:

M Hussnain Tariq 70057492

Hafiz Faisal Bilal 70057399
Ali Hassan 7005721
H20 Agent: IoT based System
5. Design
5.1 Design Tools
5.2 System Designing
5.3 User Experience Measure
6. Implementation
6.1 Implementation tools and Framework
6.2 Implementation Procedure
7. Testing
7.1 Testing Procedure
7.2 Testing Result
8. Conclusion and Further Work
8.1 Limitation and Strength of the System
8.2 Future recommendation
9. Bibliography and Reference
10. Plagiarism Report
11. Appendices
CH 1:

1. INTRODUCTION:

1.1. Introduction

Water is essential to all living organisms, as it serves as a solvent for minerals, vitamins, amino
acids, glucose, and many other nutrients. Water also plays a key role in digestion, absorption,
and nutrient transportation. Furthermore, it is the medium for the safe elimination of toxins
and waste products. Without water, life cannot be sustained beyond a few days, because the
lack of access to adequate water supply leads to the spread of diseases like cholera, typhoid
fever, hepatitis, and diarrhea.

Nowadays, the availability of fresh-water has become a problem all around the world. One-
sixth of the world population suffers from the freshwater unavailability situation. It is seen that
workplaces suffer most from this problem. Providing fresh and safe water for all is a challenging
task. Water contamination is the other common problem around the world.

In homes and workplaces, the availability of freshwater is a severe problem due to

environmental pollution. So various water supply companies have been activated to facilitate.
As time goes on. The need of fresh drinking water has become more than ever. In the next few
years, the drinking water would become more precious than the fuel. The traditional water
supply service organizations are doing their jobs but not in the most adequate way. Their
process is more open to germs and bacteria. Not forgetting the wastage of water.

On the other side, the customer may have a day on which a family gathering arranged, and
then he needs more water than as usual. The supplier delivers a fixed quantity of water. This
situation pushes the customer in trouble to arrange more water. Furthermore, the monitoring
of water availability on dispenser has become problematic for the consumers due to busy
routine. The empty bottles on dispenser demotivate people to quench their thirst on time that
consequences may cause serious diseases. In case, the client makes a call and asks the supplier
for immediate delivery of the water bottle. The suppliers never come twice a day unless the
customer pays more charges. Moreover, in Pakistan’s workplaces, there is more than one
dispenser installed. The dispensers monitoring for water availability is problematic because the
employee has to check the water quantity in each bottle and replace where required. This
situation becomes tremendously challenging in big organizations. For Example, in Masjid-al-
Nabvi there are hundreds of water coolers and the workers have to check each water cooler
after some time if any cooler is empty and needs to refill it.

To overcome these problems, people have to subscribe to the drinking water supply services
and installed water dispensers at their homes and workplaces. Water supply companies deliver
water gallons daily to their consumers according to their daily usage. The problematic situation
is at someday consumers demand more bottles and some other days they refuse to take bottles
because customers don’t know the exact quantity of daily water consumption. This situation
creates cost and time problems for suppliers as well as down the customer value.

We are providing a solution that will automate the supply of water more. Which will help not
only to reduce the wastage of water but it will also be helpful against the germs and bacteria
and water related diseases. It will facilitate the suppliers and the users which will help them to
save time, efforts, etc.

To solve all the concerned problems, we will develop an android and web application. The
android application will facilitate water consumers to make an order for water. The web
application will facilitate water supplier companies to control the water order. For this project,
we will use the sensor has a unique id for customer identification. The customer will get
registration through sensor id and personal contact information. This sensor will check the
water quantity in the water bottle. If the water quantity reached the thresh hold number then it
will send an alarming notification to the supplier for water requests. The company will be able
to manage its business (customer information and order record) of water supply through the
web application.

1.2 Problem / solution statement

1.2.1 Problem Statement:

The availability of fresh-water has become a problem all around the world. It is seen that
workplaces and backward areas suffer most from this problem. One-sixth of the world
population suffers from the freshwater unavailability situation. Providing fresh and safe water
for all is a challenging task. Water contamination is the other common problem around the
world. Water Company has faced many problems to wastage of water. Many time companies’
supplier Many time companies’ supplier goes to the customer home then customer not accept
the order. Then company and suppliers wasted his time and efforts. because the lack of access
to adequate water supply leads to the spread of diseases like cholera, typhoid fever, hepatitis,
and diarrhea. They have many problems faced about supplying water and water wastage. And
Wastage of resources. Storage the extra water bottles should burden of the customer. Many
times, customer has not used all bottles and wasting the water.

The basic problem of the project is mentioned below:

I. Providing fresh water. As the water is stored for long it can produce different germs and
bacteria.
II. The effort and resources consumed in the process of delivery water.
III. They may take those bottles up several floors by stairs just to find out the clients does
not need more bottles today as his/her previous bottles are not yet consumed.
IV. wastage of water.
V. Time Saving.
VI. Argent Order Problems.
1.2.2 Purposed System:

We are providing a solution that will automate the supply of water more. Which will help not
only to reduce the wastage of water but it will also be helpful against the germs and bacteria
and water related diseases. It will facilitate the suppliers and the users which will help them to
save time, efforts, etc. We will develop an android and web application. The android application
will facilitate water consumers to make an order for water. The web application will facilitate
water supplier companies to control the water order. For this project, we will use the sensor
has a unique id for customer identification. The customer will get registration through sensor id
and personal contact information. This sensor will check the water quantity in the water bottle.
If the water quantity reached the thresh hold number then it will send an alarming notification
to the supplier for water requests. The company will be able to manage its business (customer
information and order record) of water supply through the web application. People with the
help of smartphones can now connect to the internet without the need for a computer, while
still offering the same functionality but through different means.

The solution of the problems is mentioned below:

I. We shall have sensors on the bottles to measure the water level and check the
threshold.
II. We shall make an android app that will collaborate with the sensors to collect data.
III. Each client is given a unique sensor id which will define the quantity of their subscribed
bottles.
IV. The sensor would detect the level of the water if the water reaches the point of alert.
V. An automatic alert will be generated and sent to the water suppling company on our
web app, then admin will check from where the alert has come from and to whom the
sensor is register to.
VI. Company will check the sensor id to see the current status of user order to replace the
bottle.
VII. The sensors will communicate with each other to check their particular status and
generate alert according to their collective status.

1.3 Aims and objective of the project:

“The Goal of “H2O Agent “is to focus on various aspects that are related to provide easy and
comfort to the system target Customer check water level and order at any time and from any
place on a platform that will be consistent and dedicated for them”. The main aim of this
system is to monitor the water level at every area so that they help in detecting the wastage of
water.

The main goal of the project is mentioned below:

 I. The goal of our project is to reduce the water related diseases and mitigate the risks
involving storing of water.
II. Monitor the water level of dispenser automatically.
III. It will provide faster, easier and cost-effective management.
IV. The goal for the water suppling companies is to expand their business and minimize
drinking water wastage.
V. In this way fresh water will be used by the clients and there will be no more headache to
store a backup of water bottles which can result in a lot of dangerous circumstances.
VI. A lot of water will be saved from wastage.
VII. The supplier does not have go every day to every single client’s location to check
whether they require more water or not. Which ultimately will reduce their resource
consumption.

1.4 Challenges

They have many problems faced to implement the hardware and connect to the system.

I. The short circuit, humidity, and extreme temperature can cause problem in the sensor.
II. The water consumption in large company will enhance their water cost due to sensors.
III. When the company expands you have to add new sensors.
IV. Time can be short due to unavailability of development resources, developer illness.
V. With time, sensors cost can be increased.
VI. The supervisor can leave the university.

1.5 Nature of End Product

I. Android Application
II. Web Application
III. Sensor
CH 2

REVIEW OF THE LITERATURE

2.1 Similar work/literature review

International Research Journal of Engineering and Technology (IRJET) has an article [1]. They
are using IOT to prevent the water from overflowing and prevent the water from wastage. They
have not developed it. The main aim of this system is to monitor the water level at rural areas
so that they help in detecting the wastage of water and measures can be taken to avoid
unnecessary overflowing of water in the areas where monitoring is a difficult task. This system
helps to prevent the wastage of water by informing about the liquid levels of the containers

International Research Journal of Engineering and Technology (IRJET) has an article. They only
discus about wastage of water during transmission. Problems faced by most of the countries is
the issue of water scarcity in the world and wastage during transmission has been identified as
a major technology to prevent the water. This article writer strictly saying work on this project
because of prevent the water wastage. They also used the sensor to check the water level and
alarm to the system bottle are filled and next the bottle. The system makes use of AVR family
microcontroller, Raspberry Pi, LCD screen, Wi-Fi modem for sending data and a buzzer. A 12 V
transformer is used for power supply in this system. The LCD screen is used to display the status
of the level of liquid in the containers.

This paper deals with brief explanation of using Arduino to automate the homes. The existing
system of the Bluetooth method of automation limitations was analyzed to prove that android
and Arduino make up for a better method of automation. The hardware and software
specifications are also explained.

Sensor Set on the transmission machine and send the signals in the bottle and detect the water
level. And set the level. If level is 80 percent then next bottle replace to first bottle and not
wasting the water. This paper presents the design and implementation concepts for a wireless
real-time Water level monitoring system based on Arduino Uno microcontroller as central
controllers. International Research Journal of Engineering and Technology (IRJET) present
system diagram below figure 1.0. [1][2]
Figure 1.0:

2.2 Related Studies

In recent years, wireless sensor networks (WSN) has become a so popular study area in
computer science and preferred to use on different areas and applications such as military,
health, industrial controls, fire brigade, house and etc. Water distribution systems are one of
these. WSN based monitoring systems implemented on water distribution systems are used
worldwide. Its main advantages are real-time monitoring and detecting leakages to prevent
resource loss. But WSN have some challenges like power consumption (finite energy sources),
storage area, coverage, security. IOT based Water Level Monitoring system is an innovative
system which will inform the users about the level of liquid and will prevent it from
overflowing. To demonstrate this the system makes use of containers, where the sensors
placed over the containers to detect the liquid level. Different types of system data in tables.
[3]

Differ types of Water Level Monitoring system based on the control are: [4]

Table 1
Individual systems:
This is a very control type of systems. Here the whole model is
implemented on a targeted single source system.
Advantages Disadvantages
I. These systems use less resources I. This system only one-sided control.
and complexity of them is less so it
is easy to maintain.
 II. A water level controller helps save II. Great dependency to byer and supplier.
money by limiting the waste of
water and electricity.

III. Another notable advantage with III. Increase vulnerability of supply.

these devices is that they regulate
on their own.

IV. This results in an appropriate level IV. Increased risk of supply interruption
of water at all times being especially for assets specific product.
maintained.

V. This system includes less requests V. No warranty hardwires.

to hardware and software at a
time so they have less chance to
damage.

Table 2
Large control systems:
Their water level is implemented on a very large-scale basis and huge
amounts of sensors are used.
Advantages Disadvantages
I. Alternative source of material in I. High purchase system
case of delivery stoppage by the
delivery.

II. Reduced probability of bottlenecks II. Electronics are usually built separately.
due to insufficient production
capacity to meet peak demand.

III. More flexible to react unexpected III. More difficult installation.

IV. Wireless products are everywhere, IV. Most float switches are outdated.
from tablets and mobiles to
security systems.

V. Better knowledge of V. No Warranty or Guarantee.

manufacturing.
 Table 3
Central Control systems
Computerized systems programmed to handle all the functions of
multiple utilities like air conditioning or home entertainment systems, refrigerators all at the
same instant regardless of your presence. Control device can be accessed through the
telephone or internet from any corner of the City.
Advantages Disadvantages
I. Living in an age where we need to I. Many times, all functionality not properly
be more conscious of the energy work.
that we use, a water level
controller is ideal at saving power.
II. A water level controller helps save II. The rust, foul and deteriorate
money by limiting the waste of
water and electricity.
III. Another notable advantage with III. Electronics are usually built separately
these devices is that they regulate
on their own.
IV. This results in an appropriate level IV. More difficult installation
of water at all times being
maintained, while providing you
with the maximum use of your
water at the appropriate times.
V. Each function of the integrated V. Most float switches are outdated
electronics and relays use LED
lights to offer operators the ability
to visually scan them in order to
verify proper operations.
VI. lights to offer operators the ability VI. No Warranty or Guarantee
to visually scan them in order to
verify proper operations.

2.3 Related Technologies:

The combination of real-time monitoring, transmission, and advanced data management

system for smart water and wastewater treatment and management.[5]

These are the Related technologies:

2.3.1. General Sensor-Based Water Quality Monitoring Systems:

Basic work to use this general sensor-based system Geetha and Gouthami (2016) these steps as
follows: First, the field water quality data is collected by wireless sensors and transmitted to a
controller by a wireless or wired system. Second, the data transmission system transmits the
collected data from the controller to the data storage cloud. Finally, the stored data in the
cloud is used for the analysis and operation of a system.

2.3.2. Physical Monitoring Sensors:

This suitable method allows for measuring variables directly in the environmental medium in
continuous time intervals and for data to be sent to land-based facilities. This sensor has been
used for years to measure physical-based parameters, such as oxygen, pH, and CO2 in
seawater; conductivity, depth, and temperature (CDT); and nephelometric turbidity units
(NTU). Arrays of sensors are typically used together in automated systems, either deployed
from a ship or on mooring, as part of an observation system

2.3.3. Optical Remote Sensors:

Satellite sensing works by using direct solar radiation entering the water column and absorbing
or scattering, depending on the types and constituents within the column. This radiation is
reflected in the atmosphere the ratio of outward radiance to the direct sun radiation on the sea
floor is referred to as reflectance, and this could be passively recorded by a sensor.

CH 3

RERQUIRMENT ENGENRING

3.1 Requirement Gathering

3.1.1. Current Mechanism:

These days there is no specified social platform for women in Pakistan that
provides a facility to gain knowledge about different fields on a single platform. Women feel
hesitate to share their ideas in public. An uneducated woman finds it difficult to learn new skills
because of unavailability of such platforms. Most of the sites are paid that results in a low
progress in Learning. A complex interface of different sites is difficult to understand by most of
the user. Gender Discrimination is an alarming issue for Pakistan. Most of women feel hesitant
to contribute due to fear of criticism. The problems like lack of knowledge, unequal rights,
sexual harassment and domestic violence etc. Working women are facing big challenges in
navigating career opportunities while maximizing motherhood. A large group number of
women stay at home. So, there is a need of an online platform for creating a right kind of
linkage between women workforce and organization. For exploring these problems, we asked
set of questions from women to tell us: What do you think is the biggest challenge facing
women in the Pakistan today? And what do you think is the biggest challenge facing women
internationally today? After close ended interview we explore some problems of women. The
problematic situation is women have limited access to prenatal and infant care. A final area of
focus in attaining gender equality is women's economic and political empowerment. Though
women comprise more than 50% of the world's population, they only own 1% of the world's
wealth. Throughout the world, women and girls perform long hours of unpaid domestic work.
In some places, women still lack rights to own land or to inherit property, obtain access to
credit, earn income, or to move up in their workplace, free from job discrimination. At all levels,
including at home and in the public arena, women are widely underrepresented as decision-
makers. In legislatures around the world, women are outnumbered 4 to 1, yet women's political
participation is crucial for achieving gender equality and genuine democracy.

3.1.2. Scope of the Project:

This application will help women to get specified knowledge to solve their problems related to
health, household and different aspect of their life. This platform will introduce a new concept
of learning by conducting workshops. It will be a trusted platform in Pakistan for women that
target all the specific issues of women at one platform.

3.1.3. Elicitation:

To validate our requirement, we conduct survey with and data is attached and they solve
questionnaire. After solving questionnaire, we observe the problem exists. The most problems
that women face that are given below. Data is questionnaires attached last of the
documentation. [a]

 Providing a platform where women can easily discuss various aspects of their daily
lifecycle such as health, career and get educated while staying at home.
 Provide support and built confidence to share their knowledge and skills all over the
world through workshops and communities.
 Providing a chance for unemployed and uneducated women to get different
opportunities of their interest by asking questions from different professionals.

3.1.4. Elaboration:
The working of the application is that when user enter Whispers, it will ask about whether you are
joining as a professional or common user. User will provide necessary information to application. Now
user will be able to successfully join community. After joining community, user can attend workshops
and get latest updates about their interested topics. User will be able to post their problem in
community for getting suitable solution by professionals on aspects of their growth journey. User can
also share their problem though voice notes in community. There will be a specific period to post and
review on a problem. User will have a right to share their reviews about workshops. A professional must
have to conduct 1 workshop per week to stay as a professional in 30 days’ trial period for authentication
otherwise she will be change into a common user of Whispers by administrator. User can conduct
workshops via zoom, YouTube or Facebook on the basis of professional’s choice.

3.2 Requirement Analysis and Specification

3.2.1 Business Requirements:

These are the business requirements:

I. Put women in contact with female mentors:

Sharing stories and experiences has always been one of the most effective ways to
change your mind and provoke action. That’s why matching women with strong female role
models is one of the many ways to empower your employees to succeed in both your company
and their industry.

II. Remind women that they are valued:

It is important to remind women that they are respected for who they are and what you have
hired them for their unique perspective, skills, dedication and strong work ethic .

III. Voluntary engagement for the interest of women:

By participating in different meetings held by different professionals to overcome a lack

of self-confidence and recognized their full potential as leaders, team members, and
negotiators.

3.2.2 Domain Requirements:

Requirement that come from the application domain of the system and that reflected
characteristics of domain.
 I. Android phone
II. System (For Browser)
III. Libraries for Animation (implementation 'me.itangqi.waveloadingview:library:0.3.5)
IV. Cloud Messages (Used for messages)
V. Fire Base cloud (messages Notification)

3.2.3. Functional Requirements

1. Administrator

 Administrator will be able to login to his/her account by using the username and
password.
 Admin will be able to check all the information of the users and professional.
 Admin will manage the latest updates of communities.
 A professional must have to conduct 1 workshop per week to stay as a professional in 30
days’ trial period for authentication otherwise she will be change into a common user of
Whispers by administrator.

2. User

 User will be able to signup/register an account.

 User will be able to login to his account by using username and password.
 User will be able to set the threshold of the bottle for the alert.
 User will be able to modify their assigned sensors name. So, the app can become more
user friendly.
 User will be able to live monitor the water levels in all his subscribed bottles.
 User will be able to check their current as well bill history.
 User will be able to pre-order the water bottles for any special occasion.
 User will be able to set the service type (Urgent, Regular).
3.2.4. Non-Functional Requirements
I. Availability:

The system should be available 24/7 including the servers and the internet to constantly
measure real time data.

II. Performance:

The system should perform at high standards to real time monitor the water level.

III. Durability:

The system should be durable.

 IV. Maintainability:

As hardware is used, the maintainability of that hardware matters a lot.

V. Scalability:

System should handle a growing amount of work by adding resources to the system.

3.2.5. User Interface Requirements:

I. Use ability:

The name and icon both are mention in each module. Each module has its own user-friendly
icon. User performs every task in fewer steps.

II. Consistency:

The icon’s and dropdown menus are in consistence manners.

III. Avoid Scrolling:

The link of home page is sticky and home page consist all module so it will provide the facility
to avoid scrolling.

IV. Responsiveness:

The application should be fit to view any size of screen. Give response to each action in few
seconds.

CH 4

FORMAL MODELING OF THE SYSTEM:

CH 5

DESIGN

4.1. Designing Tools

 MS word
 MS PowerPoint
 MS Project
 Draw.io
4.2. System Design:

Systems design is the process of defining elements of a system like modules, architecture,
components and their interfaces and data for a system based on the specified requirements.

4.2.1. Unified Modeling Language (Use Cases):

A standard form of use case diagram is defined in the Unified Modeling Language.

1. Actor:
 Name by noun.
 Actor plays a role in the business
 User can play different roles
2. Use Case:

 System Main functions.

 Named by verb + Noun.
 Each Actor must be linked to a use case, while some use cases may not be linked
to actors.

3. Communication Link:

 The any of an actor in a use case is connecting an actor to a use case by a solid link.
 Actors different way connected to use cases by associations, indicating that the actor
and the use case communicate with one another using messages.

4. System Boundary:

 The system boundary is defined in the requirements document.

 For large and complex systems, each module may be the system boundary.
 All Functionality Perform this set of boundaries.

5. Extend:

 The stereotype "<<extends>>" identifies as an extend relationship

 <<extend>>

6. Include:

 An include relationship is depicted with a directed arrow having a dotted line.

The tip of arrowhead points to the child use case and the parent use case
connected at the base of the arrow.
Use Case Diagram
Figure: Login UC

Login Use Case:

Use Case ID: UC1

Use Case Name: Login Use Case
Created Date: Last Created Date:
Actor: User
Description: The user will login using the id and password given during
registration. The new user first fills the form registration and
then go to the login page. If you change and forget the
password to click the option and change or forget password.
 Precondition: First user register in database. Then open the web/app.

Post User can access the system.

Condition:
Normal Flow:
1. User Open the app/web and view the login page.
2. New User First go to registration page.
3. System present the login page.
4. User enter a correct Id and Password.
5. System present home page.
6. User check new schemes of the company.
7. User send a new order.
8. System accept the order and send to the company.
9. User check all his records.
10. End Use Case

Alter Native Flow:

 User are not register.
 User enter invalid id and password.
 New User password not strong.

Figure 2. Forget Password UC

Forget Use Case:

Use Case ID: UC2

 Use Case Name: Forget Password Use Case
Created Date: Last Created Date:
Actor: User
Description: User first visit login page and enter a correct information. Then
all information authorized check in database. if all information
is correct then user forget the password easily.

Precondition: User open the web/app. User login the web/app.

Post Username and password details are authentication in our
Condition: database. If the member exists and information is valid then
forget the password.

Normal Flow:
1. User open the app/web and the view login page.
2. System present login page.
3. User enter correct Password and ID.
4. System present Home page.
5. User select forget option.
6. Forget the password.
7. End Use Case.

Alter Native Flow:

 User are not register.
 User enter invalid id and password.
 User enter wrong password and ID then system
not permeation to forget password.

Figure 3. Check User Information Use Case:

Check User Information Use Case:
 Use Case ID: UC3
Use Case Name: Check User Information Use Case
Created Date: Last Created Date:
Actor: Admin
Description: Admin first visit login page and enter a correct information.
Then all information check in database. Then admin check all
user record.
Precondition: User
Post Admin can access the system. And see All users record easily.
Condition:
Normal Flow:
1. Admin open the web and view the login page.
2. System present the login page.
3. Admin enter valid information.
4. System present the home screen.
5. Admin click the dashboard.
6. Admin click find option.
7. Admin enter user name and search user.
8. Admin open the user profile.
9. Admin check the new order.
10. Admin check all record of the user.
11. End use case.

Alter Native Flow:

 Invalid information.
 Error generate wrong password.
 Only admin check all user records.

Figure 4. Send Bill Use Case:

Send Bill Use Case:
 Use Case ID: UC4
Use Case Name: Send Bill
Created Date: Last Created Date:
Actor: Admin
Description: Admin first visit login page and enter a correct information.
Then all information check in database. Then admin check all
user record. And last send the Bill.
Precondition: Admin first login the Page. And check the user records.
Post Condition: Admin send bill to the user.
Normal Flow:
1. Admin open the web and view the login page.
2. System present the login page.
3. Admin enter valid information.
4. System present the home screen.
5. Admin click the dashboard.
6. Admin click find option.
7. Admin enter user name and search user.
8. System present the user.
9. Admin open the user profile.
10. Admin check the new order.
11. Admin check all users’ records.
12. Admin check the bill.
13. Admin send the bill.
14. End use case.

Alter Native Flow:

 Invalid information.
 Error generate wrong password.
 Bill are not properly sending the user.
 Wrong calculate the bill.

Figure 5. Receive Alert Use Case:

Receive Alert Use Case:
 Use Case ID: UC5
Use Case Name: Receive Alert
Created Date: Last Created Date:
Actor: Admin
Description: Admin shall receive Alerts and Notifications by
devices/mediums registered by the end-user.
Precondition: User has created and sent Alert Messages
Post Admin receives alert message
Condition:
Normal Flow:
1. Admin open the web and view the login page.
2. System present the login page.
3. Admin enter valid information.
4. System present the home screen.
5. Admin click the dashboard.
6. Admin click Order option.
7. Admin see new order.
8. Admin check Order ID.
9. Admin accept the order
10. End Use Case.

Alter Native Flow:

n/a

Figure 6. Order Type Use Case:

Order Type Use Case:
 Use Case ID: UC6
Use Case Name: Order Type
Created Date: Last Created Date:
Actor: Admin
Description: Admin shall receive Alerts and Notifications by
devices/mediums registered by the end-user. And See Order
Type is Argent/Regular.
Precondition: Admin first login the website. And select click on dashboard.
Post Admin receive alert massage. And Successfully accept the
Condition: order.
Normal Flow:
1. Admin open the web and view the login page.
2. System present the login page.
3. Admin enter valid information.
4. System present the home screen.
5. Admin click the dashboard.
6. Admin click Order option.
7. Admin see new order.
8. Admin check Order ID.
9. Admin check order type.
10. Order type is Argent/Regular.
11. Admin accept the order.
12. End Use Case.

Alter Native Flow:

n/a

Figure 7. New Updates Images Use Case:

New Updates Images/Videos Use Case:
Use Case ID: UC7
Use Case Name: New Updates Videos/Images
Created Date: Last Created Date:
Actor: Admin
Description: All Editing functionality control only admin. Admin add new
videos and photos related company products.

Precondition: Admin first login the website. Admin has update Videos and
photos related company products.
Post Admin Successfully Update new videos and Images.
Condition:
Normal Flow:
1. Admin open the web and view the login page.
2. System present the login page.
3. Admin enter valid information.
4. System present the home screen.
5. Admin click the dashboard.
6. Admin click Editing.
7. Admin click new updates button.
8. Admin add new videos and images.
9. System Successfully update videos and images.
10. System present on screen videos and images.
11. End Use Case.

Alter Native Flow:

 Wrong images size.
 Videos not successfully upload
 Video are not supported
Figure 8. Sending Email Use Case:

Sending Email Use Case:

 Use Case ID: UC8
Use Case Name: Sending Email Use case
Created Date: Last Created Date:
Actor: Admin
Description: The user will login using the id and password given during
registration. Email is information stored on a computer that is
exchanged between two users over telecommunications. E-mail
is a message that may contain text, files, images, or other
attachments sent through a network to a specified individual or
group of individuals.

Precondition: User login the website. And select user records in dashboard.

Post E-mail is sent to perfectly and completely.

Condition:
Normal Flow:
1. Admin Open the Web and view the login page.
2. System present the login page.
3. User enter a correct Id and Password.
4. System present home page.
5. Admin click dashboard.
6. Admin Select the Email option.
7. Admin Select users for e-mail.
8. Text email/Attached file.
9. Sent Email
10. End Use Case

Alter Native Flow:

 User enter invalid id and password.
 Network Issues.
 E-mail complete not send.

Figure 9. Log Out Use Case:

Log Out Use Case:

Use Case ID: UC9

Use Case Name: Log Out Use Case
Created Date: Last Created Date:
Actor: User
Description: Logging out informs the computer or App that the current user
wishes to end the login session.
Precondition: User Open web/app. Then login the web/app.
Post User can logout the system.
Condition:
Normal Flow:
1. User Open the app and view the login page.
2. System present the login page.
3. User enter a correct Id and Password.
4. System present home page.
5. User click the dash board.
6. Then User logout the system.
7. End Use Case

Alter Native Flow:

n/o

High Level Use Case:

A use case diagram doesn't go into a lot of detail for example, don't expect it to model the order in
which steps are performed. Instead, a proper use case diagram depicts a high-level overview of the
relationship between use cases, actors, and systems.

Figure 10. H2O Agent System High Level Use Case:

 Use Case ID: UC9
Use Case Name: H2O Agent: System Diagram
Created Date: Last Created Date:
Actor: User, Admin, Sensor
Description: All Users are register in database. Users login the web/app.
Then access the system and used his/her profile. If user is
admin then access only admin modules. If User is Customer
then used only customer module. Sensor generate alert and
water level record sent to the data base. Sensor have main two
functions (Alert generate, Sensor record) and sent to the data
base. All actors connected to data base.
Precondition: Users Open the Web/App. Then login the system with valid
information. Sensor generate alert and water level monitor.
Post Users used the system. And properly work all functionalities.
Condition:
Normal Flow:
1. System (sensor) and users all register in database.
2. Users Open the app/web and view the login page.
3. User enter the password and

Alter Native Flow:

n/o

Figure 11. Android App Use Case:

Figure 12. Website Use Case:
4.2.2. Activity Diagram:
Activity diagram is just like the flow chart of the system where shows flow of the system
comprehensively by activity to activity. These activities can be called as operation of the system.
This flow can be sequential, branched or concurrent. Below Diagrams are showing the complete
flow of our system according to the module.

 Starting symbol is

 Activity

Activity

 Condition
Yes

No

 Parallel Activity

 Connect Symbol

 End

H2O Agent Activity Diagram:

Sign Up

Sign In
Admin Activity Diagram:
Activity Diagram Customer:
4.2.3. Class Diagram:
A description of a group of objects all with same roles in the system. Structural features (attributes)
define what objects of the class "know" Represent the state of an object of the class. Are descriptions of
the structural or static features of a class. Class diagram is used to look at application statically. It can
visualize different aspects of system by defining different type of relationships between classes. It helps
us to manage, understand and reuse functionality. It includes properties/attributes and related
functionality of a class. It helps us to analyze ‘what are the responsibilities of a system’ by showing
interaction and collaboration between classes and interfaces. Class diagrams are most popular because
coders feel relax if that are well designed.

Class Notation:

My Class
+attribute: int
-attribute: float
#attribute: circle
Operations

1. Class Name
 The First Block in class notation.
 The name of the class appears in the first partition.

2. Class Attributes

 Second Block in class notation.

 Attributes are shown in the second partition.
 The attribute type is shown after the color
 Attributes map onto member variables (data members) in code.

3. Class Operations

 Operations are added in the third partition. They are services the class provides.
 All operations are class block.
 Class Relationship:

1. Inheritance
Super class

Operations

Sub Class 1 Sub Class 2

Operations Operations

 Represents an is a relationship.
 Sub classes are specialization of super class.

2. Simple Association

 A structural link between two peer classes.

 There is an association between two classes.
 A solid line connecting two classes

3. Aggregation

 Its special type of association.

 Many instances (denoted by the *) of Class 2 can be associated with Class1.
 Its solid line with the unfiled diamond one side.
 4. Composition

 Its special type of aggregation.

 Objects of Class2 live and die with Class1.
 A solid line with a filled diamond at the association connected to the class of composite

5. Dependency

 A dashed line with an open arrow.

 One class depend on other class.

Diagram Class:
H2O Agent Sequence Diagram:
H2O Agent DFD (Data Flow Diagram) Diagram:
H2O Agent Flow Chart:
CH 6

IMPLEMENTATION

6.1. Implementation Tools and Framework:

Development Tools

• Arduino IDE
• Android Studio
• Git
• Visual studio
Documentation Tools

 MS word
 MS PowerPoint
 MS Project
 Draw.io
Technologies and Frame Work

 Pub/sub architecture
 Real time database (Firebase)
 Number Auth (Firebase auth)
 C#
 Java script
 jQuery
 Bootstrap
 CSS
 HTML
 Java
 XML
 Asp.net MVC

Hardware

 Node MCU
 Sensor
 6.1.1. Reasoning

Why ASP.Net

 Keep you Asp.net applications secured with the built-in Windows authentication and
per-application configuration.
 Asp.Net has reduced the long lines of code required to develop large applications.
 Asp.Net and Html, together generate dynamic web pages smoothly.
 Being an ideal server-side scripting technology, Asp.Net code first runs on Windows
server before displaying on the web browser.
 Asp.Net framework is language independent, means you can choose any
programming language which best suited to your application.
 With the built-in configuration information, Asp.Net is easy to deploy.
 The windows web server thoroughly monitors the web pages, multiple components,
and applications running over it.
 The Dot Net Framework quickly gives an alert for memory leaks, unbounded loops,
and other wrong behaviors, immediately killing them and restart them over again.
Why Not Angular JS

 No backward compatibility with Angular 1.x

 The web developer has to get familiar with TypeScript before starting angular
development work.
 Angular might not look like SEO friendly because indexing text is not directly there in
HTML.
 The developers who want to create a simple dynamic looking website can choose
Angular as their main web development framework.
Why Not React

 You cannot create a full-featured server-side application using ReactJS. If you move

to another development framework than rewriting all HTML codes from scratch.
 In addition, it’s quite complicated to move the complex Photoshop or any other
sketch to JSX file.
 ReactJS can be used by developers who want full-featured based web portals.
Why not Vue Js

 Doesn’t provide features “in the box” for integrating data from the server you
will need additional tools and libraries to make that work.
 It’s a new web development framework and has very less documentation and
plugins than any other competitors.
Why C#
  C# uses almost similar syntax which follows by C so it easy to understand for those
who know C language
 Easy Integration with Windows
 Fully integrated with the .NET library which provides access to a repository of
functionality and support.
 Safer than its namesakes (C/++) as pointer types are not permitted
Why Not PHP

 Error handling facility is poor as PHP lacks debugging tool

 PHP is not secure as it is one of the open source languages
 Developing a website with PHP Web Development is slower than other
programming languages.

Why Not C++

 The syntax is complex, and the standard library is small, making this language very
difficult to learn for the beginner programmer.
 C++ program can't support garbage collection or Dynamic Memory Allocation
 The object orientation system in C++ is unnecessarily basic compared to other
languages.

Why Not Python

 Note ideal for Mobile Computing

 Python's database access layer is bit underdeveloped and primitive.

Why Js

 Client-side JavaScript is very fast as it can be run quickly in the client-side browser
 JavaScript is relatively simple to learn.
 It can work smoothly with other languages and can be used in a huge variety of
applications.
 Grease monkey support to write snippets of JavaScript which can execute on specific
web pages

Why Java

 Object- Oriented language

 Java offers APIs for different activities like Database connection, networking, XML
parsing, utilities, etc.
  Powerful open source Rapid Development tools
 A large number of open source libraries

Why Bootstrap

 Reduce cross-browser errors

 A consistent framework that supports most browser and CSS compatibility fixes
 Lightweight and customizable
 Structure and style of reception
 Use jQuery's various JavaScript plugins
 Great grid system

Why jQuery

 Eliminates a lot of cross browser JavaScript issues

 Can perform complicated JavaScript operations in little code
 Can easily add Ajax functionality to app
 Has built in UI and effects libraries

Why Html

 First advantage it is widely used.

 Every browser supports HTML language.
 Easy to learn and use.
 It is by default in every window so you don't need to purchase extra software.

Why CSS

 Speeds up your development

 Enables cross-browser functionality
 Gives you clean and symmetrical layouts

Why XML

 It can represent common computer science data structures: records, lists, and trees.
 Its self-documenting format describes structure and field names as well as specific
values.
 The strict syntax and parsing requirements make the necessary parsing algorithms
extremely simple, efficient, and consistent.
 XML is heavily used as a format for document storage and processing, both online
offline.
Why Use Node MCU

 Low cost.
 Integrated support for WIFI network.
 Reduced size of the board.
 Low energy consumption.
 Can be used for real time applications for both software and hardware
 Open source.

Why Not Adriano

 Cost - NodeMCU is cheaper compared to Arduino original(duplicates can be cheaper

than nodeMCU)
 Flash - 32KB for Arduino , 4MB for NodeMCU
 SRAM - 2KB for Arduino, upto 50KB for NodeMCU
 Clock Speed - 16MHz for Arduino, 24–52MHZ for NodeMCU
 GPIO pins - 14(6 PWM) for Arduino, 17(All PWM) for NodeMCU
 ADC - 6 for Arduino , 1 for NodeMCU
 Operating Voltage - 5V for Arduino(board is powered from jack then 7–12V) , 3.3V for
NodeMCU

Implementation procedure:

The working of the application is that when user enter Whispers, it will ask about whether you are
joining as a professional or common user. User will provide necessary information to application. Now
user will be able to successfully join community. After joining community, user can attend workshops
and get latest updates about their interested topics. User will be able to post their problem in
community for getting suitable solution by professionals on aspects of their growth journey. User can
also share their problem though voice notes in community. There will be a specific period to post and
review on a problem. User will have a right to share their reviews about workshops. A professional must
have to conduct 1 workshop per week to stay as a professional in 30 days’ trial period for authentication
otherwise she will be change into a common user of Whispers by administrator. User can conduct
workshops via zoom, YouTube or Facebook on the basis of professional’s choice.
CH 7

TESTING

Customer Test Cases about Sign up:

Project H2O Agent

Name:
Module Sign up
Name:
Created H2O Agent Development Team
By:
Tested By:
             
Test Test Scenario Test Test Case Expected Result Actual Result Status
Scenario Description Case Description
ID ID
Ts-1 Verify the Tci-1 User get User sign-up page page displayed Pass
User sign-up started button should display successfully
functionality nevi-gate to
User sign-up
page
Ts-1 Verify the Tci-2 verify User Name, CNIC, E- sign-up page Pass
User sign up sign-up page mail password, contains Name,
functionality contain Name, phone number CNIC, E-mail
CNIC, E-mail field available password,
password, with get started phone number
phone number button and Register
fields and a button
get started
button
Ts-1 Verify the Tci-3 Name field Name should Name field Pass
User sign-up should be on display above the displayed
functionality top of CNIC CNIC field before CNIC
field field
Ts-1 Verify the Tci-4 Name, CNIC, "enter user All fields have Pass
User sign up E-mail name", "enter their respective
functionality password, CNIC", and "enter place holders
 phone number password" …..
should contain should appear
place holders
for user
understanding
Ts-1 Verify the Tci-5 Select service Service type Service type Pass
User sign up type should should appear button display
functionality contain for
user
Ts-1 Verify the Tci-6 password field password text password field Pass
user sign up text should be should hide text is hidden
functionality bullet or with bullet text
asterisk
format
Ts-1 Verify the Tci-7 username field username field username field Pass
user sign up should be accept user with validate the
functionality @se.uol.edu.p domain user domain
k @se.uol.edu.pk successfully
Ts-1 Verify the Tci-8 validation invalid username domain error Pass
user Sign up message for should be message
functionality valid validated with displayed
username proper message properly
Ts-1 Verify the Tci-9 password password should successfully Pass
user sign up length should be limited length check the
functionality be monitor password
length
Ts-1 Verify the Tci-10 password invalid password successfully Pass
user sign up length error length msg should validate the
functionality display password
Ts-1 Verify the Tci-11 validation validation msg displayed in Pass
user sign up message should be below proper place
functionality placing their respective
field
Ts-1 Verify the Tci-12 hind for min and max min 8 -max 10 Pass
user sign up password length should be is mentioned
functionality length mentioned for below
user password field
Ts-1 Verify the Tci-13 Validation msg validation msg displayed in Pass
user login color should be of red proper red
functionality color color
Ts-1 Verify the Tci-14 validate the check if the validates the Pass
user sign up user entered new user user and
 functionality information exists display msg if
or not and display user not exits
msg
Ts-1 Verify the Tci-15 Verify that tab move to next field successfully Pass
user sign up functionality is when tab key change field on
functionality working press tab key press
properly or
not
Ts-1 Verify the Tci-16 Verify that pressing enter key enter key work Pass
user sign up Enter/Tab key system start the as substitute
functionality works as a sign-in process for sign-in
substitute for button
the Register
button
Ts-1 Verify the Tci-17 Verify that system should instructor Pass
user sign up instructor is disallow instructor restricted the
functionality not able to to get sign-up system with All
sign up with with invalid information
invalid information
information
Ts-1 Verify the Tci-18 Verify that required msg for Empty field Pass
sign-up sign User is not any field should required
up able to sign up appear if fields are displayed
functionality with any blank empty information
field
Ts-1 Verify the Tci-19 Verify that instructor profile User profile Pass
user sign up User is should be display displayed
functionality redirected to after successfully successfully
appropriate sign up
page after
successful sign
up

Customer Test Cases about Login:

Login Test case:

Project H2O Agent
Name:
Module Login
Name:
Created H2O Agent Development Team
By:
Tested By:
             
Test Test Scenario Test Test Case Expected Result Actual Result Status
Scenario Description Case Description
ID ID
Ts-1 Verify the Tci-1 customer sign- customer sign-in page displayed Pass
Customer in button nevi- page should successfully
login gate to display
functionality customer sign-
in page
Ts-1 Verify the Tci-2 verify username, sign-in page Pass
customer customer sign- password field contains
login in page available with username,
functionality contain sign-in button password and
username, Sign-in button
password
fields and a
Sign-in button
Ts-1 Verify the Tci-3 username field username should username field Pass
customer should be on display above the displayed
login top of password field before
functionality password field password field
Ts-1 Verify the Tci-4 username and "enter user name" Both fields have Pass
customer password and "enter their respective
login should contain password" should place holders
functionality place holders appear
for user
understanding
Ts-1 Verify the Tci-5 password field password text password field Pass
customer text should be should hide text is hidden
login bullet or with bullet text
functionality asterisk
format
Ts-1 Verify the Tci-6 username field username field username field Pass
customer should be accept user with validate the
login @se.uol.edu.p domain user domain
functionality k @cse.uol.edu.pk successfully
Ts-1 Verify the Tci-7 validation invalid username domain error Pass
customer message for should be message
login valid validated with displayed
functionality username proper message properly
Ts-1 Verify the Tci-8 password password should successfully Pass
customer length should be limited length check the
login be monitor password
functionality length
Ts-1 Verify the Tci-9 password invalid password successfully Pass
customer length error length msg should validate the
login display password
functionality
Ts-1 Verify the Tci-10 validation validation msg displayed in Pass
customer message should be below proper place
login placing their respective
functionality field
Ts-1 Verify the Tci-11 hind for min and max min 8 -max 10 Pass
customer password length should be is mentioned
login length mentioned for below
functionality user password field
Ts-1 Verify the Tci-12 Validation msg validation msg displayed in Pass
customer color should be of red proper red
login color color
functionality
Ts-1 Verify the Tci-13 validate the check if the validates the Pass
customer user entered user user and
login exists or not and display msg if
functionality display msg user not exits
Ts-1 Verify the Tci-14 Verify that tab move to next field successfully Pass
customer functionality is when tab key change field on
login working press tab key press
functionality properly or
not
Ts-1 Verify the Tci-15 Verify that pressing enter key enter key work Pass
customer Enter/Tab key system start the as substitute
login works as a sign-in process for sign-in
functionality substitute for button
 the Sign in
button
Ts-1 Verify the Tci-16 Verify that system should instructor Pass
customer instructor is disallow instructor restricted the
login not able to to get sign-in with system with
functionality Login with in valid username username other
invalid and password than
Username and @cs.uol.edu.pk
invalid
Password
Ts-1 Verify the Tci-17 Verify that required msg for "username Pass
customer User is not username and required” msg
login able to Login password field displayed and
functionality with blank should appear if username and
Username or fields are empty "password is
Password required
“displayed for
password
Ts-1 Verify the Tci-18 Verify that instructor profile profile Pass
customer User is should be display displayed
login redirected to after successfully successfully
functionality appropriate logged-in
page after
successful
login

Admin Test Cases about Login:

Project H2O Agent

Name:
Module Login
Name:
Created H2O Agent Development Team
By:
Tested By:
             
Test Test Scenario Test Test Case Expected Result Actual Result Status
Scenario Description Case Description
ID ID
Ts-1 Verify the Tci-1 Admin sign-in customer sign-in page displayed Pass
Admin login button nevi- page should successfully
functionality gate to Admin display
sign-in page
Ts-1 Verify the Tci-2 verify Admin username, sign-in page Pass
Admin login sign-in page password field contains
functionality contain available with username,
username, sign-in button password and
password Sign-in button
fields and a
Sign-in button
Ts-1 Verify the Tci-3 username field username should username field Pass
Admin login should be on display above the displayed
functionality top of password field before
password field password field
Ts-1 Verify the Tci-4 username and "enter user name" Both fields have Pass
Admin login password and "enter their respective
functionality should contain password" should place holders
place holders appear
for user
understanding
Ts-1 Verify the Tci-5 password field password text password field Pass
Admin login text should be should hide text is hidden
functionality bullet or with bullet text
asterisk
format
Ts-1 Verify the Tci-6 username field username field username field Pass
Admin login should be accept user with validate the
functionality @se.uol.edu.p domain user domain
k @cse.uol.edu.pk successfully
Ts-1 Verify the Tci-7 validation invalid username domain error Pass
 Admin login message for should be message
functionality valid validated with displayed
username proper message properly
Ts-1 Verify the Tci-8 password password should successfully Pass
Admin login length should be limited length check the
functionality be monitor password
length
Ts-1 Verify the Tci-9 password invalid password successfully Pass
Admin login length error length msg should validate the
functionality display password
Ts-1 Verify the Tci-10 validation validation msg displayed in Pass
Admin login message should be below proper place
functionality placing their respective
field
Ts-1 Verify the Tci-11 hind for min and max min 8 -max 10 Pass
Admin login password length should be is mentioned
functionality length mentioned for below
user password field
Ts-1 Verify the Tci-12 Validation msg validation msg displayed in Pass
Admin login color should be of red proper red
functionality color color
Ts-1 Verify the Tci-13 validate the check if the validates the Pass
Admin login user entered user user and
functionality exists or not and display msg if
display msg user not exits
Ts-1 Verify the Tci-14 Verify that tab move to next field successfully Pass
Admin login functionality is when tab key change field on
functionality working press tab key press
properly or
not
Ts-1 Verify the Tci-15 Verify that pressing enter key enter key work Pass
Admin login Enter/Tab key system start the as substitute
functionality works as a sign-in process for sign-in
substitute for button
the Sign in
button
Ts-1 Verify the Tci-16 Verify that system should instructor Pass
Admin login instructor is disallow instructor restricted the
functionality not able to to get sign-in with system with
Login with in valid username username other
invalid and password than
 Username and @cs.uol.edu.pk
invalid
Password
Ts-1 Verify the Tci-17 Verify that required msg for "username Pass
Admin login User is not username and required” msg
functionality able to Login password field displayed and
with blank should appear if username and
Username or fields are empty "password is
Password required
“displayed for
password
Ts-1 Verify the Tci-18 Verify that instructor profile profile Pass
Admin login User is should be display displayed
functionality redirected to after successfully successfully
appropriate logged-in
page after
successful
login

Admin Test Cases about Profile module:

Project H2O Agent

Name:
Module Profile Module
Name:
Created H20 Agent Development Team
By:

Tested By:

Test Test Scenario Test Test Case Expected Actual Result Status
Scenario Description Case ID Description Result
ID
Ts-1 Admin profile Tcap-1 verify that admin should profile display Pass
design admin profile be navigating properly
 displays after to admin
successfully profile after
sign-in sign-in
verification
process
Ts-1 Admin profile Tcap-2 verify that username, sign-up page Pass
design profile page password field contains
contains the available with username,
Nav-bar at the sign-up button password and
top of the page Sign-in button
Ts-1 Admin profile Tcap-3 Nav-bar nav-bar should Nav-bar is Pass
design alignment be on top with displaying
should be horizontal properly
horizontal alignment
Ts-1 Admin profile Tcap-4 software logo Logo should be Logo is Pass
design should be displayed on displaying
appearing at the left side of properly as
the left corner the nav-bar expected
of the Nav-bar
Ts-1 Admin profile Tcap-5 Nav-bar should drop-down setting drop- Pass
design contain the control should down control is
dropdown be available available at right
controls for with multiple side of the nav-
profile options for bar
operation profile
management
Ts-1 Admin profile Tcap-6 verify that "setting" "setting" option Pass
design "Settings" option should should is a
option is a be dropdown dropdown
dropdown control control
control
Ts-1 Admin profile Tcap-7 setting "settings" "settings" Pass
design dropdown dropdown dropdown
should contain should show: showing the
options for 1-profile profile settings
profile edit setting options along
2-Password with "logout"
reset
3-Logout
Ts-1 Admin profile Tcap-8 "profile personal Personal Pass
design setting" option information information
 under the edit page page is showing
"settings" should display properly.
dropdown item when click the
should "profile
navigate to edit setting" option
"personal
information"
page
Ts-1 Admin profile Tcap-9 profile Personal Personal Pass
design information information information
should be should display page is showing
display on on top of properly.
profile view profile in a
top separate
container
Ts-1 Admin profile Tcap- Verify personal personal Personal Pass
design 10 information are information information
in proper order should be page showing in
display in desired
following sequence
pattern: properly.
1 -Name of
user
2-admin
designation
3-Email
4-Contact no
5-Gender

Admin Test Cases about Profile module:

Project H2O Agent
Name:
Module Admin Dashboard
Name:
Created H2O Agent Development Team
By:
Tested By:
             
Test Test Scenario Test Test Case Expected Result Actual Result Status
Scenario Description Case Description
ID ID
Ts-1 Verify Admin Tci-1 Admin Admin Dashboard page displayed Pass
Dashboard Dashboard page should successfully
functionality button nevi- display
gate to
dashboard
page
Ts-1 Verify Admin Tci-2 Side Bar Side bar Side bar display Pass
Dashboard button should be display successfully
functionality navigate to
Dashboard
page
Ts-1 Verify Admin Tci-3 verify contain User Side bar Pass
Dashboard instructor Side management, live contain User
functionality bar page monitoring, order management,
contain User management live monitoring,
management, available with order
live View button and management
monitoring, logout Button. available with
order View button
management, and logout
View Button Button.
and Logout
Button
Products
fields and a
Sign-in button
Ts-1 Verify Admin Tci-4 Total sales Success sales page Display Sales Pass
Dashboard button nevi- display record
functionality gate to Total
sales page
Ts-1 Verify Admin Tci-5 verify that "Total Sales" "Total Sales" Pass
Dashboard "Total Sales" button should be button is
functionality button should clickable and in working
be working working state properly
properly
Ts-1 Verify Admin Tci-6 verify that " Total order " " Total order " Pass
Dashboard "Total order" button should be button is
functionality button should clickable and in working
be working working state properly
properly
Ts-1 Verify Admin Tci-7 verify that " " Active Board " " Active Board " Pass
Dashboard Active Board " button should be button is
functionality button should clickable and in working
be working working state properly
properly
Ts-1 Verify Admin Tci-8 verify that " " User " User Pass
Dashboard User Management " Management "
functionality Management " button should be button should
button should clickable and in be clickable and
be working working state in working state
properly
Ts-1 Verify Admin Tci-9 verify that " " Live Monitoring " Live Pass
Dashboard Live " button should be Monitoring "
functionality Monitoring " clickable and in button should
button should working state be clickable and
be working in working state
properly
Ts-1 Verify Admin Tci-9 verify that " " Live Monitoring " Live Pass
Dashboard Live " button should be Monitoring "
functionality Monitoring " clickable and in button should
button should working state be clickable and
be working in working state
properly
Ts-1 Verify Admin Tci-10 verify that " " Order " Order Pass
Dashboard Order Management " Management "
functionality Management " button should be button should
button should clickable and in be clickable and
be working working state in working state
properly
Ts-1 Verify Admin Tci-11 verify that " " Product " button " Product " Pass
Dashboard Product " should be button should
functionality button should clickable and in be clickable and
be working working state in working state
properly
CH 8

CONCLUSION AND FUTURE WORK

8.1. Limitation and Strength of the System:

It requires its users to use web services on computer systems

Before this not working this kind of project. One Articles publish related this project but not same
like that. One of this IOT based Water Level Monitoring system is an innovative system which will
inform the users about the level of liquid and will prevent it from overflowing. But this project
slightly different we work on water supply problem and water storage for user all the concerned
problems, we will develop an android and web application. The android application will facilitate
water consumers to make an order for water. The web application will facilitate water supplier
companies to control the water order. For this project, we will use the sensor has a unique id for
customer identification. The customer will get registration through sensor id and personal contact
information. This sensor will check the water quantity in the water bottle. If the water quantity
reached the thresh hold number then it will send an alarming notification to the supplier for water
requests. The company will be able to manage its business (customer information and order record)
of water supply through the web application. We are providing a solution that will automate the
supply of water more. Which will help not only to reduce the wastage of water but it will also be
helpful against the germs and bacteria and water related diseases. It will facilitate the suppliers and
the users which will help them to save time, efforts, etc.

8.2. Future Recommendation:

 We will implement intelligent environment in the future.

 The sensors will detect the surrounding environment like lights, persons to send the alert
accordingly.
 We will implement payment with credit card.
 We will have contracts with the agents/suppliers to which we are going to supply water and
they will distribute that water in their specific areas.
 Admin and user will be able to track the supplier’s location.
CH 9

BIBLIOGRAPHY / REFERENCE

Reference 1.

International Research Journal of Engineering and Technology (IRJET)

 https://www.irjet.net/archives/V4/i12/IRJET-V4I12333.pdf
Reference 2.

Just a sensor used for water sense not similar type of work.

Recent Advances in Information and Communications Technology (ICT) and Sensor Technology for
Monitoring Water Quality.

 file:///C:/Users/Hussnain%20Ali/Downloads/water-12-00510-v2.pdf