This document outlines a mobile app project to provide easy access to water supply in areas with scarcity. The app will allow users to order water from local dealers. It describes the problem of insufficient water supply, user requirements like registration and payment options, and functional requirements like placing orders and confirmations. UML diagrams including use case, activity and sequence diagrams are mentioned. Screen designs are provided for features like login, ordering, and refunds. The conclusion discusses lessons learned in software prototyping and understanding requirements to provide a solution.

1. MIT Academy Of Engineering
S.Y. B. Tech. E&TC 2017-2018
Course-Software Prototyping

2. Project Title:
Group Members:
Group Name:

3. Content:
1) Problem Statement
2) Motivation
3) Requirements
4) User Requirement
5) Functional Requirement
6) UML Design
7) Use Case Diagram
8) Sequential Diagram
9) Activity Diagram
10) Conclusion

4. Problem Statement:
 To design a mobile app for the purpose of people, student living in water
scarcity area for easy access of water supply at cheaper cost from nearby
dealers.
Motivation:
 Many students and local people facing problems related to scarcity due to insufficient,
irregular and impure supply of water. So, they have to pay high prices to local dealer and every
people can afford it.

5. Requirements:
1) User Requirement:
 Register
 Separate Log In for user.
 User can directly place order as per their convenience
 User can also track their order
 User can choose between different kind of water supply
 Various Payment option are available
 User can get various kind of delivery option
 Simple and concise to use

6. 2) Functional Requirement
(i) Login(Registration)
Purpose To login into app
User Any user who will place order has to
login
Dealer Any dealer who want to track and
control his business has to login. Dealer
can manage orders through this account.
Input data User ID and password
Output data Login in to the user/dealer account.

7. (ii) Create New Account
Purpose To create an account (Username &
Password)
User Any user who don’t have existing account
or want to create new account
Dealer Any dealer who don’t have existing
account or want to create new account
Input data Create new password and confirm it.
Output data Recheck and confirm details

8. (iii) Placing order:
Purpose To place the order
User Customer who want to place the order
Input data Area, Type of water(drinking/daily-use),
Quantity, date and time
Output data Display of details of placed order.

9. (iv)Order Confirmation
Purpose To confirm order details.
User Type and quantity of water supply
Delivery date and time User can select his/her requirement
as per convenience.
Delivery option Home delivery, Tanker service or
Packaged water supply.
Input data Delivery date, time and delivery
options.
Output data Confirmation of order

10. (v) Payment Option:
Purpose Choosing various payments method
User User can make payment via online banking, paytm,
and cash on delivery.
Dealer If user cancels the order, dealer can refund the
money.
Input data Payment of the order.
Output data Display of total cost, payment and order
confirmation.

12. UML Design
(1) Use Case Diagram:

13. (2) ACTIVITY DIAGRAM

14. (3) Sequential Diagram

15. Story board
First Screen Login Screen Signup Screen Home Page Slide in Menu Order Screen

16. User Defined Order Confirmation
Screen
Payment Screen Order Details Refund/Return
Screen
Refund Message

17. App View On
iPhone X
IOS

18. Conclusion:
In software prototyping we initially learnt to develop the prerequisites of any app
designing. We were introduced to new software’s such as Lucid Chart for making UML
diagrams and Proto.io tools for designing the app screens. We improved our team
work qualities, patience and management skills. We have also learnt fundamental
stage of software development life cycle. Through this software prototyping we were
able to understand user and functional requirement so that we could provide a
proper solution to user based upon our app.