Report on jal app

1. Software Prototyping MIT Academy of Engineering, Alandi.
1 | P a g e
1. Introduction
1.1 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.
1.2 Background and Motivation
People living in Alandi area faces problems related to scarcity due to insufficient,
irregular and impure supply of water. So, they have to pay high prices to local
dealer to solve their problems and every people can’t afford to pay it. Not only
the local people but the students living in this area also faces the same problem
and can’t afford to pay the cost to the dealer as it increases during the summer
and rainy season.
We observed that this is the major problem that should be resolved. So, we got
an idea to make suchapp which would solve the water scarcity problem and avoid
the costly prices of water provided by the local dealer. So, we discussed the
problem among the local people and the students and they too agreed and
motivated us to make suchapp which will save their time and money. So, the idea
of making “Jal app” was finalized.

2. Software Prototyping MIT Academy of Engineering, Alandi.
2 | P a g e
2. Requirement Analysis
2.1 User Requirement:
It involves understanding the user problem and their requirement for
designing application.
 Register
 Separate Log In for user.
 User can directly place order as per their convenience
 User also can track their order
 User can choosebetween different kind of water supply
 Various Payment option are available
 User can get various kind of delivery option
 Simple and concise to use
2.2 Functional Requirements
1) Login (Registration):
Table 2.2.1 login page
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.

3. Software Prototyping MIT Academy of Engineering, Alandi.
3 | P a g e
2) Create an account:
Table 2.2.2 To Create 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’thave existing account or want to
create new account
Input data Create new password and confirm it.
Output data Recheck and confirm details
3) Placing order:
Table 2.2.3 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.
4)Order Confirmation:
Table 2.2.4 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

4. Software Prototyping MIT Academy of Engineering, Alandi.
4 | P a g e
5) Payment Option:
Table 2.2.5 Payment methods
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.
2.3 Limitations:
1) This app is online and without stable Internet connection the order can’t be
placed.
2) To access “Jal app” e-mail id and password is required.
3) Users should be comfortable with smart phone.
4) Only registered users can access the app.
2.4 Constraint:
1) User and dealer both register once and then they get authorized to place order,
make payments, cancel order, refund payments, etc.
2) To update the information, user and dealer both should register in application.
3) App takes care about privacy, i.e. it won’t exchange information by itself.
2.5 Analysis
Our app is society related app. In this app, user and dealer both can access the
features of order placement, payments, etc. Students and local people facing
many problems regarding the insufficient and impure water supply. So we design
this app. In this app, notifications are received on time, various dealer options are
available to choose from. This app decreases the confusion of the dealers
regarding the location of the user. This app is very useful and easy to use.

5. Software Prototyping MIT Academy of Engineering, Alandi.
5 | P a g e
3. UML Diagram
The Unified Modeling Language (UML) is a general-purpose, developmental,
modeling language in the field of software engineering that is intended to provide
a standard way to visualize the design of a system. In software engineering,
a class diagram in the Unified Modeling Language(UML) is a type of static
structure diagram that describes the structure of a system by showing the
system's classes, their attributes, operations (or methods), and the relationships
among objects.
1) Standard language for specifying, visualizing, constructing, and
documenting the artifacts of software systems, business modeling and
other non-software systems.
2) The UML represents a collection of best engineering practices that have
proven successful in the modeling of large and complex systems.
3) The UML is a very important part of developing objects oriented software
and the software development process.
4) The UML uses mostly graphical notations to express the design ofsoftware
projects.
5) Using the UML helps project teams communicate, explore potential
designs, and validate the architectural design of the software.

6. Software Prototyping MIT Academy of Engineering, Alandi.
6 | P a g e
3.1 Use Case Diagram:
An actor in the Unified Modeling Language (UML) "specifies a role played by a
user or any other system that interacts with the subject." "An Actor models a type
of role played by an entity that interacts with the subject (e.g., by exchanging
signals and data), but which is external to the subject." A primary purposeof the
model of business use cases and actors is to describehow the business is used by
its customers and partners. Activities that directly concern the customer, or
partner, as well as supporting or managerial tasks that indirectly concern the
external party can be presented
Figure3.1 Use case diagram

7. Software Prototyping MIT Academy of Engineering, Alandi.
7 | P a g e
3.2. Sequence Diagram:
It is a construct of a message sequence chart. A sequence diagram shows object
interactions arranged in time sequence. It depicts the objects and classes involved
in the scenario and the sequence of messages exchanged between the objects
needed to carry out the functionality of the scenario. In software engineering,
a system sequence diagram (SSD) is a sequence diagram that shows, for a
particular scenario of a use case, the events that external actors generate their
order, and possible inter-system events.
Figure 3.2 Sequence diagram

8. Software Prototyping MIT Academy of Engineering, Alandi.
8 | P a g e
3.3. Activity Diagram:
Activity diagram is another important diagram in UML to describe the dynamic
aspects of the system. Activity diagram is basically a flowchart to represent the
flow from one activity to another activity. Activity diagram is another
important diagram in UML to describe the dynamic aspects of the
system. Activity diagram is basically a flowchart to represent the flow from
one activity to another activity. The activity can be described as an operation of
the system. The control flow is drawn from one operation to another.
Figure3.3 Activity Diagram

9. Software Prototyping MIT Academy of Engineering, Alandi.
9 | P a g e
4.Working Prototype UI design
Figure4.1 First Screen
Figure 4.4 Home Page Figure 4.5 Slide in Menu Figure 4.6 Order Screen
Figure4.2 Login Screen Figure 4.3 Signup Screen

10. Software Prototyping MIT Academy of Engineering, Alandi.
10 | P a g e
Figure 4.7 User Defined Order Figure 4.8 Confirmation Screen Figure 4.9 Payment Screen
Figure 4.10 Order Details Figure 4.11 Refund/Return Screen Figure 4.12 Refund Message

11. Software Prototyping MIT Academy of Engineering, Alandi.
11 | P a g e
5. Conclusion
In software prototyping we initially learnt to develop the prerequisites of any app
designing. We were introduced to new software’s suchas 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.

12. Software Prototyping MIT Academy of Engineering, Alandi.
12 | P a g e
6. Reference
Website Reference
[ 1 ] https://en.wikipedia.org/wiki/Unified_Modeling_Language
[ 2 ] https://proto.io/en/signin/
[ 3 ] https://www.smartdraw.com/activity-diagram/
[ 4 ] https://www.uml-diagrams.org/use-case-diagrams.html
[ 5 ] https://www.lucidchart.com/pages/uml/sequence-diagram
Books Reference
[ 1 ] Unified Modeling Language, second edition by Booch, Rumbaugh and
Jacobson
[ 2 ] Martin Fowler's UML distilled, third edition
[ 3 ] Craig Larman's Applying UML and Patterns
[ 4 ] Martin Fowler's UML Distilled and Scott Ambler's Elements of UML 2.0
Style